Editor's note: Minutes received 4/12/93. These minutes have not been edited and the attendee list has not been appended. Reported by Kaj Tesink ATM MIB BOF MEETING NOTES On April 1, 1993, Kaj Tesink/Bellcore convened an ATM MIB BOF. The purpose of the BOF was to determine if there was sufficient interest to create a WG to develop managed objects for ATM. The BOF agenda included four presentations, plus a discussion period: 1) Overview, Proposed Charter (Kaj Tesink) 2) ATM MIB Strawperson Proposal (Masuma Ahmed) 3) ATM ILMI (Keith McCloghrie) 4) SONET MIB (Kaj Tesink) Overview - Kaj Tesink ------------------------- Following unanimous agreement that a WG is necessary to develop managed objects related to ATM, Kaj identified the following "terms of reference" as the basis for the proposed charter of the ATM MIB work effort: + Priority on ATM PVCs + Keep the MIB small + Priority is creation of a SNMPv1 managed objects, support of SNMPv2 may be a future effort + Difference between interface and end-to-end view of NM information for ATM Kaj discussed the relationship of the proposed ATM MIB with physical layer MIBs. He suggested that the WG include work on the SONET MIB which was posted by Tracy Cox. The Trunk MIB WG which had developed MIBs for DS1/E1 and DS3/E3 no longer exists. Ayal Opher cautioned against assuming that the SONET MIB is "done". Since there are more implementations of SONET equipment, folks may pay more attention and have more comments on the proposed SONET MIB module. There was discussion on the different perspectives on ATM-related network management information: + Local DTE view of ATM-based communication over the local interface + Network view of the local interface + End-to-end view of the communication path + ATM Switch Management - both private and public + ATM-based Service information - both private and public These different perspectives drive identification of different sets of managed objects. Based on this discussion, a charter was agreed upon, that directs the proposed WG to undertake work on ATM and SONET management (attached). ATM MIB Proposal - Masuma Ahmed ------------------------------- Masuma gave an overview of a Bellcore strawperson proposal for an ATM MIB. See the copy of the viewgraphs for a detailed list of proposed management information. The strawperson MIB is based on the ILMI, and includes configuration information about the ATM interface, ATM layer statistics, but (unlike the ILMI) also VPL/VCL level performance information. Virtual Channel Links are the interfaces between two adjacent ATM devices. A Virtual Channel Connection is the set of VCLs used end-point to end-point. A VCL is identified by a Virtual Channel Identifier (VCI). Similarly, a Virtual Path Connection consists of VPLs, identified by VPIs. Issues identified during the discussion included: + Relation to the existing ILMI MIB (see Keith's talk) + The need for end-to-end PVC configuration information + Modelling of ATM in relation to MIB II interfaces table + Need to keep the MIB small + Need to coordinate modelling of PVCs with FR MIB effort + Need for AAL performance statistics + Need for VPC/VCC level performance statistics ATM Forum ILMI - Keith McCloghrie --------------------------------- Keith gave a presentation on the ATM Forum's Interim Local Management Interface ILMI, stressing that even though the ILMI uses SNMP packet formats, the purpose of the ILMI is not network management, but rather "interface management". However, since the management information needed for interface management is a subset of the information needed for network management, the ILMI's MIB should be appropriate for use by network management as well as for interface management. The ATM Forum's ILMI MIB was designed to be symmetric -- that is, to have the same MIB on each side of the interface. It currently contains read-only objects. The ILMI MIB contains information on the physical port (e.g.,operStatus), ATM Layer, ATM Cell, and VPC/VCCs. There are no VCL or VPL level statistics in the ILMI. Keith recommended that the proposed IETF Working Group use the ILMI MIB as a base for the development of IETF ATM MIB(s). The management of the local interface should use a common MIB module/table/group. SONET MIB - Kaj Tesink ---------------------- Kaj gave a short presentation of the SONET MIB. The SONET MIB has been posted as Internet-Draft for a long time. It is consistent with other trunk MIBs. A minor change may be needed on table indexing. Interested people are encouraged to review this MIB. Internet-Draft: "Definitions of Managed Objects for the SONET Interface Type", Jan.1993, Tracy A. Cox, Kaj Tesink, . Conclusions of the Working Group ------------------------------- 1) There is interest in forming a Working Group to develop standard managed objects for ATM and SONET. Deirdre Kostick suggested to call it the AToMMIB WG, with the "o" signifying SONET, and the "AToM as a reminder to keep MIBs small(!). 2) It is likely that there will be multiple MIB modules for ATM developed to support the different management perspectives identified during the BOF. 3) The MIB module(s) for management for the local interface should build on the ATM Forum ILMI MIB. Charter proposed AToM MIB WG (atommib) -------------------------------------- Chair(s): Kaj Tesink Network Management Area Director(s) Marshall Rose NM-Directorate Consultant: Keith McCloghrie Mailing Lists: General Discussion:atommib@thumper.bellcore.com To Subscribe: atommib-request@thumper.bellcore.com Archive: thumper.bellcore.com:pub/tob/atommib Description of Working Group: The AToM MIB Working Group is chartered to define sets of managed objects which will be useful in the management of ATM and SONET equipment, interfaces, networks, and/or services that conform to the relevant ATM and SONET specifications. The initial sets defined will be: - an interface-specific MIB for ATM interfaces, which is aligned with the managed objects for interface layering being defined by the Interfaces MIB WG. The working group should consider the ATM Forum's ILMI MIB for its suitability in this respect, plus any extensions necessary to instrument the layers between the ATM layer and the IP layer (e.g., AAL5). The latter should be take into account the work of the IP-over-ATM working-group (e.g., the "Multi-Protocol over AAL5" specification). - managed objects for the monitoring and control of ATM PVCs and SVCs, both in ATM end-points and in ATM switches or networks. (objects for ATM SVCs will be considered after completion of the work on ATM PVCs). - managed objects that instrument devices with SONET interfaces that conform with the relevant SONET specifications. This work should closely align to other trunk MIBs (DS1/E1 MIB, DS3/E3 MIB). The working group should consider the existing Internet-Draft SONET MIB for its suitability in this respect. The objects defined by the working group will be consistent with the SNMP framework. Goals and Milestones: May 93 Begin developing internet-drafts for discussion. Oct 93 Post revised internet-drafts for discussion. Dec 93 Submit internet-drafts to IESG for standards track evaluation.