Last Modified: 2004-06-15
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 | |
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 |
RFC | Status | Title |
---|---|---|
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 |
RFC3606 | Standard | Definitions of Supplemental Managed Objects for ATM Interface |
AToM MIB WG meeting Tuesday 8/3/2004 IETF San Diego
The atommib working group met for one session on Tuesday afternoon at the San Diego IETF-60th meeting. The WG discussed the status of the implementation feedbacks and the IMA MIB Internet Draft. Implementation feedback had been requested long time ago for the following PS: RFC2494 (DS0), RFC2495 (DS1/DS2), RFC2496 (DS3), RFC2512 (ATM acct), RFC2513 (collection), RFC2514 (ATM TC), and RFC2515 (ATM). The received implementation feedbacks are not sufficient for some of the objects in order to advance any of the MIB modules as full modules without deprecating those objects. For RFC2495 and RFC2496, it was suggested to leave them with no further reports because both MIBs will be obsolete once RFC2495bis and RFC2496bis are published. For the other MIBs, it was suggested to make another request to the list. If no additional feedback (even in the form of MIB walk) within couple weeks, the work items will be dropped from the milestone list. It was noted that there might be several IETF MIB modules that reference the RFC2514 TCs. If that is the case, that should be included in the report and may be able to advance RFC2514. If nothing becomes available, the available implementation feedback of RFC2514 will be submitted as is to IESG for information to others. The IMA MIB would require rechartering. However, unless there is enough interest from the list, the IMA MIB will not be a new WG work item. In Addition, it was agreed that the new MIB should be rewritten as a supplement MIB to the ATM Forum IMA MIB and should not copy the ATM Forum IMA MIB objects as currently done in the I-D. An alternative will be to give input to ATMF for them to extend the IMA MIB. In summary, the existing WG milestones are either done (e.g., RFC2495, RFC2496) or will be dropped by September-October time frame (e.g., RFC 2515) due to lack of active participation and interest. The WG will be concluded, if nothing changes. |