tech-invite   World Map     

IETF     RFCs     Groups     SIP     ABNFs    |    3GPP     Specs     Glossaries     Architecture     IMS     UICC    |    search     info

RFC 7453

Proposed STD
Pages: 62
Top     in Index     Prev     Next
in Group Index     Prev in Group     Next in Group     Group: MPLS

MPLS Transport Profile (MPLS-TP) Traffic Engineering (TE) Management Information Base (MIB)

Part 1 of 3, p. 1 to 13
None       Next RFC Part

 


Top       ToC       Page 1 
Internet Engineering Task Force (IETF)                     M. Venkatesan
Request for Comments: 7453                                     Dell Inc.
Category: Standards Track                                     K. Sampath
ISSN: 2070-1721                                                   Redeem
                                                               S. Aldrin
                                                     Huawei Technologies
                                                               T. Nadeau
                                                                 Brocade
                                                           February 2015


       MPLS Transport Profile (MPLS-TP) Traffic Engineering (TE)
                   Management Information Base (MIB)

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 additional managed objects and textual
   conventions for tunnels, identifiers, and Label Switching Routers to
   support Multiprotocol Label Switching (MPLS) MIB modules for
   transport networks.

Status of This Memo

   This is an Internet Standards Track document.

   This document is a product of the Internet Engineering Task Force
   (IETF).  It represents the consensus of the IETF community.  It has
   received public review and has been approved for publication by the
   Internet Engineering Steering Group (IESG).  Further information on
   Internet Standards is available in Section 2 of RFC 5741.

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at
   http://www.rfc-editor.org/info/rfc7453.

Page 2 
Copyright Notice

   Copyright (c) 2015 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1. Introduction ....................................................4
   2. The Internet-Standard Management Framework ......................5
   3. Overview ........................................................5
      3.1. Conventions Used in This Document ..........................5
      3.2. Terminology ................................................6
      3.3. Acronyms ...................................................6
   4. Motivations .....................................................6
   5. Feature List ....................................................7
   6. Outline .........................................................7
      6.1. MIB Module Extensions ......................................8
           6.1.1. Summary of MIB Module Changes .......................8
      6.2. MPLS-TE-EXT-STD-MIB ........................................9
           6.2.1. mplsTunnelExtNodeConfigTable ........................9
           6.2.2. mplsTunnelExtNodeIpMapTable .........................9
           6.2.3. mplsTunnelExtNodeIccMapTable .......................10
           6.2.4. mplsTunnelExtTable .................................10
      6.3. MPLS-TC-EXT-STD-MIB .......................................10
      6.4. MPLS-ID-STD-MIB ...........................................10
      6.5. MPLS-LSR-EXT-STD-MIB ......................................11
      6.6. The Use of RowPointer .....................................11
   7. MIB Modules' Interdependencies .................................11
   8. Dependencies between MIB Module Tables .........................13
   9. Example of MPLS-TP Tunnel Setup ................................13
      9.1. Example of MPLS-TP Static Co-routed Bidirectional
           Tunnel Setup ..............................................15
           9.1.1. mplsTunnelEntry ....................................15
           9.1.2. mplsTunnelExtEntry .................................16
           9.1.3. Forward-Direction mplsOutSegmentEntry ..............16
           9.1.4. Reverse-Direction mplsInSegmentEntry ...............16
           9.1.5. Forward-Direction mplsXCEntry ......................17
           9.1.6. Reverse-Direction mplsXCEntry ......................17

