datatracker.ietf.org
AToM MIB (atommib)
| ||||||||||||||||||||||||||||||||||||||||||||||||||
| Personnel | |
| Chairs: |
Faye Ly <fayely@juniper.net> Kam Lam <hklam@lucent.com> |
| Area Director: | ? |
| Tech Advisor: |
Mike Heard <heard@pobox.com> |
|
Mailing List |
|
| Address: | atommib@research.telcordia.com |
| To Subscribe: | atommib-request@research.telcordia.com |
| Archive: | ftp://ftp.research.telcordia.com/pub/Group.archive/atommib |
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.
| 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 |
| Done | Re-evaluate charter or close the WG |
| Jan 2004 | Submit any needed revisions of RFC2494 to the IESG for standards track advancement as appropriate |
| Jan 2004 | Submit any needed revisions of RFC2512-2513 to the IESG for consideration of standards track advancement as appropriate |
| Mar 2004 | Submit any needed revisions of RFC2514-2515 to the IESG for consideration of standards track advancement as appropriate |
| Done | Submit any needed revisions of RFC2495-2496 to the IESG for standards track advancement as appropriate |
| Done | Report on implementation experience on RFC 2514-2515 |
| Done | Report on implementation experience on RFC 2512-2513 |
| Mar 2004 | Report on implementation experience on RFC 2494 |