Distributed Management (disman)
This Working Group Did Not Meet.
NOTE: This charter is a snapshot of the 47th IETF Meeting in Adelaide, Australia. It may now be out-of-date. Last Modified: 29-Feb-00
Chair(s):
Randy Presuhn <rpresuhn@bmc.com>
Operations and Management Area Director(s):
Randy Bush <randy@psg.com>
Bert Wijnen <bwijnen@lucent.com>
Operations and Management Area Advisor:
Bert Wijnen <bwijnen@lucent.com>
Technical Advisor(s):
Bob Stewart <bstewart@cisco.com>
Mailing Lists:
General Discussion:disman@dorothy.bmc.com
To Subscribe: disman-request@dorothy.bmc.com
In Body: subscribe disman your_email_address
Archive: ftp://ftp.peer.com/pub/disman/archives
Description of Working Group:
The Distributed Management Working Group is chartered to define an initial set of managed objects for specific distributed network management applications and a framework in which these applications and others can be consistently developed and deployed. A distributed network manager is an applicaton that acts in a manager role to perform management functions and in an agent role so that it can be remotely controlled and observed.
Distributed network management is widely recognized as a requirement for dealing with today's growing internets. A manager application is a good candidate for distribution if it requires minimal user interaction, it would potentially consume a significant amount of network resources due to frequent polling or large data retrieval, or it requires close association with the device(s) being managed.
The working group will limit its work to distributed network management applications where the main communication mechanism for monitoring and control is SNMP. Future work (and other working groups) may be chartered to investigate other distribution techniques such as CORBA or HTTP. The objects defined by the working group will be consistent with the SNMP framework. The working group will especially keep security considerations in mind when defining the interface to distributed management.
The working group will complete these tasks:
Define a Script MIB
Define a Scheduling MIB
Define a Threshold Monitoring MIB
The working group will consider existing definitions, including:
o RFC1451, The Manager to Manager MIB which was being considered by the SNMPv2 working group
o the RMON working group's work in this area
o the SNMP Mid-Level-Manager MIB which is now an expired Internet-Draft
o the work of the Application MIB working group
It is recognized that the scope of this working group is narrow relative to the potential in the area of distributed network management. This is intentional in order to increase the likelihood of producing useful, quality specifications in a timely manner. However, we will keep in mind and account for potential related or future work when developing the framework including:
o Event and alarm logging and distribution
o Historical data collection/summarization
o Topology discovery
Goals and Milestones:
Done |
|
Post Internet-Draft for Threshold Monitoring MIB. |
Done |
|
Meet at the Montreal IETF meeting to discuss charter and review the Threshold Monitoring MIB Internet-Draft. |
Done |
|
Post Internet-Draft for Framework document. |
Done |
|
Post Internet-Draft for Script MIB. |
Done |
|
Submit final version of Threshold Monitor MIB Internet-Draft for consideration as a Proposed Standard. Submit updated versions of Internet-Drafts for Script MIB. |
Done |
|
Meet at the IETF meeting to discuss Internet-Drafts and issues that come up on the mailing list. |
Done |
|
Submit final versions of Internet-Drafts for Script MIB and Schedule MIB document for consideration as Proposed Standards. |
Done |
|
Agree on charter revisions for future work. |
May 99 |
|
Submit final versions of Internet-Drafts for Expression, Event and Notification MIB documents for consideration as Proposed Standards. |
Jun 99 |
|
Submit final version of Internet-Draft for Remote Ping, Traceroute, and Lookup Operations Using SMIv2 |
Jul 99 |
|
Meeting in Oslo to discuss implementation and deployment experience with Schedule and Script mibs, identify any updates needed to these documents. |
Nov 99 |
|
Submit updated Script and Schedule MIBs for consideration as Draft Standards. |
Internet-Drafts:
· Distributed Management Expression MIB
· Definitions of Managed Objects for Remote Ping, Traceroute, and Lookup Operations
· Definitions of Managed Objects for Scheduling Management Operations
· Definitions of Managed Objects for the Delegation of Management Scripts
Request For Comments:
RFC |
Status |
Title |
RFC2591 |
PS |
Definitions of Managed Objects for Scheduling Management Operations |
RFC2592 |
PS |
Definitions of Managed Objects for the Delegation of Management Scripts |