Network Working Group                                   Thomas D. Nadeau
Internet Draft                                       Cisco Systems, Inc.
Expires: December 2002 February 2004
                                                       Cheenu Srinivasan
                                                  Parama Networks, Inc.
                                                          Bloomberg L.P.

                                                           Adrian Farrel
                                                   Movaz Networks, Inc.
                                                      Old Dog Consulting

                                                                Tim Hall
                                                        Edward
                                                             Ed Harrison
                                                    Data Connection Ltd.

                                                              June 2002

                                                             August 2003

         Generalized Multiprotocol Label Switching (GMPLS)
      Label Switch Switching Router (LSR) Management Information Base

            draft-ietf-ccamp-gmpls-lsr-mib-00.txt

              draft-ietf-ccamp-gmpls-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 RFC 2026
   [RFC2026]. 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.

   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 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 a portion of the Management Information Base (MIB)
   for use with network management protocols in the Internet community.
   In particular, it describes managed objects for to configure and/or
   monitor a Generalized Multiprotocol Label Switching (GMPLS) Label Switched Routers
   Switching Router (LSRs).

Table of Contents

   1. Changes and Pending Work Introduction                                       2
   1.1. Changes Since the Last Version                      2
 1.2. Pending Work                                        3
2. Introduction                                           3
 2.1. Migration Strategy                               2
   2. Terminology                                        3
   3. The SNMP Management Framework                          4                      3
   4. Terminology                                            5
5. Feature List                                           5
6. Outline                                            3
   4.1. Summary of the GMPLS LSR MIB                                     5
7. Module              4
   5. Bidirectional LSPs                                     5
8.                                 4
   6. Example of LSP Setup                                   6
9.                               5
   7. GMPLS Label Switching Router MIB Definitions           7
10.       6
   8. GMPLS Label MIB Definitions                          13
11.                       14
   9. Security Considerations                              22
12.                           25
   10. Acknowledgments                                      23
13.                                  26
   11. IANA Considerations                              27
   11.1. IANA Considerations for GMPLS-LSR-STD-MIB      27
   11.2. IANA Considerations FOR GMPLS-LABEL-STD-MIB    27
   12. References                                           23
 13.1.                                       27
   12.1. Normative References                              23
 13.2.                           27
   12.2. Informational References                          25
14.                       28
   13. Authors' Addresses                                   27
15.                               29
   14. Full Copyright Statement                             27

1.                         30
   15. Intellectual Property Notice                     30
   16. Changes and Pending Work

   This section must be removed before the draft progresses
   to RFC.

1.1.  Changes Since the Last Version

   This is the first version of this draft.

1.2.                         31
   16.1. Pending Work

   The following work items have been identified for this
   draft.  They will be addressed in a future version.

   -  Expand conformance statements to give one for
      monitoring only, and one for monitoring and control.

   -  Bring references up to date, include all drafts
      referenced from this document, and exclude those that
      are not referenced.

   -- Provide support for monitoring tunnel resources in
      GMPLS systems.  For example, SONET/SDH or G.709.  This
      might be done through an arbitrary RowPointer to an
      external MIB.

   -  Extend mplsTrafficParamsTable from the MPLS-LSR-MIB to
      support GMPLS traffic parameters for signaled and
      static LSPs.

   -  Extendthe performance tables from the MPLS-LSR-MIB for
      technology-specific GMPLS LSPs.

2.                                   31

1. Introduction

   This memo defines a 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 a
   Generalized Multiprotocol Label Switching (GMPLS) [GMPLSArch] Label
   Switching Routers
   (LSRs). Router (LSR).

   Comments should be made directly to the CCAMP mailing list at
   ccamp@ops.ietf.org.

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED",  "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in RFC 2119, reference
   [RFC2119].

2.1.

1.1. Migration Strategy

   This MIB module extends the Label Switching Router MIB module defined
   for use with MPLS [LSRMIB].  The only changes made are additions for
   support of GMPLS or changes that are necessary to support the
   increased complexity of a GMPLS system.

   The companion document modeling and managing GMPLS based traffic
   engineering [GMPLSTEMIB] extends the MPLS TE MIB module [TEMIB] with
   the same intentions.

   Textual conventions and OBJECT-IDENTIFIERS are defined in
   [GMPLSTCMIB] which extends the set of textual conventions originally
   defined in [TCMIB].

3. The SNMP Management Framework

   The SNMP Management Framework presently consists of five
   major components:

   -  An overall architecture, described in RFC 2571
      [RFC2571].

   -  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 STD 16, RFC
      1155 [RFC1155], STD 16, RFC 1212 [RFC1212] and STD 16,
      RFC 1215 [RFC1215].  The second version, called SMIv2,
      is described in STD 58, RFC 2578 [RFC2578], STD 58,
      RFC 2579 [RFC2579] and STD 58, RFC 2580 [RFC2580].

   -  Message protocols for transferring management
      information.  The first version of the SNMP message
      protocol is called SNMPv1 and described in STD 15, RFC
      1157 [RFC1157].  A second version of the SNMP message
      protocol, which is not an Internet standards track
      protocol, is called SNMPv2c and described in RFC 1901
      [RFC1901] and RFC 1906 [RFC1906].  The third version
      of the message protocol is called SNMPv3 and described
      in RFC 1906 [RFC1906], RFC 2572 [RFC2572] and RFC 2574
      [RFC2574].

   -  Protocol operations for accessing management
      information.  The first set of protocol operations and
      associated PDU formats is described in STD 15, RFC
      1157 [RFC1157].  A second set of protocol operations
      and associated PDU formats is described in RFC 1905
      [RFC1905].

   -  A set of fundamental applications described in RFC
      2573 [RFC2573] and the view-based access control
      mechanism described in RFC 2575 [RFC2575].

   A more detailed introduction to the current SNMP
   Management Framework can be found in RFC 2570 [RFC2570].

   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 information in SMIv2 will be converted into
   textual descriptions in SMIv1 during the translation
   process.  However, this loss of machine readable
   information is not considered to change the semantics of
   the MIB.

4.

2. Terminology

   This document uses terminology from the document describing the MPLS
   architecture [RFC3031]. [RFC3031] and the GMPLS architecture [GMPLSArch].

   A label switched path (LSP) is modeled as a connection consisting of
   one or more incoming segments (in-segments) and/or one or more
   outgoing segments (out-segments) at a
   Label Switching Router (LSR). an LSR. The association or
   interconnection of the in-segments and out-segments is accomplished
   by using a cross-connect. We use the terminology "connection" and
   "LSP" interchangeably where the meaning is clear from the context.

5. Feature List

   The GMPLS Label Switching Router MIB

      in-segment     This is analogous to a GMPLS label on an interface.
      out-segment    This is designed analogous to
   satisfy a GMPLS label on an interface.
      cross-connect  This describes the following requirements conceptual connection between a
                     set of in-segments and constraints out-segments.
                     Note that either set may be 0; that is, a cross-
                     connect may connect only out-segments together with
                     no in-segments in
   addition the case where an LSP is
                     originating on an LSR.

3. The SNMP Management Framework

   For a detailed overview of the documents that describe the current
   Internet-Standard Management Framework, please refer to those addressed by section 7 of
   RFC 3410 [RFC3410].

   Managed objects are accessed via a virtual information store, termed
   the MPLS Management Information Base or MIB.  MIB objects are generally
   accessed through the Simple Network Management Protocol (SNMP).
   Objects in the MIB are defined using the mechanisms defined in the
   Structure of Management Information (SMI).  This memo specifies a
   MIB module that is compliant to the SMIv2, which is described in STD
   58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC
   2580 [RFC2580].

4. Outline

   Configuring statically provisioned GMPLS LSPs through an LSR MIB: involves
   the following steps:

   -  The  Configuring an interface using the MPLS LSR MIB supports both manually configured LSPs as well
      as those configured via any module.

   -  Enabling GMPLS signaling protocol. on GMPLS capable interfaces using this MIB module.

   -  The  Configuring in-segments and out-segments using the MPLS LSR MIB supports
      module.

   -  Configuring GMPLS extensions to the enabling in-segments and disabling of GMPLS
      capability on out-segments
      using this MIB module.

   -  Setting up the cross-connect table in the MPLS LSR MIB module to
      associate segments and/or to indicate connection origination and
      termination.

   -  Optionally setting up labels in the label table in this MIB module
      if the textual convention
      MplsLabel is not capable interfaces of an LSR.

6. holding the required label (for
      example, if the label requires more than 32 bits to encode it), or
      if the operator wishes to disambiguate GMPLS label types.

   -  Optionally specifying label stack actions in the MPLS LSR MIB
      module.

   -  Optionally specifying segment traffic parameters in the MPLS LSR
      MIB module.

4.1. Summary of the GMPLS LSR MIB Module

   The MIB tables in this draft are: MIB module are as follows.

   -  The interface configuration table
      (gmplsInterfaceConfTable), (gmplsInterfaceTable), which
      extends
      mplsInterfaceConfTable mplsInterfaceTable to enable the GMPLS protocol on
      MPLS-capable MPLS-
      capable interfaces.

   -  The in-segment (gmplsInSegmentTable) and out-segment
      (gmplsOutSegmentTable) tables extend mplsInSegmentTable and
      mplsOutSegmentTable to configuring GMPLS-specific parameters for
      LSP segments at an LSR.

   -  The gmplsLabelTable extends mplsLabelTable and allows Generalized
      Labels to be defined and managed in a central location.
      Generalized Labels can be of variable length and have distinct
      bit-by-bit interpretations according to the use that is made of
      them.

   These tables are described in the subsequent sections.

7.

