NOTE: This charter is a snapshot of the 51st IETF Meeting in London, England. It may now be out-of-date. Last Modified: 31-Jul-01
Faye Ly <faye@salira.com>
Nathan Kohn <mvnk@lucent.com>
Thomas Narten <narten@raleigh.ibm.com>
Erik Nordmark <nordmark@eng.sun.com>
Erik Nordmark <nordmark@eng.sun.com>
Keith McCloghrie <kzm@cisco.com>
General Discussion: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 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.
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 |
· Definitions of Supplemental Managed Objects for ATM Interface
· Definitions of Managed Objects for SONET Linear APS Architectures
· Definitions of Managed Objects for the Optical Interface Type
RFC |
Status |
Title |
RFC1595 |
PS |
Definitions of Managed Objects for the SONET/SDH Interface Type |
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 |
See HUBMIB WG for joint session.
Meeting Minutes for the AToMMIB WG, 51st IETF, London
Thursday 9 Aug 2001, 1530
Chairs: Faye Ly faye@SALIRA.com and Nathan Kohn mvnk@lucent.com
Minutes by Mike Ayers and Nathan Kohn
1. Agenda bashing - Nathan Kohn
2. Review of hubMIB/AToMMIB joint meeting - Dan Romascanu
We have learned that there are several things to consider in designing the WIS MIB:
- This interface will be deployed in both LAN and WAN (SONET) environments
- Therefore it must be manageable by both LAN and WAN managers, which use different management paradigms
- Many of the WIS objects are similar to those in RFC2558, but many are different
- The first draft is available as draft-ietf-hubmib-wis-mib-00.txt
- Several comments have already been received from IEEE and AToMMIB members
We have determined 3 key issues:
1. The ifStackTable mappings
2. 802.3ae mappings - for which can we use the SONET MIB?
3. Performance counters - we need to provide two types to work with the two types of managers.
A design team will be formed to research the solution. It will contain the WIS MIB editors, Mike Heard and Kaj Tessink, who submitted a rebuttal draft, and any volunteers (Kam Lam volunteered). The design team will have two months to finish their work.
3. SONET MIB - Faye Ly
We still have not received any implementation reports. This would be a good time if any extensions were needed.
Mike Ayers: We need time to determine if we will want to extend for the WIS. Do we have 2 months?
Faye: We'll see.
4. WG Status - Faye Ly
SONET APS and ATM2 MIBs are in the RFC queue pending IESG review.
Implementation experience calls have gone out for RFCs 2494, 2495, 2496, and 2558. No reports have been received for 2494 or 2558.
PWE3 group appears to be using 2494. Another call will be sent out. Also need one more report for DS3 MIB (RFC2496).
ATM MIB is waiting for the call for implementation experience.
Optical MIB is at draft 1, will need a time extension.
5. Optical MIB - Kam Lam
Review objectives:
- manage OTN and pre-OTN (DWDM) systems
- RFC2863 compliant
- new ifTypes
ITU-T is a members only organization, so we do not have WG access to ITU documents. However, the SG4 chair has opened a website with some docs on it(URL?). We can use this site to post relevant docs.
Changes:
- describe Tandem Connection Monitoring usage
- OTUkT usage configuration table changes
- editorial changes: new TC IntervalNumber, moved interval objects, changed numValidIntervals to numIntervals, threshhold objects now read/write, aligned with G.cemr, aligned configuration parameters with G.798
6. Close
A. Action Items
Faye Ly: Send ADSL TCs to WG
Faye Ly: Use IETF mailing list to call for implementations
Kam Lam: Make ITU docs available
Faye Ly and Nathan Kohn to update the time line and ask for approval from the directors for extending Optical Interface MIB and advancing ATM MIBs.