Network Working Group                               Cheenu Srinivasan
Internet Draft                                 Tachion Network Technologies Networks, Inc.
Expires: December 1999 August 2000
                                                     Arun Viswanathan
                                                  Lucent Technologies
                                                     Force10 Networks

                                                     Thomas D. Nadeau
                                                  Cisco Systems, Inc.

  MPLS Label Switch Router Management Information Base Using SMIv2

                   draft-ietf-mpls-lsr-mib-00.txt

                   draft-ietf-mpls-lsr-mib-01.txt

Status of this Memo

   This document is an Internet-Draft and is in full conformance with
   all provisions of Section 10 of RFC2026. RFC 2026.

   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 "work
   in progress."

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/ietf/1id-abstracts.txt.

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html.

Abstract

   This memo defines an experimental portion of the Management
   Information Base  (MIB) for use with network management protocols
   in the Internet community.  In particular, it describes managed
   objects for modeling  an a Multi-Protocol Label Switching (MPLS)
   [MPLSArch, MPLSFW] Label Switch Router (LSR).

Open Issues

   -  Does mplsTSpecTable belong in this document?
   -  Support

   Still waiting for signalled COS value.

   -  Do  we  need  objects to keep track of ownership of entries  in
      various tables?

   -  More descriptive text and detailed example.

   -  Reconcile  mplsInterfaceConfTable with  the  interface  related
      objects   in  the  LDP  MIB  [LDPMIB]  including  objects new IANA ifType for
      negotiated label ranges.

   -  Address multipath related issues.

   -  Introduce  a  scalar  to indicate the maximum  supported  label
      stack depth.

   -  For   each MPLS  capable  interface,  we  need   objects   in
      mplsInterfaceConfTable that indicate the resource  availability
      for  MPLS,  such  as total bandwidth, available  bandwidth  for
      each priority level, available buffer etc.

   -  Fragmentation counter in mplsInterfacePerfTable. interface layer.

1. Introduction
   This memo defines an experimental portion of the Management
   Information Base (MIB) for use with network management protocols
   in the Internet community. In particular, it describes managed
   objects for modeling  an a Multi-Protocol Label Switching (MPLS)
   [MPLSArch, MPLSFW] Label Switch Router (LSR).

   Comments should be made directly to the MPLS mailing list at
   mpls@uu.net.

   This memo does not, in its draft form, specify a standard for the
   Internet community.

2. Terminology

   This document uses terminology from the document describing the
   MPLS architecture document [MPLSArch]. A label switched path (LSP) is modelled
   modeled as a connection consisting of one or more in-segments incoming
   segments (in-segments) and/or one or more out-segments outgoing segments (out-
   segments) at a label switch router (LSR). The binding association or
   interconnection between of the in-segments and out-segments in performed is
   accomplished by using a cross-connect. We use the  terms connection terminology
   "connection" and LSP "LSP" interchangeably where the meaning is clear
   from the context.

3. The SNMP Management Framework

   The SNMP Management Framework presently consists of five major
   components:

   -  An overall architecture, described in RFC 2271 [SNMPArch].

   -  Mechanisms for describing and naming objects and events for the
      purpose of management.  The first version of this Structure of
      Management Information (SMI) is called SMIv1 and described in
      RFC 1155 [SMIv1], RFC 1212 [SNMPv1MIBDef] and RFC 1215
      [SNMPv1Traps].  The second version, called SMIv2, is described
      in RFC 1902 [SMIv2], RFC 1903 [SNMPv2TC] and RFC 1904
      [SNMPv2Conf].

   -  Message protocols for transferring management information.  The
      first version of the SNMP message protocol is called SNMPv1
      and described in RFC 1157 [SNMPv1].  A second version of the
      SNMP message protocol, which is not an Internet standards
      track protocol, is called SNMPv2c and described in RFC 1901
      [SNMPv2c] and RFC 1906 [SNMPv2TM].  The third version of the
      message protocol is called SNMPv3 and described in RFC 1906
      [SNMPv2TM], RFC 2272 [SNMPv3MP] and RFC 2274 2574 [SNMPv3USM].

   -  Protocol operations for accessing management information.  The
      first set of protocol operations and associated PDU formats is
      described in RFC 1157 [SNMPv1].  A second set of protocol
      operations and associated PDU formats is described in RFC 1905
      [SNMPv2PO].

   -  A set of fundamental applications described in RFC 2273
      [SNMPv3App] and the view-based access control mechanism
      described in RFC  2275 2575 [SNMPv3VACM].

   Managed objects are accessed via a virtual information store,
   termed the Management Information Base or MIB.  Objects in the MIB
   are defined using the mechanisms defined in the SMI.  This memo
   specifies a MIB module that is compliant to the SMIv2.  A MIB
   conforming to the SMIv1 can be produced through the appropriate
   translations.  The resulting translated MIB must be semantically
   equivalent, except where objects or events are omitted because no
   translation is possible (use of Counter64).  Some  machine  readable machine-readable
   information in SMIv2 will be converted into textual descriptions
   in SMIv1 during the translation process.  However, this loss of machine readable
   machine-readable information is not considered to change the
   semantics of the MIB.

3.1.  Object Definitions

   Managed objects are accessed via a virtual information store,
   termed the Management Information Base or MIB.  Objects in the MIB
   are defined using the subset of Abstract Syntax Notation One
   (ASN.1) defined in the SMI.  In particular, each object type is
   named by an OBJECT IDENTIFIER, an administratively assigned name.
   The object type together with an object instance serves to
   uniquely identify a specific instantiation of the object.  For
   human convenience, we often use a textual string, termed the
   descriptor, to also refer to the object type.