5. Bidirectional LSPs

   This MIB supports bidirectional LSPs as required for GMPLS.
   A single entry in the value of mplsXCIndex is shared by all of the segments for
   the entire bidirectional LSP. This facilitates a simple reference
   from [TEMIB] and [GMPLSTEMIB], and makes fate-sharing more obvious.

   It is, however, important that the direction of segments is
   understood to avoid connecting all in-segments to all out-segments.
   This is achieved by an object in each segment that indicates the
   direction of the segment with respect to data flow.

   A segment that is marked as 'forward' carries data from the 'head' of
   the LSP to the 'tail'. A segment marked as 'reverse' carries data in
   the reverse direction.

   Where an LSP is signaled using a conventional signaling protocol, the
   'head' of the LSP is the source of the signaling (also known as the
   ingress) and the 'tail' is the destination (also known as the
   egress). For manually configured LSPs an arbitrary decision must be
   made about which segments are 'forward' and which 'reverse'. For
   consistency this decision should be made across all LSRs that
   participate in the LSP by assigning 'head' and 'tail' ends to the
   LSP.

8.

6. Example of LSP Setup

   In this section we provide a brief example of using the MIB objects
   described in section 9. 9 to set up an 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. A prerequisite is an
   understanding of [LSRMIB].

   Suppose that one would like to manually create a best-
   effort, bi-directional best-effort, bi-
   directional LSP. Assume that, in the forward direction, the LSP
   enters the LSR via MPLS interface A with ifIndex 12 and exits the LSR
   via MPLS interface B with ifIndex 13. For the reverse direction, we
   assume the LSP enters via interface B and leaves via interface A
   (i.e. the forward and reverse directions use the same bi-
   directional bi-directional
   interfaces). Let us also assume that we do not wish to have a label
   stack beneath the top label on the outgoing labeled packets. The
   following example illustrates which rows and corresponding objects
   might be created to accomplish this.

   First, the traffic parameter entries must be set-up for both
   segments. These are configured entirely in the MPLS LSR MIB through
   the mplsTrafficParamTable.

   Note that for a bi-directional LSP, the segments in the reverse
   direction MAY share the traffic parameter entries (and hence
   resources) with the segments in the forward direction.

   We must next create the appropriate in-segment and out-
   segment out-segment
   entries with suitable traffic parameters by pointing to the
   appropriate traffic parameter entries that we have just created. This
   is also done in the MPLS LSR MIB using mplsInSegmentTable and
   mplsOutSegmentTable.

   These table entries are extended by entries in gmplsInSegmentTable
   and gmplsOutSegmentTable. Note that the nature of the 'extends'
   relationship is that the entry in gmplsInSegmentTable has the same
   index values as the entry in mplsInSegmentTable. Similarly, the entry
   in gmplsOutSegmentTable has the same index values as the entry in
   mplsOutSegmentTable.

   First for the forward direction:

   In gmplsInSegmentTable
   {
     gmplsInSegmentDirection          = forward (1),
   }

   In gmplsOutSegmentTable
   {
     gmplsOutSegmentDirection         = forward (1)
   }
   Next for the reverse direction:

   In gmplsInSegmentTable
   {
     gmplsInSegmentDirection          = reverse (2)
   }

   In gmplsOutSegmentTable
   {
     gmplsOutSegmentDirection         = reverse (2)
   }

   Next, two cross-connect entries are created in the mplsXCTable of the
   MPLS LSR MIB, thereby associating the newly created segments
   together.

9.

7. GMPLS Label Switching Router MIB Definitions

GMPLS-LSR-MIB

   GMPLS-LSR-STD-MIB DEFINITIONS ::= BEGIN

   IMPORTS
     MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE,
   experimental, Unsigned32, Unsigned32
       FROM SNMPv2-SMI
     MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP OBJECT-GROUP
       FROM SNMPv2-CONF
     GmplsSegmentDirection
       FROM GMPLS-TC-MIB GMPLS-TC-STD-MIB
   ;

gmplsLsrMIB

   gmplsLsrStdMIB MODULE-IDENTITY
     LAST-UPDATED
      "200206240900Z
       "200308190900Z "  -- 24 June 2002 19 August 2003 9:00:00 GMT"
     ORGANIZATION
       "Common Control And Management Protocols (CCAMP)
        Working Group"
     CONTACT-INFO
       "       Thomas D. Nadeau
      Postal:
               Cisco Systems, Inc.
              250 Apollo Drive
              Chelmsford, MA 01824
         Tel: +1-978-244-3051
        Email: tnadeau@cisco.com

               Cheenu Srinivasan
      Postal: Parama Networks, Inc.
              1030 Broad Street
              Shrewsbury, NJ 07702
         Tel: +1-732-544-9120 x731
               Bloomberg L.P.
        Email: cheenu@paramanet.com
         Tel: +1-732-544-9120x731 cheenu@bloomberg.net

               Adrian Farrel
      Postal: Movaz Networks, Inc.
              7926 Jones Branch Drive
              McLean, VA 22102
         Tel: +1-703-847-1867
               Old Dog Consulting
        Email: afarrel@movaz.com

              Edward adrian@olddog.co.uk

               Ed Harrison
      Postal:
               Data Connection Ltd.
              100 Church Street
              Enfield, Middlesex
              EN2 6BQ, United Kingdom
         Tel: +44-20-8366-1177
        Email: eph@dataconnection.com ed.harrison@dataconnection.com

               Tim Hall
      Postal:
               Data Connection Ltd.
              100 Church Street
              Enfield, Middlesex
              EN2 6BQ, United Kingdom
         Tel: +44-20-8366-1177
        Email: timhall@dataconnection.com

      Email comments
        Comments about this document should be emailed direct to the
        CCAMP WG Mailing List working group mailing list at
      ccamp@ops.ietf.org." ccamp@ops.ietf.org"
     DESCRIPTION
       "This MIB module contains managed object definitions
        for the Generalized Multiprotocol Label Switching
        (GMPLS)
        Router." Router as defined in: Ashwood-Smith et al.,
        Generalized Multiprotocol Label Switching (GMPLS)
        Architecture, Internet Draft <draft-many-gmpls-
        architecture-01.txt>, March 2001, work in progress.

        Copyright (C) The Internet Society (2003).  This
        version of this MIB module is part of RFCXXX; see
        the RFC itself for full legal notices."

     -- Revision history.
     REVISION
       "200206240900Z"
       "200308190900Z"  -- 24 June 2002 9:00:00 19 August 2003 09:00:00 GMT
   DESCRIPITION
       "First revision draft version."
   -- Above revision history to be replaced as below
   --  REVISION "yyyymmddhhmmZ"
   --
     DESCRIPTION
       "Initial version, revision, published as part of RFC xxxx"
   -- xxxx to be assigned by RFC Editor XXXX."
   ::= { experimental XXX gmplsStdMIB xx }

   -- To Be Assigned by IANA Top level components of this MIB module.

   -- Notifications
   -- no notifications are currently defined.
   gmplsLsrNotifications OBJECT IDENTIFIER ::= { gmplsLsrStdMIB 0 }

   -- Tables, Scalars
   gmplsLsrObjects       OBJECT IDENTIFIER ::= { gmplsLsrMIB gmplsLsrStdMIB 1 }

   -- Notifications
-- Conformance
   gmplsLsrConformance   OBJECT IDENTIFIER ::= { gmplsLsrMIB gmplsLsrStdMIB 2 }

   -- GMPLS Interface Configuration Table.

gmplsInterfaceConfTable

   gmplsInterfaceTable OBJECT-TYPE
     SYNTAX        SEQUENCE OF GmplsInterfaceConfEntry GmplsInterfaceEntry
     MAX-ACCESS    not-accessible
     STATUS        current
     DESCRIPTION
       "This table specifies per-interface GMPLS capability
        and associated information. It extends the
        information in
        mplsInterfaceConfTable." mplsInterfaceTable."
     ::= { gmplsLsrObjects 1 }

gmplsInterfaceConfEntry

   gmplsInterfaceEntry OBJECT-TYPE
     SYNTAX        GmplsInterfaceConfEntry        GmplsInterfaceEntry
     MAX-ACCESS    not-accessible
     STATUS        current
     DESCRIPTION
       "An entry
       "A conceptual row in this table is created
        automatically by an LSR for every interface capable
        of supporting
        GMPLS.  Each entry GMPLS and which is configured to do
        so. A conceptual row in this table will exist if and
        only if a corresponding entries entry in
        mplsInterfaceConfTable mplsInterfaceTable
        exists, and a corresponding entry in ifTable exists. exists
        with ifType = mpls(166). If the associated entry in
        mplsInterfaceConfTabel or
        ifTable is operationally disabled (thus removing the
        GMPLS capabilities on the interface) or the entry in
        mplsInterfaceTable is deleted, the corresponding
        entry in this table must also MUST be deleted shortly
        thereafter.

        The indexing is the same as that for
        mplsInterfaceConfTabel.
        mplsInterfaceTable. Thus, the entry with index 0
        represents the per-platform label space and contains
        parameters that apply to all interfaces that
        participate in the per-platform label space."
     INDEX { mplsInterfaceConfIndex mplsInterfaceIndex }
   ::= { gmplsInterfaceConfTable gmplsInterfaceTable 1 }

GmplsInterfaceConfEntry

   GmplsInterfaceEntry ::= SEQUENCE {

      gmplsInterfaceConfSignalingCaps
     gmplsInterfaceSignalingCaps      BITS
   }

