CURRENT_MEETING_REPORT_

Reported by Kaj Tesink/Bellcore

Minutes of the AToM MIB Working Group (ATOMMIB)

The reactivated AToMMIB Working Group met two times during the Danvers
meeting.  The working group has a number of objectives:


   o To define managed objects for ATM that address functions beyond
     those defined in RFC 1695, e.g., for ATM SVCs.

   o To decide the maturity level of RFC 1695 and 1595 and to assess
     whether these specifications should be advanced on the standards
     track.


The Danvers meeting was used to review the first objective, and in
particular the posted Internet-Draft, draft-ietf-atommib-atm2-00.txt.

The second objective for now is best handled on the mailing list.  Kaj
will send out a call for implementation experience.  In addition to the
mailing list, the Stockholm meeting can be used for a first review of
the feedback.  Note that RFC 1595 may benefit from the review of the
DS1/E1/DS3/E3 MIBs which is expected after the Stockholm meeting.

The posted Internet-Draft, draft-ietf-atommib-atm2-00.txt, is the result
of efforts both in the ATM Forum and on the mailing list.  Host and
network perspectives have now been combined in this document.  The
current draft was introduced by Fay Ly and Mike Noto.  In addition,
George Mouradian presented issues encountered in the ATM Forum NM SWG.

The goal of the following discussion was to resolve issues that have
been raised on the mailing list as well as additional issues raised
during this meeting.

Due to lack of time not all issues could be addressed.  One conclusion
was to create a separate document on textual conventions for ATM MIBs.
This will be a `living' document to be used by other ATM MIB
specifications.

A revised issues list will be posted that includes newly identified
issues and the resolutions agreed upon during the meeting.  The editors
will revise the Internet-Draft accordingly and post the new version
together with the new ATMMIBTC specification.