Definitions of Textual Conventions and OBJECT-IDENTITIES for ATM Management June 26, 1996 Michael Noto (editor) Bell Communications Research noto@cc.bellcore.com Kaj Tesink (editor) Bell Communications Research kaj@cc.bellcore.com 1. Status of this Memo This document is an Internet-Draft. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its Areas, and its Working Groups. Note that other groups may also distribute working documents as Internet- Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet- Drafts as reference material or to cite them other than as a "work in progress". To learn the current status of any Internet-Draft, please check the "1id-abstracts.txt" listing contained in the Internet-Drafts Shadow Directories on ds.internic.net (US East Coast), nic.nordu.net (Europe), ftp.isi.edu (US West Coast), or munnari.oz.au (Pacific Rim). draft ATM Textual Conventions and OBJECT-IDENTITIES 6/26/96 2. Introduction This memo describes Textual Conventions and OBJECT-IDENTITIES used for managing ATM-based interfaces, devices, networks and services. When designing a MIB module, it is often useful to define new types similar to those defined in the SMI. In comparison to a type defined in the SMI, each of these new types has a different name, a similar syntax, but a more precise semantics. These newly defined types are termed textual conventions, and are used for the convenience of humans reading the MIB module. This is done through Textual Conventions as defined in RFC1903[1]. It is the purpose of this document to define the set of textual conventions available to ATM MIB modules. When designing MIB modules, it is also often useful to register further properties with object identifier assignments so that they can be further used by other MIB modules. This is done through the OBJECT-IDENTITY macro defined in RFC1902[2]. This document defines OBJECT-IDENTITIES available to ATM MIB modules. This memo does not specify a standard for the Internet community. Expires 12/26/96 [Page 2] draft ATM Textual Conventions and OBJECT-IDENTITIES 6/26/96 3. Definitions ATM-TC-MIB DEFINITIONS ::= BEGIN IMPORTS MODULE-IDENTITY, OBJECT-IDENTITY, Integer32 FROM SNMPv2-SMI TEXTUAL-CONVENTION, TimeStamp FROM SNMPv2-TC atmMIB, atmTrafficDescriptorTypes FROM ATM-MIB; atmTCMIB MODULE-IDENTITY LAST-UPDATED "9606261200Z" ORGANIZATION "IETF AToMMIB Working Group" CONTACT-INFO " Michael Noto Postal: Bell Communications Research 331 Newman Springs Road Red Bank, NJ 07701 USA Tel: +1 908 758 5104 Fax: +1 908 758 4177 E-mail: noto@cc.bellcore.com Kaj Tesink Postal: Bell Communications Research 331 Newman Springs Road Red Bank, NJ 07701 USA Tel: +1 908 758 5254 Fax: +1 908 758 4177 E-mail: kaj@cc.bellcore.com" DESCRIPTION "This MIB Module provides Textual Conventions and OBJECT-IDENTITY Objects to be used by ATM systems." ::= { atmMIB 3 } -- The Textual Conventions defined below are organized -- alphabetically Expires 12/26/96 [Page 3] draft ATM Textual Conventions and OBJECT-IDENTITIES 6/26/96 AtmAddr ::= TEXTUAL-CONVENTION DISPLAY-HINT "1x" STATUS current DESCRIPTION "The ATM address used by the network entity. The address types are: no address (0 octets), E.164 (8 octets), and NSAP (20 octets). Note: The E.164 address is encoded in BCD format." SYNTAX OCTET STRING (SIZE(0|8|20)) AtmConnCastType ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "The type of topology of a connection (point- to-point, point-to-multipoint). In the case of point-to-multipoint, the orientation of this VPL or VCL in the connection. On a host: - p2mpRoot indicates that the host is the root of the p2mp connection. - p2mpLeaf indicates that the host is a leaf of the p2mp connection. On a switch: - p2mpRoot indicates that cells received by the switching fabric from the interface are from the root of the p2mp connection. - p2mpLeaf indicates that cells transmitted to the interface from the switching fabric are to the leaf of the p2mp connection." SYNTAX INTEGER { p2p(1), p2mpRoot(2), p2mpLeaf(3) } AtmConnKind ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "The use of call control. The use is as follows: pvc(1) Virtual link of a PVC. Should not be used in an PVC/SVC (i.e., SPVC) crossconnect. Expires 12/26/96 [Page 4] draft ATM Textual Conventions and OBJECT-IDENTITIES 6/26/96 svcIncoming(2) Virtual link established after a received signaling request to setup an SVC. svcOutgoing(3) Virtual link established after a transmitted or forwarded signaling request to setup an SVC. spvcInitiator(4) Virtual link at the PVC side of an SVC/PVC crossconnect, where the switch is the initiator of the SPVC setup. spvcTarget(5) Virtual link at the PVC side of an SVC/PVC crossconnect, where the switch is the target of the SPVC setup. An spvcInitiator is always cross-connected to an svcOutgoing, and an spvcTarget is always cross-connected to an svcIncoming." SYNTAX INTEGER { pvc(1), svcIncoming(2), svcOutgoing(3), spvcInitiator(4), spvcTarget(5) } AtmServiceCategory ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "The service category for a connection." REFERENCE "ATM Forum Traffic Management 4.0." SYNTAX INTEGER { other(1), -- none of the following cbr(2), -- constant bit rate rtVbr(3), -- real-time variable bit rate nrtVbr(4), -- non real-time variable bit rate abr(5), -- available bit rate ubr(6) -- unspecified bit rate } Expires 12/26/96 [Page 5] draft ATM Textual Conventions and OBJECT-IDENTITIES 6/26/96 AtmSigDescrParamIndex ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "The value of this object identifies a row in the atmSigDescrParamTable. The value 0 signifies that none of the signalling parameters defined in the atmSigDescrParamTable are applicable." SYNTAX Integer32 AtmSignallingType ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "The type of signalling that is used for the identified interface and protocol suite. other: A signalling protocol other than those listed below. Auto-configuration: Indicates that the signalling protocol is to be or has yet to be determined. One such mechanism is via ATM Forum ILMI auto-configuration procedures. ATM Forum UNI 4.0: ATM Forum, Integrated Local Management Interface Specification Version 4.0, July 1996 [12]. ITU-T DSS2: - ITU-T Recommendation Q.2931, Broadband Integrated Service Digital Network (B-ISDN) Digital Subscriber Signalling System No.2 (DSS2) User-Network Interface (UNI) Layer 3 Specification for Basic Call/Connection Control (September 1994) [5] - ITU-T Draft Recommendation Q.2961, B-ISDN DSS 2 Support of Additional Traffic Parameters (May 1995) [8] NOTE: Update this reference when the draft matures - ITU-T Draft Recommendation Q.2971, B-ISDN DSS 2 User Network Interface Layer 3 Specification for Point-to-multipoint Call/connection Control (May 1995) [9] Expires 12/26/96 [Page 6] draft ATM Textual Conventions and OBJECT-IDENTITIES 6/26/96 ATM Forum UNI 3.0: ATM Forum, ATM User-Network Interface, Version 3.0 (UNI 3.0) Specification, (1994) [3]. ATM Forum UNI 3.1: ATM Forum, ATM User-Network Interface, Version 3.1 (UNI 3.1) Specification, (November 1994) [4]. ATM Forum UNI 4.0: ATM Forum, ATM User-Network Interface, Version 4.0 (UNI 4.0) Specification, af-sig-0061.000 (June 1996) [7]. ATM Forum IISP (based on UNI 3.0 or UNI 3.1) : Interim Inter-switch Signaling Protocol (IISP)Specification, Version 1.0, af-pnni-0026.000, (December 1994) [10]. ATM Forum PNNI 1.0 : ATM Forum, Private Network-Network Interface Specification, Version 1.0, af-pnni-0055.000, (March 1996) [6]. ATM Forum B-ICI: ATM Forum, B-ICI Specification, Version 2.0, af-bici-0013.002, (November 1995) [11]." SYNTAX INTEGER { other(1), autoConfig(2), ituDss2(3), atmfUni3Dot0(4), atmfUni3Dot1(5), atmfUni4Dot0(6), atmfIispUni3Dot0(7), atmfIispUni3Dot1(8), atmfIispUni4Dot0 (9) atmfPnni1Dot0(10), atmfBici2Dot0(11) } AtmTrafficDescrParamIndex ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "The value of this object identifies a row in the Expires 12/26/96 [Page 7] draft ATM Textual Conventions and OBJECT-IDENTITIES 6/26/96 atmTrafficDescrParamTable. The value 0 signifies that no row has been identified." SYNTAX INTEGER (0..4294967295) AtmVcIdentifier ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "The VCI value for a VCL. The maximum VCI value cannot exceed the value allowable by atmInterfaceMaxVciBits defined in ATM-MIB." SYNTAX INTEGER (0..65535) AtmVpIdentifier ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "The VPI value for a VPL or VCL. The value VPI=0 is only allowed for a VCL. For ATM UNIs supporting VPCs the VPI value ranges from 1 to 255. For ATM UNIs supporting VCCs the VPI value ranges from 0 to 255. The maximum VPI value cannot exceed the value allowable by atmInterfaceMaxVpiBits defined in ATM-MIB." SYNTAX INTEGER (0..4095) AtmVorXAdminStatus ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "The value determines the desired administrative status of a virtual link or cross-connect. The up and down states indicate that the traffic flow is enabled or disabled respectively on the virtual link or cross-connect." SYNTAX INTEGER { up(1), down(2) } AtmVorXLastChange ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "The value of MIB II's sysUpTime at the time this virtual link or cross-connect entered its current operational state. If the current state was entered prior to the last re-initialization of the agent then this object contains a zero value." Expires 12/26/96 [Page 8] draft ATM Textual Conventions and OBJECT-IDENTITIES 6/26/96 SYNTAX TimeStamp AtmVorXOperStatus ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "The value determines the desired administrative status of a virtual link or cross-connect. The up and down states indicate that the traffic flow is enabled or disabled respectively on the virtual link or cross-connect. The unknown state indicates that the state of it cannot be determined. The state will be down or unknown if the supporting ATM interface(s) is down or unknown respectively." SYNTAX INTEGER { up(1), down(2), unknown(3) } -- OBJECT-IDENTITIES: atmObjectIdentities OBJECT IDENTIFIER ::= {atmTCMIB 1} -- The following values are defined for use as -- possible values of the ATM traffic descriptor type. atmNoTrafficDescriptor OBJECT-IDENTITY STATUS deprecated DESCRIPTION "This identifies the no ATM traffic descriptor type. Parameters 1, 2, 3, 4, and 5 are not used. This traffic descriptor type can be used for best effort traffic." ::= {atmTrafficDescriptorTypes 1} atmNoClpNoScr OBJECT-IDENTITY STATUS current DESCRIPTION "Indicates the CBR.1 Conformance Definition [13] if Best Effort is No. Indicates the UBR.1 and UBR.2 Conformance Definitions [13] if Best Effort is Yes. Expires 12/26/96 [Page 9] draft ATM Textual Conventions and OBJECT-IDENTITIES 6/26/96 This traffic descriptor is for no CLP and no Sustained Cell Rate. The use of the parameter vector for this type: Parameter 1: peak cell rate in cells/second for CLP=0+1 traffic Parameter 2: CDVT in tenths of microseconds Parameter 3: not used Parameter 4: not used Parameter 5: not used. This traffic descriptor type can be used for best effort traffic." ::= {atmTrafficDescriptorTypes 2} atmClpNoTaggingNoScr OBJECT-IDENTITY STATUS deprecated DESCRIPTION "This traffic descriptor is for CLP without tagging and no Sustained Cell Rate. The use of the parameter vector for this type: Parameter 1: peak cell rate in cells/second for CLP=0+1 traffic Parameter 2: peak cell rate in cells/second for CLP=0 traffic Parameter 3: not used Parameter 4: not used Parameter 5: not used." ::= {atmTrafficDescriptorTypes 3} atmClpTaggingNoScr OBJECT-IDENTITY STATUS deprecated DESCRIPTION "This traffic descriptor is for CLP with tagging and no Sustained Cell Rate. The use of the parameter vector for this type: Parameter 1: peak cell rate in cells/second for CLP=0+1 traffic Parameter 2: peak cell rate in cells/second for CLP=0 traffic, excess tagged as CLP=1 Parameter 3: not used Parameter 4: not used Parameter 5: not used." ::= {atmTrafficDescriptorTypes 4} atmNoClpScr OBJECT-IDENTITY Expires 12/26/96 [Page 10] draft ATM Textual Conventions and OBJECT-IDENTITIES 6/26/96 STATUS current DESCRIPTION "Indicates the VBR.1 Conformance Definition [13]. This traffic descriptor is for no CLP with Sustained Cell Rate. The use of the parameter vector for this type: Parameter 1: peak cell rate in cells/second for CLP=0+1 traffic Parameter 2: sustainable cell rate in cells/second for CLP=0+1 traffic Parameter 3: maximum burst size in cells Parameter 4: CDVT in tenths of microseconds Parameter 5: not used." ::= {atmTrafficDescriptorTypes 5} atmClpNoTaggingScr OBJECT-IDENTITY STATUS current DESCRIPTION "Indicates the VBR.2 Conformance Definition [13]. This traffic descriptor is for CLP with Sustained Cell Rate and no tagging. The use of the parameter vector for this type: Parameter 1: peak cell rate in cells/second for CLP=0+1 traffic Parameter 2: sustainable cell rate in cells/second for CLP=0 traffic Parameter 3: maximum burst size in cells Parameter 4: CDVT in tenths of microseconds Parameter 5: not used." ::= {atmTrafficDescriptorTypes 6} atmClpTaggingScr OBJECT-IDENTITY STATUS current DESCRIPTION "Indicates the VBR.3 Conformance Definition [13]. This traffic descriptor is for CLP with tagging and Sustained Cell Rate. The use of the parameter vector for this type: Parameter 1: peak cell rate in cells/second for CLP=0+1 traffic Parameter 2: sustainable cell rate in cells/second for CLP=0 traffic, excess tagged as CLP=1 Parameter 3: maximum burst size in cells Parameter 4: CDVT in tenths of microseconds Expires 12/26/96 [Page 11] draft ATM Textual Conventions and OBJECT-IDENTITIES 6/26/96 Parameter 5: not used." ::= {atmTrafficDescriptorTypes 7} atmClpNoTaggingMCR OBJECT-IDENTITY STATUS current DESCRIPTION "Indicates the ABR Conformance Definition [13]. The use of the parameter vector for this type: Parameter 1: Peak Cell Rate (PCR) Parameter 2: CDVT (PCR) Parameter 3: Minimum Cell Rate (MCR) Parameter 4: unused Parameter 5: unused." ::= {atmTrafficDescriptorTypes 8} END Expires 12/26/96 [Page 12] draft ATM Textual Conventions and OBJECT-IDENTITIES 6/26/96 4. Acknowledgments This document is a product of the AToMMIB Working Group. Expires 12/26/96 [Page 13] draft ATM Textual Conventions and OBJECT-IDENTITIES 6/26/96 5. References [1] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Textual Conventions for Version 2 of the Simple Network Management Protocol (SNMPv2)", RFC1903, SNMP Research,Inc., Cisco Systems, Inc., Dover Beach Consulting, Inc., International Network Services, January 1996. [2] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Structure of Management Information for Version 2 of the Simple Network Management Protocol (SNMPv2)", RFC1902, SNMP Research,Inc., Cisco Systems, Inc., Dover Beach Consulting, Inc., International Network Services, January 1996. [3] ATM Forum, "ATM User-Network Interface, Version 3.0 (UNI 3.0) Specification", 1994. [4] ATM Forum, "ATM User-Network Interface, Version 3.1 (UNI 3.1) Specification", November 1994. [5] ITU-T Recommendation Q.2931, "Broadband Integrated Service Digital Network (B-ISDN) Digital Subscriber Signalling System No.2 (DSS2) User-Network Interface (UNI) Layer 3 Specification for Basic Call/Connection Control", September 1994. [6] ATM Forum, "Private Network-Network Interface Specification Version 1.0 (P-NNI 1.0)", af-pnni-0055.000, March 1996. [7] ATM Forum, "ATM User-Network Interface Signalling Specification, Version 4.0 (UNI 4.0)", af-sig-0061.000, June 1996. [8] ITU-T Draft Recommendation Q.2961, "Broadband Integrated Service Digital Network (B-ISDN) Digital Subscriber Signalling System No.2 (DSS2) Support of Additional Traffic Parameters", May 1995. [9] ITU-T Draft Recommendation Q.2971, "Broadband Integrated Service Digital Network (B-ISDN) Digital Subscriber Signalling System No.2 (DSS2) User Network Interface Layer 3 Specification for Point-to-multipoint Expires 12/26/96 [Page 14] draft ATM Textual Conventions and OBJECT-IDENTITIES 6/26/96 Call/connection Control", May 1995. [10] ATM Forum, "Interim Inter-switch Signaling Protocol (IISP)Specification, Version 1.0", af-pnni-0026.000, December 1994. [11] ATM Forum, "B-ICI Specification, Version 2.0", af-bici- 0013.002, November 1995. [12] ATM Forum, "Integrated Local Management Interface Specification, Version 4.0", af-ilmi-0065.000, July 1996. [13] ATM Forum, "Traffic Management Specification, Version 4.0", af-tm-0056.000, June 1996. Expires 12/26/96 [Page 15] draft ATM Textual Conventions and OBJECT-IDENTITIES 6/26/96 6. Security Considerations Security issues are not discussed in this memo. 7. Authors' Addresses Michael Noto Bell Communications Research Room 1E-348 331 Newman Springs Road P.O. Box 7020 Red Bank, NJ 07701-7020 Phone: (908) 758-5104 EMail: noto@cc.bellcore.com Kaj Tesink Bell Communications Research Room 1A-427 331 Newman Springs Road P.O. Box 7020 Red Bank, NJ 07701-7020 Phone: (908) 758-5254 EMail: kaj@cc.bellcore.com Expires 12/26/96 [Page 16] draft ATM Textual Conventions and OBJECT-IDENTITIES 6/26/96 Table of Contents 1 Status of this Memo ................................... 1 2 Introduction .......................................... 2 3 Definitions ........................................... 3 4 Acknowledgments ....................................... 13 5 References ............................................ 14 6 Security Considerations ............................... 16 7 Authors' Addresses .................................... 16 Expires 12/26/96 [Page 17]