""gmplsInterfaceConfSignalingCaps

   gmplsInterfaceSignalingCaps OBJECT-TYPE
     SYNTAX  BITS {
       rsvp-gmpls (1),
       crldp-gmpls (2), -- note the use of CR-LDP is deprecated
       other-gmpls (3)
     }
     MAX-ACCESS   read-create
     STATUS       current
     DESCRIPTION
       "Defines the signaling capabilities on this
        interface. Multiple bits may legitimately be set at
        once. Setting no bits implies that GMPLS signaling
        cannot be performed on this interface and all LSPs
        must be manually provisioned."
   ::= { gmplsInterfaceConfEntry gmplsInterfaceEntry 1 }

   -- End of gmplsInterfaceConfTable gmplsInterfaceTable

   -- In-segment table.

   gmplsInSegmentTable  OBJECT-TYPE
     SYNTAX        SEQUENCE OF GmplsInSegmentEntry
     MAX-ACCESS    not-accessible
     STATUS        current
     DESCRIPTION
       "This table extends the mplsInSegmentTable to provide
        GMPLS-specific information about incoming segments
        to an LSR."
   ::= { gmplsLsrObjects 2 }

   gmplsInSegmentEntry  OBJECT-TYPE
     SYNTAX        GmplsInSegmentEntry
     MAX-ACCESS    not-accessible
     STATUS        current
     DESCRIPTION
       "An entry in this table extends the representation of
        an incoming segment represented by an entry in
        mplsInSegmentTable. An entry can be created by a
        network administrator or an SNMP agent, or a GMPLS
        signaling protocol.
        "

        Note that the storage type for this entry SHOULD be
        inherited from the corresponding entry in the
        mplsInSegmentTable given by the value of the
        mplsInSegmentStorageType object."
     INDEX { mplsInSegmentIndex }
   ::= { gmplsInSegmentTable 1 }

   GmplsInSegmentEntry ::= SEQUENCE {
     gmplsInSegmentDirection   GmplsSegmentDirection
   }

   gmplsInSegmentDirection OBJECT-TYPE
     SYNTAX        GmplsSegmentDirection
     MAX-ACCESS    read-create
     STATUS        current
     DESCRIPTION
       "This variable object indicates the direction of data flow on
        this segment." segment. This object cannot be modified if
        mplsInSegmentRowStatus for the associated entry in
        the mplsInSegmentTable is active(1)."
     DEFVAL        { forward }
   ::= { gmplsInSegmentEntry 1 }

   -- End of gmplsInSegmentTable

   -- Out-segment table.

   gmplsOutSegmentTable  OBJECT-TYPE
     SYNTAX        SEQUENCE OF GmplsOutSegmentEntry
     MAX-ACCESS    not-accessible
     STATUS        current
     DESCRIPTION
       "This table extends the mplsOutSegmentTable to
        provide GMPLS-specific information about outgoing
        segments from an LSR."
   ::= { gmplsLsrObjects 3 }

   gmplsOutSegmentEntry  OBJECT-TYPE
     SYNTAX        GmplsOutSegmentEntry
     MAX-ACCESS    not-accessible
     STATUS        current
     DESCRIPTION
       "An entry in this table extends the representation of
        an outgoin outgoing segment represented by an entry in
        mplsOutSegmentTable. An entry can be created by a
        network administrator or an SNMP agent, or a GMPLS
        signaling protocol.
        "
        Note that the storage type for this entry SHOULD be
        inherited from the corresponding entry in the
        mplsOutSegmentTable given by the value of the
        mplsOutSegmentStorageType object."
     INDEX  { mplsOutSegmentIndex }
   ::= { gmplsOutSegmentTable 1 }
   GmplsOutSegmentEntry ::= SEQUENCE {
     gmplsOutSegmentDirection     GmplsSegmentDirection,
     gmplsOutSegmentTTLDecrement  Unsigned32
   }

"gmplsOutSegmentDirection

   gmplsOutSegmentDirection OBJECT-TYPE
     SYNTAX        GmplsSegmentDirection
     MAX-ACCESS    read-create
     STATUS        current
     DESCRIPTION
       "This variable object indicates the direction of data flow on
        this segment. This object cannot be modified if
        mplsOutSegmentRowStatus for the associated entry in
        the mplsOutSegmentTavle mplsOutSegmentTable is active(1)."
     DEFVAL  { forward }
   ::= { gmplsOutSegmentEntry 1 }

   gmplsOutSegmentTTLDecrement OBJECT-TYPE
     SYNTAX        Unsigned32 (0..255)
     MAX-ACCESS    read-create
     STATUS        current
     DESCRIPTION
       "This variable object indicates the amount by which to
        decrement the TTL of any payload packets forwarded
        on this segment if per-hop decrementing is being
        done.

        A value of zero indicates that no decrement should
        be made or that per-hop decrementing is not in
        force.

        See the gmplsTunnelTTLDecrement object in the
        gmplsTunnelTable of [GMPLSTEMIB] for a value by
        which to decrement the TTL for the whole of a
        tunnel.

        This object cannot be modified if
        mplsOutSegmentRowStatus for the associated entry in
        the mplsOutSegmentTavle mplsOutSegmentTable is active(1)."
     DEFVAL  { 0 }
   ::= { gmplsOutSegmentEntry 2 }

   -- End of gmplsOutSegmentTable

""

   -- Module compliance.

   gmplsLsrGroups
     OBJECT IDENTIFIER ::= { gmplsLsrConformance 1 }

   gmplsLsrCompliances
     OBJECT IDENTIFIER ::= { gmplsLsrConformance 2 }

gmplsLsrModuleCompliance
   -- Compliance requirement for fully compliant implementations.

   gmplsLsrModuleFullCompliance MODULE-COMPLIANCE
     STATUS current
     DESCRIPTION
       "Compliance statement for agents that provide full
        support the GMPLS for GMPLS-LSR-STD-MIB."

     MODULE IF-MIB -- The Interfaces Group MIB, RFC 2863.

     MANDATORY-GROUPS {
       ifGeneralInformationGroup,
       ifCounterDiscontinuityGroup
     }

     MODULE MPLS-LSR-STD-MIB û The MPLS LSR MIB." MIB

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

     MODULE -- this module

     MANDATORY-GROUPS    {
       gmplsInterfaceGroup,
       gmplsInSegmentGroup,
       gmplsOutSegmentGroup
     }

     -- The mandatory groups have gmplsInSegmentTable

     OBJECT      gmplsInSegmentDirection
     SYNTAX      GmplsSegmentDirection
     MIN-ACCESS  read-write
     DESCRIPTION
       "Only forward(1) needs to be implemented
   -- supported by all LSRs
        implementations that only support GMPLS.  However, they unidirectional
        LSPs."

     -- may all gmplsOutSegmentTable

     OBJECT      gmplsOutSegmentDirection
     SYNTAX      GmplsSegmentDirection
     MIN-ACCESS  read-write
     DESCRIPTION
       "Only forward(1) needs to be supported as by
        implementations that only support unidirectional
        LSPs."
     OBJECT      gmplsOutSegmentTTLDecrement
     SYNTAX      Unsigned32 (0..255)
     MIN-ACCESS  read-only objects in
   -- the case where manual configuration
     DESCRIPTION
       "Write access is unsupported. not required."

   ::= { gmplsLsrCompliances 1 }

   -- Compliance requirement for implementations that provide read-only
   -- access.

   gmplsLsrModuleReadOnlyCompliance MODULE-COMPLIANCE
     STATUS current
     DESCRIPTION
       "Compliance requirement for implementations that only
        provide read-only support for GMPLS-LSR-STD-MIB. Such
        devices can then be monitored but cannot be configured
        using this MIB modules."

     MODULE IF-MIB -- The interfaces Group MIB, RFC 2863

     MANDATORY-GROUPS {
       ifGeneralInformationGroup,
       ifCounterDiscontinuityGroup
     }

     MODULE MPLS-LSR-STD-MIB

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

     MODULE -- this module

     MANDATORY-GROUPS {
       gmplsInterfaceGroup,
       gmplsInSegmentGroup,
      gmplsOutSegmentGroup,
      gmplsInterfaceGroup
       gmplsOutSegmentGroup
     }

   "--

     -- gmplsInterfaceGroup

     OBJECT      gmplsInterfaceSignalingCaps
     SYNTAX      BITS
     MIN-ACCESS  read-only
     DESCRIPTION
       "Write access is not required."
     -- gmplsInSegmentTable

     OBJECT      gmplsInSegmentDirection
     SYNTAX      GmplsSegmentDirection
     MIN-ACCESS  read-only
     DESCRIPTION
       "Only
       "Write access is not required. Only forward(1) needs
        to be supported." supported by implementations that only support
        unidirectional LSPs."

     -- gmplsOutSegmentTable

     OBJECT      gmplsOutSegmentDirection
     SYNTAX      GmplsSegmentDirection
     MIN-ACCESS  read-only
     DESCRIPTION
       "Only
       "Write access is not required. Only forward(1) needs
        to be supported." supported by implementations that only support
        unidirectional LSPs."

     OBJECT      gmplsOutSegmentTTLDecrement
     SYNTAX      Unsigned32 (0..255)
     MIN-ACCESS  read-only
     DESCRIPTION
       "Write access is not required."

   ::= { gmplsLsrCompliances 1 2 }

   -- Units of conformance.

   gmplsInterfaceGroup OBJECT-GROUP
     OBJECTS {
      gmplsInterfaceConfSignalingCaps
       gmplsInterfaceSignalingCaps
     }
     STATUS  current
     DESCRIPTION
       "Collection of objects needed for GMPLS interface
        configuration and performance information."
   ::= { gmplsLsrGroups 1 }

   gmplsInSegmentGroup  OBJECT-GROUP
     OBJECTS {
       gmplsInSegmentDirection
     }
     STATUS  current
     DESCRIPTION
       "Collection of objects needed to implement a GMPLS
        in-segment."
   ::= { gmplsLsrGroups 2 }
   gmplsOutSegmentGroup  OBJECT-GROUP
     OBJECTS {
       gmplsOutSegmentDirection,
       gmplsOutSegmentTTLDecrement
     }
     STATUS  current
     DESCRIPTION
       "Collection of objects needed to implement a GMPLS
        out-segment."
   ::= { gmplsLsrGroups 3 }

   END