Top      ToC       Page 3 
           9.1.7. Forward-Direction mplsXCExtEntry ...................18
           9.1.8. Reverse-Direction mplsXCExtEntry ...................18
      9.2. Example of MPLS-TP Static Associated Bidirectional
           Tunnel Setup ..............................................18
           9.2.1. Forward-Direction mplsTunnelEntry ..................18
           9.2.2. Forward-Direction mplsTunnelExtEntry ...............19
           9.2.3. Forward-Direction mplsOutSegmentTable ..............20
           9.2.4. Forward-Direction mplsXCEntry ......................20
           9.2.5. Forward-Direction mplsXCExtEntry ...................20
           9.2.6. Reverse-Direction mplsTunnelEntry ..................21
           9.2.7. Reverse-Direction mplsTunnelExtEntry ...............22
           9.2.8. Reverse-Direction mplsInSegmentEntry ...............22
           9.2.9. Reverse-Direction mplsXCEntry ......................22
           9.2.10. Reverse-Direction mplsXCExtEntry ..................23
      9.3. Example of MPLS-TP Signaled Co-routed
           Bidirectional Tunnel Setup ................................23
           9.3.1. mplsTunnelEntry ....................................23
           9.3.2. mplsTunnelExtEntry .................................24
           9.3.3. Forward-Direction mplsOutSegmentEntry ..............24
           9.3.4. Reverse-Direction mplsInSegmentEntry ...............25
           9.3.5. Forward-Direction mplsXCEntry ......................25
           9.3.6. Reverse-Direction mplsXCEntry ......................25
           9.3.7. Forward-Direction mplsXCExtEntry ...................25
           9.3.8. Reverse-Direction mplsXCExtEntry ...................25
   10. MPLS Textual Convention Extension MIB Definitions .............26
   11. MPLS Identifier MIB Definitions ...............................29
   12. MPLS LSR Extension MIB Definitions ............................34
   13. MPLS Tunnel Extension MIB Definitions .........................39
   14. Security Considerations .......................................57
   15. IANA Considerations ...........................................58
      15.1. IANA Considerations for MPLS-TC-EXT-STD-MIB ..............58
      15.2. IANA Considerations for MPLS-ID-STD-MIB ..................58
      15.3. IANA Considerations for MPLS-LSR-EXT-STD-MIB .............58
      15.4. IANA Considerations for MPLS-TE-EXT-STD-MIB ..............59
   16. References ....................................................59
      16.1. Normative References .....................................59
      16.2. Informative References ...................................60
   Acknowledgments ...................................................62
   Authors' Addresses ................................................62

Top      ToC       Page 4 
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 additional textual conventions and
   managed objects for tunnels, identifiers, and Label Switching Routers
   to support Multiprotocol Label Switching (MPLS) MIB modules for
   transport networks.  MIB modules defined in this document extend the
   existing MPLS MIB objects in such a way that they support the MPLS
   Transport Profile (MPLS-TP) but also other MPLS networks.  Hence,
   "MPLS-TP" is not included in the MIB module names.

   As described in the MPLS Traffic Engineering (TE) MIB definition
   [RFC3812], MPLS traffic engineering is concerned with the creation
   and management of MPLS tunnels.  This term is a shorthand for a
   combination of one or more LSPs linking an ingress and an egress LSR.
   Several types of point-to-point MPLS tunnels may be constructed
   between a pair of LSRs A and B:

      - Unidirectional with a single LSP (say, from A to B).

      - Associated bidirectional consisting of two separately routed
        LSPs, one linking A to B and the other linking B to A.
        Together, the pair provides a single logical bidirectional
        transport path.

      - Co-routed bidirectional consisting of an associated
        bidirectional tunnel but with the second LSP from B to A
        following the reverse of the path of the LSP from A to B, in
        terms of both nodes and links.

   Tunnels may be either statically configured by management action or
   dynamically created using an LSP management protocol.

   The existing MPLS TE MIB [RFC3812] and the GMPLS TE MIB [RFC4802]
   address only a subset of the combinations of statically and
   dynamically configured tunnel types, catering to statically
   configured unidirectional tunnels together with dynamically
   configured unidirectional and co-routed bidirectional tunnels.  They
   are also restricted to two endpoint LSRs identified by IP addresses.

   The MPLS-TP TE MIB defined in this document extends the MIB modules
   defined in [RFC3812] to cover all six combinations (that is, adding
   support for statically configured associated and co-routed
   bidirectional plus dynamically configured associated bidirectional
   tunnels).  It also extends support to endpoints that have identifiers
   other than IP addresses.

