Current Meeting Report
Slides


2.3.1 AToM MIB (atommib)

NOTE: This charter is a snapshot of the 54th IETF Meeting in Yokohama, Japan. It may now be out-of-date.

Last Modifield: 06/25/2002

Chair(s):
Faye Ly <fayely98@hotmail.com>
Nathan Kohn <mvnk@lucent.com>
Internet Area Director(s):
Thomas Narten <narten@us.ibm.com>
Erik Nordmark <erik.nordmark@sun.com>
Internet Area Advisor:
Erik Nordmark <erik.nordmark@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:
  • - draft-ietf-atommib-atm2-18.txt
  • - draft-ietf-atommib-sonetaps-mib-08.txt
  • - draft-ietf-atommib-opticalmib-05.txt
  • - draft-ietf-atommib-rfc2558bis-00.txt
  • - draft-ietf-atommib-rfc2496bis-00.txt
  • - draft-ietf-atommib-rfc2495bis-00.txt
  • - draft-ietf-atommib-rfc2493bis-00.txt
  • Request For Comments:
    RFCStatusTitle
    RFC1595 PS Definitions of Managed Objects for the SONET/SDH Interface Type
    RFC1695 PS Definitions of Managed Objects for ATM Management Version 8.0 using SMIv2
    RFC2493 PS Textual Conventions for MIB Modules Using Performance History Based on 15 Minute Intervals
    RFC2512 PS Accounting Information for ATM Networks
    RFC2515 PS Definitions of Managed Objects for ATM Management
    RFC2513 PS Managed Objects for Controlling the Collection and Storage of Accounting Information for Connection-Oriented Networks
    RFC2514 PS Definitions of Textual Conventions and OBJECT-IDENTITIES for ATM Management
    RFC2558 PS Definitions of Managed Objects for the SONET/SDH Interface Type

    Current Meeting Report

    54th IETF AToMMIB working group meeting minutes:
    Tuesday 7/16/02 13:00:

    1. Agenda bashing

    Kam requested to add the ITU-T study group 15 status update.
    Orly requested to talk about 2595/2596bis status as well.
    Agenda updated

    2. Kam presented Optical Interface mib

    - monitors input, output power, and laser temperature on both source and
    transmit directions. Bring this to the list for any other DWDM vendor is
    supporting this. If yes, incorporate Rish’s suggestion. If not, suggest to Rish
    to use the Sensor MIB done in the Entity MIB. Sensor MIB can be used to model
    any measurement including power or temperature in either directions.

    3. Orly – correction to 53rd meeting minutes
    - RFC 2495 – no issue

    4. Orly –
    - Fixed RFC 2495bis and 2496bis (mostly text errors)
    - So we can move forward the 2493bis
    - After all 4 drafts are published, expect WG last call on all 4 of them.

    5. Kam to post the ITU-T Study group 15 status update slides to the mailing
    list.

    Slides

    Agenda
    Optical Interface MIB
    DS1 Changes
    Current Status of ITU-T Transport Network Network Management Standards Work