10.

8. GMPLS Label MIB Definitions

GMPLS-LABEL-MIB

   GMPLS-LABEL-STD-MIB DEFINITIONS ::= BEGIN

   IMPORTS
     MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE,
   experimental, Unsigned32
       FROM SNMPv2-SMI
     MODULE-COMPLIANCE, OBJECT-GROUP
       FROM SNMPv2-CONF
     RowStatus, StorageType
       FROM SNMPv2-TC
     InterfaceIndexOrZero
       FROM IF-MIB
     MplsLabel
       FROM MPLS-TC-STD-MIB
     GmplsGeneralizedLabelTypes,
GmplsGeneralizedLabelSubtypes, GmplsFreeformLabel
       FROM GMPLS-TC-MIB GMPLS-TC-STD-MIB
   ;

gmplsLabelMIB

   gmplsLabelStdMIB MODULE-IDENTITY
     LAST-UPDATED
      "200206240900Z
       "200308190900Z "  -- 24 June 2002 9:00:00" 19 August 2003 9:00:00 GMT"
     ORGANIZATION
       "Common Control And Management Protocols (CCAMP)
        Working Group"
     CONTACT-INFO
       "       Thomas D. Nadeau
      Postal:
               Cisco Systems, Inc.
              250 Apollo Drive
              Chelmsford, MA 01824
         Tel: +1-978-244-3051
        Email: tnadeau@cisco.com

               Cheenu Srinivasan
      Postal: Parama Networks, Inc.
              1030 Broad Street
              Shrewsbury, NJ 07702
         Tel: +1-732-544-9120 x731
               Bloomberg L.P.
        Email: cheenu@paramanet.comTel: +1-732-544-9120x731 cheenu@bloomberg.net

               Adrian Farrel
      Postal: Movaz Networks, Inc.
              7926 Jones Branch Drive
              McLean, VA 22102
         Tel: +1-703-847-1867
               Old Dog Consulting
        Email: afarrel@movaz.com

              Edward adrian@olddog.co.uk

               Ed Harrison
      Postal:
               Data Connection Ltd.
              100 Church Street
              Enfield, Middlesex
              EN2 6BQ, United Kingdom
         Tel: +44-20-8366-1177
        Email: eph@dataconnection.com ed.harrison@dataconnection.com

               Tim Hall
      Postal:
               Data Connection Ltd.
              100 Church Street
              Enfield, Middlesex
              EN2 6BQ, United Kingdom
         Tel: +44-20-8366-1177 Connection Ltd.
        Email: timhall@dataconnection.com" timhall@dataconnection.com
        Comments about this document should be emailed direct to the
        CCAMP working group mailing list at ccamp@ops.ietf.org"
     DESCRIPTION
       "This MIB module contains managed object definitions
        for labels within GMPLS systems."

     -- Revision history.
     REVISION
       "200206240900Z "  -- 24 June 2002 9:00:00
        GMT"
   DESCRIPTION
       "Initial version."
   -- Above revision history to be replaced as below
   -- REVISION "yyyymmddhhmmZ"
       "200308190900Z"  -- 19 August 2003 09:00:00 GMT
     DESCRIPTION
       "Initial version, revision, published as part of RFC xxxx"
   -- xxxx to be assigned by RFC Editor XXXX."
   ::= { experimental XXX gmplsStdMIB 2 }

   -- To Be Assigned by IANA

-- Top level components of this MIB. MIB module.

   -- tables, scalars
gmplsLabelObjects Notifications
   -- no notifications are currently defined.
   gmplsLsrNotifications   OBJECT IDENTIFIER ::= {
gmplsLabelMIB gmplsLabelStdMIB 0 }
gmplsLabelConformance

   -- Tables, Scalars
   gmplsLabelObjects       OBJECT IDENTIFIER ::= {
gmplsLabelMIB gmplsLabelStdMIB 1 }

   -- Conformance
   gmplsLabelConformance   OBJECT IDENTIFIER ::= { gmplsLabelStdMIB 2 }

   -- GMPLS Label Table.

   gmplsLabelTable OBJECT-TYPE
     SYNTAX        SEQUENCE OF GmplsLabelEntry
     MAX-ACCESS    not-accessible
     STATUS        current
     DESCRIPTION
       "Table of GMPLS Labels.  This table extends
        mplsLabelTable to handle allows the
        representation of the more complex label forms
        required for GMPLS. GMPLS which cannot be held within the
        textual convention MplsLabel. That is labels that
        cannot be encoded within 32 bits. It is,
        nevertheless also capable of holding 32 bit labels
        or regular MPLS labels if desired.

        Each entry in this table represents an individual
        GMPLS label value.  Labels in the tables in other
        MIBs are referred to using index entries row pointer into mplsLabelTable. this
        table. The indexing of this table is identical.
        In effect, this table taken together with
        mplsLabelTable provides an integer mapping for label values that may be more complex
        than simple integers."
        arbitrary indexing and also for concatenation of
        labels. "
   ::= { gmplsLabelObjects 1 }

   gmplsLabelEntry OBJECT-TYPE
     SYNTAX        GmplsLabelEntry
     MAX-ACCESS    not-accessible
     STATUS        current
     DESCRIPTION
       "An entry in this table extends represents a single label
        value. There are three indexes into the table.
        -  The interface index may be helpful to distinguish
           which labels are in use on which interfaces or to
           handle cases where there are a very large number
           of labels in use in the system. When label
           representation is desired to apply to the whole
           system or when it is not important to distinguish
           labels by their interfaces, this index MAY be set
           to zero.
        -  The label index provides a way of identifying the
           label.
        -  The label sub-index is only used for concatenated
           labels. It identifies each component label. When
           non-concatenated labels are used, this index
           SHOULD be set to zero.

        A storage type object is supplied to control the
        storage type for each entry, but implementations
        should note that the storage type of conceptual rows
        in other tables that include row pointers to an
        entry in this table SHOULD dictate the storage type
        of the rows in this table where the label
        defintion row in mplsLabelTable for use with
        certain types of switching appropriate to
        GMPLS." the other
        table is more persistent."
     INDEX { mplsLabelInterface, mplsLabelIndex,
gmplsSublabelIndex
       gmplsLabelInterface,
       gmplsLabelIndex,
       gmplsLabelSubindex }
   ::= { gmplsLabelTable 1 }

   GmplsLabelEntry ::= SEQUENCE {
  gmplsSublabelIndex
     gmplsLabelInterface           InterfaceIndexOrZero,
     gmplsLabelIndex               Unsigned32,
     gmplsLabelSubindex            Unsigned32,
     gmplsLabelType                GmplsGeneralizedLabelTypes,
  gmplsLabelSubtype  GmplsGeneralizedLabelSubtypes,
  gmplsPortWavelengthLabel
     gmplsLabelMplsLabel           MplsLabel,
     gmplsLabelPortWavelength      Unsigned32,
  gmplsFreeformLength
     gmplsLabelFreeformLength      INTEGER,
  gmplsFreeformLabel
     gmplsLabelFreeform            GmplsFreeformLabel,
  gmplsSonetSdhSignalIndex
     gmplsLabelSonetSdhSignalIndex INTEGER,
  gmplsSdhVc
     gmplsLabelSdhVc               INTEGER,
  gmplsSdhVcBranch
     gmplsLabelSdhVcBranch         INTEGER,
  gmplsSonetSdhBranch
     gmplsLabelSonetSdhBranch      INTEGER,
  gmplsSonetSdhGroupBranch
     gmplsLabelSonetSdhGroupBranch INTEGER,
  gmplsWavebandId
     gmplsLabelWavebandId          Unsigned32,
  gmplsWavebandStartLabel
     gmplsLabelWavebandStartLabel  Unsigned32,
  gmplsWavebandEndLabel
     gmplsLabelWavebandEndLabel    Unsigned32,
     gmplsLabelRowStatus           RowStatus,
     gmplsLabelStorageType         StorageType
   }

   gmplsLabelInterface OBJECT-TYPE
     SYNTAX        InterfaceIndexOrZero
     MAX-ACCESS    not-accessible
     STATUS        current
     DESCRIPTION
       "The interface on which this label is used. If the
        label has or could have applicability across the
        whole system, this object SHOULD be set to zero."
   ::= { gmplsLabelEntry 1 }
   gmplsLabelIndex OBJECT-TYPE
     SYNTAX        Unsigned32 (0..4294967295)
     MAX-ACCESS    not-accessible
     STATUS        current
     DESCRIPTION
       "An arbitrary index into the table to identify a
        label.
        Note that implementations that are representing 32
        bit labels within this table MAY choose to align
        this index with the value of the label, but should
        be aware of the implications of sparsely populated
        tables."
   ::= { gmplsLabelEntry 2 }