Top      ToC       Page 5 
   This support is provided by a suite of four MIB modules that are to
   be used in conjunction with the MIB modules defined in [RFC3812] and
   the companion document [RFC3813] for MPLS-TP tunnel management.

   At the time of writing, SNMP SET is no longer recommended as a way to
   configure MPLS networks as described in [RFC3812].  However, since
   the MIB modules specified in this document extend and are intended to
   work in parallel with the MIB modules for MPLS specified in
   [RFC3812], certain objects defined here are specified with MAX-ACCESS
   of read-write or read-create so that specifications of the base
   tables in [RFC3812] and the extensions in this document are
   consistent.  Although the examples described in Section 9 specify
   means to configure MPLS-TP Tunnels in a similar way to the examples
   in [RFC3812], this should be seen as indicating how the MIB values
   would be returned if the specified circumstances were configured by
   alternative means.

2.  The Internet-Standard Management Framework

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

   Managed objects are accessed via a virtual information store, termed
   the 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].

3.  Overview

3.1.  Conventions Used in This Document

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

Top      ToC       Page 6 
3.2.  Terminology

   This document uses terminology from the "Multiprotocol Label
   Switching Architecture" [RFC3031], "Multiprotocol Label Switching
   (MPLS) Traffic Engineering (TE) Management Information Base (MIB)"
   [RFC3812], "Multiprotocol Label Switching (MPLS) Label Switching
   Router (LSR) Management Information Base (MIB)" [RFC3813], and"MPLS
   Transport Profile (MPLS-TP) Identifiers" [RFC6370].

3.3.  Acronyms

   CC: Country Code
   ICC: ITU Carrier Code
   LSP: Label Switched Path
   LSR: Label Switching Router
   MPLS-TP: MPLS Transport Profile
   TE: Traffic Engineering
   TP: Transport Profile

4.  Motivations

   "Multiprotocol Label Switching (MPLS) Traffic Engineering (TE)
   Management Information Base (MIB)" [RFC3812] provides support for
   Traffic Engineering tunnels.  In MPLS, the actual transport of
   packets is provided by Label Switched Paths (LSPs).  A transport
   service may be composed of multiple LSPs.  In order to clearly
   identify the MPLS-TP service, as defined in [RFC6370], we use the
   term "MPLS-TP Tunnel" or simply "tunnel".  However, with MPLS-TP, the
   characteristics of the tunnels were enhanced.  For example, MPLS-TP
   Tunnels are bidirectional in nature and could be used with non-IP
   identifiers for the tunnel endpoints.  As the existing
   MPLS-TE-STD-MIB and GMPLS-TE-STD-MIB were defined mainly to support
   unidirectional tunnels and signaled co-routed bidirectional tunnel
   definitions, respectively, these existing MIB modules are not
   sufficient to capture all the characteristics of the tunnels.  Hence,
   enhancing the MIB modules to support MPLS-TP Tunnels is required.  As
   most of the attributes of MPLS Traffic Engineering tunnels are also
   applicable to MPLS-TP Tunnels, it is optimal to reuse and extend the
   existing MIB module definition instead of defining a new MIB module.

   This document defines four additional MIB modules, namely,
   MPLS-TE-EXT-STD-MIB, MPLS-TC-EXT-STD-MIB, MPLS-ID-STD-MIB, and
   MPLS-LSR-EXT-STD-MIB.  As these additional MIB modules are required
   for MPLS-TP functionality, these are all defined in this document,
   instead of being documented separately.

