AToM MIB (atommib)

This Working Group did not meet

NOTE: This charter is a snapshot of the 59th IETF Meeting in Seoul, Korea. It may now be out-of-date.

Last Modified: 2004-01-07

Chair(s):
Faye Ly <faye@pedestalnetworks.com>
Kam Lam <hklam@lucent.com>
Operations and Management Area Director(s):
Bert Wijnen <bwijnen@lucent.com>
David Kessens <david.kessens@nokia.com>
Operations and Management Area Advisor:
Bert Wijnen <bwijnen@lucent.com>
Technical Advisor(s):
Mike Heard <heard@pobox.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 currently chartered to:

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

2. 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:
Done  Revised OpticalMIB Internet-Draft and make available for discussion
Done  Submit the SONET APS MIB to the IESG for consideration as a Proposed Standard
Done  Report on implementation experience on RFC 2558
Done  Submit OpticalMIB Internet-Draft to IESG for standards track elevation
Done  Submit the ATM Supplemental to the IESG for consideration as a Proposed Standard
Done  Report on implementation experience on RFC 2493
Done  Report on implementation experience on RFC 2495-2496
Done  Submit any needed revisions of RFC2493 to the IESG for standards track advancement as appropriate
Done  Submit any needed revisions of RFC2558 to the IESG for standards track advancement as appropriate
Jan 04  Re-evaluate charter or close the WG
Jan 04  Submit any needed revisions of RFC2494 to the IESG for standards track advancement as appropriate
Jan 04  Submit any needed revisions of RFC2512-2513 to the IESG for consideration of standards track advancement as appropriate
Mar 04  Submit any needed revisions of RFC2514-2515 to the IESG for consideration of standards track advancement as appropriate
Mar 04  Submit any needed revisions of RFC2495-2496 to the IESG for standards track advancement as appropriate
Mar 04  Report on implementation experience on RFC 2514-2515
Mar 04  Report on implementation experience on RFC 2512-2513
Mar 04  Report on implementation experience on RFC 2494
Internet-Drafts:
  • - draft-ietf-atommib-rfc2496bis-05.txt
  • - draft-ietf-atommib-rfc2495bis-06.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
    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
    RFC2515 PS Definitions of Managed Objects for ATM Management
    RFC2558 PS Definitions of Managed Objects for the SONET/SDH Interface Type
    RFC3498 PS Definitions of Managed Objects for Synchronous Optical Network (SONET) Linear Automatic Protection Switching (APS) Architectures
    RFC3591 PS Definitions of Managed Objects for the Optical Interface Type
    RFC3592 DS Definitions of Managed Objects for the Synchronous Optical Synchronous Digital Hierarchy (SONET/SDH) Interface Type
    RFC3593 DS Textual Conventions for MIB Modules Using Performance History Based on 15 Minute Intervals
    RFC3606StandardDefinitions of Supplemental Managed Objects for ATM Interface

    Current Meeting Report

    None received.

    Slides

    None received.