Editor's note: These minutes have not been edited. AToMMIB WG Montreal Meeting Report The WG discussed all the documents currently under consideration: - SONET/SDH MIB - RFC1595 - ATM MIB - RFC1695 - Supplemental ATM MIB - I-D - ATM Textual Conventions - I-D - ATM Tests - I-D - ATM Accounting - I-D The results were as follows: 1. SONET/SDH MIB RFC1595 Minor polishing is necessary following other trunk MIBs and some minor issues brought up on the list. The issue of accommodating full T1.231 support and support for multiple 24 hour history will be attempted to be resolved in a single MIB together with the other trunk MIBs. The editor is asked to produce a next I-D of the revised RFC1595 as the basis for further processing as Draft Standard. 2. ATM MIB - RFC1695 Discussion was limited to minor technical issues such as inclusion of atmNextAvailVpiHint, atmNextAvailVciHint and connection names. Also some further alignement with the Supplemental MIB is necessary, e.g., PVC/SVC conformance clauses. The editor is asked to produce a next I-D of the revised RFC1695 as the basis for further processing as Draft Standard. 3. ATM Supplemental MIB All open issues were resolved resulting in a series of amendments including the relationship with RFC1695. In particular: - History counters based on 15-minute timre intervals will be posted as a separate I-D. - ILMI service registration should be included. - The trap issue should be reposted to solicit comments. - Support should not include ABR at this point. A list of minor issues was discussed and resolved; in some cases additional discussion on the list is necessary. The editor is asked to produce a next I-D as the basis for further processing as Proposed Standard. 4. ATM Textual Conventions Some minor fixes were discussed and agreed upon. The editor is asked to produce an I-D as the basis for further processing as Proposed Standard. 5. ATM Tests The Interfaces MIB WG has discussed a revision of the Test MIB which has some changes relative to RFC1573. The ATM-TEST-MIB will be adapted accordingly and moved together with the generic test MIB. 6. ATM Accounting Discussion focussed on both direction and technical issues. In particular: - With the latest draft the number of comments seems to have gone up rather than down. - Several comments were made expressing the desire to have a general purpose mechnism that can be applied to technologies other than ATM as well (e.g., FR, RMON). After discussion the following consensus was reached: - The new document structure should include: a) a specification of the generic accounting mechnism. b) a specification of the accounting information for ATM. This structure is meant to facilitate work by other groups to define their particular accounting information. - The starting point for the new specifications should be the posted I-D by J.Heinanen/K.McCloghrie, adapted to the new specification structure, and accommodating any issues that appear to have rough consensus. The importance of carrier perspectives and common practices was noted and input is sollicited. - The chair asked a single editor (K. McCloghrie) to prepare the new I-Ds and post them for discussion.