NOTE: This charter is a snapshot of the 50th IETF Meeting in Minneapolis, Minnesota. It may now be out-of-date. Last Modified: 14-Mar-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
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 |
AToM MIB WG minutes Minneapolis, MN 50th IETF
Tue 20-mar-2001
Co-Chairs: Nathan Kohn, Faye Ly
Presentors (with slides)
Faye Ly
Randy Presuhn (disman WG chair)
An-ni Huynh (+Mark Stewart)
Kam Lam (+Lakshmi Raman)
0. AToMMIB Met for one hour at the 50 IETF in Minneapolis, MN. The session was lively attended by 25 people.
1. Thanks to Kaj Tessink for his years of chairing the AToMMIB WG. Kaj has decided to return to ordinary human existence, but will hopefully still contribute his wisdom and insights to the WG.
2. New co-chairs. It was not possible for only one person to fill the vacancy that Kaj left. Fortunately, Kaj has offered to continue coaching his replacements, Faye Ly and Nathan Kohn. Congrats, thank you, and good luck to both of them. Thanks also to the Area Directors, Thomas Narten and Erik Nordmark, for keeping the new co-chairs out of trouble.
3. Name Change. It has been pointed out that AToMMIB has outgrown it's original name and charter - ATM. The AD ponted out that changing the acronym is NOT trivial and ill-advised, but changing the definition of the acronym is not so bad. How would the following be??? :
A ATM
T TDM
o Optical
M Management
MIB MIB
4. No one from the SONET Linear APS MIB (which defines additional sets of SONET managed objects beyond those defined in RFC2558) was there at the meeting but it was menyioned that there was a last issue pending to the mailing list. once this last issue is resolved (perhaps just a clarification is needed) , this MIB is ready for last call. call. A few clarifications will be made as part of the last call.
5. ATM 2 MIB status was given and it is also pending last issue raised by Mike Sneed. Once the editor publishes the last draft including Mike's comments, this last draft should be the candidate for last call.
6. It was generally agreed to advance RFC 2512-2515, 2558, and 2493-2496 from Proposed standard to Draft standard.
7. Randy Presuhn, disman WG chair, provided an update (with slides) of activities in disman, and provided details on the ARC (Alarm Report Control) and Condition Tables. Thanks Randy!
8. An-ni Huynh presented the changes to the Optical Channel MIB she and Mark Stewart have been working on. One item actively discussed concerned moving to fixed TCM Levels (Tandem Connection) since it simplifies management without losing functionality. Tammy Ferris raised some operational concerns, such as whether one operator could inadvertently disable monitoring by other operators. There was additional discussion concerning the independance of OtnODUkTCM Sink and Source and whether separate table were necessary. Randy questioned how mismatches would be handled. Rajesh Abbi raised questions about overlapping, nested, and cascaded TCM layers. An-ni will make appropriate clarifications to the MIB.
9. There was interest in doing additional work for the Optical Channel MIB to support Cross-Connects and Add/Drop. These will probably be in a separate table.
10. Kam Lam (+Lakshmi Raman) reported on the doings from ITU-T Study Group 15, which has decided to do its work using protocol-neutral UML. Kam also provided insights into the activities of SG 4.
nathan kohn
Agenda
Status of ITU-T NM Activities
Optical Interface MIB
Condition MIB
Alarm Report Control MIB update