Top      ToC       Page 7 
5.  Feature List

   The MIBs in this document satisfy the following requirements and
   constraints:

   The MIB modules, taken together, support statically configured and
   dynamically signaled point-to-point, co-routed bidirectional and
   associated bidirectional tunnels.

      - The MPLS tunnels need not be interfaces, but it is possible to
        configure an MPLS-TP Tunnel as an interface.  The same ifType
        150, as defined in Section 8 of [RFC3812], will be used for
        MPLS-TP Tunnels as well.

      - The mplsTunnelTable [RFC3812] is also to be used for MPLS-TP
        Tunnels.

      - New MPLS-TP-specific textual conventions and identifiers are
        required.

      - The mplsTunnelTable is sparsely extended to support objects
        specific to MPLS-TP Tunnels.

      - A node configuration table (mplsTunnelExtNodeConfigTable), as
        detailed in Section 6.2.1, below, is used to translate the
        Global_ID::Node_ID or ICC_Operator_ID::Node_ID to the local
        identifier in order to index the mplsTunnelTable.

      - The mplsXCTable is sparsely extended to support objects specific
        to MPLS-TP XC (Cross Connect).

      - The MIB module supports persistent, as well as non-persistent,
        tunnels.

6.  Outline

   Traffic Engineering support for the MPLS-TP Tunnels requires the
   setup of the co-routed or associated bidirectional tunnel.  The
   tables and MIB modules that are mentioned in the below subsections
   support the functionality described in [RFC5654] and [RFC6370].
   These tables support both IP-compatible and ICC-based tunnel
   configurations.

   Figure 1, below, depicts how the table references are followed in
   this MIB.

Top      ToC       Page 8 
            Tunnel1-->XC1<--------------
             ^ ^      | |               |
             | |      | |-->InSeg1      |
             | |      | |-->OutSeg1     |
             | |      v                 |
             |  ------XCext1            |
             |         |                |
             V         v                |
            Tunnel2-->XC1               |
               ^      | |               |
               |      | |-->InSeg2      |
               |      | |-->OutSeg2     |
               |      v                 |
                ------XCext2------------

                 Figure 1: Table References of MIB Modules

6.1.  MIB Module Extensions

   Four MIB modules are extended to support MPLS-TP Tunnels, namely,
   MPLS-TE-EXT-STD-MIB, MPLS-TC-EXT-STD-MIB, MPLS-ID-STD-MIB, and
   MPLS-LSR-EXT-STD-MIB.  The following section provides the summary of
   changes.

6.1.1.  Summary of MIB Module Changes

   - Node configuration table (mplsTunnelExtNodeConfigTable) for setting
     the local identifier for Tunnel Ingress and Egress identifiers.

   - Node IP map table (mplsTunnelExtNodeIpMapTable) for querying the
     local identifier for a given Global_ID and Node_ID.

   - Node ICC map table (mplsTunnelExtNodeIccMapTable) for querying the
     local identifier for a given ICC_Operator_ID and Node_ID.

   - Tunnel extension table (mplsTunnelExtTable) for setting up MPLS-TP
     Tunnels with sparse extension of mplsTunnelTable.

   - Textual conventions and object definitions for MPLS-TP Tunnels.

   - Cross-connect extension table (mplsXCExtTable) for setting up the
     MPLS-TP LSPs.

     These tables are described in the subsequent sections.

Top      ToC       Page 9 
6.2.  MPLS-TE-EXT-STD-MIB

     The TE MIB module extensions and details of the tables are
     described in the following sections.

