AToM MIB (atommib)
------------------
Charter
Last Modified: 2004-08-19
Current Status: Active Working Group
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:
Posted Revised I-D Title <Filename>
------ ------- --------------------------------------------
Jun 04 Jun 04 <draft-ietf-atommib-imamib-00.txt>
Definitions of Managed Objects for the IMA Interface Type
Request For Comments:
RFC Stat Published Title
------- -- ----------- ------------------------------------
RFC1595 PS Mar 94 Definitions of Managed Objects for the SONET/SDH
Interface Type
RFC1695 PS Aug 94 Definitions of Managed Objects for ATM Management
Version 8.0 using SMIv2
RFC2493 PS Jan 99 Textual Conventions for MIB Modules Using Performance
History Based on 15 Minute Intervals
RFC2512 PS Feb 99 Accounting Information for ATM Networks
RFC2513 PS Feb 99 Managed Objects for Controlling the Collection and
Storage of Accounting Information for
Connection-Oriented Networks
RFC2514 PS Feb 99 Definitions of Textual Conventions and OBJECT-IDENTITIES
for ATM Management
RFC2515 PS Feb 99 Definitions of Managed Objects for ATM Management
RFC2558 PS Mar 99 Definitions of Managed Objects for the SONET/SDH
Interface Type
RFC3498 PS Mar 03 Definitions of Managed Objects for Synchronous Optical
Network (SONET) Linear Automatic Protection Switching
(APS) Architectures
RFC3591 PS Sep 03 Definitions of Managed Objects for the Optical Interface
Type
RFC3592 DS Sep 03 Definitions of Managed Objects for the Synchronous
Optical Synchronous Digital Hierarchy (SONET/SDH)
Interface Type
RFC3593 DS Sep 03 Textual Conventions for MIB Modules Using Performance
History Based on 15 Minute Intervals
RFC3606Standard Nov 03 Definitions of Supplemental Managed Objects for ATM
Interface
RFC3896Standard Sep 04 Definitions of Managed Objects for the DS3/E3 Interface
Type
RFC3895Standard Sep 04 Definitions of Managed Objects for the DS1, E1, DS2 and
E2 Interface Types