gmplsSublabelIndex

   gmplsLabelSubindex OBJECT-TYPE
     SYNTAX        Unsigned32 (1..4294967295) (0..4294967295)
     MAX-ACCESS    read-only    not-accessible
     STATUS        current
     DESCRIPTION
       "In conjunction with mplsLabelInterface gmplsLabelInterface and
        mplsLabelIndex,
        gmplsLabelIndex, this object uniquely identifies
        this row. This sub-index allows a single GMPLS label
        to be defined as a concatenation of labels.  This is
        particularly useful in TDM.
        The ordering of sub-labels is strict with the sub-label sub-
        label with lowest
        gmplsSublabelIndex gmplsLabelSubindex appearing
        first. Note that all sub-labels of a single GMPLS
        label must share the same mplsLabelInterface gmplsLabelInterface and
        mplsLabelIndex
        gmplsLabelIndex values. For labels that are not
        composed of concatenated sub-labels, this value should
        SHOULD be set to zero."
   ::= { gmplsLabelEntry 1 3 }

   gmplsLabelType OBJECT-TYPE
     SYNTAX        GmplsGeneralizedLabelTypes
     MAX-ACCESS    read-create
     STATUS        current
     DESCRIPTION
       "Identifies the type of this label as it
        appears label. Note that this
        object does not determine whether MPLS or GMPLS
        signaling is in use: a Generalized Label. value of gmplsMplsLabel (1)
        denotes that a 23 bit MPLS packet label is present,
        but does not describe whether this is signaled using
        MPLS or GMPLS.
        The value of this object helps determine which of
        the following objects are valid.
        This object has meaning only cannot be modified if the value of
        mplsLabelType
        gmplsLabelRowStatus is other(1)." active(1)."
   ::= { gmplsLabelEntry 2 4 }

gmplsLabelSubtype

   gmplsLabelMplsLabel OBJECT-TYPE
     SYNTAX        GmplsGeneralizedLabelSubtypes         MplsLabel
     MAX-ACCESS     read-create
     STATUS         current
     DESCRIPTION
       "Subtype to help determine which
       "The value of an MPLS label (that is a packet label)
        if this table is used to store it. This may be used
        in MPLS systems even though the
        subsequent fields should label values can be
        adequately stored in the MPLS MIB modules. Further,
        in mixed MPLS and GMPLS systems it may be
        advantageous to store all labels in a single label
        table. Lastly, in GMPLS systems where packet labels
        are used (that is in systems that use GMPLS
        signaling and GMPLS labels for packet switching) it
        may be desirable to form
        the Generalized Label." use this table.
        This object is only valid if gmplsLabelType is set
        to gmplsMplsLabel (1).
        This object cannot be modified if
        gmplsLabelRowStatus is active(1)."
   ::= { gmplsLabelEntry 3 6 }

gmplsPortWavelengthLabel

   gmplsLabelPortWavelength OBJECT-TYPE
     SYNTAX        Unsigned32
     MAX-ACCESS    read-create
     STATUS        current
     DESCRIPTION
       "The value of a Port or Wavelength Label when carried
        as a Generalized Label. Only valid if mplsLabelType is set to other(1), gmplsLabelType
        is set to
        generalizedLabel(2), and gmplsLabelSubtype gmplsPortWavelengthLabel(2).
        This object cannot be modified if
        gmplsLabelRowStatus is set to portWavelengthLabel(2)." active(1)."
   ::= { gmplsLabelEntry 4 7 }

gmplsFreeformLength

   gmplsLabelFreeformLength OBJECT-TYPE
     SYNTAX        INTEGER (1..64)
     MAX-ACCESS    read-create
     STATUS        current
     DESCRIPTION
       "The length of a freeform Generalized Label indicated
        in the gmplsFreeformLabel object.  Only valid if mplsLabelType is set to
        other(1),
        gmplsLabelType is set to
        generalizedLabel(2), and gmplsLabelSubtype
        gmplsFreeformGeneralizedLabel(3).
        This object cannot be modified if
        gmplsLabelRowStatus is set to freeformGeneralizedLabel(3)." active(1)."
   ::= { gmplsLabelEntry 5 8 }

gmplsFreeformLabel

   gmplsLabelFreeform OBJECT-TYPE
     SYNTAX        GmplsFreeformLabel
     MAX-ACCESS    read-create
     STATUS        current
     DESCRIPTION
       "The value of a freeform Generalized Label that does
        not conform to one of the standardized label
        encoding or that an implementation chooses to

        represent as an octet string without further
        decoding. The length of this object is given by the
        value of gmplsFreeformLength.  Only valid if
        mplsLabelType is set to other(1),
        gmplsLabelType is set to
        generalizedLabel(2), and gmplsLabelSubtype
        gmplsFreeformGeneralizedLabel(3).
        This object cannot be modified if
        gmplsLabelRowStatus is set to freeformGeneralizedLabel(3)." active(1)."
   ::= { gmplsLabelEntry 6 9 }

gmplsSonetSdhSignalIndex
   gmplsLabelSonetSdhSignalIndex OBJECT-TYPE
     SYNTAX        INTEGER (0..4095)
     MAX-ACCESS    read-create
     STATUS        current
     DESCRIPTION
      "The Signal Index value (S) of a Sonet SONET or SDH
       Generalized Label.  0 Zero indicates that this field is non-significant.
       not significant. Only valid if mplsLabelType is set to other(1), gmplsLabelType is set
       to
        generalizedLabel(2), and gmplsLabelSubtype
        is set to sonetLabel(4) gmplsSonetLabel(4) or sdhLabel(5)." gmplsSdhLabel(5).
       This object cannot be modified if
       gmplsLabelRowStatus is active(1)."
   ::= { gmplsLabelEntry 7 10 }

gmplsSdhVc

   gmplsLabelSdhVc OBJECT-TYPE
     SYNTAX        INTEGER (0..15)
     MAX-ACCESS    read-create
     STATUS        current
     DESCRIPTION
      "The VC Indicator (U) of an SDH Generalized Label.  0
       Zero indicates that this field is non-
        significant. non-significant.
       Only valid if mplsLabelType
        is set to other(1), gmplsLabelType is set to generalizedLabel(2), and
        gmplsLabelSubtype
       gmplsSdhLabel(5).
       This object cannot be modified if
       gmplsLabelRowStatus is set to sdhLabel(5)." active(1)."
   ::= { gmplsLabelEntry 8 11 }

gmplsSdhVcBranch

   gmplsLabelSdhVcBranch OBJECT-TYPE
     SYNTAX        INTEGER (0..15)
     MAX-ACCESS    read-create
     STATUS        current
     DESCRIPTION
       "The VC Branch Indicator (K) of an SDH Generalized
        Label.  0 Zero indicates that this field is non-significant. non-
        significant. Only valid if
        mplsLabelType is set to other(1), gmplsLabelType is set to
        generalizedLabel(2), and gmplsLabelSubtype
        gmplsSdhLabel(5).
        This object cannot be modified if
        gmplsLabelRowStatus is set to sdhLabel(5)." active(1)."
   ::= { gmplsLabelEntry 9 12 }

gmplsSonetSdhBranch

   gmplsLabelSonetSdhBranch OBJECT-TYPE
     SYNTAX        INTEGER (0..15)
     MAX-ACCESS    read-create
     STATUS        current
     DESCRIPTION
       "The Branch Indicator (L) of a Sonet SONET or SDH
        Generalized Label.  0 Zero indicates that this field is
        non-significant. Only valid if
        mplsLabelType is set to other(1), gmplsLabelType is set to
        generalizedLabel(2), and gmplsLabelSubtype
        is set to sonetLabel(4)
        gmplsSonetLabel(4) or SdhLabel(5)." gmplsSdhLabel(5).
        This object cannot be modified if
        gmplsLabelRowStatus is active(1)."
   ::= { gmplsLabelEntry 10 13 }

gmplsSonetSdhGroupBranch
   gmplsLabelSonetSdhGroupBranch OBJECT-TYPE
     SYNTAX        INTEGER (0..15)
     MAX-ACCESS    read-create
     STATUS        current
     DESCRIPTION
       "The Group Branch Indicator (M) of a Sonet SONET or SDH
        Generalized Label.  0 Zero indicates that this field is
        non-significant. Only valid if mplsLabelType is set to other(1), gmplsLabelType is set
        to
        generalizedLabel(2), and gmplsLabelSubtype
        is set to sonetLabel(4) gmplsSonetLabel(4) or sdhLabel(5)." gmplsSdhLabel(5).
        This object cannot be modified if
        gmplsLabelRowStatus is active(1)."
   ::= { gmplsLabelEntry 11 14 }

gmplsWavebandId

   gmplsLabelWavebandId OBJECT-TYPE
     SYNTAX        Uunsigned32
     MAX-ACCESS    read-create
     STATUS        current
     DESCRIPTION
       "The waveband identifier component of a waveband
        label. Only valid if
        mplsLabelType is set to other(1), gmplsLabelType is set to
        generalizedLabel(2), and gmplsLabelSubtype
        gmplsWavebandLabel(6).
        This object cannot be modified if
        gmplsLabelRowStatus is set to wavebandLabel(6)." active(1)."
   ::= { gmplsLabelEntry 12 15 }

gmplsWavebandStartLabel

   gmplsLabelWavebandStart OBJECT-TYPE
     SYNTAX        Uunsigned32
     MAX-ACCESS    read-create
     STATUS        current
     DESCRIPTION
       "The starting label component of a waveband label.
        Only valid if mplsLabelType is set
        to other(1), gmplsLabelType is set to
        generalizedLabel(2), and gmplsLabelSubtype
        gmplsWavebandLabel(6).
        This object cannot be modified if
        gmplsLabelRowStatus is set to wavebandLabel(6)." active(1)."
   ::= { gmplsLabelEntry 13 16 }