4. Feature Checklist

   The MPLS label switch router (LSR) MIB (LSR-MIB) is designed to satisfy
   the following requirements and constraints. constraints:

   -  The MIB should be able to support both manually configured LSPs
      as well as those configured via LDP CR-LDP and/or RSVP signaling.

   -  The MIB must support the enabling and disabling of MPLS
      capability on MPLS capable interfaces of an LSR.

   -  The MIB should allow resource sharing between two or more LSPs.

   -  Both per-platform and per-interface label spaces must be
      supported.

   -  MPLS packets must be forwarded solely based on an incoming top
      label [MPLSArch, LblStk].

   -  Support must be provided for next-hop resolution when the
      outgoing interface is a shared media interface.  In the point-
      to-multipoint case, each outgoing segment can  be reside on a
      different shared media interface.

   -  The MIB must support point-to-point, point-to-multipoint and
      multipoint-to-point connections at an LSR.

   -  For multipoint-to-point connections all the outgoing packets must
      have the same top label.

   -  For multipoint-to-point connections connections, the outgoing resources of
      the merged connections must be shared.

   -  For multipoint-to-point connections, packets from different
      incoming connections may have distinct outgoing label  stacks, stacks
      beneath the (identical) top label.

   -  In the point-to-multipoint case each outgoing connection can
      have a distinct label stack including the top label.

   -  In  All the members of a point-to-multipoint connection share the ingress
      resources  are
      shared by all the members of allocated for the connection. ingress segments.

   -  The MIB must provide cross-connect capability to "pop" an
      incoming label and forward the packet with the  rest remainder of
      the label stack unchanged and without pushing any labels ("pop-and-
      go") ("pop-
      and-go") [LblStk].

   -  It must be possible to assign or remap COS re-map the Class of Service
      (COS) bits [LblStk] on the outgoing label. In the multipoint-to-point multipoint-
      to-point case, each  in-
      segment in-segment can have a different outgoing
      COS value.  In the point-
      to-multipoint point-to-multipoint case, each out-segment
      can have a different outgoing COS value.

   -  It should be possible to support persistent as well as non-
      persistent LSPs.

   -  Performance counters must be provided for in-segments and out-
      segments as well as for measuring MPLS performance on a per-
      interface basis.

5. Outline
   Configuring LSPs through an LSR involves the following steps. steps:

   -  Enabling MPLS on MPLS capable interfaces.

   -  Configuring in in-segments and out segments. out-segments.

   -  Setting up the cross-connect table to switch between associate segments and/or
      to indicate connection origination and termination.

   -  (Optionally)  Optionally specifying label stack actions.

   -  (Optionally)  Optionally specifying segment traffic parameters.

5.1.  Summary of LSR MIB

   The MIB objects for performing these actions consist of the
   following tables. tables:

   -  Interface  The interface configuration table  (mplsInterfaceConfTable) (mplsInterfaceConfTable),
      which is used for enabling the MPLS protocol on MPLS capable MPLS-capable
      interfaces.

   -  In-segment  The in-segment (mplsInSegmentTable) and out-segment
      (mplsOutSegmentTable) tables tables, which are used for configuring
      LSP segments at an LSR.

   -  Cross-connect  The cross-connect table  (mplsXCTable) for creating  relationships
      between (mplsXCTable), which is used to
      associate in and out segments constituting together, in order to form a
      cross-connect.

   -  Label  The label stack table (mplsLabelStackTable) (mplsLabelStackTable), which is used for
      specifying label stack operations.

   -  The TSpec table  (mplsTSpecTable) (mplsTSpecTable), which is used for specifying  LSP   related
      LSP-related traffic parameters.

   Further, the MPLS in-segment and out-segment performance tables,
   mplsInSegmentPerfTable and mplsOutSegmentPerfTable, contain the
   objects necessary to measure the performance of LSPs, and
   mplsInterfacePerfTable has objects to measure MPLS performance on
   a per-interface basis.

   These tables are described in the subsequent sections.

6. Brief Description of MIB Objects

   Sections  6.1-6.2 6.1-6.3 describe objects pertaining to MPLS capable
   interfaces of an LSR. The objects described in Sections  6.3-6.8, 6.4-6.9,
   when considered together, are equivalent to the tables described
   in the MPLS architecture document [MPLSArch], that is, the
   Incoming Label Map (ILM) and the Next Hop Label Forwarding Entry
   (NHLFE) tables. Section  6.9 6.10 describes objects for specifying
   traffic parameters for in and out segments.

6.1.  mplsInterfaceConfTable

   This table represents the interfaces that are MPLS capable.  An
   LSR creates an entry in this table for every MPLS capable
   interface on that LSR.  Each entry contains information about per-
   interface label ranges.  The administrator can specify the desired
   MPLS status (enable/up, disable/down, testing) of an interface by
   writing the object mplsInterfaceAdminStatus.  The actual status is
   indicated by the object mplsInterfaceOperStatus.

6.2.  mplsInterfaceResTable

   This table provides resource information such as available and
   allocated bandwidth and buffers on each MPLS capable interface for
   each priority level.

6.3.  mplsInterfacePerfTable

   This table contains objects to measure the MPLS performance of
   MPLS capable interfaces and is an AUGMENT to
   mplsInterfaceConfTable.  High capacity counters are provided for
   objects that are likely to wrap around quickly on high-speed
   interfaces.

6.3.

6.4.  mplsInSegmentTable

   This table contains a description of the incoming MPLS segments to
   an LSR and their associated parameters.

6.4.

6.5.  mplsInSegmentPerfTable

   The MPLS In-Segment Performance Table has objects to measure the
   performance of an incoming segment configured on an LSR.  It is an
   AUGMENT to mplsInSegmentTable.  High capacity counters are
   provided for objects that are likely to wrap around quickly on
   high-speed interfaces.

6.5.

6.6.  mplsOutSegmentTable

   The Out-Segment Table contains a description of the outgoing MPLS
   segments at an LSR and their associated parameters.

6.6.

6.7.  mplsOutSegmentPerfTable

   The MPLS Out-Segment Table contains objects to measure the
   performance of an outgoing segment configured on an LSR.  It is an
   AUGMENT to mplsOutSegmentTable.  High capacity counters are
   provided for objects that are likely to wrap around quickly on
   high-speed interfaces.

6.7.

6.8.  mplsXCTable

   The mplsXCTable specifies information for switching associating segments
   together in order to instruct the LSR to switch between the
   specified segments.  It supports point-to-point, point-to-multipoint and multipoint-to- point-to-multi-
   point and multi-point-to-point connections.

6.8.

6.9.  mplsLabelStackTable

   The mplsLabelStackTable specifies the label stack to be pushed
   onto a packet, beneath the top label.  Entries to this table are
   referred to from mplsXCTable.

6.9.

6.10. mplsTSpecTable

   The mplsTSpecTable contains objects for specifying the traffic
   parameters of  in in-segments and out segments. out-segments. Entries in this table
   are referred to from mplsInSegmentTable and mplsOutSegmentTable.

7. Specifying the Segments Example of an LSR

   Suppose  that LSP Setup

   In this section we  want  to  manually  create provide a  best-effort  bi-
   directional LSP, consisting brief example of using the MIB
   objects described in Section 8 to set up an in-segment and an out-segment on LSP. While this
   example is not meant to illustrate every nuance of the MIB, it is
   intended as an aid to understanding some of the key concepts. It
   is meant to be read after going through the MIB itself.

   Suppose that one would like to manually create a best-effort,
   unidirectional LSP. Assume that the LSP enters the LSR (with no via MPLS
   interface A with ifIndex 12 and exits the LSR via MPLS interface B
   with ifIndex 13. Let us assume that we do not wish to have a label
   stack beneath the top label on the outgoing labeled  packets). packets.  The
   following example illustrates which rows and corresponding objects
   need to
   might be created to do accomplish this.

   First, the TSpec entries must be set-up for both segments.

   In mplsTSpecTable for the incoming direction:
   {
      mplsTSpecIndex           = 5
      mplsTSpecDirection       = in(1),
      mplsTSpecMaxRate         = 100000,
      mplsTSpecMeanRate        = 100000,
      mplsTSpecMaxBurstSize    = 2000,
      mplsTSpecRowStatus       = createAndGo(4)
   }

   In mplsTSpecTable for the outgoing direction:
   {
      mplsTSpecIndex           = 6
      mplsTSpecDirection       = out(2),
      mplsTSpecMaxRate         = 100000,
      mplsTSpecMeanRate        = 100000,
      mplsTSpecMaxBurstSize    = 2000,
      mplsTSpecRowStatus       = createAndGo(4)

   }

   Note that if we were setting up a bi-directional LSP, the segments
   in the reverse direction can share the TSpec entries (and hence
   resources) with the segments in the forward direction.

   We must next create the appropriate in-segment and the out-segment are created
   entries with suitable traffic parameters by pointing to the
   appropriate traffic parameters. TSpec entries that we have just created.

   In mplsInSegmentTable:
   {
      mplsInSegmentIfIndex     = i1, 12, -- incoming interface
      mplsInSegmentLabel       = l1, 21, -- incoming label
      mplsInSegmentNPop        = 1,
      mplsInSegmentTSpecIndex  = 0, 5,
      mplsInSegmentRowStatus   = createAndGo(3) createAndGo(4)
   }

   In mplsOutSegmentTable:
   {
      mplsOutSegmentIndex          = o, 1,
      mplsOutSegmentIfIndex        = i2, 13, -- outgoing interface
      mplsOutSegmentPushTopLabel   = true(1),
      mplsOutSegmentTopLabel       = l2, 22, -- outgoing label
      mplsOutSegmentTSpecIndex     = 0, 6,
      mplsOutSegmentRowStatus      = createAndGo(3) createAndGo(4)
   }

   Next, two a cross-connect entries entry is created thereby associating these two segments by
   sharing the same mplsXCIndex are created.
   newly created segments together.

   In mplsXCTable, for the in-segment: mplsXCTable:
   {
      mplsXCIndex             = x, 2,
      mplsXCLspId             = "1.2.3.4-2",
      mplsInSegmentIfIndex    = i1, 12,
      mplsInSegmentLabel      = l1, 21,
      mplsOutSegmentIndex     = 0,
      mplsLabelStackIndex = 0,
      mplsXCRowStatus = createAndGo(3)
   }

   In mplsXCTable, for the out-segment:
   {
      mplsXCIndex = x,
      mplsInSegmentIfIndex = 0,
      mplsInSegmentLabel 1,
      mplsXCCOS               = 0,
      mplsOutSegmentIndex
      mplsXCIsPersistent      = o,
      mplsXCLabelStackIndex false (1),
      mplsLabelStackIndex     = 0, -- only a single outgoing label
      mplsXCRowStatus         = createAndGo(3) createAndGo(4)
   }

   Note that the     objects mplsInSegmentXCIndex and mplsOutSegmentXCIndex
   objects will automatically get be populated with the value   "x" 2 when
   these segments are referred to from the
   corresponding cross-connect entries.

8. corresponding cross-
   connect entry.

8. Application of the Interface Group to MPLS

   The Interfaces Group of MIB II defines generic managed objects for
   managing interfaces.  This memo contains the media-specific
   extensions to the Interfaces Group for managing MPLS interfaces.

   This memo assumes the interpretation of the Interfaces Group to be
   in accordance with [IFMIB] which states that the interfaces table
   (ifTable) contains information on the managed resource's
   interfaces and that each sub-layer below the internetwork layer of
   a network interface is considered an interface.  Thus, the MPLS
   layer interface is represented as an entry in the ifTable.  This
   entry is concerned with the MPLS layer as a whole, and not with
   individual LSPs/tunnels which are managed via the MPLS-specific
   managed objects specified in this memo and [TEMIB].  The inter-
   relation of entries in the ifTable is defined by Interfaces Stack
   Group defined in [IFMIB].

8.1.  Support of the MPLS Layer by ifTable

   Some specific interpretations of ifTable for the MPLS layer
   follow.

   Object        Use for the MPLS layer

   ifIndex       Each MPLS interface is represented by an ifEntry.

   ifDescr       Description of the MPLS interface.

   ifType        The value that is allocated for MPLS is <TBD>.

   ifSpeed       The total bandwidth in bits per second for use by
                 the MPLS layer.

   ifPhysAddress Unused.

   ifAdminStatus See [IFMIB].

   ifOperStatus  Assumes the value down(2) if the MPLS layer is
                 down.

   ifLastChange  See [IFMIB].

   ifInOctets    The number of received octets over the interface,
                 i.e., the number of received, octets received as
                 labeled packets.

   ifOutOctets   The number of transmitted octets over the
                 interface, i.e., the number of octets transmitted
                 as labeled packets.

   ifInErrors    The number of labeled packets dropped due to
                 uncorrectable errors.

   ifInUnknownProtos
                 The number of received packets discarded during
                 packet header validation, including packets with
                 unrecognized label values.

   ifOutErrors   See [IFMIB].

   ifName        Textual name (unique on this system) of the
                 interface or an octet string of zero length.

   ifLinkUpDownTrapEnable
                 Default is disabled (2).

   ifConnectorPresent
                 Set to false (2).

   ifHighSpeed   See [IFMIB].

   ifHCInOctets  The 64-bit version of ifInOctets; supported if
                 required by the compliance statements in [IFMIB].

   ifHCOutOctets The 64-bit version of ifOutOctets; supported if
                 required by the compliance statements in [IFMIB].

   ifAlias       The non-volatile 'alias' name for the interface as
                 specified by a network manager.

9. MPLS Label Switch Router MIB Definitions

MPLS-LSR-MIB DEFINITIONS ::= BEGIN

IMPORTS
   MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE,
   experimental, Integer32, Unsigned32, Counter32,
   Counter64, Gauge32, IpAddress
      FROM SNMPv2-SMI
   MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
      FROM SNMPv2-CONF
   TEXTUAL-CONVENTION, TruthValue, RowStatus
      FROM SNMPv2-TC
   ifIndex, InterfaceIndex, InterfaceIndexOrZero
      FROM IF-MIB
   BitRate, BurstSize
      FROM INTEGRATED-SERVICES-MIB; IF-MIB;

mplsLsrMIB MODULE-IDENTITY
   LAST-UPDATED "9906161200Z" "200002161200Z"  -- 16 June 1999 February 2000 12:00:00 EST
   ORGANIZATION "Multiprotocol Label Switching (MPLS) Working Group"
   CONTACT-INFO
       "        Cheenu Srinivasan
        Postal: Tachion Network Technologies Networks, Inc.
                2 Meridian Road
                Eatontown, NJ 07724 0772
        Tel:    +1 732 542 7750 x234
        Email:  cheenu@tachion.com

                Arun Viswanathan
        Postal: Lucent Technologies
             4D537, 101 Crawfords Corner Road
             Holmdel, NJ 07733 Force10 Networks
                1440 McCarthy Blvd
                Milpitas, CA 95035
        Tel:    +1 732 332 5163    +1-408-571-3516
        Email:  arun@force10networks.com

                Thomas D. Nadeau
        Postal: Cisco Systems, Inc.
                250 Apollo Drive
                Chelmsford, MA 01824
        Tel:    +1-978-244-3051
        Email:  arunv@lucent.com"  tnadeau@cisco.com"
   DESCRIPTION
       "Proposed
       "This MIB  module contains managed object definitions for MPLS the
        Multiprotocol Label Switch  Router.
        See: Switching (MPLS) Router as
        defined in: Rosen, E., Viswanathan, A., and R.
        Callon, Multiprotocol Label Switching Architecture,
        Internet Draft <draft-ietf-mpls-arch-05.txt>, <draft-ietf-mpls-arch-06.txt>,
        February 2000."

   -- Revision history.
   REVISION
       "199907161200Z"  -- 16 July 1999 12:00:00 EST
   DESCRIPTION
      "Initial draft version."
   REVISION
       "200002161200Z"  -- 16 February 1999." 2000 12:00:00 EST
   DESCRIPTION
       "Second draft version."

   ::= { experimental 96 }

-- Textual Conventions.

MplsLSPID ::= TEXTUAL-CONVENTION
   STATUS        current
   DESCRIPTION
       "An identifier that is assigned to each LSP and is
        used to uniquely identify it. This is assigned at
        the head end of the LSP and can be used by all LSRs
        to identify this LSP. This value is piggybacked by
        the signaling protocol when this LSP is signaled
        within the network. This identifier can then be used
        at each LSR to identify which labels are being
        swapped to other labels for this LSP. For IPv4
        addresses this results in a 6-octet long cookie."
   SYNTAX        OCTET STRING (SIZE (0..63))

MplsLsrIANAAddrFamily ::= TEXTUAL-CONVENTION
   STATUS        current
   DESCRIPTION
       "An address family.  Values  These values are defined in RFC
        1700 -
        Assigned Numbers. and are maintained by The IANA.  All values may
        not be relevant in all contexts when used in this
        MIB, but are included for completeness."
   REFERENCE
       "RFC 1700 - Assigned Numbers, Reynolds Reynolds, J. and J.
        Postel, Oct. 1994"
   SYNTAX        INTEGER {
                   other(0),
                    ipv4(1),
                    ipv6(2),
                    nsap(3),
                    hdlc(4),
                    bbn1822(5),
                    ieee802(6),
                    e163(7),
                    e164(8),
                    f69(9),
                    x121(10),
                    ipx(11),
                    appleTalk(12),
                    decnetIV(13),
                    banyanVines(14),
                    e164WithNsap(15)
                }

-- An MPLS label.
MplsLabel ::= TEXTUAL-CONVENTION
   STATUS        current
   DESCRIPTION
       "Represents an MPLS label.  Note that the contents of
        a label field are interpreted in an interface-type
        specific fashion.  For example, the 20-bit wide
        label carried in the MPLS shim header is 20 contained
        in bits wide 0-19 and the top  12 bits 20-31 must be zero.  The frame
        relay label can be either 10, 17 or 23 bits wide
        depending on the size of the DLCI field size and the top 22, 15, or 9 bits 10-
        31, 17-31 or 23-31 must be zero, respectively.  For
        an ATM interface,
        the  lowermost 16 bits are 0-15 must be interpreted as
        the VCI,
        the  next  8 bits 16-23 as the VPI and the remaining bits 24-31 must
        be zero.   Also  note  Note that the permissible label values are
        also a function of the interface type.  For example,
        the value 3 has special semantics in the control
        plane for an MPLS shim header label and is not a
        valid label value in the datapath." data path."
   REFERENCE
       "1. MPLS Label Stack Encoding, Rosen et al, draft-
        ietf-mpls-label-encaps-04.txt, April 1999.
        ietf-mpls-label-encaps-07.txt, March 2000.
        2. Use of Label Switching on Frame Relay Networks,
        Conta et al, draft-ietf-mpls-fr-03.txt, Nov. 1998."
   SYNTAX Integer32

Ipv6Address ::= TEXTUAL-CONVENTION
   STATUS      current
   DESCRIPTION
       "IPv6 address."
   SYNTAX      OCTET STRING (SIZE(16))

BitRate ::= TEXTUAL-CONVENTION
   DISPLAY-HINT "d"
   STATUS      current
   DESCRIPTION
       " The rate in bits/second."
   SYNTAX      INTEGER (0..'7FFFFFFF'h)

BurstSize ::= TEXTUAL-CONVENTION
   DISPLAY-HINT "d"
   STATUS      current
   DESCRIPTION
       "The number of octets of.MPLS data that the stream
        may send without concern for policing."
   SYNTAX      INTEGER (0..'7FFFFFFF'h)

BufferSize ::= TEXTUAL-CONVENTION
   DISPLAY-HINT "d"
   STATUS      current
   DESCRIPTION
       "Size of buffer in octets of.MPLS data."
   SYNTAX      INTEGER (0..'7FFFFFFF'h)

-- Top level components of this MIB.

-- tables, scalars
mplsLsrObjects       OBJECT IDENTIFIER ::= { mplsLsrMIB 1 }
-- traps
mplsLsrNotifications OBJECT IDENTIFIER ::= { mplsLsrMIB 2 }
-- conformance
mplsLsrConformance   OBJECT IDENTIFIER ::= { mplsLsrMIB 3 }

-- MPLS Interface Configuration Table.

mplsInterfaceConfTable  OBJECT-TYPE
   SYNTAX        SEQUENCE OF MplsInterfaceConfEntry
   MAX-ACCESS    not-accessible
   STATUS        current
   DESCRIPTION
       "This table specifies per-interface MPLS capability
        and associated information."
   ::= { mplsLsrObjects 1 }

mplsInterfaceConfEntry OBJECT-TYPE
   SYNTAX        MplsInterfaceConfEntry
   MAX-ACCESS    not-accessible
   STATUS        current
       DESCRIPTION
       "An entry in this table is created by  an  LSR  for
        every  interface  capable  of  supporting  MPLS  and
        represents the label space of that interface.  A row
        with index 0 represents the global label space." table is created by an LSR for
        every interface capable of supporting MPLS."
   INDEX       { mplsInterfaceConfIndex }
      ::= { mplsInterfaceConfTable 1 }

MplsInterfaceConfEntry ::= SEQUENCE {
      mplsInterfaceConfIndex          InterfaceIndexOrZero,
      mplsInterfaceLabelMinIn         MplsLabel,
      mplsInterfaceLabelMaxIn         MplsLabel,
      mplsInterfaceLabelMinOut        MplsLabel,
      mplsInterfaceLabelMaxOut        MplsLabel,
      mplsInterfaceTotalBandwidth        BitRate,
      mplsInterfaceAvailableBandwidth    BitRate,
      mplsInterfaceTotalBuffer        BufferSize,
      mplsInterfaceAvailableBuffer    BufferSize,
      mplsInterfaceIsGlobalLabelSpace    TruthValue,
      mplsInterfaceAdminStatus        INTEGER,
      mplsInterfaceOperStatus         INTEGER
   }

mplsInterfaceConfIndex OBJECT-TYPE
   SYNTAX        InterfaceIndexOrZero
   MAX-ACCESS    read-only
   STATUS        current
   DESCRIPTION
       "Index
       "This is a unique index for  this row of an entry in the table.
        MplsInterfaceConfTable. A  value  of  0 non-zero index for an
        entry indicates the ifIndex for the corresponding
        interface entry in of the MPLS-layer in the ifTable.
        Note that the global label space may apply to
        several interfaces, and this  entry  is
        created  by therefore the configuration
        of the LSR if it supports a global label
        space.   A  non-zero  index is  also  the space interface
        index,  ifIndex,  for parameters will
        apply to all of the  corresponding  interface
        entry interfaces that are
        participating in ifTable." the global label space."
   REFERENCE
       "RFC 2233 - The Interfaces Group MIB using SMIv2,
        McCloghrie
        McCloghrie, K., and F. Kastenholtz, Nov. 1997"
   ::= { mplsInterfaceConfEntry 1 }

mplsInterfaceLabelMinIn OBJECT-TYPE
   SYNTAX        MplsLabel
   MAX-ACCESS    read-only
   STATUS        current
   DESCRIPTION
       "Minimum
       "This is the minimum value of an MPLS label that this
        LSR is willing to receive on this interface."
   ::= { mplsInterfaceConfEntry 2 }

mplsInterfaceLabelMaxIn OBJECT-TYPE
   SYNTAX        MplsLabel
   MAX-ACCESS    read-only
   STATUS        current
   DESCRIPTION
       "Maximum
       "This is the maximum value of an MPLS label that this
        LSR is willing to receive on this interface."
   ::= { mplsInterfaceConfEntry 3 }

mplsInterfaceLabelMinOut OBJECT-TYPE
   SYNTAX        MplsLabel
   MAX-ACCESS    read-only
   STATUS        current
   DESCRIPTION
       "Minimum
       "This is the minimum value of an MPLS label that this
        LSR is willing to send on this interface."
   ::= { mplsInterfaceConfEntry 4 }

mplsInterfaceLabelMaxOut OBJECT-TYPE
   SYNTAX        MplsLabel
   MAX-ACCESS    read-only
   STATUS        current
   DESCRIPTION
       "This is the maximum value of an MPLS label that this
        LSR is willing to send on this interface."
   ::= { mplsInterfaceConfEntry 4 5 }

mplsInterfaceTotalBandwidth        OBJECT-TYPE
   SYNTAX        BitRate
   MAX-ACCESS    read-only
   STATUS        current
   DESCRIPTION
       "This value indicates the total amount of usable
        bandwidth on this interface and is specified in
        kilobytes per second (Kbps/sec)."
::= { mplsInterfaceConfEntry 6 }

mplsInterfaceAvailableBandwidth       OBJECT-TYPE
   SYNTAX        BitRate
   MAX-ACCESS    read-only
   STATUS        current
   DESCRIPTION
       "This value indicates the total amount of available
        bandwidth available on this interface and is
        specified in kilobytes per second (Kbps/sec). This
        value is calculated as the difference between the
        amount of bandwidth currently in use and that
        specified in mplsInterfaceTotalBandwidth."
::= { mplsInterfaceConfEntry 7 }

mplsInterfaceTotalBuffer        OBJECT-TYPE
   SYNTAX        BufferSize
   MAX-ACCESS    read-only
   STATUS        current
   DESCRIPTION
       "This value indicates the total amount of buffer
        space allocated for this interface."
::= { mplsInterfaceConfEntry 8 }

mplsInterfaceAvailableBuffer       OBJECT-TYPE
   SYNTAX        BufferSize
   MAX-ACCESS    read-only
   STATUS        current
   DESCRIPTION
       "This value reflects the total amount of buffer space
        available on this interface."
::= { mplsInterfaceConfEntry 9 }

mplsInterfaceLabelMaxOut

mplsInterfaceIsGlobalLabelSpace    OBJECT-TYPE
   SYNTAX        MplsLabel        TruthValue
   MAX-ACCESS    read-only
   STATUS        current
   DESCRIPTION
       "Maximum
       "This value of MPLS indicates whether or not this interface
        participates in the global label that space. If this LSR is willing
        to send on
        interface participates in the platform-specific
        label space, then this interface." value will be set to false."
::= { mplsInterfaceConfEntry 5 10 }

mplsInterfaceAdminStatus OBJECT-TYPE
   SYNTAX        INTEGER {
         up(1),     -- enable MPLS on this interface
         down(2),   -- disable MPLS on this interface
         testing(3) -- in some test mode
      }
   MAX-ACCESS    read-write
   STATUS        current
   DESCRIPTION
       "Indicates
       "This variable indicates the administrator's intent
        as to whether MPLS should be  enabled enabled, disabled, or  disabled
        running in some diagnostic testing mode on this
        interface."
   DEFVAL        { down }
   ::= { mplsInterfaceConfEntry 6 11 }

mplsInterfaceOperStatus OBJECT-TYPE
   SYNTAX        INTEGER {
         up(1),          -- ready to pass packets
         down(2),
         testing(3),     -- in some test mode
         unknown(4),     -- status cannot be determined for some
                         -- reason
         dormant(5),
         notPresent(6),  -- some component is missing
         lowerLayerNotPresent(7)
         lowerLayerDown(7)
                       -- down due to the state of
                       -- lower layer interfaces
      }
   MAX-ACCESS    read-only
   STATUS        current
   DESCRIPTION
       "Indicates
       "This value reflects the actual or operational status
        of MPLS on this interface."
   ::= { mplsInterfaceConfEntry 7 12 }

-- End of mplsInterfaceConfTable

-- MPLS Interface Performance Table.

mplsInterfacePerfTable  OBJECT-TYPE
   SYNTAX        SEQUENCE OF MplsInterfacePerfEntry
   MAX-ACCESS    not-accessible
   STATUS        current
   DESCRIPTION
       "This table provides per-interface MPLS performance
        information." information on
        a per-interface basis."
   ::= { mplsLsrObjects 2 }

mplsInterfacePerfEntry OBJECT-TYPE
   SYNTAX        MplsInterfacePerfEntry
   MAX-ACCESS    not-accessible
   STATUS        current
   DESCRIPTION
       "An entry in this table is created by the LSR for
        every interface capable of supporting MPLS.  Its is
        an extension to mplsInterfaceConfEntry." the mplsInterfaceConfEntry table."
   AUGMENTS      { mplsInterfaceConfEntry }
      ::= { mplsInterfacePerfTable 1 }

MplsInterfacePerfEntry ::= SEQUENCE {
      -- incoming direction
      mplsInterfaceInLabelsUsed           Gauge32,
      mplsInterfaceInOctets               Counter32,
      mplsInterfaceInPackets              Counter32,
      mplsInterfaceInErrors               Counter32,
      mplsInterfaceInDiscards             Counter32,
      mplsInterfaceFailedLabelLookup      Counter32,

      -- outgoing direction
      mplsInterfaceOutLabelsUsed          Gauge32,
      mplsInterfaceOutOctets              Counter32,
      mplsInterfaceOutPackets             Counter32,
      mplsInterfaceOutErrors              Counter32,
      mplsInterfaceOutDiscards            Counter32,

      -- high capacity counters
      mplsInterfaceInHCOctets             Counter64,
      mplsInterfaceOutHCOctets            Counter64
      mplsInterfaceOutFragments           Counter32
   }

mplsInterfaceInLabelsUsed OBJECT-TYPE
   SYNTAX        Gauge32
   MAX-ACCESS    read-only
   STATUS        current
   DESCRIPTION
       "The
       "This value indicates the specific number of labels
        that are in use at this point in time on this
        interface in the incoming direction."
   ::= { mplsInterfacePerfEntry 1 }

mplsInterfaceInOctets OBJECT-TYPE
   SYNTAX        Counter32
   MAX-ACCESS    read-only
   STATUS        current
   DESCRIPTION
       "The  number  of  octets that have been  received  in
        labeled packets on this interface."
   ::= { mplsInterfacePerfEntry 2 }

mplsInterfaceInPackets OBJECT-TYPE
   SYNTAX        Counter32
   MAX-ACCESS    read-only
   STATUS        current
   DESCRIPTION
       "The
       "This variable reflects the number of labeled packets
        that have been received on this interface."
   ::= { mplsInterfacePerfEntry 3 }

mplsInterfaceInErrors OBJECT-TYPE
   SYNTAX        Counter32
   MAX-ACCESS    read-only
   STATUS        current
   DESCRIPTION
       "The   number  of  labeled  packets  that  have  been
        received on this interface that were errored."
   ::= { mplsInterfacePerfEntry 4 2 }

mplsInterfaceInDiscards OBJECT-TYPE
   SYNTAX        Counter32
   MAX-ACCESS    read-only
   STATUS        current
   DESCRIPTION
       "The number of inbound labeled  packets  that  have  been
        received on this interface that packets, which were discarded."
        chosen to be discarded even though no errors had
        been detected to prevent their being transmitted.
        One possible reason for discarding such a labeled
        packet could be to free up buffer space."
   ::= { mplsInterfacePerfEntry 5 3 }

mplsInterfaceFailedLabelLookup OBJECT-TYPE
   SYNTAX        Counter32
   MAX-ACCESS    read-only
   STATUS        current
   DESCRIPTION
       "The
       "This value indicates the number of labeled packets
        that have been received on this interface  that and were
        discarded because there were no matching entries   were
        found for them in mplsInSegmentTable."
   ::= { mplsInterfacePerfEntry 6 }

mplsInterfaceOutLabelsUsed OBJECT-TYPE
   SYNTAX        Gauge32
   MAX-ACCESS    read-only
   STATUS        current
   DESCRIPTION
       "The  number of labels that are in use at this  point
        on this interface in the outgoing direction."
   ::= { mplsInterfacePerfEntry 7 }

mplsInterfaceOutOctets OBJECT-TYPE
   SYNTAX        Counter32
   MAX-ACCESS    read-only
   STATUS        current
   DESCRIPTION
       "The  number of octets that have been sent as labeled
        packets on this interface."
   ::= { mplsInterfacePerfEntry 8 4 }

mplsInterfaceOutPackets

mplsInterfaceOutLabelsUsed OBJECT-TYPE
   SYNTAX        Counter32        Gauge32
   MAX-ACCESS    read-only
   STATUS        current
   DESCRIPTION
       "The
       "Indicates the number of labeled packets top-most labels in the
        outgoing label stacks that have been sent are in use at this point
        in time on this interface."
   ::= { mplsInterfacePerfEntry 9 5 }

mplsInterfaceOutErrors

mplsInterfaceOutPackets OBJECT-TYPE
   SYNTAX        Counter32
   MAX-ACCESS    read-only
   STATUS        current
   DESCRIPTION
       "The
       "This variable contains the number of labeled packets
        that could not be sent have been transmitted on this interface due to errors." interface."
   ::= { mplsInterfacePerfEntry 10 6 }

mplsInterfaceOutDiscards OBJECT-TYPE
   SYNTAX        Counter32
   MAX-ACCESS    read-only
   STATUS        current
   DESCRIPTION
       "The number of  outgoing outbound labeled  packets  on  this
        interface that had packets, which were
        chosen to be discarded due to even though no errors  or
        other conditions had
        been detected to prevent their being transmitted.
        One possible reason for discarding such as a labeled
        packet could be to free up buffer overflows." space."
   ::= { mplsInterfacePerfEntry 11 7 }

mplsInterfaceInHCOctets

mplsInterfaceOutFragments OBJECT-TYPE
   SYNTAX        Counter64        Counter32
   MAX-ACCESS    read-only
   STATUS        current
   DESCRIPTION
       "The  number  of  octets that have been  received  in
        labeled packets on this interface.  This is
       "This variable indicates the  64
        bit version of mplsInterfaceInOctets."
   ::= { mplsInterfacePerfEntry 15 }

mplsInterfaceOutHCOctets OBJECT-TYPE
   SYNTAX        Counter64
   MAX-ACCESS    read-only
   STATUS        current
   DESCRIPTION
       "The number of octets that have been sent in labeled outgoing MPLS
        packets that were fragmented before transmission on
        this interface.  This  is  the  64  bit
        version of mplsInterfaceOutOctets." interface."
::= { mplsInterfacePerfEntry 16 8 }

-- End of mplsInterfacePerfTable

-- In-segment table.

mplsInSegmentTable  OBJECT-TYPE
   SYNTAX        SEQUENCE OF MplsInSegmentEntry
   MAX-ACCESS    not-accessible
   STATUS        current
   DESCRIPTION
       "This table contains a description collection of the incoming
        segments to a an LSR."
   ::= { mplsLsrObjects 3 }

mplsInSegmentEntry  OBJECT-TYPE
   SYNTAX        MplsInSegmentEntry
   MAX-ACCESS    not-accessible
   STATUS        current
   DESCRIPTION
       "An entry in this table represents one incoming
        segment.  An entry can be created by a network
        administrator or by an SNMP agent as instructed by
        LDP
        CR-LDP or RSVP.   It  The creator of the entry is denoted
        by mplsInSegmentOwner. An entry in this table is
        indexed by the ifIndex of the incoming interface index and
        the (top) label.  Note that some  of
        the segments are
        associated with a tunnel, so the traffic parameters
        of these rows are supported as read-only objects and
        their modification can be done only via the tunnel
        table, mplsTunnelTable.  This
        issue   will   be  addressed  more  naturally   when
        ownership related objects are introduced into  these
        tables." mplsTunnelTable."
   REFERENCE
       "MPLS Traffic Engineering Management Information Base
        Using SMIv2, Srinivasan Srinivasan, Viswanathan and Viswanathan, draft-ietf-
        mpls-te-mib-01.txt, June 1999." Nadeau,
        draft-ietf-mpls-te-mib-02.txt, February 2000."
   INDEX         { mplsInSegmentIfIndex, mplsInSegmentLabel }
   ::= { mplsInSegmentTable 1 }

MplsInSegmentEntry ::= SEQUENCE {
      mplsInSegmentIfIndex         InterfaceIndex,
      mplsInSegmentLabel           MplsLabel,
      mplsInSegmentNPop            Integer32,
      mplsInSegmentAddrFamily      MplsLsrIANAAddrFamily,
      mplsInSegmentXCIndex         Integer32,
      mplsInSegmentTSpecIndex      Unsigned32,
      mplsInSegmentOwner           INTEGER,
      mplsInSegmentAdminStatus     INTEGER,
      mplsInSegmentOperStatus      INTEGER,
      mplsInSegmentRowStatus       RowStatus
   }

mplsInSegmentIfIndex OBJECT-TYPE
   SYNTAX        InterfaceIndexOrZero
   MAX-ACCESS    read-create
   STATUS        current
   DESCRIPTION
       "Incoming
       "This is a unique index for an entry in the
        MplsInSegmentTable. This value represents the
        interface  index. index for the incoming MPLS interface.  A
        value of zero represents an incoming label from the
        per-platform label space.  In this case, the
        mplsInSegmentLabel is interpreted to be an MPLS-type
        label."
   ::= { mplsInSegmentEntry 1 }

mplsInSegmentLabel OBJECT-TYPE
   SYNTAX        MplsLabel
   MAX-ACCESS    not-accessible    read-create
   STATUS        current
   DESCRIPTION
       "The incoming label." label for this segment."
   ::= { mplsInSegmentEntry 2 }

mplsInSegmentNPop OBJECT-TYPE
   SYNTAX        Integer32        Unsigned32(1..4294967295)
   MAX-ACCESS    read-create
   STATUS        current
   DESCRIPTION
       "The number of labels to pop from the incoming
        packet.  Normally only the top label is popped
        (based on which from
        the packet and used for all switching decisions are taken)." for
        that packet."
   DEFVAL        { 1 }
   ::= { mplsInSegmentEntry 3 }

mplsInSegmentAddrFamily OBJECT-TYPE
   SYNTAX        MplsLsrIANAAddrFamily
   MAX-ACCESS    read-create
   STATUS        current
   DESCRIPTION
       "The IANA address family of the incoming packet.  A
        value of zero indicates that the family type is
        either unknown or undefined (which could happen undefined. This latter case is
        possible for
        example example, when packet streams of
        different types are merged in a multipoint-to-point connection)."
        connection."
   REFERENCE
       "RFC 1700 - Assigned Numbers, Reynolds and Postel,
        October 1994."
   DEFVAL        { 0 }
   ::= { mplsInSegmentEntry 4 }

mplsInSegmentXCIndex OBJECT-TYPE
   SYNTAX        Integer32
   MAX-ACCESS    read-only
   STATUS        current
   DESCRIPTION
       "Index
       "The index into mplsXCTable is used to identify which  cross-
        connect
        cross-connect entry this segment is part of.  A  Note
        that a value of zero indicates that it is not being
        referred to by any cross-connect entry."
   DEFVAL        { 0 }
   ::= { mplsInSegmentEntry 5 }

mplsInSegmentTSpecIndex OBJECT-TYPE
   SYNTAX        Unsigned32
   MAX-ACCESS    read-create
   STATUS        current
   DESCRIPTION
       "Pointer
       "This variable represents a pointer into the
        mplsTSpecTable indicating and indicates the TSpec which is to
        be assigned  for to this segment.  A value of zero
        indicates best-effort treatment.  Two or more
        segments can indicate resource sharing by pointing
        to the same entry in mplsTSpecTable."
   DEFVAL        { 0 0 }
   ::= { mplsInSegmentEntry 6 }

mplsInSegmentOwner OBJECT-TYPE
   SYNTAX        INTEGER {
                snmp(1),
                crldp(2),
                rsvp(3),
                policyAgent(4),
                other(5)
      }
   MAX-ACCESS    read-create
   STATUS        current
   DESCRIPTION
       "Denotes the entity that created and is responsible
        for managing this segment."
   ::= { mplsInSegmentEntry 6 7 }

mplsInSegmentAdminStatus OBJECT-TYPE
   SYNTAX        INTEGER {
                up(1),      -- ready to pass packets
                down(2),
                testing(3)  -- in some test mode
      }
   MAX-ACCESS    read-create
   STATUS        current
   DESCRIPTION
       "Desired
       "This value is used to represent the managerĘs
        desired operational status of this segment."
   ::= { mplsInSegmentEntry 7 8 }

mplsInSegmentOperStatus OBJECT-TYPE
   SYNTAX        INTEGER {
         up(1),          -- ready to pass packets
         down(2),
         testing(3),     -- in some test mode
         unknown(4),     -- status cannot be determined for
                       -- some reason
         dormant(5),
         domant(5),
         notPresent(6),  -- some component is missing
         lowerLayerNotPresent(7)
         lowerLayerDown(7)
                       -- down due to the state of
                       -- lower layer interfaces
      }
   MAX-ACCESS    read-only
   STATUS        current
   DESCRIPTION
       "The
       "This value represents the actual operational status
        of this segment."
   ::= { mplsInSegmentEntry 8 9 }

mplsInSegmentRowStatus OBJECT-TYPE
   SYNTAX        RowStatus
   MAX-ACCESS    read-create
   STATUS        current
   DESCRIPTION
       "For creating, modifying, and deleting
       "This variable is used to create, modify, and/or
        delete a row in this row." table."
   ::= { mplsInSegmentEntry 9 10 }

-- End of mplsInSegmentTable

-- In-segment performance table.

mplsInSegmentPerfTable  OBJECT-TYPE
   SYNTAX        SEQUENCE OF MplsInSegmentPerfEntry
   MAX-ACCESS    not-accessible
   STATUS        current
   DESCRIPTION
       "This table contains statistical information  about for
        incoming MPLS segments to an LSR."
   ::= { mplsLsrObjects 4 }

mplsInSegmentPerfEntry  OBJECT-TYPE
   SYNTAX        MplsInSegmentPerfEntry
   MAX-ACCESS    not-accessible
   STATUS        current
   DESCRIPTION
       "An entry in this table contains statistical
        information about one incoming segment which was
        configured in the mplsInSegmentTable."
   AUGMENTS      { mplsInSegmentEntry }
      ::= { mplsInSegmentPerfTable 1 }

MplsInSegmentPerfEntry ::= SEQUENCE {
      mplsInSegmentOctets             Counter32,
      mplsInSegmentPackets            Counter32,
      mplsInSegmentErrors             Counter32,
      mplsInSegmentDiscards           Counter32,

      -- high capacity counter
      mplsInSegmentHCOctets           Counter64
   }

mplsInSegmentOctets OBJECT-TYPE
   SYNTAX        Counter32
   MAX-ACCESS    read-only
   STATUS        current
   DESCRIPTION
       "Total
       "This value represents the total number of octets received."
        received by this segment."
   ::= { mplsInSegmentPerfEntry 1 }

mplsInSegmentPackets OBJECT-TYPE
   SYNTAX        Counter32
   MAX-ACCESS    read-only
   STATUS        current
   DESCRIPTION
       "Total number of packets received." received by this segment."
   ::= { mplsInSegmentPerfEntry 2 }

mplsInSegmentErrors OBJECT-TYPE
   SYNTAX        Counter32
   MAX-ACCESS    read-only
   STATUS        current
   DESCRIPTION
       "Number
       "The number of errored packets received." received in error by this
        LSR."
   ::= { mplsInSegmentPerfEntry 3 }

mplsInSegmentDiscards OBJECT-TYPE
   SYNTAX        Counter32
   MAX-ACCESS    read-only
   STATUS        current
   DESCRIPTION
       "Number
       "The number of labeled packets received that had on this in-
        segment, which were chosen to be  dropped
        either  because of discarded even
        though no errors or had been detected to prevent their
        being transmitted.  One possible reason for other reasons
        discarding such
        as a labeled packet could be to free up
        buffer overflows." space."
   ::= { mplsInSegmentPerfEntry 4 }

mplsInSegmentHCOctets OBJECT-TYPE
   SYNTAX        Counter32
   MAX-ACCESS    read-only
   STATUS        current
   DESCRIPTION
       "Total
       "The total number of octets received.  This is the 64
        bit version of mplsInSegmentOctets."
   ::= { mplsInSegmentPerfEntry 5 }

-- End of mplsInSegmentPerfTable.

-- Out-segment table.

mplsOutSegmentIndexNext OBJECT-TYPE
   SYNTAX        Integer32
   MAX-ACCESS    read-only
   STATUS        current
   DESCRIPTION
       "This object contains the next appropriate value to
        be used for mplsOutSegmentIndex when creating
        entries in the mplsOutSegmentTable. If the number of
        unassigned entries is exhausted, this object will
        take on the value of 0.  To obtain the
        mplsOutSegmentIndex value for a new entry, the
        manager must first issue a management protocol
        retrieval operation to obtain the current value of
        this object. The agent should modify the value to
        reflect the next unassigned index after each
        retrieval operation. After a manager retrieves a
        value the agent will determine through its local
        policy when this index value will be made available
        for reuse."
::= { mplsLsrObjects 5 }

mplsOutSegmentTable  OBJECT-TYPE
   SYNTAX        SEQUENCE OF MplsOutSegmentEntry
   MAX-ACCESS    not-accessible
   STATUS        current
   DESCRIPTION
       "This table contains a description representation of the outgoing
        segments from an LSR."
   ::= { mplsLsrObjects 5 6 }

mplsOutSegmentEntry  OBJECT-TYPE
   SYNTAX        MplsOutSegmentEntry
   MAX-ACCESS    not-accessible
   STATUS        current
   DESCRIPTION
       "An entry in this table represents one  outgoing incoming
        segment.  An entry can be created by a network
        administrator or by an SNMP agent as instructed by
        LDP
        CR-LDP or RSVP.  The creator of the entry is denoted
        by mplsOutSegmentOwner. An entry in this table is
        indexed by the ifIndex of the incoming interface and
        the (top) label.  Note that since it is possible
        that some of the segments are associated with a tunnel, the
        traffic parameters of these rows are supported as
        read-only objects and their modification can be done
        only via the  tunnel
        table, mplsTunnelTable. This issue will be addressed
        more  naturally when ownership related  objects  are
        introduced into these tables." the tunnel table, mplsTunnelTable."
   REFERENCE
       "MPLS Traffic Engineering Management Information Base
        Using SMIv2, Srinivasan Srinivasan, Viswanathan and Viswanathan, draft-ietf-
        mpls-te-mib-01.txt, June 1999." Nadeau,
        draft-ietf-mpls-te-mib-02.txt, February 2000."

   INDEX         { mplsOutSegmentIndex }
      ::= { mplsOutSegmentTable 1 }

MplsOutSegmentEntry ::= SEQUENCE {
      mplsOutSegmentIndex                     Integer32,
      mplsOutSegmentIfIndex                   InterfaceIndex,
      mplsOutSegmentPushTopLabel              TruthValue,
      mplsOutSegmentTopLabel                  MplsLabel,
      mplsOutSegmentNextHopIpAddrType         INTEGER,
      mplsOutSegmentNextHopIpv4Addr           IpAddress,
      mplsOutSegmentNextHopIpv6Addr           Ipv6Address,
      mplsOutSegmentXCIndex                   Integer32,
      mplsOutSegmentTSpecIndex                Unsigned32,
      mplsOutSegmentOwner                     INTEGER,
      mplsOutSegmentAdminStatus               INTEGER,
      mplsOutSegmentOperStatus                INTEGER,
      mplsOutSegmentRowStatus                 RowStatus
   }

mplsOutSegmentIndex OBJECT-TYPE
   SYNTAX        Integer32
   MAX-ACCESS    not-accessible    read-create
   STATUS        current
   DESCRIPTION
       "Unique
       "This value contains a unique index for this row.
        While a value of 0 is not valid as an index for this
        row it can be supplied as a valid value to index
        mplsXCTable to access entries for which no out-segment out-
        segment has been configured."
   ::= { mplsOutSegmentEntry 1 }

mplsOutSegmentIfIndex OBJECT-TYPE
   SYNTAX        InterfaceIndex
   MAX-ACCESS    read-create
   STATUS        current
   DESCRIPTION
       "Interface
       "This value contains the interface index of the
        outgoing interface."
   ::= { mplsOutSegmentEntry 2 }

mplsOutSegmentPushTopLabel OBJECT-TYPE
   SYNTAX        TruthValue
   MAX-ACCESS    read-create
   STATUS        current
   DESCRIPTION
       "Whether
       "This value indicates whether or not a top label
        should be pushed onto the outgoing packet's label
        stack.  Its  The value has to of this variable must be set to
        true if the outgoing interface is ATM (which ATM, which does
        not support  `pop-and-go') pop-and-go, or if it is a tunnel
        origination. Note  also that it is considered an error in
        the case   where that mplsOutSegmentPushTopLabel is set to false
        false, but the cross-connect entry that which refers to
        this out-segment has a non-zero mplsLabelStackIndex is an error which
        the mplsLabelStackIndex.
        The LSR should ensure doesn't happen." that this situation cannot
        happen "
   ::= { mplsOutSegmentEntry 3 }

mplsOutSegmentTopLabel OBJECT-TYPE
   SYNTAX        MplsLabel
   MAX-ACCESS    read-create
   STATUS        current
   DESCRIPTION
       "If mplsOutSegmentPushTopLabel is true then this is
        the label that should be pushed onto the outgoing
        packet's label stack.  Note that the contents of the
        label field can be interpreted in an outgoing
        interface specific fashion.  For example, the label
        carried in the MPLS shim header is 20 bits wide and
        the top 12 bits must be zero.  The Frame Relay label
        is 24 bits wide and the top 8 bits must be zero.
        For ATM interfaces the lowermost 16 bits are
        interpreted as the VCI, the next 8 bits as the VPI
        and the remaining bits must be zero."
   ::= { mplsOutSegmentEntry 4 }

mplsOutSegmentNextHopIpAddrType OBJECT-TYPE
   SYNTAX        INTEGER { none (1), ipV4 (2), ipV6 (3) }
   MAX-ACCESS    read-create
   STATUS        current
   DESCRIPTION
       "Whether
       "Indicates whether the next hop address is IPv4 or
        IPv6.   A  Note that a value of none (1) is valid (only) only
        when the outgoing interface is of type point-to-point." point-to-
        point."
   DEFVAL        { none }
   ::= { mplsOutSegmentEntry 5 }

mplsOutSegmentNextHopIpv4Addr OBJECT-TYPE
   SYNTAX        IpAddress
   MAX-ACCESS    read-create
   STATUS        current
   DESCRIPTION
       "IPv4 Address of the next hop.  Its value is
        significant only when
        mplsOutSegmentNextHopIpAddrType is ipV4 (2),
        otherwise it should return a value of 0."
   ::= { mplsOutSegmentEntry 6 }

mplsOutSegmentNextHopIpv6Addr OBJECT-TYPE
   SYNTAX        Ipv6Address
   MAX-ACCESS    read-create
   STATUS        current
   DESCRIPTION
       "IPv6 address of the next hop.  Its value is
        significant only when
        mplsOutSegmentNextHopIpAddrType is ipV6 (3),
        otherwise it should return a value of 0."
   ::= { mplsOutSegmentEntry 7 }

mplsOutSegmentXCIndex OBJECT-TYPE
   SYNTAX        Integer32
   MAX-ACCESS    read-create
   STATUS        current
   DESCRIPTION
       "Index into mplsXCTable to  identify which identifies which cross-
        connect entry this segment is part of.  A value of
        zero indicates that it this entry is not being referred to by
        any cross-connect entry."
   DEFVAL        { 0 }
   ::= { mplsOutSegmentEntry 8 }

mplsOutSegmentTSpecIndex OBJECT-TYPE
   SYNTAX        Unsigned32
   MAX-ACCESS    read-create
   STATUS        current
   DESCRIPTION
       "Pointer
       "A pointer into the mplsTSpecTable indicating the
        TSpec to be assigned for this segment.  A value of
        zero indicates best-effort treatment.  Two or more
        segments can indicate resource sharing by pointing
        to the same entry in mplsTSpecTable."
   DEFVAL        { 0 }
   ::= { mplsOutSegmentEntry 9 }

mplsOutSegmentOwner OBJECT-TYPE
   SYNTAX        INTEGER {
         snmp(1),
         crldp(2),
         rsvp(3),
         policyAgent(4),
         other(5)
      }
   MAX-ACCESS    read-create
   STATUS        current
   DESCRIPTION
       "Denotes the entity which created and is responsible
        for managing this segment."
::= { mplsOutSegmentEntry 10 }

mplsOutSegmentAdminStatus OBJECT-TYPE
   SYNTAX        INTEGER {
         up(1),     -- ready to pass packets
         down(2),
         testing(3) -- in some test mode
      }
   MAX-ACCESS    read-create
   STATUS        current
   DESCRIPTION
       "Desired
       "The desired operational status of this segment."
   ::= { mplsOutSegmentEntry 10 11 }

mplsOutSegmentOperStatus OBJECT-TYPE
   SYNTAX        INTEGER {
         up(1),          -- ready to pass packets
         down(2),
         testing(3),     -- in some test mode
         unknown(4),     -- status cannot be determined for
                       -- some reason
         dormant(5),
         notPresent(6),  -- some component is missing
         lowerLayerNotPresent(7)
         lowerLayerDown(7)
                       -- down due to the state of
                       -- lower layer interfaces
      }
   MAX-ACCESS    read-only
   STATUS        current
   DESCRIPTION
       "The actual operational status of this segment."
   ::= { mplsOutSegmentEntry 11 12 }

mplsOutSegmentRowStatus OBJECT-TYPE
   SYNTAX        RowStatus
   MAX-ACCESS    read-create
   STATUS        current
   DESCRIPTION
       "For creating, modifying, and deleting this row."
   ::= { mplsOutSegmentEntry 12 13 }

-- End of mplsOutSegmentTable

-- Out-segment performance table.

mplsOutSegmentPerfTable  OBJECT-TYPE
   SYNTAX        SEQUENCE OF MplsOutSegmentPerfEntry
   MAX-ACCESS    not-accessible
   STATUS        current
   DESCRIPTION
       "This table contains statistical information about
        incoming segments to an LSR."
   ::= { mplsLsrObjects 6 7 }

mplsOutSegmentPerfEntry  OBJECT-TYPE
   SYNTAX        MplsOutSegmentPerfEntry
   MAX-ACCESS    not-accessible
   STATUS        current
   DESCRIPTION
       "An entry in this table contains statistical
        information about one incoming segment configured in
        mplsOutSegmentTable."
   AUGMENTS      { mplsOutSegmentEntry }
      ::= { mplsOutSegmentPerfTable 1 }

MplsOutSegmentPerfEntry ::= SEQUENCE {
      mplsOutSegmentOctets                Counter32,
      mplsOutSegmentPackets               Counter32,
      mplsOutSegmentErrors                Counter32,
      mplsOutSegmentDiscards              Counter32,

      -- HC counter
      mplsOutSegmentHCOctets              Counter64
   }

mplsOutSegmentOctets OBJECT-TYPE
   SYNTAX        Counter32
   MAX-ACCESS    read-only
   STATUS        current
   DESCRIPTION
       "Total
       "This value contains the total number of octets sent." sent
        on this segment."
   ::= { mplsOutSegmentPerfEntry 1 }

mplsOutSegmentPackets OBJECT-TYPE
   SYNTAX        Counter32
   MAX-ACCESS    read-only
   STATUS        current
   DESCRIPTION
       "Total
       "This value contains the total number of packets sent." sent
        on this segment."
   ::= { mplsOutSegmentPerfEntry 2 }

mplsOutSegmentErrors OBJECT-TYPE
   SYNTAX        Counter32
   MAX-ACCESS    read-only
   STATUS        current
   DESCRIPTION
       "Number of packets that could not be sent due to
        errors."
   ::= { mplsOutSegmentPerfEntry 3 }

mplsOutSegmentDiscards OBJECT-TYPE
   SYNTAX        Counter32
   MAX-ACCESS    read-only
   STATUS        current
   DESCRIPTION
       "Number
       "The number of  outgoing labeled packets that received on this out-
        segment, which were chosen to be discarded even
        though no errors had been detected to prevent their
        being transmitted.  One possible reason for
        discarding such a labeled packet could be to free up
        buffer space."
   ::= { mplsOutSegmentPerfEntry 4 }

mplsOutSegmentHCOctets OBJECT-TYPE
   SYNTAX        Counter64
   MAX-ACCESS    read-only
   STATUS        current
   DESCRIPTION
       "Total number of octets sent.  This is the 64 bit
        version of mplsOutSegmentOctets."
   ::= { mplsOutSegmentPerfEntry 5 }

-- End of mplsOutSegmentPerfTable.

-- Cross-connect table.

mplsXCIndexNext OBJECT-TYPE
   SYNTAX        Integer32
   MAX-ACCESS    read-only
   STATUS        current
   DESCRIPTION
       "This object contains an appropriate value to be used
        for mplsXCIndex when creating entries in the
        mplsXCTable. The value 0 indicates that no
        unassigned entries are available. To obtain the
        value of mplsXCIndex for a new entry in the
        mplsXCTable, the manager issues a management
        protocol retrieval operation to be  dropped
        either  because of errors or for other reasons  such
        as buffer overflows."
   ::= { mplsOutSegmentPerfEntry 4 }

mplsOutSegmentHCOctets OBJECT-TYPE
   SYNTAX        Counter64
   MAX-ACCESS    read-only
   STATUS obtain the current
   DESCRIPTION
       "Total  number
        value of octets sent.  This is mplsXCIndex. After each retrieval
        operation, the  64  bit
        version of mplsOutSegmentOctets." agent should modify the value to
        reflect the next unassigned index. After a manager
        retrieves a value the agent will determine through
        its local policy when this index value will be made
        available for reuse."
::= { mplsOutSegmentPerfEntry 5 mplsLsrObjects 8 }

-- End of mplsOutSegmentPerfTable.

-- Cross-connect table.

mplsXCTable  OBJECT-TYPE
   SYNTAX        SEQUENCE OF MplsXCEntry
   MAX-ACCESS    not-accessible
   STATUS        current
   DESCRIPTION
       "This table specifies information for switching
        between LSP segments.  It supports point-to-point,
        point-to-multipoint and multipoint-to-point
        connections.  mplsLabelStackTable specifies the
        label stack information for a cross-connect LSR and
        is referred to from mplsXCTable."
   ::= { mplsLsrObjects 7 9 }

mplsXCEntry  OBJECT-TYPE
   SYNTAX        MplsXCEntry
   MAX-ACCESS    not-accessible
   STATUS        current
   DESCRIPTION
       "A row in this table represents one cross-connect
        entry.  It is indexed by the  The following objects: objects index it:

       - cross-connect index mplsXCIndex that uniquely
        identifies a group of cross-connect entries
       - interface index of the in-segment,
        mplsInSegmentIfIndex
       - incoming label(s), mplsInSegmentLabel
       - out-segment index, mplsOutSegmentIndex

        Originating LSPs:
       These are represented by using the special
        combination of values mplsInSegmentIfIndex=0 and
        mplsInSegmentLabel=0 as indexes.  In this case the
        mplsOutSegmentIndex MUST be non-zero.

       Terminating LSPs:
       These are represented by using the special value
        mplsOutSegmentIndex=0 as index.

       Special labels:
       Entries indexed by reserved MPLS label values 0
        through 15 imply terminating LSPs and MUST have
        mplsOutSegmentIndex=0.

       An entry can be created by a network administrator or
        by an SNMP agent as instructed by LDP CR-LDP or RSVP."
   INDEX         { mplsXCIndex, mplsInSegmentIfIndex,
                mplsInSegmentLabel, mplsOutSegmentIndex }
      ::= { mplsXCTable 1 }

MplsXCEntry ::= SEQUENCE {
      mplsXCIndex                 INTEGER,
      mplsXCLspId              MplsLSPID,
      mplsXCLabelStackIndex       Integer32,
      mplsXCCOS                   Integer32,
      mplsXCIsPersistent          TruthValue,
      mplsXCAdminStatus           INTEGER,
      mplsXCOperStatus            INTEGER,
      mplsXCRowStatus             RowStatus
   }

mplsXCIndex OBJECT-TYPE
   SYNTAX        INTEGER (0..4294967295)
   MAX-ACCESS    not-accessible    read-create
   STATUS        current
   DESCRIPTION
       "Primary index for the row identifying a group of
        cross-connect segments."
   ::= { mplsXCEntry 1 }

mplsXCLspId OBJECT-TYPE
   SYNTAX        MplsLSPID
   MAX-ACCESS    read-create
   STATUS        current
   DESCRIPTION
       "This value identifies the label switched path that
        this cross-connect entry belongs to."
   ::= { mplsXCEntry 2 }

mplsXCLabelStackIndex OBJECT-TYPE
   SYNTAX        Integer32
   MAX-ACCESS    read-create
   STATUS        current
   DESCRIPTION
       "Primary index into mplsLabelStackTable identifying a
        stack of labels to be pushed beneath the top label.
        Note that the top label is identified in by the out-
        segment which ensures that all the components of a
        multipoint-to-point connection have the same
        outgoing label.  A value of 0 indicates that no
        labels are to be stacked beneath the top label."
   ::= { mplsXCEntry 2 3 }

mplsXCCOS OBJECT-TYPE
   SYNTAX        Integer32
   MAX-ACCESS    read-create
   STATUS        current
   DESCRIPTION
       "Value
       "This value is used to override the incoming COS
        field with for a
        cross-connect  or  the cross-connect. It may also be used as a
        value to assign to outgoing packets for an outgoing
        segment of a tunnel." tunnel. Note that packet treatment at
        this LSR is determined by the incoming COS value and
        the new COS value only impacts packet treatment at a
        downstream LSR."
   ::= { mplsXCEntry 3 4 }

mplsXCIsPersistent OBJECT-TYPE
   SYNTAX        TruthValue
   MAX-ACCESS    read-create
   STATUS        current
   DESCRIPTION
       "Whether
       "Denotes whether or not this cross-connect entry and
        associated in- and out-segments should be restored
        automatically after failures."
   DEFVAL        { false }
   ::= { mplsXCEntry 4 5 }

mplsXCAdminStatus OBJECT-TYPE
   SYNTAX        INTEGER {
                up(1),     -- ready to pass packets
                down(2),
                testing(3) -- in some test mode
                }
   MAX-ACCESS    read-create
   STATUS        current
   DESCRIPTION
       "Desired
       "The desired operational status of this segment."
   ::= { mplsXCEntry 5 6 }

mplsXCOperStatus OBJECT-TYPE
   SYNTAX        INTEGER {
         up(1),          -- ready to pass packets
         down(2),
         testing(3),     -- in some test mode
         unknown(4),     -- status cannot be determined for
                       -- some reason
         dormant(5),
         notPresent(6),  -- some component is missing
         lowerLayerNotPresent(7)
         lowerLayerDown(7)
                       -- down due to the state of
                       -- lower layer interfaces
      }
   MAX-ACCESS    read-only
   STATUS        current
   DESCRIPTION
       "The actual operational status of this segment." cross-
        connect."
   ::= { mplsXCEntry 6 7 }

mplsXCRowStatus OBJECT-TYPE
   SYNTAX        RowStatus
   MAX-ACCESS    read-create
   STATUS        current
   DESCRIPTION
       "For creating, modifying, and deleting
   DESCRIPTION
       "For creating, modifying, and deleting this row."
   ::= { mplsXCEntry 8 }

-- End of mplsXCTable

-- Label stack table.
mplsMaxLabelStackDepth  OBJECT-TYPE
   SYNTAX        Integer32
   MAX-ACCESS    read-only
   STATUS        current
   DESCRIPTION
       "The maximum stack depth supported by this LSR."
::= { mplsLsrObjects 10 }

mplsLabelStackIndexNext  OBJECT-TYPE
   SYNTAX        Integer32
   MAX-ACCESS    read-only
   STATUS        current
   DESCRIPTION
       "This object contains an appropriate value to be used
        for mplsLabelStackIndex when creating entries in the
        mplsLabelStackTable.  The value 0 indicates that no
        unassigned entries are available.  To obtain an
        mplsLabelStackIndex value for a new entry, the
        manager issues a management protocol retrieval
        operation to obtain the current value of this row."
        object. After each retrieval operation, the agent
        should modify the value to reflect the next
        unassigned index. After a manager retrieves a value
        the agent will determine through its local policy
        when this index value will be made available for
        reuse."
::= { mplsXCEntry 7 mplsLsrObjects 11 }

-- End of mplsXCTable

-- Label stack table.

mplsLabelStackTable OBJECT-TYPE
   SYNTAX        SEQUENCE OF MplsLabelStackEntry
   MAX-ACCESS    not-accessible
   STATUS        current
   DESCRIPTION
       "This table specifies the label stack to be pushed
        onto a packet, beneath the top label.  Entries into
        this table are referred to from mplsXCTable."
   ::= { mplsLsrObjects 8 12 }

mplsLabelStackEntry OBJECT-TYPE
   SYNTAX        MplsLabelStackEntry
   MAX-ACCESS    not-accessible
   STATUS        current
   DESCRIPTION
       "An entry in this table represents one label which is
        to be pushed onto an outgoing packets packet, beneath the
        top label.  An entry can be created by a network
        administrator or by an SNMP agent as instructed by
        LDP
        CR-LDP or RSVP."
   INDEX         { mplsLabelStackIndex mplsLabelStackIndex, mplsLabelStackLabelIndex }
      ::= { mplsLabelStackTable 1 }

MplsLabelStackEntry ::= SEQUENCE {
      mplsLabelStackIndex             Integer32,
      mplsLabelStackLabelIndex        Integer32,
      mplsLabelStackLabel             MplsLabel,
      mplsLabelStackRowStatus         RowStatus
   }

mplsLabelStackIndex OBJECT-TYPE
   SYNTAX        Integer32
   MAX-ACCESS    not-accessible    read-create
   STATUS        current
   DESCRIPTION
       "Primary index for this row identifying a stack of
        labels to be pushed on an outgoing packet packet, beneath
        the top label."
   ::= { mplsLabelStackEntry 1 }

mplsLabelStackLabelIndex OBJECT-TYPE
   SYNTAX        Integer32
   MAX-ACCESS    not-accessible
   STATUS        current
   DESCRIPTION
       "Secondary index for this row identifying one label
        of the stack." stack. Note that an entry with a smaller
        mplsLabelStackLabelIndex would refer to a label
        higher up the label stack and would be popped before
        a label represented by a higher
        mplsLabelStackLabelIndex at a downstream LSR."
   ::= { mplsLabelStackEntry 2 }

mplsLabelStackLabel OBJECT-TYPE
   SYNTAX        MplsLabel
   MAX-ACCESS    read-create
   STATUS        current
   DESCRIPTION
       "Label
       "The label to pushed."
   ::= { mplsLabelStackEntry 3 }

mplsLabelStackRowStatus OBJECT-TYPE
   SYNTAX        RowStatus
   MAX-ACCESS    read-create
   STATUS        current
   DESCRIPTION
       "For creating, modifying, and deleting this row."
   ::= { mplsLabelStackEntry 4 }

-- End of mplsLabelStackTable

-- TSpec table.

mplsTSpecIndexNext OBJECT-TYPE
   SYNTAX        Integer32
   MAX-ACCESS    read-only
   STATUS        current
   DESCRIPTION
       "This object contains an appropriate value which will
        be used for mplsTSpecIndex when creating entries in
        the mplsTSpecTable.  The value 0 indicates that no
        unassigned entries are available.  To obtain the
        mplsTSpecIndex value for a new entry, the manager
        issues a management protocol retrieval operation to
        obtain the current value of this object. After each
        retrieval operation, the agent should modify the
        value to reflect the next unassigned index. After a
        manager retrieves a value the agent will determine
        through its local policy when this index value will
        be made available for reuse."
::= { mplsLsrObjects 13 }

mplsTSpecTable OBJECT-TYPE
   SYNTAX        SEQUENCE OF MplsTSpecEntry
   MAX-ACCESS    not-accessible
   STATUS        current
   DESCRIPTION
       "This table specifies TSpec the Traffic Specification
        (TSpec) objects for in and  out-
        segments." out-segments."
   ::= { mplsLsrObjects 9 14 }

mplsTSpecEntry OBJECT-TYPE
   SYNTAX        MplsTSpecEntry
   MAX-ACCESS    not-accessible
   STATUS        current
   DESCRIPTION
       "An entry in this table represents the TSpec objects
        for one or more in or out segments.  A single entry
        can be pointed to by multiple segments indicating
        resource sharing."
   INDEX         { mplsTSpecIndex }
      ::= { mplsTSpecTable 1 }

MplsTSpecEntry ::= SEQUENCE {
      mplsTSpecIndex                  Unsigned32,
      mplsTSpecIfIndex                InterfaceIndex,
      mplsTSpecDirection              INTEGER,
      mplsTSpecMaxRate                BitRate,
      mplsTSpecMeanRate               BitRate,
      mplsTSpecMaxBurstSize           BurstSize,
      mplsTSpecRowStatus              RowStatus
   }

mplsTSpecIndex OBJECT-TYPE
   SYNTAX        Unsigned32
   MAX-ACCESS    read-create
   STATUS        current
   DESCRIPTION
       "Uniquely identifies this row of the table.  Zero  is
        not a valid  Note
        that zero represents an invalid index."
   ::= { mplsTSpecEntry 1 }

mplsTSpecIfIndex OBJECT-TYPE
   SYNTAX        InterfaceIndex
   MAX-ACCESS    read-create
   STATUS        current
   DESCRIPTION
       "Identifies the interface that this entry refers to."
   ::= { mplsTSpecEntry 2 }

mplsTSpecDirection OBJECT-TYPE
   SYNTAX        INTEGER { in(1), out(2) }
   MAX-ACCESS    read-create
   STATUS        current
   DESCRIPTION
       "Direction
       "The direction that these objects pertain to, to. Valid
        values specify either incoming or
        outgoing." outgoing
        directions."
   ::= { mplsTSpecEntry 3 2 }

mplsTSpecMaxRate OBJECT-TYPE
   SYNTAX        BitRate
   UNITS         "bits per second"
   MAX-ACCESS    read-create
   STATUS        current
   DESCRIPTION
       "Maximum rate in bits/second."
   ::= { mplsTSpecEntry 4 3 }

mplsTSpecMeanRate OBJECT-TYPE
   SYNTAX        BitRate
   UNITS         "bits per second"
   MAX-ACCESS    read-create
   STATUS        current
   DESCRIPTION
       "Mean rate in bits/second."
   ::= { mplsTSpecEntry 5 4 }

mplsTSpecMaxBurstSize OBJECT-TYPE
   SYNTAX        BurstSize
   UNITS         "bytes"
   MAX-ACCESS    read-create
   STATUS        current
   DESCRIPTION
       "Maximum burst size in bytes."
   ::= { mplsTSpecEntry 6 5 }

mplsTSpecRowStatus OBJECT-TYPE
   SYNTAX        RowStatus
   MAX-ACCESS    read-create
   STATUS        current
   DESCRIPTION
       "For creating, modifying, and deleting this row."
   ::= { mplsTSpecEntry 7 6 }

-- End of mplsTSpecTable

-- Notifications.

-- Interface configuration.

mplsInterfaceUp NOTIFICATION-TYPE
   OBJECTS     { mplsInterfaceConfIndex,
                mplsInterfaceAdminStatus, mplsInterfaceOperStatus }
   STATUS      current
   DESCRIPTION
       "This notification is generated when a
        mplsInterfaceOperStatus object for one of the
        entries in mplsInterfaceConfTable is about to leave
        the down state and transition into some other state
        (but not into the notPresent state).  This other
        state is indicated by the included value of
        mplsInterfaceOperStatus."
   ::= { mplsLsrNotifications 1 }

mplsInterfaceDown NOTIFICATION-TYPE
   OBJECTS     { mplsInterfaceConfIndex,
                mplsInterfaceAdminStatus, mplsInterfaceOperStatus }
   STATUS      current
   DESCRIPTION
       "This notification is generated when a
        mplsInterfaceOperStatus object for one of the
        entries in mplsInterfaceConfTable is about to enter
        the down state from some other state (but not from
        the notPresent state).  This other state is
        indicated by the included value of
        mplsInterfaceOperStatus."
   ::= { mplsLsrNotifications 2 }

-- In-segment.

mplsInSegmentUp NOTIFICATION-TYPE
   OBJECTS     { mplsInSegmentIfIndex, mplsInSegmentLabel,
                mplsInSegmentAdminStatus, mplsInSegmentOperStatus }
   STATUS      current
   DESCRIPTION
       "This notification is generated when a
        mplsInSegmentOperStatus object for one of the
        configured in-segments is about to leave the down
        state and transition into some other state (but not
        into the notPresent state).  This other state is
        indicated by the included value of
        mplsInSegmentOperStatus."
   ::= { mplsLsrNotifications 3 }

mplsInSegmentDown NOTIFICATION-TYPE
   OBJECTS     { mplsInSegmentIfIndex, mplsInSegmentLabel,
                mplsInSegmentAdminStatus, mplsInSegmentOperStatus }
   STATUS      current
   DESCRIPTION
       "This notification is generated when a
        mplsInSegmentOperStatus object for one of the
        configured in-segments is about to enter the down
        state from some other state (but not from the
        notPresent state).  This other state is indicated by
        the included value of mplsInSegmentOperStatus."
   ::= { mplsLsrNotifications 4 }

-- Out-segment.

mplsOutSegmentUp NOTIFICATION-TYPE
   OBJECTS     { mplsOutSegmentIndex, mplsInSegmentAdminStatus,
                mplsInSegmentOperStatus }
   STATUS      current
   DESCRIPTION
       "This notification is generated when a
        mplsOutSegmentOperStatus object for one of the
        configured out-segments is about to leave the down
        state and transition into some other state (but not
        into the notPresent state).  This other state is
        indicated by the included value of
        mplsOutSegmentOperStatus."
   ::= { mplsLsrNotifications 5 }

mplsOutSegmentDown NOTIFICATION-TYPE
   OBJECTS     { mplsOutSegmentIndex, mplsInSegmentAdminStatus,
                mplsInSegmentOperStatus }
   STATUS      current
   DESCRIPTION
       "This notification is generated when a
        mplsOutSegmentOperStatus object for one of the
        configured out-segments is about to enter the down
        state from some other state (but not from the
        notPresent state).  This other state is indicated by
        the included value of mplsOutSegmentOperStatus."
   ::= { mplsLsrNotifications 6 }

-- Cross-connect.

mplsXCUp NOTIFICATION-TYPE
   OBJECTS     { mplsXCIndex,
                mplsInSegmentIfIndex, mplsInSegmentLabel,
                mplsOutSegmentIndex,
                mplsXCAdminStatus, mplsXCOperStatus }
   STATUS      current
   DESCRIPTION
       "This notification is generated when a
        mplsXCOperStatus object for one of the configured
        cross-connect entries is about to leave the down
        state and transition into some other state (but not
        into the notPresent state).  This other state is
        indicated by the included value of
        mplsXCOperStatus."
   ::= { mplsLsrNotifications 7 }

mplsXCDown NOTIFICATION-TYPE
   OBJECTS     { mplsXCIndex,
                mplsInSegmentIfIndex, mplsInSegmentLabel,
                mplsOutSegmentIndex,
                mplsXCAdminStatus, mplsXCOperStatus }
   STATUS      current
   DESCRIPTION
       "This notification is generated when a
        mplsXCOperStatus object for one of the configured
        cross-connect entries is about to enter the down
        state from some other state (but not from the
        notPresent state).  This other state is indicated by
        the included value of mplsXCOperStatus."
   ::= { mplsLsrNotifications 8 }

-- End of notifications.

-- Module compliance.

mplsLsrGroups
   OBJECT IDENTIFIER ::= { mplsLsrConformance 1 }

mplsLsrCompliances
   OBJECT IDENTIFIER ::= { mplsLsrConformance 2 }

mplsLsrModuleCompliance MODULE-COMPLIANCE
   STATUS current
   DESCRIPTION
       "Compliance statement for agents that support the
        MPLS LSR MIB."
   MODULE -- this module

      -- The mandatory groups have to be implemented by all LSRs.
      -- However, they may all be supported as read-only objects
      -- in the case where manual configuration is not
      -- supported. unsupported.

      MANDATORY-GROUPS    { mplsInSegmentGroup, mplsOutSegmentGroup,
                          mplsXCGroup, mplsInterfaceGroup,
                          mplsPerfGroup }

      GROUP mplsHCInterfacePerfGroup
      DESCRIPTION
          "This group is mandatory for high-speed MPLS
           capable interfaces for which the objects
           mplsInterfaceInOctets and mplsInterfaceOutOctets
           wrap around too quickly."

      GROUP mplsHCInSegmentPerfGroup
      DESCRIPTION
          "This group is mandatory for those in-segment
           entries for which the object
           mplsInSegmentOutOctets wraps around too
           quickly."

      GROUP mplsHCOutSegmentPerfGroup
      DESCRIPTION
          "This group is mandatory for those out-segment
           entries for which the object
           mplsOutSegmentOctets wraps around too quickly."

      GROUP mplsTSpecGroup
      DESCRIPTION
          "This group is mandatory for those LSRs that
           support int-serv Int-Serv style resource reservation."

      -- Depending on whether the device implements persistent
      -- cross-connects or not one of the following two groups
      -- is mandatory.

      GROUP mplsXCIsPersistentGroup
      DESCRIPTION
          "This group is mandatory for devices which
           support persistent cross-connects.  The
           following constraints apply: mplsXCIsPersistent
           must at least be read-only returning true(2)."

      GROUP mplsXCIsNotPersistentGroup
      DESCRIPTION
          "This group is mandatory for devices which
           support non-persistent cross-connects.  The
           following constraints apply: mplsXCIsPersistent
           must at least be read-only returning false(1)."

      -- mplsInterfaceConfTable

      OBJECT      mplsInterfaceAdminStatus
      SYNTAX      INTEGER { up(1), down(2) }
      MIN-ACCESS  read-only
      DESCRIPTION
          "A value of testing(3) need not be supported."

      OBJECT      mplsInterfaceOperStatus
      SYNTAX      INTEGER { up(1), down(2) }
      MIN-ACCESS  read-only
      DESCRIPTION
          "Only up(1) and down(2) need to be supported."

      -- mplsInSegmentTable

      OBJECT      mplsInSegmentIfIndex
      MIN-ACCESS  read-only
      DESCRIPTION
          "Write access is not required."

      OBJECT      mplsInSegmentLabel
      MIN-ACCESS  read-only
      DESCRIPTION
          "Write access is not required."

      OBJECT     mplsInSegmentXCIndex
      MIN-ACCESS  read-only
      DESCRIPTION
          "Write access is not required."
      OBJECT      mplsInSegmentTSpecIndex
      MIN-ACCESS  read-only
      DESCRIPTION
          "Write access is not required."

      OBJECT      mplsInSegmentNPop
      MIN-ACCESS  read-only
      DESCRIPTION
          "Write access if not required.  This object
           should be set to 1 if it is read-only."

      OBJECT      mplsInSegmentAddrFamily
      SYNTAX      INTEGER { other(0) }
      MIN-ACCESS  read-only
      DESCRIPTION
          "Write access is not required.  A value of
           other(0) should be supported."

      OBJECT      mplsInSegmentAdminStatus
      SYNTAX      INTEGER { up(1), down(2) }
      MIN-ACCESS  read-only
      DESCRIPTION
          "A value of testing(3) need not be supported."

      OBJECT      mplsInSegmentOperStatus
      SYNTAX      INTEGER { up(1), down(2) }
      MIN-ACCESS  read-only
      DESCRIPTION
          "Only up(1) and down(2) need to be supported."

      OBJECT      mplsInSegmentRowStatus
      SYNTAX      INTEGER { active(1), notInService(2),
      createAndGo(4),
                          destroy(6) }
      MIN-ACCESS  read-only
      DESCRIPTION
          "The notReady(3) and createAndWait(5) states need
           not be supported."

      -- mplsOutSegmentTable

      OBJECT mplsOutSegmentIndexNext
      MIN-ACCESS    read-only
      DESCRIPTION
          "Write access is not required."

      OBJECT      mplsOutSegmentIndex
      MIN-ACCESS  read-only
      DESCRIPTION
          "Write access is not required."

      OBJECT      mplsOutSegmentIfIndex
      MIN-ACCESS  read-only
      DESCRIPTION
          "Write access is not required."

      OBJECT      mplsOutSegmentPushTopLabel
      MIN-ACCESS  read-only
      DESCRIPTION
          "Write access is not required."

      OBJECT      mplsOutSegmentTopLabel
      MIN-ACCESS  read-only
      DESCRIPTION
          "Write access is not required."

      OBJECT      mplsOutSegmentNextHopIpAddrType
      SYNTAX      INTEGER { none(1), ipV4(2) }
      MIN-ACCESS  read-only
      DESCRIPTION
          "ipV6(3) need not be supported."

      OBJECT      mplsOutSegmentNextHopIpv4Addr
      MIN-ACCESS  read-only
      DESCRIPTION
          "Write access is not required."

      OBJECT      mplsOutSegmentNextHopIpv6Addr
      MIN-ACCESS  read-only
      DESCRIPTION
          "Write access is not required."

      OBJECT      mplsOutSegmentXCIndex
      MIN-ACCESS  read-only
      DESCRIPTION
          "Write access is not required."

      OBJECT      mplsOutSegmentTSpecIndex
      MIN-ACCESS  read-only
      DESCRIPTION
          "Write access is not required."

      OBJECT      mplsOutSegmentAdminStatus
      SYNTAX      INTEGER { up(1), down(2) }
      MIN-ACCESS  read-only
      DESCRIPTION
          "A value of testing(3) need not be supported."

      OBJECT      mplsOutSegmentOperStatus
      SYNTAX      INTEGER { up(1), down(2) }
      MIN-ACCESS  read-only
      DESCRIPTION
          "Only up(1) and down(2) need to be supported."

      OBJECT      mplsOutSegmentRowStatus
      SYNTAX      INTEGER { active(1), notInService(2),
                            createAndGo(4), destroy(6) }
      MIN-ACCESS  read-only
      DESCRIPTION
          "The notReady(3) and createAndWait(5) states need
           not be supported."

      -- mplsXCTable

      OBJECT      mplsXCIndex mplsXCIndexNext
      MIN-ACCESS    read-only
      DESCRIPTION
          "Write access is not required."

      OBJECT      mplsXCIndex
      MIN-ACCESS  read-only
      DESCRIPTION
          "Write access is not required."

      OBJECT mplsXCLabelStackIndexNext
      MIN-ACCESS    read-only
      DESCRIPTION
          "Write access is not required."

      OBJECT      mplsXCLabelStackIndex
      MIN-ACCESS  read-only
      DESCRIPTION
          "Write access is not required."

      OBJECT      mplsXCCOS
      MIN-ACCESS  read-only
      DESCRIPTION
          "Write access is not required."

      OBJECT      mplsXCIsPersistent
      MIN-ACCESS  read-only
      DESCRIPTION
          "Write access is not required."

      OBJECT      mplsXCAdminStatus
      SYNTAX      INTEGER { up(1), down(2) }
      MIN-ACCESS  read-only
      DESCRIPTION
          "A value of testing(3) need not be supported."

      OBJECT      mplsXCOperStatus
      SYNTAX      INTEGER { up(1), down(2) }
      MIN-ACCESS  read-only
      DESCRIPTION
          "Only up(1) and down(2) need to be supported."

      OBJECT      mplsXCRowStatus
      SYNTAX      INTEGER { active(1), notInService(2),
                            createAndGo(4), destroy(6) }
      MIN-ACCESS  read-only
      DESCRIPTION
          "The notReady(3) and createAndWait(5) states need
           not be supported."

   ::= { mplsLsrCompliances 1 }

-- Units of conformance.

mplsInterfaceGroup OBJECT-GROUP
   OBJECTS { mplsInterfaceConfIndex,
             mplsInterfaceLabelMinIn, mplsInterfaceLabelMaxIn,
             mplsInterfaceLabelMinOut, mplsInterfaceLabelMaxOut,
             mplsInterfaceAdminStatus, mplsInterfaceOperStatus,
             mplsInterfaceInLabelsUsed,
             mplsInterfaceOutLabelsUsed }
   STATUS  current
   DESCRIPTION
          "Collection of objects needed for MPLS interface
           configuration and performance information."
   ::= { mplsLsrGroups 1 }

mplsInSegmentGroup  OBJECT-GROUP
   OBJECTS { mplsInSegmentIfIndex, mplsInSegmentLabel,
             mplsInSegmentNPop, mplsInSegmentAddrFamily,
             mplsInSegmentXCIndex, mplsInSegmentTSpecIndex,
             mplsInSegmentAdminStatus, mplsInSegmentOperStatus,
             mplsInSegmentRowStatus,
             mplsInSegmentOctets, mplsInSegmentDiscards }
   STATUS  current
   DESCRIPTION
          "Collection of objects needed to implement an in-
           segment."
   ::= { mplsLsrGroups 2 }

mplsOutSegmentGroup  OBJECT-GROUP
   OBJECTS { mplsOutSegmentIndexNext,
             mplsOutSegmentIndex, mplsOutSegmentIfIndex,
             mplsOutSegmentPushTopLabel, mplsOutSegmentTopLabel,
             mplsOutSegmentNextHopIpAddrType,
             mplsOutSegmentNextHopIpv4Addr,
             mplsOutSegmentNextHopIpv6Addr,
             mplsOutSegmentXCIndex, mplsOutSegmentTSpecIndex,
             mplsOutSegmentAdminStatus, mplsOutSegmentOperStatus,
             mplsOutSegmentRowStatus,
             mplsOutSegmentOctets, mplsOutSegmentDiscards }
   STATUS  current
   DESCRIPTION
          "Collection of objects needed to implement an out-
           segment."
   ::= { mplsLsrGroups 3 }

mplsXCGroup  OBJECT-GROUP
   OBJECTS { mplsXCIndexNext,
             mplsXCIndex, mplsXCLabelStackIndex,
             mplsXCAdminStatus, mplsXCOperStatus,
             mplsXCRowStatus }
   STATUS  current
   DESCRIPTION
          "Collection of objects needed to implement a  cross-
        connect
           cross-connect entry."
   ::= { mplsLsrGroups 4 }

mplsPerfGroup OBJECT-GROUP
   OBJECTS { mplsInterfaceInOctets, mplsInterfaceInPackets, mplsInterfaceInDiscards,
             mplsInterfaceOutOctets,
             mplsInterfaceOutPackets, mplsInterfaceOutDiscards,
             mplsInSegmentOctets, mplsInSegmentPackets,
             mplsInSegmentDiscards,
             mplsOutSegmentOctets, mplsOutSegmentPackets,
             mplsOutSegmentDiscards }
   STATUS  current
   DESCRIPTION
          "Collection of objects providing performance
           information
        about an LSR."
   ::= { mplsLsrGroups 5 }

mplsHCInterfacePerfGroup OBJECT-GROUP
   OBJECTS { mplsInterfaceInHCOctets, mplsInterfaceOutHCOctets }
   STATUS  current
   DESCRIPTION
       "Collection    of   objects   providing   performance
        information  specific to high-speed  interfaces  for
        which   the   objects   mplsInterfaceInOctets    and
        mplsInterfaceOutOctets wrap-around too quickly."
   ::= { mplsLsrGroups 6 }

mplsHCInSegmentPerfGroup OBJECT-GROUP
   OBJECTS { mplsInSegmentHCOctets }
   STATUS  current
   DESCRIPTION
          "Object(s) providing performance information
           specific to out-segments for which the object
           mplsInterfaceInOctets wraps around too quickly."
   ::= { mplsLsrGroups 7 6 }

mplsHCOutSegmentPerfGroup OBJECT-GROUP
   OBJECTS { mplsOutSegmentHCOctets }
   STATUS  current
   DESCRIPTION
          "Object(s) providing performance information
           specific to out-segments for which the object
           mplsInterfaceOutOctets wraps around too
           quickly."
   ::= { mplsLsrGroups 8 7 }

mplsTSpecGroup OBJECT-GROUP
   OBJECTS { mplsTSpecIndex, mplsTSpecIfIndex, mplsTSpecDirection,
             mplsTSpecMaxRate, mplsTSpecMeanRate,
             mplsTSpecMaxBurstSize, mplsTSpecRowStatus }
   STATUS  current
   DESCRIPTION
          "Object(s) required for supporting  int-serv Int-Serv style
           resource reservation."
   ::= { mplsLsrGroups 9 8 }

mplsXCIsPersistentGroup OBJECT-GROUP
   OBJECTS { mplsXCIsPersistent }
   STATUS  current
   DESCRIPTION
          "Objects needed to support persistent cross-
           connects."
   ::= { mplsLsrGroups 10 9 }

mplsXCIsNotPersistentGroup OBJECT-GROUP
   OBJECTS { mplsXCIsPersistent }
   STATUS  current
   DESCRIPTION
          "Objects needed to support non-persistent cross-
           connects."
   ::= { mplsLsrGroups 11 10 }

mplsLsrNotificationGroup NOTIFICATION-GROUP
   NOTIFICATIONS { mplsInterfaceUp, mplsInterfaceDown,
                mplsInSegmentUp, mplsInSegmentDown,
                mplsOutSegmentUp, mplsOutSegmentDown,
                mplsXCUp, mplsXCDown }
   STATUS  current
   DESCRIPTION
          "Set of notifications implemented in this module.
           None is mandatory."
   ::= { mplsLsrGroups 12 11 }

-- End of MPLS-LSR-MIB
END

9. Security Considerations

   The  MIB  specified MPLS-LSR-MIB
END

10.   Security Considerations
   It is clear that this MIB is potentially useful for monitoring of
   MPLS LSRs. This MIB can also be used for configuration of certain
   objects, and anything that can be configured can be incorrectly
   configured, with potentially disastrous results.

   At this writing, no security holes have been identified beyond
   those that SNMP Security [SNMPArch] is itself intended to address.
   These relate to primarily controlled access to sensitive
   information and the ability to configure a device - or which might
   result from operator error, which is beyond the scope of any
   security architecture.

   There are a number of management objects defined in this MIB which
   have a MAX-ACCESS clause of read-write and/or read-create. Such
   objects may be considered sensitive or vulnerable in some network
   environments.  The support for SET operations in a non-secure
   environment without proper protection can have a negative effect
   on network operations. The use of SNMP Version 3 is recommended
   over prior versions, for configuration control, as its security
   model is improved.

   SNMPv1 or SNMPv2 are by themselves not a secure environment. Even
   if the network itself is secure (for example by using IPSec
   [IPSEC]), there is no control as to who on the secure network is
   allowed to access and GET/SET (read/change/create/delete) the
   objects in this MIB. It is recommended that the implementers
   consider the security features as provided by the SNMPv3
   framework. Specifically, the use of the User-based Security Model
   [SNMPv3USM] and the View- based Access Control [SNMPv3VACM] is
   recommended. It is then a customer/user responsibility to ensure
   that the SNMP entity giving access to an instance of this MIB is
   properly configured to give access to the objects only to those
   principals (users) that have legitimate rights to indeed GET or
   SET (change/create/delete) them.

   There are a number of managed objects in this document does not raise  any  security
   issues   other   than  those  present MIB that may contain
   information that may be sensitive from a business perspective, in
   that they represent a customer's interface to the MPLS  architecture
   [MPLSArch] network.
   Allowing uncontrolled access to these objects could result in
   malicious and unwanted disruptions of network traffic or those imposed by SNMP itself.

10. incorrect
   configurations for these customers. There are no objects that are
   particularly sensitive in their own right, such as passwords or
   monetary amounts.

11.   Acknowledgments
   We wish to thank Ron Bonica, Eric Gray, and Bonica of MCI, Dan Tappan of Cisco Systems,
   Bala Rajagopalan of NEC CCRL, and Eric Gray and Vasanthi
   Thirumalai of Lucent Technogies for their comments and input on
   this draft.

11. document.

12.   References

   [MPLSArch]    Rosen, E., Viswanathan, A., and R. Callon,
                 "Multiprotocol Label Switching Architecture",
                 Internet Draft    <draft-ietf-mpls-arch-05.txt>,
                 February <draft-ietf-mpls-arch-06.txt>,
                 August 1999.

   [MPLSFW]      Callon, R., Doolan, P., Feldman, N., Fredette, A.,
                 Swallow, G., and A. Viswanathan, "A Framework for
                 Multiprotocol Label Switching", Internet Draft
                 <draft-ietf-mpls-framework-02.txt>, November 1997.
                 <draft-ietf-mpls-framework-05.txt>, September 1999.

   [TEMIB]       Srinivasan, C., Viswanathan, A. and Nadeau, T.,
                 "MPLS Traffic Engineering Management Information
                 Base Using SMIv2", Internet Draft <draft-ietf-mpls-
                 te-mib-02.txt>, February 2000.

   [LDPMIB]      Cucchiara, J., Sjostrand, H., and J. Luciani, "
                 Definitions of Managed Objects for the
                 Multiprotocol Label Switching, Label Distribution
                 Protocol (LDP)", Internet Draft <draft-ietf-mpls-
                 ldp-mib-00.txt>, August 1998.
                 ldp-mib-04.txt>, February 2000.

   [LblStk]      Rosen, E., Rekhter, Y., Tappan, D., Farinacci, D.,
                 Federokow, G., Li, T., and A. Conta, "MPLS Label
                 Stack Encoding", Internet Draft <draft-ietf-mpls-
                 label-encaps-04.txt>, April
                 label-encaps-07.txt>, September 1999.

   [RSVPTun]     Awaduche, D., Berger, L., Der-Haw, G., Li, T.,
                 Swallow, G., and V. Srinivasan, "Extensions to RSVP
                 for LSP Tunnels", Internet Draft <draft-mpls-rsvp-
                 lsp-tunnel-02.txt>, March
                 lsp-tunnel-04.txt>, September 1999.

   [CRLDP]       B. Jamoussi (Editor), "Constraint-Based LSP Setup
                 using LDP", Internet Draft <draft-ietf-mpls-cr-ldp-
                 01.txt>, February
                 03.txt>, September 1999.

   [Assigned]    Reynolds, J., and J. Postel, "Assigned Numbers",
                 RFC 1700, October 1994. See also:
                 http://www.isi.edu/in-notes/iana/assignments/smi-
                 numbers

   [SNMPArch]    Harrington, D., Presuhn, R., and B. Wijnen, "An
                 Architecture for Describing SNMP Management
                 Frameworks", RFC 2271, January 1998.

   [SMIv1]       Rose, M., and K. McCloghrie, "Structure and
                 Identification of Management Information for TCP/IP-
                 based Internets", RFC 1155, May 1990.

   [SNMPv1MIBDef]Rose, M., and K. McCloghrie, "Concise MIB
                 Definitions", RFC 1212, March 1991.

   [SNMPv1Traps] M. Rose, "A Convention for Defining Traps for use
                 with the SNMP", RFC 1215, March 1991.

   [SMIv2]       Case, J., McCloghrie, K., Rose, M., and S.
                 Waldbusser, "Structure of Management Information
                 for Version 2 of the Simple Network Management
                 Protocol (SNMPv2)", RFC 1902, January 1996.

   [SNMPv2TC]    Case, J., McCloghrie, K., Rose, M., and S.
                 Waldbusser, "Textual Conventions for Version 2 of
                 the Simple Network Management Protocol (SNMPv2)",
                 RFC 1903, SNMP Research, Inc., Cisco Systems, Inc.,
                 January 1996.

   [SNMPv2Conf]  Case, J., McCloghrie, K., Rose, M., and S.
                 Waldbusser, "Conformance Statements for Version 2
                 of the Simple Network Management Protocol
                 (SNMPv2)", RFC 1904, January 1996.

   [SNMPv1]      Case, J., Fedor, M., Schoffstall, M., and J. Davin,
                 "Simple Network Management Protocol", RFC 1157, May
                 1990.

   [SNMPv2c]     Case, J., McCloghrie, K., Rose, M., and S.
                 Waldbusser, "Introduction to Community-based
                 SNMPv2", RFC 1901, January 1996.

   [SNMPv2TM]    Case, J., McCloghrie, K., Rose, M., and S.
                 Waldbusser, "Transport Mappings for Version 2 of
                 the Simple Network Management Protocol (SNMPv2)",
                 RFC 1906, January 1996.

   [SNMPv3MP]    Case, J., Harrington D., Presuhn R., and B. Wijnen,
                 "Message Processing and Dispatching for the Simple
                 Network Management Protocol (SNMP)", RFC 2272,
                 January 1998.

   [SNMPv3USM]   Blumenthal, U., and B. Wijnen, "User-based Security
                 Model (USM) for version 3 of the Simple Network
                 Management Protocol (SNMPv3)", RFC  2274,  January
                 1998. 2574, April
                 1999.

   [SNMPv2PO]    Case, J., McCloghrie, K., Rose, M., and S.
                 Waldbusser, "Protocol Operations for Version 2 of
                 the Simple Network Management Protocol (SNMPv2)",
                 RFC 1905, January 1996.

   [SNMPv3App]   Levi, D., Meyer, P., and B. Stewart, "SNMPv3
                 Applications", RFC 2273, January 1998 1998.

   [SNMPv3VACM]  Wijnen, B., Presuhn, R., and K. McCloghrie, "View-
                 based Access Control Model (VACM) for the Simple
                 Network Management Protocol (SNMP)", RFC   2275,
                 January 1998

12.   Authors's 2575,
                 April 1999.

   [IPSEC]       Kent, S., and Atkinson, R., "Security Architecture
                 for the Internet Protocol", RFC 2401, November
                 1998.

   [IFMIB]       McCloghrie, K., and F. Kastenholtz, "The Interfaces
                 Group MIB using SMIv2", RFC 2233, Nov. 1997

13.   Authors' Addresses

  Cheenu Srinivasan
  Tachion Network Technologies Networks, Inc.
  2 Meridian Road
  Eatontown, NJ 07724
  Phone: +1-732-542-7750 x234
  Email: cheenu@tachion.com

  Arun Viswanathan
   Lucent Technologies
   4D537, 101 Crawfords Corner Road
   Holmdel, NJ 07733
  Force10 Networks
  1440 McCarthy Blvd
  Milpitas, CA 95035
  Phone: +1-408-571-3516
  Email: arun@force10networks.com

  Thomas D. Nadeau
  Cisco Systems, Inc.
  250 Apollo Drive
  Chelmsford, MA 01824
  Phone: +1-732-332-5163 +1-978-244-3051
  Email: arunv@lucent.com tnadeau@cisco.com

14.   Full Copyright Statement

   Copyright (C) The Internet Society (2000). All Rights Reserved.

   This document and translations of it may be copied and furnished
   to others, and derivative works that comment on or otherwise
   explain it or assist in its implementation may be prepared,
   copied, published and distributed, in whole or in part, without
   restriction of any kind, provided that the above copyright notice
   and this paragraph are included on all such copies and derivative
   works.  However, this document itself may not be modified in any
   way, such as by removing the copyright notice or references to the
   Internet Society or other Internet organizations, except as needed
   for the  purpose of developing Internet standards in which case
   the procedures for copyrights defined in the Internet Standards
   process must be followed, or as required to translate it into
   languages other than English.

   The limited permissions granted above are perpetual and will not
   be revoked by the Internet Society or its successors or assigns.
   This document and the information contained herein is provided on
   an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET
   ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR
   IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
   THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
   WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.