6.2.1.  mplsTunnelExtNodeConfigTable

   The mplsTunnelExtNodeConfigTable is used to assign a local identifier
   for a given ICC_Operator_ID::Node_ID or Global_ID::Node_ID
   combination as defined in [RFC6923] and [RFC6370], respectively.  The
   CC is a string of two characters, each being an uppercase Basic Latin
   alphabetic (i.e., A-Z).  The ICC is a string of one to six
   characters, each an uppercase Basic Latin alphabetic (i.e., A-Z) or
   numeric (i.e., 0-9).  All of the characters are encoded using [T.50]
   as described in [RFC6370].

   In the IP-compatible mode, Global_ID::Node_ID, is used to uniquely
   identify a node.  For each ICC_Operator_ID::Node_ID or
   Global_ID::Node_ID, there is a unique entry in the table representing
   a node.  As the regular TE tunnels use the IP address as the LSR ID,
   the local identifier should be below the first valid IP address,
   which is 16777216[1.0.0.0].  Every node is assigned a local
   identifier within a range of 0 to 16777215.  This local identifier is
   used for indexing into mplsTunnelTable as mplsTunnelIngressLSRId and
   mplsTunnelEgressLSRId.

   For IP-compatible environments, an MPLS-TP Tunnel is indexed by
   Tunnel Index, Tunnel Instance, Source Global_ID, Source Node_ID,
   Destination Global_ID, and Destination Node_ID.

   For ICC-based environments, an MPLS-TP Tunnel is indexed by Tunnel
   Index, Tunnel Instance, Source CC, Source ICC, Source Node_ID,
   Destination CC, Destination ICC, and Destination Node_ID.

   As mplsTunnelTable is indexed by mplsTunnelIndex, mplsTunnelInstance,
   mplsTunnelIngressLSRId, and mplsTunnelEgressLSRId, the MPLS-TP tunnel
   identifiers cannot be used directly.

   The mplsTunnelExtNodeConfigTable will be used to store an entry for
   ICC_Operator_ID::Node_ID or Global_ID::Node_ID with a local
   identifier to be used as the LSR ID in mplsTunnelTable.

6.2.2.  mplsTunnelExtNodeIpMapTable

   The read-only mplsTunnelExtNodeIpMapTable is used to query the local
   identifier assigned and stored in mplsTunnelExtNodeConfigTable for a
   given Global_ID::Node_ID.  In order to query the local identifier, in

Top      ToC       Page 10 
   the IP-compatible mode, this table is indexed with
   Global_ID::Node_ID.  In the IP-compatible mode for a TP tunnel,
   Global_ID::Node_ID is used.

   A separate query is made to get the local identifier of both Ingress
   and Egress Global_ID::Node_ID identifiers.  These local identifiers
   are used as mplsTunnelIngressLSRId and mplsTunnelEgressLSRId when
   indexing mplsTunnelTable.

6.2.3.  mplsTunnelExtNodeIccMapTable

   The read-only mplsTunnelExtNodeIccMapTable is used to query the local
   identifier assigned and stored in the mplsTunnelExtNodeConfigTable
   for a given ICC_Operator_ID::Node_ID.

   A separate query is made to get the local identifier of both Ingress
   and Egress ICC_Operator_ID::Node_ID.  These local identifiers are
   used as mplsTunnelIngressLSRId and mplsTunnelEgressLSRId when
   indexing mplsTunnelTable.

6.2.4.  mplsTunnelExtTable

   This table sparsely extends the mplsTunnelTable in order to support
   MPLS-TP Tunnels with additional objects.  All the additional
   attributes specific to supporting a TP tunnel are contained in this
   extended table and could be accessed with the mplsTunnelTable
   indices.

   The gmplsTunnelReversePerfTable [RFC4802] should be used to provide
   per-tunnel packet performance information for the reverse direction
   of a bidirectional tunnel.  It can be seen as supplementing the
   mplsTunnelPerfTable, which augments the mplsTunnelTable.

6.3.  MPLS-TC-EXT-STD-MIB

   This MIB module contains textual conventions for LSPs of MPLS-based
   transport networks.

6.4.  MPLS-ID-STD-MIB

   This MIB module contains identifier object definitions for MPLS
   Traffic Engineering in transport networks.

Top      ToC       Page 11 
6.5.  MPLS-LSR-EXT-STD-MIB

   This MIB module contains generic object definitions (including the
   mplsXCExtTable -- cross-connect extension table -- for setting up the
   MPLS-TP LSPs with sparse extension of mplsXCTable) for MPLS LSRs in
   transport networks.

