2.3.2 AToM MIB (atommib) *

This Working Group Did Not Meet

NOTE: This charter is a snapshot of the 40th IETF Meeting in Washington, DC. It may now be out-of-date. Last Modified: 06-Nov-97


Kaj Tesink <kaj@cc.bellcore.com>

Internet Area Director(s):

Jeffrey Burgan <burgan@home.net>
Thomas Narten <narten@raleigh.ibm.com>

Internet Area Advisor:

Jeffrey Burgan <burgan@home.net>

Technical Advisor(s):

Keith McCloghrie <kzm@cisco.com>

Mailing Lists:

General Discussion:atommib@thumper.bellcore.com
To Subscribe: atommib-request@thumper.bellcore.com
Archive: ftp://thumper.bellcore.com/pub/Group.archive/atommib

Description of Working Group:

The AToM MIB Working Group is chartered to evaluate RFC 1695, a Proposed Standard, with respect to the standards track. As a part of its evaluation, the working group will prepare a revised version and recommend the appropriate level of standardization for this revision to the IESG (i.e., that it be advanced to Draft Standard status, or that it cycle at Proposed Standard status).

As a part of its evaluation, the AToM MIB Working Group may also define additional sets of managed objects, to reflect growing experience and industry requirements for management of:

o ATM services

o The Frame based UNI (F-UNI)

o ATM tests

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

Goals and Milestones:



Post an Internet-Draft of the ATM and SONET MIB.



Submit the ATM and SONET MIB to the IESG for consideration as a Proposed Standard.



Begin developing Internet-Drafts for discussion.



Revised Internet-Draft and make available for discussion.

Oct 95


Submit Internet-Drafts to IESG for standards track evaluation.


Request For Comments:







Definitions of Managed Objects for the SONET/SDH Interface Type



Definitions of Managed Objects for ATM Management Version 8.0 using SMIv2

Previous PageNext Page