Distributed Management (disman) Charter

Distributed Management (disman)

This Working Group did not meet

NOTE: This charter is a snapshot of the 53rd IETF Meeting in Minneapolis, MN USA. It may now be out-of-date. Last Modified: 07-Jan-02

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>

Mailing Lists:

General Discussion:disman@dorothy.bmc.com
To Subscribe: disman-request@dorothy.bmc.com
In Body: subscribe disman your_email_address
Archive: ftp://amethyst.bmc.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 which 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 architecture defined in RFC 2571. 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 Scheduling MIB

Define a Script MIB

Define a Remote Operations MIB

Define an Expression and Event MIB to support Threshold Monitoring

Define a Notification Log MIB

Define an Alarm MIB

The working group will consider existing definitions, including:

o the RMON working group's work in this area

o the Application MIB (RFC 2564), SysAppl MIB (RFC 2287) and related standards.

The work on the Alarm MIB will take into consideration existing standards and practices, such as ITU-T X.733. Whether any mappings to these other standards appear in the Alarm MIB or in separate documents will be decided by the WG. The WG will actively seek participation from ITU participants to make ensure that the ITU work is correctly understood.

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.
Done		Submit final versions of Internet-Drafts for Expression, Event and Notification MIB documents for consideration as Proposed Standards.
Done		Submit final version of Internet-Draft for Remote Ping, Traceroute, and Lookup Operations Using SMIv2
Done		Meeting in Oslo to discuss implementation and deployment experience with Schedule and Script mibs, identify any updates needed to these documents.
Done		WG agreement on direction regarding mappings to / from other alarm frameworks
Done		Submit updated Script and Schedule MIBs for consideration as Draft Standard (or recycle at Proposed).
Done		Submit updated draft of Alarm MIB for IETF meeting
Done		decision on question of whether recycle the Log MIB.
Done		Submit updated draft of Alarm MIB for IETF meeting.
Done		call for implementation experience and updates to the remote operations MIB.
Done		call for implementation experience and updates to the Event and Expression MIBs.
Dec 01		WG last call on Alarm Management MIB.
Jan 02		Alarm Management MIB delivered to IESG for consideration as a Proposed Standard.

Internet-Drafts:

Request For Comments:

RFC	Status	Title

RFC2925	PS	Definitions of Managed Objects for Remote Ping, Traceroute, and Lookup Operations
RFC2982	PS	Distributed Management Expression MIB
RFC2981	PS	Event MIB
RFC3014	PS	Notification Log MIB
RFC3165	PS	Definitions of Managed Objects for the Delegation of Management Scripts
RFC3231	PS	Definitions of Managed Objects for Scheduling Management Operations

Current Meeting Report

None received.

Slides

None received.