Current Meeting Report
Slides


2.2.1 AToM MIB (atommib)

NOTE: This charter is a snapshot of the 52nd IETF Meeting in Salt Lake City, Utah USA. It may now be out-of-date. Last Modified: 18-Oct-01
Chair(s):
Faye Ly <fayely98@hotmail.com>
Nathan Kohn <mvnk@lucent.com>
Internet Area Director(s):
Thomas Narten <narten@us.ibm.com>
Erik Nordmark <nordmark@eng.sun.com>
Internet Area Advisor:
Erik Nordmark <nordmark@eng.sun.com>
Technical Advisor(s):
Keith McCloghrie <kzm@cisco.com>
Mailing Lists:
General Discussion:atommib@research.telcordia.com
To Subscribe: atommib-request@research.telcordia.com
Archive: ftp://ftp.research.telcordia.com/pub/Group.archive/atommib
Description of Working Group:
The AToM MIB Working Group is chartered to:

1. Complete the ATM Supplemental MIB, which defines additional sets of ATM managed objects beyond those defined in RFC2515, to reflect growing experience and industry requirements for management of ATM.

2. Complete the SONET Linear APS MIB, which defines additional sets of SONET managed objects beyond those defined in RFC2558, to reflect growing experience and industry requirements for management of SONET Automatic Protection Switching.

3. Evaluate and define managed objects for optical channels and interfaces.

4. Maintain and advance on the standards track the existing specifications for ATM management (RFC2512-2515).

5. Maintain and advance on the standards track the existing specification for SONET/SDH management (RFC2558).

6. Maintain and advance on the standards track other trunk-mib specifications (i.e., for DS0 - DS3-E3, RFC2493-2496).

The objects defined by the working group will be consistent with the Internet-standard Management framework.

Goals and Milestones:
Jan 01   Revised OpticalMIB Internet-Draft and make available for discussion
Mar 01   Submit the SONET APS MIB to the IESG for consideration as a Proposed Standard
Mar 01   Submit the ATM Supplemental to the IESG for consideration as a Proposed Standard
Jun 01   Report on implementation experience on RFC 2493-2496
Jun 01   Report on implementation experience on RFC 2512-2515
Jun 01   Report on implementation experience on RFC 2558
Oct 01   Submit OpticalMIB Internet-Draft to IESG for standards track elevation
Oct 01   Submit any needed revisions of RFC2512-2515 to the IESG for consideration of standards track advancement as appropriate
Oct 01   Submit any needed revisions of RFC2493-2496 to the IESG for standards track advancement as appropriate
Oct 01   Submit any needed revisions of RFC2558 to the IESG for standards track advancement as appropriate
Internet-Drafts:
Request For Comments:
RFCStatusTitle
RFC1595PSDefinitions of Managed Objects for the SONET/SDH Interface Type
RFC2493PSTextual Conventions for MIB Modules Using Performance History Based on 15 Minute Intervals
RFC2512PSAccounting Information for ATM Networks
RFC2513PSManaged Objects for Controlling the Collection and Storage of Accounting Information for Connection-Oriented Networks
RFC2514PSDefinitions of Textual Conventions and OBJECT-IDENTITIES for ATM Management
RFC2515PSDefinitions of Managed Objects for ATM Management
RFC2558PSDefinitions of Managed Objects for the SONET/SDH Interface Type

Current Meeting Report

None received.

Slides

Joint Atom & Hub Agenda
Optical Interface MIB
Remaining work before SONET MIB update can be published as an RFC