--- 1/draft-ietf-mpls-tp-te-mib-09.txt 2014-12-14 22:14:51.969701203 -0800 +++ 2/draft-ietf-mpls-tp-te-mib-10.txt 2014-12-14 22:14:52.069703652 -0800 @@ -1,32 +1,32 @@ Network Working Group INTERNET-DRAFT M.Venkatesan Intended Status: Standards Track Dell Inc. -Expires: March 26, 2015 Kannan KV Sampath +Expires: June 17, 2015 Kannan KV Sampath Redeem Sam K. Aldrin Huawei Technologies Thomas D. Nadeau Brocade - September 22, 2014 + December 14, 2014 MPLS-TP Traffic Engineering (TE) Management Information Base (MIB) - draft-ietf-mpls-tp-te-mib-09.txt + draft-ietf-mpls-tp-te-mib-10.txt 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 of Tunnels, - Identifiers, Label Switching Router and Textual conventions to + In particular, it describes additional managed objects and textual + conventions for Tunnels, Identifiers and Label Switching Router to support Multiprotocol Label Switching (MPLS) MIB modules for transport networks. Status of this Memo This Internet-Draft is submitted to IETF in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that @@ -37,128 +37,173 @@ and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt. The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html. - This Internet-Draft will expire on March 26, 2015. + This Internet-Draft will expire on June 17, 2015. Copyright and License Notice Copyright (c) 2014 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 . . . . . . . . . . 4 - 3. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 - 3.1. Conventions used in this document . . . . . . . . . . . . . 4 - 3.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . 4 + 2. The Internet-Standard Management Framework . . . . . . . . . . 5 + 3. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 + 3.1. Conventions used in this document . . . . . . . . . . . . . 5 + 3.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . 5 3.3. Acronyms . . . . . . . . . . . . . . . . . . . . . . . . . 6 4. Motivations . . . . . . . . . . . . . . . . . . . . . . . . . . 6 5. Feature List . . . . . . . . . . . . . . . . . . . . . . . . . 6 - 6. Brief description of MIB modules . . . . . . . . . . . . . . . 7 - 6.1. mplsTunnelExtNodeConfigTable . . . . . . . . . . . . . . . 7 - 6.2. mplsTunnelExtNodeIpMapTable . . . . . . . . . . . . . . . . 8 - 6.3. mplsTunnelExtNodeIccMapTable . . . . . . . . . . . . . . . 8 - 6.4. mplsTunnelExtTable . . . . . . . . . . . . . . . . . . . . 9 - 6.5 MPLS-TC-EXT-STD-MIB . . . . . . . . . . . . . . . . . . . . 9 - 6.6 MPLS-ID-STD-MIB . . . . . . . . . . . . . . . . . . . . . . 9 - 6.7 MPLS-LSR-EXT-STD-MIB . . . . . . . . . . . . . . . . . . . . 9 - 7. MIB Module Interdependencies . . . . . . . . . . . . . . . . . 9 - 8. Dependencies between MIB Module Tables . . . . . . . . . . . . 11 - 9. Example of MPLS-TP Tunnel Setup . . . . . . . . . . . . . . . . 12 + 6. Outline . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 + 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 . . . . . . . . . . . . . . 10 + 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 . . . . . . . . . . . . . . . . . 12 + 8. Dependencies between MIB Module Tables . . . . . . . . . . . . 13 + 9. Example of MPLS-TP Tunnel Setup . . . . . . . . . . . . . . . . 14 9.1. Example of MPLS-TP static co-routed bidirectional tunnel - setup . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 - 9.1.1. mplsTunnelEntry . . . . . . . . . . . . . . . . . . . . 14 - 9.1.2. mplsTunnelExtEntry . . . . . . . . . . . . . . . . . . 14 - 9.1.3. Forward direction mplsOutSegmentEntry . . . . . . . . . 15 - 9.1.4. Reverse direction mplsInSegmentEntry . . . . . . . . . 15 - 9.1.5. Forward direction mplsXCEntry . . . . . . . . . . . . . 16 - 9.1.6. Reverse direction mplsXCEntry . . . . . . . . . . . . . 16 - 9.1.7. Forward direction mplsXCExtEntry . . . . . . . . . . . 16 - 9.1.8. Reverse direction mplsXCExtEntry . . . . . . . . . . . 16 + 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 + 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 . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 - 9.2.1. Forward direction mplsTunnelEntry . . . . . . . . . . . 17 - 9.2.2. Forward direction mplsTunnelExtEntry . . . . . . . . . 18 - 9.2.3. Forward direction mplsOutSegmentTable . . . . . . . . . 18 - 9.2.4. Forward direction mplsXCEntry . . . . . . . . . . . . . 18 - 9.2.5. Forward direction mplsXCExtEntry . . . . . . . . . . . 19 - 9.2.6. Reverse direction mplsTunnelEntry . . . . . . . . . . . 19 - 9.2.7. Reverse direction mplsTunnelExtEntry . . . . . . . . . 20 - 9.2.8. Reverse direction mplsInSegmentEntry . . . . . . . . . 20 - 9.2.9. Reverse direction mplsXCEntry . . . . . . . . . . . . . 20 - 9.2.10. Reverse direction mplsXCExtEntry . . . . . . . . . . . 21 + setup . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 + 9.2.1. Forward direction mplsTunnelEntry . . . . . . . . . . . 18 + 9.2.2. Forward direction mplsTunnelExtEntry . . . . . . . . . 19 + 9.2.3. Forward direction mplsOutSegmentTable . . . . . . . . . 19 + 9.2.4. Forward direction mplsXCEntry . . . . . . . . . . . . . 20 + 9.2.5. Forward direction mplsXCExtEntry . . . . . . . . . . . 20 + 9.2.6. Reverse direction mplsTunnelEntry . . . . . . . . . . . 20 + 9.2.7. Reverse direction mplsTunnelExtEntry . . . . . . . . . 21 + 9.2.8. Reverse direction mplsInSegmentEntry . . . . . . . . . 21 + 9.2.9. Reverse direction mplsXCEntry . . . . . . . . . . . . . 22 + 9.2.10. Reverse direction mplsXCExtEntry . . . . . . . . . . . 22 9.3. Example of MPLS-TP signaled co-routed bidirectional - tunnel setup . . . . . . . . . . . . . . . . . . . . . . . 21 - 9.3.1. mplsTunnelEntry . . . . . . . . . . . . . . . . . . . . 21 - 9.3.2. mplsTunnelExtEntry . . . . . . . . . . . . . . . . . . 22 - 9.3.3. Forward direction mplsOutSegmentEntry . . . . . . . . . 23 - 9.3.4. Reverse direction mplsInSegmentEntry . . . . . . . . . 23 - 9.3.5. Forward direction mplsXCEntry . . . . . . . . . . . . . 23 - 9.3.6. Reverse direction mplsXCEntry . . . . . . . . . . . . . 23 - 9.3.7. Forward direction mplsXCExtEntry . . . . . . . . . . . 23 - 9.3.8. Reverse direction mplsXCExtEntry . . . . . . . . . . . 23 - 10. MPLS Textual Convention Extension MIB definitions . . . . . . 23 - 11. MPLS Identifier MIB definitions . . . . . . . . . . . . . . . 26 - 12. MPLS LSR Extension MIB definitions . . . . . . . . . . . . . . 31 - 13. MPLS Tunnel Extension MIB definitions . . . . . . . . . . . . 36 - 14. Security Consideration . . . . . . . . . . . . . . . . . . . . 54 - 15. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 55 - 15.1. IANA Considerations for MPLS-TC-EXT-STD-MIB . . . . . . . 55 - 15.2. IANA Considerations for MPLS-ID-STD-MIB . . . . . . . . . 55 - 15.3. IANA Considerations for MPLS-LSR-EXT-STD-MIB . . . . . . . 55 + tunnel setup . . . . . . . . . . . . . . . . . . . . . . . 22 + 9.3.1. mplsTunnelEntry . . . . . . . . . . . . . . . . . . . . 23 + 9.3.2. mplsTunnelExtEntry . . . . . . . . . . . . . . . . . . 23 + 9.3.3. Forward direction mplsOutSegmentEntry . . . . . . . . . 24 + 9.3.4. Reverse direction mplsInSegmentEntry . . . . . . . . . 24 + 9.3.5. Forward direction mplsXCEntry . . . . . . . . . . . . . 24 + 9.3.6. Reverse direction mplsXCEntry . . . . . . . . . . . . . 24 + 9.3.7. Forward direction mplsXCExtEntry . . . . . . . . . . . 24 + 9.3.8. Reverse direction mplsXCExtEntry . . . . . . . . . . . 25 + 10. MPLS Textual Convention Extension MIB definitions . . . . . . 25 + 11. MPLS Identifier MIB definitions . . . . . . . . . . . . . . . 28 + 12. MPLS LSR Extension MIB definitions . . . . . . . . . . . . . . 32 + 13. MPLS Tunnel Extension MIB definitions . . . . . . . . . . . . 38 + 14. Security Consideration . . . . . . . . . . . . . . . . . . . . 55 + 15. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 56 + 15.1. IANA Considerations for MPLS-TC-EXT-STD-MIB . . . . . . . 56 + 15.2. IANA Considerations for MPLS-ID-STD-MIB . . . . . . . . . 56 + 15.3. IANA Considerations for MPLS-LSR-EXT-STD-MIB . . . . . . . 56 15.4. IANA Considerations for MPLS-TE-EXT-STD-MIB . . . . . . . 56 16. References . . . . . . . . . . . . . . . . . . . . . . . . . . 56 16.1. Normative References . . . . . . . . . . . . . . . . . . . 56 - 16.2. Informative References . . . . . . . . . . . . . . . . . 56 - 17. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 57 - 18. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 57 + 16.2. Informative References . . . . . . . . . . . . . . . . . 57 + 17. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 58 + 18. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 58 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 managed objects of Tunnels, -Identifiers, Label Switching Router and Textual conventions to support +particular, it describes additional textual conventions and managed +objects for Tunnels, Identifiers and Label Switching Router to support Multiprotocol Label Switching (MPLS) MIB modules for transport networks. -MIB modules defined in this document extends the existing MPLS MIB -objects in such a way that they support MPLS-TP and Non-MPLS-TP networks -as well. Hence, the MPLS-TP name is not included in the MIB module name. +MIB modules defined in this document extend the existing MPLS MIB +objects in such a way that they support MPLS-TP but also other MPLS +networks as well. Hence, the MPLS-TP name is not included in the MIB +module name. -The existing MPLS Traffic Engineering (TE) Management Information Base -(MIB) [RFC3812] and Generalized Multiprotocol Label Switching (GMPLS) -Traffic Engineering Management Information Base [RFC4802] do not support -the management of transport network requirements of Tunnel end points -with non-IP based identifiers and static bidirectional tunnels. This -document focuses on static bidirectional MIB modules that should be used -in conjunction with [RFC3812] and companion document [RFC3813] for MPLS -Transport Profile (MPLS-TP) path configuration and management. +As described in the MPLS Traffic Engineering (TE) Management Information +Base (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: -It is understood that SNMP SET is not used for MPLS configuration these -days, however the read-write and read-create option is still specified -for some objects as a way to provide the information model. + - 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 + provide 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 a LSP management protocol. + +The existing MPLS TE MIB [RFC3812] and the Generalized Multiprotocol +Label Switching (GMPLS) Traffic Engineering Management Information Base +[RFC4802] address only a subset of the combinations of statically and +dynamically configured tunnel types, catering for statically configured +unidirectional tunnels together with dynamically configured +unidirectional and co-routed bidirectional tunnels. They are also +restricted to two end point 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 end points that are identified other than with IP +addresses. + +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 Transport Profile (MPLS-TP) tunnel +management. + +At the time of writing, SNMP SET is no longer recommended as a way to +configure MPLS networks as was 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 in the specified +circumstances having been 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 @@ -190,97 +236,140 @@ LSP: Label Switching 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. However, with MPLS-TP, the characteristics of -Tunnels were enhanced. In MPLS, the actual transport of packets is +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 service, as -defined in [RFC6370], we use the term "MPLS-TP Tunnel" or simply -"tunnel" For example, MPLS-TP tunnels, are bidirectional in nature and -could be used with non-IP identifiers for the tunnel end points. As the -existing MPLS-TE-STD-MIB and GMPLS-TE-STD-MIB were defined mainly to -support unidirectional tunnel and signaled co-routed bidirectional -tunnel definitions respectively, these existing MIBs 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 re-use the existing MIB definition -instead of a defining a new MIB. +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 end +points. 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 re-use and +extend the existing MIB module definition instead of defining a new MIB +module. -This document defines four 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 -new MIB modules are required for MPLS-TP functionality, these are -retained in the same document, instead of a separate document. +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. 5. Feature List -This document identifies the following requirements and constraints: +The MIBs in this document satisfy the following requirements and +constraints: -The MIB module supports static and signaled point-to-point, co-routed -bi-directional and associated bi-directional tunnels. +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. + to configure an MPLS TP tunnel as an interface. Same ifType 150, + as defined in section 8 of [RFC3812], will be used for MPLS-TP + tunnels as well. - - The mplsTunnelTable [RFC3812] to be also used for MPLS-TP - tunnels + - The mplsTunnelTable [RFC3812] is also to be used for MPLS-TP + tunnels. - - New MPLS-TP specific textual conventions and identifiers + - New MPLS-TP specific textual conventions and identifiers are + required. - The mplsTunnelTable is sparsely extended to support MPLS-TP tunnel specific objects. - - A node configuration table (mplsTunnelExtNodeConfigTable) - is used to translate the Global_ID::Node_ID or - ICC_Operator_ID::Node_ID to the local identifier in order - to index mplsTunnelTable. + - A node configuration table (mplsTunnelExtNodeConfigTable), as + detailed in the below section 6.1.2, is used to translate + the Global_ID::Node_ID or ICC_Operator_ID::Node_ID to + the local identifier in order to index mplsTunnelTable. - The mplsXCTable is sparsely extended to support MPLS-TP XC(Cross Connect) specific objects. - The MIB module supports persistent, as well as non-persistent tunnels. -6. Brief description of MIB modules +6. Outline - This section describes the MIB modules present in this document. The - tables and MIB modules that are mentioned in the below subsections - support the functionality described in documents [RFC5654] and - [RFC6370]. The tables support both IP compatible and ICC based +Traffic Engineering support for the MPLS-TP tunnels requires the set up +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 documents [RFC5654] and [RFC6370]. These +tables support both IP compatible and ITU Carrier Code (ICC) based tunnel configurations. - The below diagram depicts how the table references are followed in - this MIB. +The below Figure 1 depicts how the table references are followed in this +MIB. Tunnel1-->XC1<-------------- ^ ^ | | | | | | |-->InSeg1 | | | | |-->OutSeg1 | | | v | | ------XCext1 | | | | V v | Tunnel2-->XC1 | ^ | | | | | |-->InSeg2 | | | |-->OutSeg2 | | v | ------XCext2------------ -6.1. mplsTunnelExtNodeConfigTable +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. 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. + +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 alphabetic characters represented with upper case letters (i.e., A-Z). The ICC is a string of one to six characters, each character being either alphabetic (i.e. A-Z) or numeric (i.e. 0-9) characters. Alphabetic characters in the ICC should be represented with upper case letters. In the IP compatible mode, Global_ID::Node_ID, is used to uniquely identify a node. For @@ -302,73 +391,94 @@ 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 LSR ID in mplsTunnelTable. -6.2. mplsTunnelExtNodeIpMapTable +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 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, while indexing mplsTunnelTable. -6.3. mplsTunnelExtNodeIccMapTable +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, while indexing mplsTunnelTable. -6.4. mplsTunnelExtTable +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 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.5 MPLS-TC-EXT-STD-MIB +6.3 MPLS-TC-EXT-STD-MIB - This MIB module contains Textual Conventions for LSPs of MPLS based + This MIB module contains textual Conventions for LSPs of MPLS based transport networks. -6.6 MPLS-ID-STD-MIB - +6.4 MPLS-ID-STD-MIB This MIB module contains generic object definitions for MPLS Traffic Engineering in transport networks. -6.7 MPLS-LSR-EXT-STD-MIB +6.5 MPLS-LSR-EXT-STD-MIB - This MIB module contains generic object definitions for MPLS LSR in - transport networks. + This MIB module contains generic object definitions (Cross connect + extension table - mplsXCExtTable, for setting up the MPLS-TP LSPs + with sparse extension of mplsXCTable) for MPLS LSRs in transport + networks. -7. MIB Module Interdependencies +6.6 The Use of RowPointer + + This document follows the RowPointer usage as described in the + section 10 of [RFC3812]. + + A new RowPointer object, mplsTunnelExtOppositeDirPtr, is added to + mplsTunnelExtTable of MPLS-TE-EXT-STD-MIB MIB module. This RowPointer + object points to the opposite direction tunnel entry. + + Two additional RowPointers objects, mplsXCExtTunnelPointer and + mplsXCExtOppositeDirXCPtr are added to mplsXCExtTable of MPLS-LSR- + EXT-STD-MIB. The RowPointer mplsXCExtTunnelPointer is 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 these RowPointer returns zeroDotZero, it implies that there is no + entry associated with the RowPointer object. + +7. MIB Modules Interdependencies This section provides an overview of the relationship 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 "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. @@ -386,20 +496,22 @@ | 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]. @@ -438,46 +550,47 @@ | | | | | | | 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. New mplsTunnelExtTable table provides the reverse direction LSP information for the existing tunnel table in order to achieve bidirectional LSPs. mplsXCExtTable sparsely extends the mplsLsrXCTable to provide backward reference to tunnel entry. 9. Example of MPLS-TP Tunnel Setup In this section, we provide an example to configure MPLS-TP bidirectional tunnels with IP tunnel identifiers. This example - provides the usage of MPLS-TP Tunnel MIB along with the extended new - MIB modules introduced in this document. + provides the usage of MPLS-TP Tunnel MIB along with the extended MIB + modules introduced in this document. Do note that a MPLS-TP tunnel could be setup statically as well as signaled via control plane. This example considers accessing MIB objects on a head-end for a static and signaled MPLS-TP tunnels. This section shows the configuration of the forward and reverse direction - MPLS-TP LSPs that runs between East and West and vice-versa. Only - relevant objects which are applicable for MPLS-TP tunnel are - illustrated here. + MPLS-TP LSPs that run between East and West and vice-versa. Only + objects relevant to MPLS-TP tunnels are illustrated here. In mplsTunnelExtNodeConfigTable: { -- Non-IP Ingress LSR-Id (Index to the table) mplsTunnelExtNodeConfigLocalId = 1, mplsTunnelExtNodeConfigGlobalId = 1234, mplsTunnelExtNodeConfigNodeId = 10, @@ -665,44 +779,44 @@ In mplsXCExtTable (0x01, 0x00000001, 0x00000000) { -- Back pointer from XC table to Tunnel table mplsXCExtTunnelPointer = mplsTunnelName.1.1.1.2 mplsXCExtOppositeDirXCPtr = mplsXCLspId.4.0.0.0.1.1.0.4.0.0.0.1 } 9.2. Example of MPLS-TP static associated bidirectional tunnel setup - The MPLS-TP associated bidirectional tunnel has two different - direction tunnels[Forward and Reverse LSPs] and these are - associated together using mplsTunnelExtTable. Two different - tunnel entries for both forward and reverse direction MAY be used - for co-routed bidirectional tunnel as well. + The MPLS-TP associated bidirectional tunnel is implemented by two + different unidirectional tunnels [Forward and Reverse LSPs] and these + are associated together using mplsTunnelExtTable. Two different + tunnel entries to provide the forward and reverse directions MAY be + used for co-routed bidirectional tunnels as well. The following denotes the associated bidirectional forward tunnel "head" entry: 9.2.1. Forward direction mplsTunnelEntry In mplsTunnelTable: { mplsTunnelIndex = 1, mplsTunnelInstance = 1, -- Local map number created in mplsTunnelExtNodeConfigTable for -- Ingress LSR-Id mplsTunnelIngressLSRId = 1, -- Local map number created in mplsTunnelExtNodeConfigTable for -- Egress LSR-Id mplsTunnelEgressLSRId = 2, - mplsTunnelName = "TP associated bi-directional + mplsTunnelName = "TP associated bidirectional forward LSP", mplsTunnelDescr = "East to West", mplsTunnelIsIf = true (1), -- RowPointer MUST point to the first accessible column mplsTunnelXCPointer = mplsXCLspId.4.0.0.0.1.1.0.4.0.0.0.1, mplsTunnelSignallingProto = none (1), mplsTunnelSetupPrio = 0, mplsTunnelHoldingPrio = 0, mplsTunnelSessionAttributes = 0, @@ -781,21 +894,21 @@ { mplsTunnelIndex = 2, mplsTunnelInstance = 1, -- Local map number created in mplsTunnelExtNodeConfigTable for -- Ingress LSR-Id mplsTunnelIngressLSRId = 2, -- Local map number created in mplsTunnelExtNodeConfigTable for -- Egress LSR-Id mplsTunnelEgressLSRId = 1, - mplsTunnelName = "TP associated bi-directional + mplsTunnelName = "TP associated bidirectional reverse LSP", mplsTunnelDescr = "West to East", mplsTunnelIsIf = true (1), -- RowPointer MUST point to the first accessible column mplsTunnelXCPointer = mplsXCLspId.4.0.0.0.1.4.0.0.0.1.1.0, mplsTunnelSignallingProto = none (1), mplsTunnelSetupPrio = 0, mplsTunnelHoldingPrio = 0, mplsTunnelSessionAttributes = 0, @@ -1004,21 +1116,21 @@ FROM SNMPv2-TC -- [RFC2579] mplsStdMIB FROM MPLS-TC-STD-MIB -- [RFC3811] ; mplsTcExtStdMIB MODULE-IDENTITY LAST-UPDATED - "201405050000Z" -- May 05, 2014 + "201412120000Z" -- December 12, 2014 ORGANIZATION "Multiprotocol Label Switching (MPLS) Working Group" CONTACT-INFO " Venkatesan Mahalingam Dell Inc, 5450 Great America Parkway, Santa Clara, CA 95054, USA Email: venkat.mahalingams@gmail.com @@ -1040,30 +1153,30 @@ "Copyright (c) 2014 IETF Trust and the persons identified as the document authors. All rights reserved. This MIB module contains Textual Conventions for LSPs of MPLS based transport networks." -- Revision history. REVISION - "201405050000Z" -- May 05, 2014 + "201412120000Z" -- December 12, 2014 DESCRIPTION "MPLS Textual Convention Extensions" - ::= { mplsStdMIB xxx } -- xxx to be replaced with correct value + ::= { mplsStdMIB www } -- www to be replaced with correct value MplsGlobalId ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION - "This object contains the Textual Convention of IP based + "This object contains the Textual Convention for IP based operator unique identifier (Global_ID), the Global_ID can contain the 2-octet or 4-octet value of the operator's Autonomous System Number (ASN). When the Global_ID is derived from a 2-octet AS number, the two high-order octets of this 4-octet identifier MUST be set to zero(0x00). Further ASN 0 is reserved. The size of the Global_ID string MUST be zero if the Global_ID is invalid. @@ -1134,26 +1247,25 @@ IMPORTS MODULE-IDENTITY, OBJECT-TYPE FROM SNMPv2-SMI -- [RFC2578] MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF -- [RFC2580] mplsStdMIB FROM MPLS-TC-STD-MIB -- [RFC3811] MplsGlobalId, MplsCcId, MplsIccId, MplsNodeId FROM MPLS-TC-EXT-STD-MIB - ; mplsIdStdMIB MODULE-IDENTITY LAST-UPDATED - "201405050000Z" -- May 05, 2014 + "201412120000Z" -- December 12, 2014 ORGANIZATION "Multiprotocol Label Switching (MPLS) Working Group" CONTACT-INFO " Venkatesan Mahalingam Dell Inc, 5450 Great America Parkway, Santa Clara, CA 95054, USA Email: venkat.mahalingams@gmail.com @@ -1176,26 +1288,27 @@ DESCRIPTION "Copyright (c) 2014 IETF Trust and the persons identified as the document authors. All rights reserved. This MIB module contains generic object definitions for MPLS Traffic Engineering in transport networks." -- Revision history. REVISION - "201405050000Z" -- May 05, 2014 + "201412120000Z" -- December 12, 2014 DESCRIPTION "This MIB modules defines the MIB objects for MPLS-TP identifiers" ::= { mplsStdMIB xxx } -- xxx to be replaced with correct value + -- notifications mplsIdNotifications OBJECT IDENTIFIER ::= { mplsIdStdMIB 0 } -- tables, scalars mplsIdObjects OBJECT IDENTIFIER ::= { mplsIdStdMIB 1 } -- conformance mplsIdConformance OBJECT IDENTIFIER ::= { mplsIdStdMIB 2 } -- MPLS common objects mplsIdGlobalId OBJECT-TYPE @@ -1377,21 +1488,21 @@ FROM MPLS-TC-STD-MIB -- [RFC3811] RowPointer FROM SNMPv2-TC -- [RFC2579] mplsXCIndex, mplsXCInSegmentIndex, mplsXCOutSegmentIndex, mplsInterfaceGroup, mplsInSegmentGroup, mplsOutSegmentGroup, mplsXCGroup, mplsLsrNotificationGroup FROM MPLS-LSR-STD-MIB; -- [RFC3813] mplsLsrExtStdMIB MODULE-IDENTITY LAST-UPDATED - "201405050000Z" -- May 05, 2014 + "201412120000Z" -- December 12, 2014 ORGANIZATION "Multiprotocol Label Switching (MPLS) Working Group" CONTACT-INFO " Venkatesan Mahalingam Dell Inc, 5450 Great America Parkway, Santa Clara, CA 95054, USA Email: venkat.mahalingams@gmail.com @@ -1413,25 +1524,25 @@ DESCRIPTION "Copyright (c) 2014 IETF Trust and the persons identified as the document authors. All rights reserved. This MIB module contains generic object definitions for MPLS LSR in transport networks." -- Revision history. REVISION - "201405050000Z" -- May 05, 2014 + "201412120000Z" -- December 12, 2014 DESCRIPTION "MPLS LSR specific MIB objects extension" - ::= { mplsStdMIB xxx } -- xxx to be replaced with correct value + ::= { mplsStdMIB yyy } -- yyy to be replaced with correct value -- notifications mplsLsrExtNotifications OBJECT IDENTIFIER ::= { mplsLsrExtStdMIB 0 } -- tables, scalars mplsLsrExtObjects OBJECT IDENTIFIER ::= { mplsLsrExtStdMIB 1 } -- conformance mplsLsrExtConformance OBJECT IDENTIFIER ::= { mplsLsrExtStdMIB 2 } @@ -1559,21 +1669,21 @@ mplsInterfaceGroup, mplsInSegmentGroup, mplsOutSegmentGroup } MODULE -- this module GROUP mplsXCExtReadOnlyObjectsGroup DESCRIPTION "This group is mandatory for devices which support - Opposite direction XC configuration of tunnels." + opposite direction XC configuration of tunnels." -- mplsXCExtTable OBJECT mplsXCExtOppositeDirXCPtr MIN-ACCESS read-only DESCRIPTION "Write access is not required. This object indicates the pointer to the opposite direction XC entry. The only valid value for XC Pointer is mplsXCTable entry." ::= { mplsLsrExtCompliances 2 } @@ -1603,42 +1713,41 @@ ::= { mplsLsrExtGroups 2 } -- MPLS-LSR-EXT-STD-MIB module ends END 13. MPLS Tunnel Extension MIB definitions MPLS-TE-EXT-STD-MIB DEFINITIONS ::= BEGIN IMPORTS - MODULE-IDENTITY, OBJECT-TYPE, Counter32, - Counter64, zeroDotZero + MODULE-IDENTITY, OBJECT-TYPE FROM SNMPv2-SMI -- [RFC2578] MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF -- [RFC2580] TruthValue, RowStatus, RowPointer, StorageType FROM SNMPv2-TC -- [RFC2579] IndexIntegerNextFree FROM DIFFSERV-MIB -- [RFC3289] MplsGlobalId, MplsNodeId, MplsCcId, MplsIccId FROM MPLS-TC-EXT-STD-MIB mplsStdMIB, MplsTunnelIndex, MplsTunnelInstanceIndex, MplsExtendedTunnelId FROM MPLS-TC-STD-MIB -- [RFC3811] mplsTunnelIndex, mplsTunnelInstance, mplsTunnelIngressLSRId, mplsTunnelEgressLSRId FROM MPLS-TE-STD-MIB -- [RFC3812] ; mplsTeExtStdMIB MODULE-IDENTITY LAST-UPDATED - "201405050000Z" -- May 05, 2014 + "201412120000Z" -- December 12, 2014 ORGANIZATION "Multiprotocol Label Switching (MPLS) Working Group" CONTACT-INFO " Venkatesan Mahalingam Dell Inc, 5450 Great America Parkway, Santa Clara, CA 95054, USA Email: venkat.mahalingams@gmail.com @@ -1659,26 +1768,26 @@ DESCRIPTION "Copyright (c) 2014 IETF Trust and the persons identified as the document authors. All rights reserved. This MIB module contains generic object definitions for MPLS Traffic Engineering in transport networks." -- Revision history. REVISION - "201405050000Z" -- May 05, 2014 + "201412120000Z" -- December 12, 2014 DESCRIPTION "MPLS TE MIB objects extension" - ::= { mplsStdMIB xxx } -- xxx to be replaced + ::= { mplsStdMIB zzz } -- zzz to be replaced -- with correct value -- Top level components of this MIB module. -- tables, scalars mplsTeExtObjects OBJECT IDENTIFIER ::= { mplsTeExtStdMIB 0 } -- conformance mplsTeExtConformance OBJECT IDENTIFIER ::= { mplsTeExtStdMIB 1 } @@ -1759,36 +1868,37 @@ MAX-ACCESS not-accessible STATUS current DESCRIPTION "This object is used in accommodating the bigger size Global_ID::Node_ID and/or the ICC_Operator_ID::Node_ID with lower size LSR identifier in order to index the mplsTunnelTable. The Local Identifier is configured between 0 and 16777215, as valid IP address range starts from 16777216(01.00.00.00). - This range is chosen to identify the mplsTunnelTable's - Ingress/Egress LSR-id is IP address or Local identifier, - if the configured range is not IP address, operator is - expected to retrieve the complete information - (Global_ID::Node_ID or ICC_Operator_ID::Node_ID) from + This range is chosen to determine whether the + mplsTunnelTable's Ingress/Egress LSR-id is an IP address or + Local identifier. If the configured range is not an + IP address, the operator is expected to retrieve the + complete information (Global_ID::Node_ID or + ICC_Operator_ID::Node_ID) from mplsTunnelExtNodeConfigTable. This way, existing mplsTunnelTable is reused for bidirectional tunnel extensions for MPLS based transport networks. - This Local Identifier allows the operator to assign + The Local Identifier allows the operator to assign a unique identifier to map Global_ID::Node_ID and/or ICC_Operator_ID::Node_ID. As this Local Identifier is unique within the node and the same syntax of this object can be - used for MPLS TE tunnel also, it is up to the operator/local - management entity to choose the non-conflicting value for + used for MPLS-TE tunnel also, it is up to the operator/local + management entity to choose non-conflicting value for indexing the MPLS and MPLS-TP tunnel entries." ::= { mplsTunnelExtNodeConfigEntry 1 } mplsTunnelExtNodeConfigGlobalId OBJECT-TYPE SYNTAX MplsGlobalId MAX-ACCESS read-create STATUS current DESCRIPTION "This object indicates the Global Operator Identifier. This object has no meaning when @@ -1893,21 +2003,21 @@ STATUS current DESCRIPTION "This read-only table allows the operator to retrieve the local identifier for a given Global_ID::Node_ID in an IP compatible operator environment. This table MAY be used in on-demand and/or proactive OAM operations to get the Ingress/Egress LSR identifier (Local Identifier) from Src-Global_Node_ID - or Dst-Global_Node_ID and the Ingress and Egress LSR + or Dst-Global_Node_ID. The Ingress and Egress LSR identifiers are used to retrieve the tunnel entry. This table returns nothing when the associated entry is not defined in mplsTunnelExtNodeConfigTable." ::= { mplsTeExtObjects 3 } mplsTunnelExtNodeIpMapEntry OBJECT-TYPE SYNTAX MplsTunnelExtNodeIpMapEntry MAX-ACCESS not-accessible STATUS current @@ -1968,21 +2078,21 @@ MAX-ACCESS not-accessible STATUS current DESCRIPTION "This read-only table allows the operator to retrieve the local identifier for a given ICC_Operator_ID::Node_ID in an ICC operator environment. This table MAY be used in on-demand and/or proactive OAM operations to get the Ingress/Egress LSR identifier (Local Identifier) from Src-ICC - or Dst-ICC and the Ingress and Egress LSR + or Dst-ICC. The Ingress and Egress LSR identifiers are used to retrieve the tunnel entry. This table returns nothing when the associated entry is not defined in mplsTunnelExtNodeConfigTable." ::= { mplsTeExtObjects 4 } mplsTunnelExtNodeIccMapEntry OBJECT-TYPE SYNTAX MplsTunnelExtNodeIccMapEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION @@ -2427,81 +2535,47 @@ STATUS current DESCRIPTION "Object(s) needed to implement ICC based tunnels." ::= { mplsTeExtGroups 3 } -- MPLS-TE-EXT-STD-MIB module ends END 14. Security Consideration - It is clear that this MIB module is potentially useful for the - monitoring of MPLS TE tunnels. This MIB module can also be used for - the configuration of certain objects, and anything that can be - configured can be incorrectly configured, with potentially disastrous - results. + This document follows the security consideration mentioned in the + section 12 of [RFC3812]. These security considerations are also + applicable to the MIB objects and tables defined in this draft, which + are identified as below. - There are a number of management objects defined in this MIB module - 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. These are the tables and objects and their - sensitivity/vulnerability: + Security consideration for read-write and/or read-create objects is + also applicable for - - the tables specified in [RFC3812], [RFC3813] and this document - MIB tables mplsTunnelExtNodeConfigTable, mplsTunnelExtTable and + - mplsTunnelExtNodeConfigTable, mplsTunnelExtTable and mplsXCExtTable collectively contain objects to provision MPLS-TP tunnels, tunnel hops, and tunnel resources. - Unauthorized access to objects in these tables, could result in - disruption of traffic on the network. This is especially true if - a tunnel has 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 v3 agent - which implements this MIB. Administrators should consider whether - read access to these objects should be allowed, since read access - may be undesirable under certain circumstances. - Some of the readable objects in this MIB module (i.e., objects - with a MAX-ACCESS other than not-accessible) may be considered - sensitive or 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 - objects when sending them over the network via SNMP. These are - the tables and objects and their sensitivity/vulnerability: + Some of the readable objects in this MIB module (i.e., objects with a + MAX-ACCESS other than not-accessible) may be considered sensitive or + vulnerable in some network environments. - - the tables specified in [RFC3812], [RFC3813] and this document - MIB tables mplsTunnelExtNodeConfigTable, mplsTunnelExtTable, + - mplsTunnelExtNodeConfigTable, mplsTunnelExtTable, and mplsXCExtTable collectively show the MPLS-TP tunnel network topology characteristics. If an Administrator does not 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 example by using IPsec), - even then, there is no control as to who on the secure network is - allowed to access and GET/SET (read/change/create/delete) - the objects in this MIB module. - - It is recommended that implementers consider the security features as - provided by the SNMPv3 framework (see [RFC3410], section 8), - including full supports for the SNMPv3 cryptographic mechanisms (for - authentication and privacy). - - Further, deployment of SNMP versions prior to SNMPv3 is not - recommended. Instead, it is recommended to deploy SNMPv3 and to - enable cryptographic security. It is then a 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 principles (users) that - have legitimate rights to indeed GET or SET (change/create/delete) - them. + When MIB is used to configure ICC_Operator_ID, as specified in + [RFC6370], it should be considered sensitive operation. Hence proper + protection should be taken to allow configuration via SET operation + in order to ensure its purpose of providing globally unique MPLS-TP + identifiers. 15. IANA Considerations As described in [RFC4221], [RFC6639] and as requested in the MPLS-TC- STD-MIB [RFC3811], MPLS related standards track MIB modules should be rooted under the mplsStdMIB subtree. There are 4 MPLS MIB Modules contained in this document, each of the following "IANA Considerations" subsections requests IANA for a new assignment under the mplsStdMIB subtree. New assignments can only be made via a Standards Action as specified in [RFC5226]. @@ -2543,81 +2618,83 @@ "Conformance Statements for SMIv2", STD 58, RFC 2580, April 1999. [RFC3031] Rosen, E., Viswanathan, A., and R. Callon, "Multiprotocol Label Switching Architecture", RFC 3031, January 2001. [RFC3289] Baker, F., Chan, K., and A. Smith, "Management Information Base for the Differentiated Services Architecture", RFC 3289, May 2002. -16.2. Informative References - - [RFC3410] J. Case, R. Mundy, D. pertain, B.Stewart, "Introduction - and Applicability Statement for Internet Standard - Management Framework", RFC 3410, December 2002. - [RFC3811] Nadeau, T., Ed., and J. Cucchiara, Ed., "Definitions of Textual Conventions (TCs) for Multiprotocol Label Switching (MPLS) Management", RFC 3811, June 2004. [RFC3812] Srinivasan, C., Viswanathan, A., and T. Nadeau, "Multiprotocol Label Switching (MPLS) Traffic Engineering (TE) Management Information Base (MIB)", RFC 3812, June 2004. [RFC3813] Srinivasan, C., Viswanathan, A., and T. Nadeau, "Multiprotocol Label Switching (MPLS) Label Switching (LSR) Router Management Information Base (MIB)", RFC 3813, June 2004. - [RFC4221] Nadeau, T., Srinivasan, C., and A. Farrel, "MSMGMT Label - Switching (MPLS) Management Overview", RFC 4221, November - 2005. - [RFC4802] Nadeau, T., Ed., and A. Farrel, Ed., "Generalized Multiprotocol Label Switching (GMPLS) Traffic Engineering Management Information Base", RFC 4802, February 2007. + [RFC6370] Bocci, M., Swallow, G., and E. Gray, "MPLS Transport + Profile (MPLS-TP) Identifiers", RFC 6370, September 2011. + + [RFC6923] Winter, R., Gray, E., Helvoort, H., and M. Betts, "MPLS-TP + Identifiers Following ITU-T Conventions", RFC 6923, May + 2013 + +16.2. Informative References + + [RFC3410] J. Case, R. Mundy, D. pertain, B.Stewart, "Introduction + and Applicability Statement for Internet Standard + Management Framework", RFC 3410, December 2002. + + [RFC4221] Nadeau, T., Srinivasan, C., and A. Farrel, "Multiprotocol + Label Switching (MPLS) Management Overview", RFC 4221, + November 2005. + [RFC5226] Narten, T. and H. Alvestrand., "Guidelines for Writing an IANA Considerations Section in RFCs", BCP 26, RFC 5226, May 2008. [RFC5654] Niven-Jenkins, B., Ed., Brungard, D., Ed., Betts, M., Ed.,Sprecher, N., and S. Ueno, "Requirements of an MPLS Transport Profile", RFC 5654, September 2009. - [RFC6370] Bocci, M., Swallow, G., and E. Gray, "MPLS Transport - Profile (MPLS-TP) Identifiers", RFC 6370, September 2011. - [RFC6639] Venkatesan, M., King, D., "Multiprotocol Label Switching Transport Profile (MPLS-TP) MIB-Based Management Overview", RFC 6639, June 2012 - [RFC6923] Winter, R., Gray, E., Helvoort, H., and M. Betts, "MPLS-TP - Identifiers Following ITU-T Conventions", RFC 6923, May - 2013 - 17. Acknowledgments The authors would like to thank Francesco Fondelli, Josh Littlefield, - Agrahara Kiran Koushik, Metrri Jain, Muly Ilan, Randy Presuhn and - Adrian Farrel for their valuable comments. A special thanks to Joan - Cucchiara for really getting the MIB modules into shape. + Agrahara Kiran Koushik, Metrri Jain, Muly Ilan, Randy Presuhn, Adrian + Farrel, Elwyn Davies and Tom Taylor for their valuable review and + comments. A special thanks to Joan Cucchiara for really getting the + MIB modules into shape. 18. Authors' Addresses Venkatesan Mahalingam Dell Inc. 5450 Great America Parkway, Santa Clara, CA 95054, USA Email: venkat.mahalingams@gmail.com + Sam Aldrin Huawei Technologies 2330 Central Express Way, Santa Clara, CA 95051, USA Email: aldrin.ietf@gmail.com Thomas D. Nadeau Brocade Email: tnadeau@lucidvision.com