6.6.  The Use of RowPointer

   This document follows the RowPointer usage as described in Section 10
   of [RFC3812].

   A new RowPointer object, mplsTunnelExtOppositeDirPtr, is added to
   mplsTunnelExtTable of MPLS-TE-EXT-STD-MIB module.  This RowPointer
   object points to the tunnel entry in the opposite direction.

   Two additional RowPointers objects, mplsXCExtTunnelPointer and
   mplsXCExtOppositeDirXCPtr, are added to the mplsXCExtTable of
   MPLS-LSR-EXT-STD-MIB.  The RowPointer mplsXCExtTunnelPointer is a
   read-only object used to indicate the back pointer to the tunnel
   entry.  The RowPointer mplsXCExtOppositeDirXCPtr object points to the
   opposite-direction XC entry.

   If either of these RowPointers return zeroDotZero, it implies that
   there is no entry associated with the RowPointer object.

7.  MIB Modules' Interdependencies

   This section provides an overview of the relationships between the
   MPLS-TP TE MIB module and other MPLS MIB modules.

   The arrows in the following diagram show a "depends on" relationship.
   A relationship of "MIB module A depends on MIB module B" means that
   MIB module A uses an object, object identifier, or textual convention
   defined in MIB module B, or that MIB module A contains a pointer
   (index or RowPointer) to an object in MIB module B.

Top      ToC       Page 12 
       MPLS-TC-EXT-STD-MIB
          ^
          |
          |
          +<---- MPLS-ID-STD-MIB
                        ^
          |             |
          +<---- MPLS-TE-EXT-STD-MIB
          |             |
          |             V
          |      MPLS-TE-STD-MIB
          |             |
          |             |
          |             V
          |      MPLS-LSR-STD-MIB
          |             ^
          |             |
          |             |
          +------MPLS-LSR-EXT-STD-MIB

       Figure 2: MIB Modules' Interdependencies

       Thus:

      - All the new MPLS extension MIB modules depend on
        MPLS-TC-EXT-STD-MIB.

      - MPLS-ID-STD-MIB contains references to objects in
        MPLS-TE-STD-MIB [RFC3812].

      - MPLS-TE-EXT-STD-MIB contains references to objects in
        MPLS-TE-STD-MIB [RFC3812].

      - MPLS-LSR-EXT-STD-MIB contains references to objects in
        MPLS-LSR-STD-MIB [RFC3813].

   The mplsTunnelExtTable sparsely extends the mplsTunnelTable of
   MPLS-TE-STD-MIB [RFC3812].  This helps in associating the reverse-
   direction tunnel information.

   The mplsXCExtTable sparsely extends the mplsXCTable of
   MPLS-LSR-STD-MIB [RFC3813].  This helps in pointing back to the
   tunnel entry for easy tunnel access from the XC entry.

   Note that all of the MIB modules shown above in the figure also have
   a dependency on MPLS-TC-STD-MIB.

Top      ToC       Page 13 
8.  Dependencies between MIB Module Tables

   The tables in MPLS-TE-EXT-STD-MIB are related as shown on the diagram
   below.  The arrows indicate a reference from one table to another.

         mplsTunnelExtNodeConfigTable
              ^          ^       ^
              |          |       |
              |          |       |
              |          |       |
              |          |       +----------------------+
              |          |                              |
              | mplsTunnelExtNodeIpMapTable mplsTunnelExtNodeIccMapTable
              |
              |              mplsXCExtTable
              |               |      ^
              |     +---------+      |
              |     |                |
              |     |                |
              |     V                V
         mplsTunnelTable ---->mplsXCTable
              ^
              |
              |
              |
        mplsTunnelExtTable

     Figure 3: Dependencies between MIB Module Tables

   An existing mplsTunnelTable uses the mplsTunnelExtNodeConfigTable
   table to map the Global_ID::Node_ID and/or ICC_Operator_ID::Node_ID
   with the local number in order to accommodate in the existing tunnel
   table's ingress/egress LSR ID.

   The new mplsTunnelExtTable provides the reverse-direction LSP
   information for the existing tunnel table so that bidirectional LSPs
   can be created.

   The mplsXCExtTable sparsely extends the mplsLsrXCTable to provide
   backward reference to tunnel entry.



(page 13 continued on part 2)

Next RFC Part