gmplsWavebandEndLabel

   gmplsLabelWavebandEnd OBJECT-TYPE
     SYNTAX        Uunsigned32
     MAX-ACCESS    read-create
     STATUS        current
     DESCRIPTION
       "The end label component of a waveband
        label.  Only valid if mplsLabelType is set a waveband label. Only
        valid if gmplsLabelType is set to
        gmplsWavebandLabel(6).
        This object cannot be modified if
        gmplsLabelRowStatus is active(1)."
   ::= { gmplsLabelEntry 17 }
   gmplsLabelRowStatus OBJECT-TYPE
     SYNTAX        RowStatus
     MAX-ACCESS    read-create
     STATUS        current
     DESCRIPTION
       "This variable is used to create, modify, and/or
        delete a row in this table. When a row in this
        table has a row in the active(1) state, no
        objects in this row can be modified except the
        gmplsLabelRowStatus and gmplsLabelStorageType."
   ::= { gmplsLabelEntry 18 }

   gmplsLabelStorageType OBJECT-TYPE
     SYNTAX        StorageType
     MAX-ACCESS    read-create
     STATUS        current
     DESCRIPTION
       "This variable indicates the storage type for this
        object.

        The agent MUST ensure that this object's value
        remains consistent with the storage type of any rows
        in other tables that contain pointers to other(1), gmplsLabelType is set this row.
        In particular, the storage type of this row must be
        at least as permanent as that of any row that point
        to
        generalizedLabel(2), and gmplsLabelSubtype
        is set it.

        Conceptual rows having the value 'permanent' need
        not allow write-access to wavebandLabel(6)." any columnar objects in
        the row."
     REFERENCE
       "See RFC2579."
     DEFVAL { volatile }
   ::= { gmplsLabelEntry 14 19 }

   -- End of GMPLS Label Table

   -- Module compliance.

   gmplsLabelGroups
     OBJECT IDENTIFIER ::= { gmplsLabelConformance 1 }

   gmplsLabelCompliances
     OBJECT IDENTIFIER ::= { gmplsLabelConformance 2 }

gmplsLabelModuleCompliance

   gmplsLabelModuleFullCompliance MODULE-COMPLIANCE
     STATUS current
     DESCRIPTION
       "Compliance statement for agents that support
        the GMPLS Label MIB." MIB module."
     MODULE -- this module

     -- The mandatory groups have to be implemented by
     -- LSRs claiming support for this MIB. MIB module. This MIB itself, module is,
     -- however, is not mandatory only on LSRs supporting for a working implementation of a GMPLS
     -- LSR with full MIB support if the GMPLS labels in use can be
     -- represented within a 32 bit quantity.

     MANDATORY-GROUPS {
       gmplsLabelTableGroup
     }

     -- Units of conformance.

     GROUP gmplsLabelTableGroup
     DESCRIPTION
       "This group is mandatory for devices which support
        the gmplsLabelTable."

     GROUP gmplsPortWavelengthLabelGroup gmplsLabelPacketGroup
     DESCRIPTION
       "This group extends gmplsLabelTableGroup for
        implementations that support packet labels."

     GROUP gmplsLabelPortWavelengthGroup
     DESCRIPTION
       "This group extends gmplsLabelTableGroup for
        implementations that support port and wavelength
        labels."

     GROUP gmplsFreeformLabelGroup gmplsLabelFreeformGroup
     DESCRIPTION
       "This group extends gmplsLabelTableGroup for
        implementations that support freeform labels."

     GROUP gmplsSonetSdhLabelGroup gmplsLabelSonetSdhGroup
     DESCRIPTION
       "This group extends gmplsLabelTableGroup for
        implementations that support SonetSdh SONET or SDH labels."

     GROUP gmplsWavebandLabelGroup gmplsLabelWavebandGroup
     DESCRIPTION
       "This group extends gmplsLabelTableGroup for
        implementations that support Waveband labels."

     -- gmplsLabelTable

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

     OBJECT      gmplsLabelSubtype      gmplsLabelMplsLabel
     MIN-ACCESS  read-only
     DESCRIPTION
       "Write access is not required."
     OBJECT      gmplsPortWavelengthLabel      gmplsLabelPortWavelength
     MIN-ACCESS  read-only
     DESCRIPTION
       "Write access is not required."

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

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

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

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

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

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

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

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

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

     OBJECT      gmplsWavebandStartLabel      gmplsLabelWavebandEnd
     MIN-ACCESS  read-only
     DESCRIPTION
       "Write access is not required."
     OBJECT      gmplsWavebandEndLabel       gmplsLabelRowStatus
     SYNTAX       RowStatus {
       active(1),
       notInService(2)
     }
     WRITE-SYNTAX RowStatus {
       active(1),
       notInService(2),
       createAndGo(4),
       destroy(6)
     }
     DESCRIPTION
       "Support for notInService, createAndWait and notReady
        is not required."

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

   ::= { gmplsLabelCompliances 1 }

   -- Units of conformance.

   gmplsLabelTableGroup OBJECT-GROUP
     OBJECTS {
       gmplsLabelType,
      gmplsLabelSubtype
       gmplsLabelSubtype,
       gmplsLabelRowStatus,
       gmplsLabelStorageType
     }
     STATUS  current
     DESCRIPTION
       "Necessary, but not sufficient, set of objects to
        implement label table support.  In addition,
        depending on the type of labels supported (for
        example, wavelength labels), the following other
        groups defined below are mandatory:
        gmplsPortWavelengthLabelGroup
        gmplsLabelPacketGroup and/or
        gmplsLabelPortWavelengthGroup and/or
        gmplsFreeformLabelGroup
        gmplsLabelFreeformGroup and/or
        gmplsSonetSdhLabelGroup."
        gmplsLabelSonetSdhGroup."
   ::= { gmplsLabelGroups 1 }

gmplsPortWavelengthLabelGroup

   gmplsLabelPacketGroup OBJECT-GROUP
     OBJECTS {
       gmplsLabelMplsLabel
     }
     STATUS  current
     DESCRIPTION
       "Object needed to implement Packet (MPLS) labels."
   ::= { gmplsLabelGroups 2 }
   gmplsLabelPortWavelengthGroup OBJECT-GROUP
     OBJECTS {
      gmplsPortWavelengthLabel
       gmplsLabelPortWavelength
     }
     STATUS  current
     DESCRIPTION
       "Object needed to implement Port and Wavelength
        labels."
   ::= { gmplsLabelGroups 2 3 }

gmplsFreeformLabelGroup

   gmplsLabelFreeformGroup OBJECT-GROUP
     OBJECTS {
      gmplsFreeformLength,
      gmplsFreeformLabel
       gmplsLabelFreeformLength,
       gmplsLabelFreeform
     }
     STATUS  current
     DESCRIPTION
       "Object needed to implement Freeform labels."
   ::= { gmplsLabelGroups 3 4 }

gmplsSonetSdhLabelGroup

   gmplsLabelSonetSdhGroup OBJECT-GROUP
     OBJECTS {
      gmplsSonetSdhSignalIndex,
      gmplsSdhVc,
      gmplsSdhVcBranch,
      gmplsSonetSdhBranch,
      gmplsSonetuSdhGroupBranch
       gmplsLabelSonetSdhSignalIndex,
       gmplsLabelSdhVc,
       gmplsLabelSdhVcBranch,
       gmplsLabelSonetSdhBranch,
       gmplsLabelSonetSdhGroupBranch
     }
     STATUS  current
     DESCRIPTION
       "Object needed to implement SONET and SDH labels."
   ::= { gmplsLabelGroups 4 5 }

gmplsWavebandLabelGroup

   gmplsLabelWavebandGroup OBJECT-GROUP
     OBJECTS {
          gmplsWavebandId,
      gmplsWavebandStartLabel,
      gmplsWavebandEndLabel
       gmplsLabelWavebandId,
       gmplsLabelWavebandStart,
       gmplsLabelWavebandEnd
     }
     STATUS  current
     DESCRIPTION
       "Object needed to implement Waveband labels."
   ::= { gmplsLabelGroups 5 6 }

   END

11.

