Definitions of Textual Convention and OBJECT-IDENTITY Objects
                                for ATM Management
          
                                  March 1st 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 Convention and OBJECT-IDENTITY Objects3/1/96
          
          
          2.  Introduction
          
          This memo describes Textual Conventions and OBJECT-IDENTITY
          objects 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 RFC1443[1].  It is the purpose of
          this document to define the set of textual conventions
          available to ATM MIB modules. OBJECT-IDENTITY objects (e.g.,
          ATM Traffic Descriptor Types) are also defined to be used by
          ATM Devices.
          
          This memo does not specify a standard for the Internet
          community.
          
          
          
          
          
          
          
          
          
          
          
          
          
          
          
          
          
          
          
          
          
          
          
          
          
          
          
          
          
          Expires XX                                            [Page 2]


          draft ATM Textual Convention and OBJECT-IDENTITY Objects3/1/96
          
          
          3.  Definitions
          
               ATMTC-MIB DEFINITIONS ::= BEGIN
          
               IMPORTS
                  MODULE-IDENTITY, OBJECT-IDENTITY,
                  Integer32, experimental
                      FROM SNMPv2-SMI
                  TEXTUAL-CONVENTION
                      FROM SNMPv2-TC;
          
          
               atmTCMIB MODULE-IDENTITY
                    LAST-UPDATED "9602231200Z"
                    ORGANIZATION "IETF AToMMIB Working Group"
                    CONTACT-INFO
                      "          Michael Noto
                        Postal:  Bell Communications Research
                                 331 Newman Springs Road
                                 Red Bank, NJ 07701
                                 US
                        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
                                 US
                        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."
                    ::= { experimental XX }
          
               atmTCMIBObjects   OBJECT IDENTIFIER ::= {atmTCMIB 1}
          
               -- This MIB Module contains the following
               -- Textual Conventions:
          
                   IfIndex ::= TEXTUAL-CONVENTION
          
          
          
          
          
          Expires XX                                            [Page 3]


          draft ATM Textual Convention and OBJECT-IDENTITY Objects3/1/96
          
          
                       STATUS  current
                       DESCRIPTION
                           "The value of this object identifies the
                           interface for which the entry contains
                           management information. The value of this
                           object for a particular interface has the
                           same value as the ifIndex object, defined in
                           RFC 1213 [2], for the same interface."
                      SYNTAX  Integer32
          
                  InterfaceIndex ::= TEXTUAL-CONVENTION
                      STATUS  current
                      DESCRIPTION
                          "The value of this object identifies the
                          atmLogicalPort interface for which the entry
                          contains management information. The value of
                          this object for a particular interface has the
                          same value as the ifIndex object, defined in
                          RFC 1213 [2], for the same atmLogicalPort
                          interface."
                     SYNTAX  Integer32
          
                 AtmAddr ::= TEXTUAL-CONVENTION
                     STATUS  current
                     DESCRIPTION
                         "The ATM address used by the network entity.
                         The address types are: no address (0 octets),
                         E.164 (8 octets), network prefix (13 octets),
                         and NSAP (20 octets).  Note: The E.164 address
                         is encoded in BCD format."
                    SYNTAX    OCTET STRING (SIZE(0|8|13|20))
          
                AtmSigDescrParamIndex ::= TEXTUAL-CONVENTION
                    STATUS  current
                    DESCRIPTION
                        "The value of this object identifies a row in
                        the atmSigDescrParamTable. "
                   SYNTAX  Integer32
          
               AtmTrafficDescrParamIndex ::= TEXTUAL-CONVENTION
                   STATUS  current
                   DESCRIPTION
                       "The value of this object identifies a row in the
                       atmTrafficDescrParamTable. The value 0 signifies
                       that no row has been identified."
          
          
          
          
          
          Expires XX                                            [Page 4]


          draft ATM Textual Convention and OBJECT-IDENTITY Objects3/1/96
          
          
                  SYNTAX  Integer32
          
          
          -- This MIB Module contains the following
          -- OBJECT-IDENTITY objects:
          
              atmTrafficDescriptorTypes OBJECT IDENTIFIER ::=
                                           {atmTCMIBObjects 1}
          
          -- The following values are defined for use as
          -- possible values of the ATM traffic descriptor type.
          
              atmNoTrafficDescriptor  OBJECT-IDENTITY
                  STATUS  current
                  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
                      "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 (PCR)
                      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  current
                  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
          
          
          
          
          
          Expires XX                                            [Page 5]


          draft ATM Textual Convention and OBJECT-IDENTITY Objects3/1/96
          
          
                      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  current
                  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
                  STATUS  current
                  DESCRIPTION
                      "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 (PCR)
                      Parameter 5: CDVT (SCR)."
                  ::= {atmTrafficDescriptorTypes 5}
          
              atmClpNoTaggingScr  OBJECT-IDENTITY
                  STATUS  current
                  DESCRIPTION
                      "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
          
          
          
          
          
          Expires XX                                            [Page 6]


          draft ATM Textual Convention and OBJECT-IDENTITY Objects3/1/96
          
          
                                   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 (PCR)
                      Parameter 5: CDVT (SCR)."
                  ::= {atmTrafficDescriptorTypes 6}
          
              atmClpTaggingScr  OBJECT-IDENTITY
                  STATUS  current
                  DESCRIPTION
                      "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 (PCR)
                      Parameter 5: CDVT (SCR)."
                  ::= {atmTrafficDescriptorTypes 7}
          
              atmClpNoTaggingMCR  OBJECT-IDENTITY
                  STATUS  current
                  DESCRIPTION
                      "This traffic descriptor is used for
                      Available Bit Rate (ABR) traffic.  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 XX                                            [Page 7]


          draft ATM Textual Convention and OBJECT-IDENTITY Objects3/1/96
          
          
          4.  Acknowledgments
          
          This document is a product of the AToMMIB Working Group.
          
          
          
          
          
          
          
          
          
          
          
          
          
          
          
          
          
          
          
          
          
          
          
          
          
          
          
          
          
          
          
          
          
          
          
          
          
          
          
          
          
          
          
          
          
          
          
          Expires XX                                            [Page 8]


          draft ATM Textual Convention and OBJECT-IDENTITY Objects3/1/96
          
          
          5.  References
          
          [1]  Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
               "Textual Conventions for SNMPv2", RFC1443, SNMP
               Research,Inc., Hughes LAN Systems, Dover Beach
               Consulting, Inc., Carnegie Mellon University, April 1993.
          
          [2]  McCloghrie, K., and M. Rose, Editors, "Management
               Information Base for Network Management of TCP/IP-based
               internets: MIB-II", STD 17, RFC 1213, Hughes LAN Systems,
               Performance Systems International, March 1991.
          
          
          
          
          
          
          
          
          
          
          
          
          
          
          
          
          
          
          
          
          
          
          
          
          
          
          
          
          
          
          
          
          
          
          
          
          
          
          
          Expires XX                                            [Page 9]


          draft ATM Textual Convention and OBJECT-IDENTITY Objects3/1/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 XX                                           [Page 10]


          draft ATM Textual Convention and OBJECT-IDENTITY Objects3/1/96
          
          
          Table of Contents
          
          
          1 Status of this Memo ...................................    1
          2 Introduction ..........................................    2
          3 Definitions ...........................................    3
          4 Acknowledgments .......................................    8
          5 References ............................................    9
          6 Security Considerations ...............................   10
          7 Authors' Addresses ....................................   10
          
          
          
          
          
          
          
          
          
          
          
          
          
          
          
          
          
          
          
          
          
          
          
          
          
          
          
          
          
          
          
          
          
          
          
          
          
          
          
          
          Expires XX                                           [Page 11]