9. Security Considerations

   It is clear that this the MIB is modules described in this document in
   association with the MPLS-LSR-STD-MIB are potentially useful for
   monitoring of MPLS GMPLS LSRs.  This These MIB modules can also be used for
   configuration of certain objects, and anything that can be configured
   can be incorrectly configured, with potentially disastrous results.

   There are a number of management objects defined in this these MIB that have modules
   with 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.

   There These are a number of managed the tables and objects in this MIB that
   may and their
   sensitivity/vulnerability:

   o  the gmplsInterfaceTable, gmplsInSegmentTable, gmplsOutSegmentTable
      and gmplsLabelTable collectively contain information that may be sensitive from a
   business perspective, in that they represent objects to provision
      GMPLS interfaces, LSPs and their associated parameters on a customer's
   interface Label
      Switching Router (LSR). Unauthorized write access to objects in
      these tables, could result in disruption of traffic on the MPLS
      network.  Allowing uncontrolled
   access to This is especially true if an LSP has already been
      established. The use of stronger mechanisms such as SNMPv3
      security should be considered where possible. Specifically, SNMPv3
      VACM and USM MUST be used with any SNMPv3 agent which implements
      these MIB modules.

   Some of the readable objects could result in malicious and
   unwanted disruptions of network traffic or incorrect
   configurations for these customers.  There are no MIB modules "i.e., objects
   that are particularly with
   a MAX-ACCESS other than not-accessible" may be considered sensitive in their own right, such
   as passwords
   or monetary amounts. vulnerable in some network environments. It is thus important to
   control even GET and/or NOTIFY access to these objects and possibly
   to even encrypt the values of these
   object objects when sending them over
   the network via SNMP. Not
   all versions of SNMP provide features for such a secure
   environment.

   At this writing, no security holes have been identified
   beyond those that SNMP Security [RFC2571] is itself
   intended to address. These relate to primarily
   controlled access to sensitive information are the tables and objects and their
   sensitivity/vulnerability:

   o  the
   ability to configure a device - or which might result
   from operator error, which is beyond gmplsInterfaceTable, gmplsInSegmentTable, gmplsOutSegmentTable
      and gmplsLabelTable collectively show the scope of any
   security architecture.

   SNMPv1 or SNMPv2 are by themselves LSP network topology and
      its capabilities. If an Administrator does not a secure
   environment. want to reveal this
      information, then these tables should be considered
      sensitive/vulnerable.

   SNMP versions prior to SNMPv3 did not include adequate security. Even
   if the network itself is secure (for "for example by using IPSec [RFC2401]), IPSec", even
   then, there is no control as to who on the secure network is allowed
   to access and GET/SET (read, change, create and/or delete) "read/change/create/delete" the objects in this MIB.
   these MIB modules. It is recommended RECOMMENDED that the implementers consider the
   security features as provided by the SNMPv3
   framework. Specifically, the use of framework "see [RFC3410],
   section 8", including full support for the User-based
   Security Model [RFC2574] SNMPv3 cryptographic
   mechanisms "for authentication and the View-based Access
   Control [RFC2575] privacy".

   Further, deployment of SNMP versions prior to SNMPv3 is NOT
   RECOMMENDED. Instead, it is recommended. RECOMMENDED to deploy SNMPv3 and to
   enable cryptographic security.  It is then a
   customer/user customer/operator
   responsibility to ensure that the SNMP entity giving access to an
   instance of this MIB module, is properly configured to give access to
   the objects only to those principals (users) "users" that have legitimate
   rights to indeed GET or SET (change/create/delete) "change/create/delete" them.

12.

10. Acknowledgments

   This draft is based heavily on extends [LSRMIB]. The authors
   would like authors would like to express their
   gratitude to all those who worked on that earlier MIB document.

   The authors would like to express their thanks to Dan Joyle for his
   careful review and comments on early versions of the Label Table.

11. IANA Considerations

   MPLS related standards track MIB modules are rooted under the
   mplsStdMIB subtree.

   One of the MIB modules contained in this document extends tables
   contained in MPLS MIB modules.

   As requested in requested in the GMPLS-TC-STD-MIB [GMPLSTCMIB] the
   two MIB modules contained in this document should be placed in the
   mplsStdMIB subtree as well.

   New assignments can only be made via a Standards Action as specified
   in [RFC2434].

11.1. IANA Considerations for GMPLS-LSR-STD-MIB

   The IANA is requested to express their gratitude assign { mplsStdMIB xx } to all those who
   worked on that earlier MIB. the
   GMPLS-LSR-STD-MIB module specified in this document.

11.2. IANA Considerations for GMPLS-LABEL-STD-MIB

   The authors would like IANA is requested to express their thanks assign { mplsStdMIB xx } to Dan
   Joyle for his careful review and comments on GMPLS
   labels.

13. the
   GMPLS-LABEL-STD-MIB module specified in this document.

12. References

13.1.

12.1. Normative References

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

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

   [RFC2119]         Bradner, S., "Key words for use in RFCs to Indicate
                     Requirement Levels", BCP 14, RFC 2119, March 1997.

   [RFC2578]         McCloghrie, K., Perkins, D., Schoenwaelder, J.,
                     Case, J., Rose, M., and S. Waldbusser, "Structure
                     of Management Information Version 2 (SMIv2)", STD
                     58, RFC 2578, April 1999.

   [RFC2579]         McCloghrie, K., Perkins, D., Schoenwaelder, J.,
                     Case, J., Rose, M., and S. Waldbusser, "Textual
                     Conventions for SMIv2", STD 58, RFC 2579, April
                     1999.

   [RFC2580]         McCloghrie, K., Perkins, D., Schoenwaelder, J.,
                     Case, J., Rose, M., and S. Waldbusser, "Conformance
                     Statements for SMIv2", STD 58, RFC 2580, April
                     1999.

   [RFC2863]         McCloghrie, K. and F. Kastenholtz, "The Interfaces
                     Group MIB", RFC 2863, June 2000.

   [RFC3032]     Rosen, E., Rekhter, Y., Tappan, D.,
                 Farinacci, D., Federokow, G., Li, T., and
                 A. Conta, "MPLS Label Stack Encoding", RFC
                 3032, January 2001.

   [RFC3036]     Anderson, L., Doolan, P., Feldman, N.,
                 Fredette, A., and B. Thomas, "LDP
                 Specification", RFC 3036, January 2001.

   [RSVPTE]      Awduche, D., Berger, L., Gan, D., Li, T.,
                 Srinivasan, V., and G. Swallow, "RSVP-TE:
                 Extensions to RSVP for LSP Tunnels", draft-
                 ietf-mpls-rsvp-lsp-tunnel-08.txt, February
                 2001, work in progress.

   [CRLDP]       Jamoussi, B., Aboul-Magd, O., Andersson,
                 L., Ashwood-Smith, P., Hellstrand, F.,
                 Sundell, K., Callon, R., Dantu, R., Wu, L.,
                 Doolan, P., Worster, T., Feldman, N.,
                 Fredette, A., Girish, M., Gray, E.,
                 Halpern, J., Heinanen, J., Kilty, T.,
                 Malis, A., and P. Vaananen, "Constraint-
                 Based LSP Setup using LDP", draft-ietf-mpls-
                 cr-ldp-05.txt, February 2001, work in
                 progress."

   [GMPLSArch]   Ashwood-Smith, P., Awduche, D., Banerjee,
                 A., Basak, D, Berger, L., Bernstein, G.,
                 Drake, J., Fan, Y., Fedyk, D., Grammel, D.,
                 Kompella, K., Kullberg, A., Lang, J., Liaw,
                 F., Papadimitriou, D., Pendarakis, D.,
                 Rajagopalan, B., Rekhter, Y., Saha, D.,
                 Sandick, H., Sharma, V., Swallow, G., Tang,
                 Z., Yu, J., Zinin, A., Nadeau, T., Mannie,
                 E., Generalized Multiprotocol MIB", RFC 2863, June 2000.

   [RFC3471]         Berger, L. (Editor), "Generalized Multi-Protocol
                     Label Switching (GMPLS) Architecture, Internet
                 Draft <draft-many-gmpls-architecture-
                 01.txt>, March 2001, work in progress.

   [GMPLSSig]    Ashwood-Smith, P., Awduche, D., Banerjee,
                 A., Basak, D, Berger, L., Bernstein, G.,
                 Drake, J., Fan, Y., Fedyk, D., Grammel, D.,
                 Kompella, K., Kullberg, A., Lang,
                 Rajagopalan, B., Rekhter, Y., Saha, D.,
                 Sharma, V., Swallow, G., Bo Tang, Z.,
                 Generalized MPLS - Signaling Functional
                 Description, <draft-ietf-mpls-generalized-
                 signaling-04.txt>, May 2001, work in
                 progress.

   [GMPLSCRLDP]
                     Descriptionö, RFC 3471, January 2003.

   [RFC3472]         Ashwood-Smith, P., Awduche, D., Banerjee,
                 A., Basak, D, Berger, L., Bernstein, G.,
                 Drake, J., Fan, Y., Fedyk, D., Grammel, D.,
                 Kompella, K., Kullberg, A., Lang,
                 Rajagopalan, B., Rekhter, Y., Saha, D.,
                 Sharma, V., Swallow, G., Bo Tang, Z.,
                 Generalized L. (Editors),
                     "Generalized MPLS Signaling - CR-LDP
                 Extensions, Internet Draft <draft-ietf-mpls-
                 generalized-cr-ldp-03.txt>, May 2001, work
                 in progress.

   [GMPLSRSVPTE] Ashwood-Smith, P., Awduche, D., Banerjee,
                 A., Basak, D, Extensions",
                     RFC 3472, January 2003.

   [RFC3473]         Berger, L., Bernstein, G.,
                 Drake, J., Fan, Y., Fedyk, D., Grammel, D.,
                 Kompella, K., Kullberg, A., Lang,
                 Rajagopalan, B., Rekhter, Y., Saha, D.,
                 Sharma, V., Swallow, G., Bo Tang, Z.,
                 Generalized L. (Editor), "Generalized MPLS Signaling -
                     RSVP-TE
                 Extensions, Extensions", RFC 3473 January 2003.

   [GMPLSArch]       Mannie, E. (Editor), "Generalized Multiprotocol
                     Label Switching (GMPLS) Architecture", Internet
                     Draft <draft-ietf-mpls-
                 generalized-rsvp-te-03.txt>, <draft-many-gmpls-architecture-07.txt>, May 2001,
                     2003, work in progress.

   [GMPLSSonetSDH]   Mannie, E., Ansorge, S., Ashwood-Smith,
                 P., Banerjee, A., Berger, L., Bernstein,
                 G., Chiu, A., Drake, J., Fan, Y., Fontana,
                 M., Grammel, G., Heiles, J., Katukam, S.,
                 Kompella, K., Lang, J. P., Liaw, F., Lin,
                 Z., Mack-Crane, B., Papadimitriou, D.,
                 Pendarakis, D., Raftelis, M., Rajagopalan,
                 B., Rekhter, Y., Saha, D., Sharma, V.,
                 Swallow, G., Bo Tang, Z., Varma, E.,
                 Vissers, M., Xu, Y., GMPLS D. (Editors),
                     "Generalized Multi-Protocol Label Switching
                     Extensions for SONET and SDH Control, Control", Internet
                     Draft
                 <draft-ietf-ccamp-gmpls-sonet-sdh-00.txt>,
                 May 2001, <draft-ietf-ccamp-gmpls-sonet-sdh-08.txt>,
                     February 2003, work in progress.

   [TCMIB]           Nadeau, T., Cucchiara, J., Srinivasan, C,
                 Viswanathan, A. and H. Sjostrand,
                 "Definition J. (Editors) "Definitions of
                     Textual Conventions and
                 OBJECT-IDENTITIES for Multiprotocol Label
                     Switching (MPLS) Management", Internet Draft <draft-ietf-mpls-tc-mib-03.txt>,
                 January 2002,
                     <draft-ietf-mpls-tc-mib-09.txt>, August 2003, work
                     in progress.

   [LSRMIB]          Srinivasan, C., Viswanathan, A. and T. Nadeau, "MPLS
                     "Multiprotocol Label Switching (MPLS) Label
                     Switching Router (LSR) Management Information Base Using SMIv2",
                     Base", Internet Draft <draft-ietf-mpls-lsr-mib-
                 08.txt>, January 2002,
                     12.txt>, August 2003, work in progress.

   [GMPLSTEMIB]      Nadeau, T., Srinivasan, C., Farrel, A., Hall, T.,
                     and Harrison, E., "Generalized Multiprotocol Label
                     Switching (GMPLS) Traffic Engineering Management
                     Information Base",
                 draft-ietf-ccamp-gmpls-te-mib-00.txt, June
                 2002, work in progress.

   [GMPLSTCMIB]  Nadeau, T., Srinivasan, C., Farrel, A.,
                 Hall, T., and Harrison, E., " Definition of
                 Textual Conventions and OBJECT-IDENTITIES
                 for Generalized Multiprotocol Label
                 Switching (GMPLS) Management", draft-ietf-
                 ccamp-gmpls-te-mib-00.txt, June 2002, draft-ietf-ccamp-gmpls-te-mib-
                     01.txt, August 2003, work in progress.

13.2. Informational References

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

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

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

   [RFC1905]     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.

   [RFC1906]     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.

   [RFC2514]     Noto, et. al., progress.

   [GMPLSTCMIB]      Nadeau, T., Srinivasan, C., Farrel, A., Hall, T.,
                     and Harrison, E., "Definitions of Textual
                     Conventions and OBJECT-IDENTITIES for ATM Multiprotocol Label Switching
                     (MPLS) Management", draft-ietf-ccamp-gmpls-te-mib-
                     01.txt, August 2003, work in progress.

12.2. Informational References

   [RFC2026]         S. Bradner, "The Internet Standards Process --
                     Revision 3", RFC 2514, Feb. 1999

   [RFC2515]     K. Tesink, "Definitions of Managed Objects
                 for ATM Management", 2026, October 1996.

   [RFC3413]         Levi, D., Meyer, P., Stewart, B., "SNMP
                     Applications", RFC 2515, Feb. 1999

   [RFC2570] 3413, December 2002.

   [RFC3410]         Case, J., Mundy, R., Partain, D., D. and B. Stewart,
                     "Introduction to Version 3 of the
                 Internet-standard Network and Applicability Statements for
                     Internet-Standard Management Framework", RFC 2570, April 1999.

   [RFC2571] 3410,
                     December 2002.

   [RFC3411]         Harrington, D., Presuhn, R., and B. Wijnen, "An
                     Architecture for Describing SNMP
                 Management Frameworks", RFC 2571, April
                 1999.

   [RFC2572]     Case, J., Harrington D., Presuhn R., and B.
                 Wijnen, "Message Processing and Dispatching
                 for the Simple Network Management Protocol
                 (SNMP)", RFC 2572, April 1999.

   [RFC2573]     Levi, D., Meyer, P., and B. Stewart,
                 "SNMPv3 Applications", RFC 2573, April
                 1999.

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

   [RFC2575]     Wijnen, B., Presuhn, R., and K. McCloghrie,
                 "View-based Access Control Model (VACM) for
                 the Simple Network
                     Management Protocol
                 (SNMP)", RFC 2575, April 1999.

   [RFC2578]     McCloghrie, K., Perkins, D., Schoenwaelder,
                 J., Case, J., Rose, M., and S. Waldbusser,
                 "Structure of (SNMP) Management Information
                 Version 2 (SMIv2)", STD 58, RFC 2578, April
                 1999.

   [RFC2580]     McCloghrie, K., Perkins, D., Schoenwaelder,
                 J., Case, J., Rose, M., and S. Waldbusser,
                 "Conformance Statements for SMIv2", STD 58, Frameworks",
                     RFC 2580, April 1999. 3411, December 2002.

   [RFC3031]         Rosen, E., Viswanathan, A., and R. Callon,
                     "Multiprotocol Label Switching Architecture", RFC
                     3031, January 2001.

   [RFC3034]     Conta, A., Doolan, P., Malis, A., "Use of
                 Label Switching on Frame Relay Networks
                 Specification",

   [RFC3209]         Awduche, D., Berger, L., Gan, D., Li, T.,
                     Srinivasan, V., and G. Swallow, "RSVP-TE:
                     Extensions to RSVP for LSP Tunnels", RFC 3034, January 3209,
                     December 2001.

   [RFC3035]     Davie,

   [RFC3212]         Jamoussi, B., Lawrence, J., McCloghrie, Aboul-Magd, O., Andersson, L.,
                     Ashwood-Smith, P., Hellstrand, F., Sundell, K.,
                 Rosen,
                     Callon, R., Dantu, R., Wu, L., Doolan, P., Worster,
                     T., Feldman, N., Fredette, A., Girish, M., Gray,
                     E., Swallow, G., Rekhter, Y., Halpern, J., Heinanen, J., Kilty, T., Malis,
                     A., and P.
                 Doolan, "MPLS Vaananen, "Constraint-Based LSP Setup
                     using LDP and ATM VC
                 switching", LDP", RFC 3035, January 2001.

   [IANAFamily]  Internet Assigned Numbers Authority (IANA),
                 ADDRESS FAMILY NUMBERS. 3212, December 2001."

   [TEMIB]           Nadeau, T., Srinivasan, C, Viswanathan, A.,
                     "Multiprotocol Label Switching (MPLS) Traffic
                     Engineering Management Information Base", Internet
                     Draft <draft-ietf-mpls-te-
                 mib-08.txt>, January 2002, <draft-ietf-mpls-te-mib-12.txt>, August 2003,
                     work in progress.

14.

13. Authors' Addresses

   Thomas D. Nadeau
   Cisco Systems, Inc.
   300 Apollo Drive
   Chelmsford, MA 01824
   Phone: +1-978-244-3051
   Email: tnadeau@cisco.com

   Cheenu Srinivasan

   Parama Networks, Inc.
   1030 Broad Street
   Shrewsbury, NJ 07702
   Bloomberg L.P.
   499 Park Ave.,
   New York, NY 10022
   Phone: +1-732-544-9120 x731 +1-212-893-3682
   Email: cheenu@paramanet.com cheenu@bloomberg.net

   Adrian Farrel
   Movaz Networks, Inc.
   7926 Jones Branch Drive, Suite 615
   McLean VA, 22102 USA
   Old Dog Consulting
   Phone: +1-703-847-9847 +44-(0)-1978-860944
   Email: afarrel@movaz.com adrian@olddog.co.uk

   Tim Hall
   Data Connection Ltd.
   100 Church Street
   Enfield, Middlesex
   EN2 6BQ, UK
   Phone: +44 20 8366 1177
   Email: timhall@dataconnection.com

   Edward
   Ed Harrison
   Data Connection Ltd.
   100 Church Street
   Enfield, Middlesex
   EN2 6BQ, UK
   Phone: +44 20 8366 1177
   Email: eph@dataconnection.com

15. ed.harrison@dataconnection.com

14. Full Copyright Statement

   Copyright (C) The Internet Society (2002). (2003). 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.

15. Intellectual Property Notice

   The IETF takes no position regarding the validity or scope of any
   intellectual property or other rights that might be claimed to
   pertain to the implementation or use of the technology described in
   this document or the extent to which any license under such rights
   might or might not be available; neither does it represent that it
   has made any effort to identify any such rights.  Information on the
   IETF's procedures with respect to rights in standards-track and
   standards-related documentation can be found in BCP-11 [RFC2028].

   Copies of claims of rights made available for publication and any
   assurances of licenses to be made available, or the result of an
   attempt made to obtain a general license or permission for the use
   of such proprietary rights by implementers or users of this
   specification can be obtained from the IETF Secretariat.

   The IETF invites any interested party to bring to its attention any
   copyrights, patents or patent applications, or other proprietary
   rights that may cover technology that may be required to practice
   this standard.  Please address the information to the IETF Executive
   Director.

16. Changes and Pending Work

   This section must be removed before the draft progresses to RFC.

16.1. Pending Work

   The following work items have been identified for this draft. They
   will be addressed in a future version.

   - Expand conformance statements to give one for monitoring only,
     and one for monitoring and control.

   - Extend mplsTrafficParamsTable from the MPLS-LSR-MIB to support
     GMPLS traffic parameters for signaled and static LSPs.

   - Provide support for monitoring tunnel resources in GMPLS systems.
     For example, SONET/SDH or G.709.  This might be done through an
     arbitrary RowPointer to an external MIB.

   - Extend the performance tables from the MPLS-LSR-MIB for
     technology-specific GMPLS LSPs.

   - Supply more and better examples, especially ones using the Label
     Table.

   - Provide a next index object to supply the next available
     arbitrary index into the Label Table.