--- 1/draft-ietf-mpls-tp-te-mib-05.txt 2013-05-09 02:14:23.642509262 +0100 +++ 2/draft-ietf-mpls-tp-te-mib-06.txt 2013-05-09 02:14:23.742511533 +0100 @@ -1,25 +1,25 @@ Network Working Group INTERNET-DRAFT M.Venkatesan Intended Status: Standards Track Dell Inc. -Expires: July 18, 2013 Kannan KV Sampath +Expires: November 09, 2013 Kannan KV Sampath Redeem Sam K. Aldrin Huawei Technologies Thomas D. Nadeau Juniper Networks - January 14, 2013 + May 08, 2013 MPLS-TP Traffic Engineering (TE) Management Information Base (MIB) - draft-ietf-mpls-tp-te-mib-05.txt + draft-ietf-mpls-tp-te-mib-06.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 managed objects of Tunnels, Identifiers, Label Switch Router and Textual conventions for Multiprotocol Label Switching (MPLS) based Transport Profile (TP). Status of this Memo @@ -36,21 +36,21 @@ 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 July 18, 2013. + This Internet-Draft will expire on November 09, 2013. Copyright and License Notice Copyright (c) 2013 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 @@ -52,105 +52,103 @@ 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 - 3.3. Acronyms . . . . . . . . . . . . . . . . . . . . . . . . . 5 - 4. Motivations . . . . . . . . . . . . . . . . . . . . . . . . . . 5 - 5. Feature List . . . . . . . . . . . . . . . . . . . . . . . . . 5 - 6. Brief description of MIB Objects . . . . . . . . . . . . . . . 5 - 6.1. mplsTunnelExtNodeConfigTable . . . . . . . . . . . . . . . 6 - 6.2. mplsTunnelExtNodeIpMapTable . . . . . . . . . . . . . . . . 6 - 6.3. mplsTunnelExtNodeIccMapTable . . . . . . . . . . . . . . . 7 - 6.4. mplsTunnelExtTable . . . . . . . . . . . . . . . . . . . . 7 - 6.5. mplsTunnelExtReversePerfTable . . . . . . . . . . . . . . . 7 - 7. MIB Module Interdependencies . . . . . . . . . . . . . . . . . 7 - 8. Dependencies between MIB Module Tables . . . . . . . . . . . . 9 - 9. Example of MPLS-TP Tunnel Setup . . . . . . . . . . . . . . . . 9 + 3.3. Acronyms . . . . . . . . . . . . . . . . . . . . . . . . . 6 + 4. Motivations . . . . . . . . . . . . . . . . . . . . . . . . . . 6 + 5. Feature List . . . . . . . . . . . . . . . . . . . . . . . . . 6 + 6. Brief description of MPLS-TE-EXT-STD-MIB Objects . . . . . . . 7 + 6.1. mplsTunnelExtNodeConfigTable . . . . . . . . . . . . . . . 7 + 6.2. mplsTunnelExtNodeIpMapTable . . . . . . . . . . . . . . . . 8 + 6.3. mplsTunnelExtNodeIccMapTable . . . . . . . . . . . . . . . 8 + 6.4. mplsTunnelExtTable . . . . . . . . . . . . . . . . . . . . 8 + 6.5. mplsTunnelExtReversePerfTable . . . . . . . . . . . . . . . 8 + 7. MIB Module Interdependencies . . . . . . . . . . . . . . . . . 8 + 8. Dependencies between MIB Module Tables . . . . . . . . . . . . 11 9.1. Example of MPLS-TP static co-routed bidirectional tunnel - setup . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 - 9.1.1. mplsTunnelEntry . . . . . . . . . . . . . . . . . . . . 10 - 9.1.2. mplsTunnelExtEntry . . . . . . . . . . . . . . . . . . 11 - 9.1.3. Forward direction mplsOutSegmentEntry . . . . . . . . . 12 - 9.1.4. Reverse direction mplsInSegmentEntry . . . . . . . . . 12 - 9.1.5. Forward direction mplsXCEntry . . . . . . . . . . . . . 12 - 9.1.6. Reverse direction mplsXCEntry . . . . . . . . . . . . . 13 - 9.1.7. Forward direction mplsXCExtEntry . . . . . . . . . . . 13 - 9.1.8. Reverse direction mplsXCExtEntry . . . . . . . . . . . 13 - 9.1.9. mplsTunnelExtReversePerfTable . . . . . . . . . . . . . 13 - + setup . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 + 9.1.1. mplsTunnelEntry . . . . . . . . . . . . . . . . . . . . 12 + 9.1.2. mplsTunnelExtEntry . . . . . . . . . . . . . . . . . . 13 + 9.1.3. Forward direction mplsOutSegmentEntry . . . . . . . . . 14 + 9.1.4. Reverse direction mplsInSegmentEntry . . . . . . . . . 14 + 9.1.5. Forward direction mplsXCEntry . . . . . . . . . . . . . 14 + 9.1.6. Reverse direction mplsXCEntry . . . . . . . . . . . . . 15 + 9.1.7. Forward direction mplsXCExtEntry . . . . . . . . . . . 15 + 9.1.8. Reverse direction mplsXCExtEntry . . . . . . . . . . . 15 + 9.1.9. mplsTunnelExtReversePerfTable . . . . . . . . . . . . . 15 9.2. Example of MPLS-TP static associated bidirectional tunnel - setup . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 - 9.2.1. Forward direction mplsTunnelEntry . . . . . . . . . . . 14 - 9.2.2. Forward direction mplsTunnelExtEntry . . . . . . . . . 15 - 9.2.3. Forward direction mplsOutSegmentTable . . . . . . . . . 15 - 9.2.4. Forward direction mplsXCEntry . . . . . . . . . . . . . 15 - 9.2.5. Forward direction mplsXCExtEntry . . . . . . . . . . . 16 - 9.2.6. Reverse direction mplsTunnelEntry . . . . . . . . . . . 16 - 9.2.7. Reverse direction mplsTunnelExtEntry . . . . . . . . . 17 - 9.2.8. Reverse direction mplsInSegmentEntry . . . . . . . . . 17 - 9.2.9. Reverse direction mplsXCEntry . . . . . . . . . . . . . 17 - 9.2.10. Reverse direction mplsXCExtEntry . . . . . . . . . . . 18 - 9.3. Example of MPLS-TP signaling co-routed bidirectional - tunnel setup . . . . . . . . . . . . . . . . . . . . . . . 18 - 9.3.1. mplsTunnelEntry . . . . . . . . . . . . . . . . . . . . 18 - 9.3.2. mplsTunnelExtEntry . . . . . . . . . . . . . . . . . . 19 - 9.3.3. Forward direction mplsOutSegmentEntry . . . . . . . . . 19 - 9.3.4. Reverse direction mplsInSegmentEntry . . . . . . . . . 19 - 9.3.5. Forward direction mplsXCEntry . . . . . . . . . . . . . 20 - 9.3.6. Reverse direction mplsXCEntry . . . . . . . . . . . . . 20 - 9.3.7. Forward direction mplsXCExtEntry . . . . . . . . . . . 20 - 9.3.8. Reverse direction mplsXCExtEntry . . . . . . . . . . . 20 - 9.3.9. mplsTunnelExtReversePerfTable . . . . . . . . . . . . . 20 - 10. MPLS Textual Convention Extension MIB definitions . . . . . . 20 - 11. MPLS Identifier MIB definitions . . . . . . . . . . . . . . . 23 - 12. MPLS LSR Extension MIB definitions . . . . . . . . . . . . . . 27 - 13. MPLS Tunnel Extension MIB definitions . . . . . . . . . . . . 31 - 14. Security Consideration . . . . . . . . . . . . . . . . . . . . 49 - 15. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 50 - 16. References . . . . . . . . . . . . . . . . . . . . . . . . . . 50 - 16.1. Normative References . . . . . . . . . . . . . . . . . . . 50 - 16.2. Informative References . . . . . . . . . . . . . . . . . 50 - 17. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 51 - 18. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 51 + setup . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 + 9.2.1. Forward direction mplsTunnelEntry . . . . . . . . . . . 16 + 9.2.2. Forward direction mplsTunnelExtEntry . . . . . . . . . 17 + 9.2.3. Forward direction mplsOutSegmentTable . . . . . . . . . 17 + 9.2.4. Forward direction mplsXCEntry . . . . . . . . . . . . . 17 + 9.2.5. Forward direction mplsXCExtEntry . . . . . . . . . . . 18 + 9.2.6. Reverse direction mplsTunnelEntry . . . . . . . . . . . 18 + 9.2.7. Reverse direction mplsTunnelExtEntry . . . . . . . . . 19 + 9.2.8. Reverse direction mplsInSegmentEntry . . . . . . . . . 19 + 9.2.9. Reverse direction mplsXCEntry . . . . . . . . . . . . . 19 + 9.2.10. Reverse direction mplsXCExtEntry . . . . . . . . . . . 20 + 9.3.1. mplsTunnelEntry . . . . . . . . . . . . . . . . . . . . 20 + 9.3.2. mplsTunnelExtEntry . . . . . . . . . . . . . . . . . . 21 + 9.3.3. Forward direction mplsOutSegmentEntry . . . . . . . . . 21 + 9.3.4. Reverse direction mplsInSegmentEntry . . . . . . . . . 21 + 9.3.5. Forward direction mplsXCEntry . . . . . . . . . . . . . 22 + 9.3.6. Reverse direction mplsXCEntry . . . . . . . . . . . . . 22 + 9.3.7. Forward direction mplsXCExtEntry . . . . . . . . . . . 22 + 9.3.8. Reverse direction mplsXCExtEntry . . . . . . . . . . . 22 + 9.3.9. mplsTunnelExtReversePerfTable . . . . . . . . . . . . . 22 + 11. MPLS Identifier MIB definitions . . . . . . . . . . . . . . . 25 + 12. MPLS LSR Extension MIB definitions . . . . . . . . . . . . . . 30 + 13. MPLS Tunnel Extension MIB definitions . . . . . . . . . . . . 35 + 14. Security Consideration . . . . . . . . . . . . . . . . . . . . 53 + 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 + 15.4. IANA Considerations for MPLS-TE-EXT-STD-MIB . . . . . . . 55 + 16. References . . . . . . . . . . . . . . . . . . . . . . . . . . 55 + 16.1. Normative References . . . . . . . . . . . . . . . . . . . 55 + 16.2. Informative References . . . . . . . . . . . . . . . . . 56 + 17. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 57 + 18. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 57 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 of Tunnels, Identifiers, Label Switch Router and Textual conventions for Multiprotocol Label Switching -(MPLS) based Transport Profile (TP). This draft extends the existing -MPLS MIB objects for both MPLS-TP and Non-MPLS-TP operations, so the -MPLS-TP name is not included in the MIB module name. +(MPLS) based Transport Profile (TP). These MIB modules extend the +existing MPLS MIB objects for both MPLS-TP and Non-MPLS-TP operations, +so the MPLS-TP name is not included in the MIB module name. The existing Multiprotocol Label Switching (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 transport network requirements of NON-IP based management and static bidirectional -tunnels. This MIB module should be used in conjunction with [RFC3812] -and companion document [RFC3813] for MPLS based traffic engineering -configuration and management. +tunnels. These MIB modules should be used in conjunction with [RFC3812] +and companion document [RFC3813] for MPLS-TP tunnel configuration and +management. The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14, RFC2119. 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 RFC3410 [RFC3410]. @@ -193,138 +191,140 @@ PW: Pseudowire 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. For example, MPLS-TP tunnels are bidirectional in -nature and could be used in non-IP environment. As the existing MPLS-TE- -STD-MIB is not sufficient to capture all the characteristics of the +nature and could be used in non-IP environments. As the existing MPLS- +TE-STD-MIB is not sufficient to capture all the characteristics of the tunnels, enhancing the MIB 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 new MIB. -This MIB also defines three other MIB modules within this document. As -these new MIB modules are small in size, MPLS-TC-EXT-STD-MIB, MPLS-ID- -STD-MIB and MPLS-LSR-EXT-STD-MIB are retained in the same document, -instead of a separate document. +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 small in size, these new MIB modules are retained in +the same document, instead of a separate document. 5. Feature List -The MPLS transport profile MIB module is designed to satisfy the -following requirements and constraints: +The MPLS-TE-EXT-STD-MIB is designed to satisfy the following +requirements and constraints: The MIB module supports static and signaling point-to-point, co-routed bi-directional and associated bi-directional tunnels. - The MPLS tunnels need not be interfaces, but it is possible to configure a TP tunnel as an interface. - The mplsTunnelTable [RFC3812] to be also used for MPLS-TP tunnels - The mplsTunnelTable is extended to support MPLS-TP specific objects. - A node configuration table (mplsTunnelExtNodeConfigTable) - is used to translate the Global_Node_ID or ICC to the local - identifier in order to index mplsTunnelTable. + is used to translate the Global_ID::Node_ID or CC::ICC to + the local identifier in order to index mplsTunnelTable. - The MIB module supports persistent, as well as non-persistent tunnels. -6. Brief description of MIB Objects +6. Brief description of MPLS-TE-EXT-STD-MIB Objects The objects described in this section support the functionality described in documents [RFC5654] and [RFC6370]. The tables support both IP compatible and ICC based tunnel configurations. 6.1. mplsTunnelExtNodeConfigTable The mplsTunnelExtNodeConfigTable is used to assign a local identifier - for a given ICC or Global_Node_ID combination as defined in - [RFC6370]. An 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_Node_ID, is used to uniquely identify a node. + for a given CC::ICC or Global_ID::Node_ID combination as defined in + [I-D.ietf-mpls-tp-itu-t-identifiers] 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. - Each ICC or Global_Node_ID contains one unique entry in the + Each CC::ICC or Global_ID::Node_ID contains one unique entry in the table representing a node. 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 environment, 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 environment, MPLS-TP tunnel is indexed by Tunnel Index, - Tunnel Instance, Source ICC and Destination ICC. + Tunnel Instance, Source CC, Source ICC, Destination CC and + Destination ICC. 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 or Global_Node_ID with a local identifier to be used as LSR ID in - mplsTunnelTable. As the regular TE tunnels use IP address as LSR ID, - the local identifier should be below the first valid IP address, - which is 16777216[1.0.0.0]. + CC::ICC or Global_ID::Node_ID with a local identifier to be used as + LSR ID in mplsTunnelTable. As the regular TE tunnels use IP address + as LSR ID, the local identifier should be below the first valid IP + address, which is 16777216[1.0.0.0]. 6.2. mplsTunnelExtNodeIpMapTable The read-only mplsTunnelExtNodeIpMaptable is used to query the local identifier assigned and stored in mplsTunnelExtNodeConfigTable for - a given Global_Node_ID. In order to query the local identifier, - in the IP compatible mode, this table is indexed with Global_Node_ID. - In the IP compatible mode for a TP tunnel, Global_Node_ID - is used. + 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_Node_ID identifiers. These local + Ingress and Egress Global_ID::Node_ID identifiers. These local identifiers are used as mplsTunnelIngressLSRId and mplsTunnelEgressLSRId, while indexing mplsTunnelTable. 6.3. mplsTunnelExtNodeIccMapTable The read-only mplsTunnelExtNodeIccMapTable is used to query the local identifier assigned and stored in the mplsTunnelExtNodeConfigTable - for a given ICC. + for a given CC::ICC. A separate query is made to get the local identifier of both - Ingress and Egress ICC. These local identifiers are used as + Ingress and Egress CC::ICC. These local identifiers are used as mplsTunnelIngressLSRId and mplsTunnelEgressLSRId, while indexing mplsTunnelTable. 6.4. mplsTunnelExtTable mplsTunnelExtTable 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. 6.5. mplsTunnelExtReversePerfTable - This table augments the mplsTunnelTable 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. + This table sparse augments the mplsTunnelTable 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. 7. MIB Module 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. @@ -390,23 +390,23 @@ | +---------+ | | | | | V V mplsTunnelTable ---->mplsXCTable ^ | | mplsTunnelExtTable An existing mplsTunnelTable uses the mplsTunnelExtNodeConfigTable - table to map the Global_Node_ID and/or ICC with the local number in - order to accommodate in the existing tunnel table's ingress/egress - LSR-id. + table to map the Global_ID::Node_ID and/or CC::ICC 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 is extended from mplsLsrXCTable to provide backward reference to tunnel entry. 9. Example of MPLS-TP Tunnel Setup In this section, we provide an example of the IP based MPLS-TP @@ -433,27 +433,27 @@ -- Non-IP Egress LSR-Id (Index to the table) mplsTunnelExtNodeConfigLocalId = 2, mplsTunnelExtNodeConfigGlobalId = 1234, mplsTunnelExtNodeConfigNodeId = 20, -- Mandatory parameters needed to activate the row go here mplsTunnelExtNodeConfigRowStatus = createAndGo (4) } This will create an entry in the mplsTunnelExtNodeConfigTable for a - Global_Node_ID. A separate entry is made for both Ingress LSR + Global_ID::Node_ID. A separate entry is made for both Ingress LSR and Egress LSR. The following read-only mplsTunnelExtNodeIpMapTable table is populated automatically upon creating an entry in mplsTunnelExtNodeConfigTable and this table is used to retrieve - the local identifier for the given Global_Node_ID. + the local identifier for the given Global_ID::Node_ID. In mplsTunnelExtNodeIpMapTable: { -- Global_ID (Index to the table) mplsTunnelExtNodeIpMapGlobalId = 1234, -- Node Identifier (Index to the table) mplsTunnelExtNodeIpMapNodeId = 10, mplsTunnelExtNodeIpMapLocalId = 1 @@ -959,21 +959,21 @@ FROM SNMPv2-TC -- [RFC2579] mplsStdMIB FROM MPLS-TC-STD-MIB -- [RFC3811] ; mplsTcExtStdMIB MODULE-IDENTITY LAST-UPDATED - "201301140000Z" -- January 14, 2013 + "201304130000Z" -- April 13, 2013 ORGANIZATION "Multiprotocol Label Switching (MPLS) Working Group" CONTACT-INFO " Venkatesan Mahalingam Dell Inc, 350 Holger way, San Jose, CA, USA Email: venkat.mahalingams@gmail.com Kannan KV Sampath @@ -991,27 +991,27 @@ Juniper Networks 10 Technology Park Drive, Westford, MA 01886 Email: tnadeau@juniper.net " DESCRIPTION "Copyright (c) 2013 IETF Trust and the persons identified as the document authors. All rights reserved. This MIB module contains Textual Conventions for - MPLS based transport networks." + LSPs and PWs of MPLS based transport networks." -- Revision history. REVISION - "201301140000Z" -- January 14, 2013 + "201304130000Z" -- April 13, 2013 DESCRIPTION "MPLS Textual Convention Extensions" ::= { mplsStdMIB xxx } -- xxx to be replaced with correct value MplsGlobalId ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "This object contains the Textual Convention of IP based @@ -1030,80 +1030,92 @@ the two high-order octets of this 4-octet identifier MUST be set to zero. Further ASN 0 is reserved. A Global_ID of zero means that no Global_ID is present. Note that a Global_ID of zero is limited to entities contained within a single operator and MUST NOT be used across an NNI. A non-zero Global_ID MUST be derived from an ASN owned by the operator." REFERENCE "MPLS Transport Profile (MPLS-TP) Identifiers, [RFC6370] - Section 3 Uniquely Identifying an Operator - the Global_ID" + Section 3" SYNTAX OCTET STRING (SIZE (4)) MplsNodeId ::= TEXTUAL-CONVENTION DISPLAY-HINT "d" STATUS current DESCRIPTION "The Node_ID is assigned within the scope of the Global_ID. The value 0(or 0.0.0.0 in dotted decimal notation) is reserved and MUST NOT be used. When IPv4 addresses are in use, the value of this object can be derived from the LSR's IPv4 loop back address. When IPv6 addresses are in use, the value of this object can be a 32-bit value unique within the scope of a Global_ID. Note that, when IP reach ability is not needed, the 32-bit Node_ID is not required to have any association with the IPv4 address space." REFERENCE - "MPLS Transport Profile (MPLS-TP) Identifiers, [RFC6370], - Section 4. Node and Interface Identifiers" - SYNTAX Unsigned32 -- the default range: (0..4294967295) + "MPLS Transport Profile (MPLS-TP) Identifiers, [RFC6370] + Section 4" + SYNTAX Unsigned32 (0|1..4294967295) + + MplsCcId ::= TEXTUAL-CONVENTION + STATUS current + DESCRIPTION + "The CC (Country Code) is a string of two alphabetic + characters represented with upper case + letters (i.e., A-Z)." + REFERENCE + "MPLS-TP Identifiers Following ITU-T Conventions, + draft-ietf-mpls-tp-itu-t-identifiers-08 (work in + progress), February 2013. Section 3" + SYNTAX OCTET STRING (SIZE (2)) MplsIccId ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "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." + with upper case letters. The ICC string should be assigned + to zero if the ICC identifier is invalid." REFERENCE "MPLS-TP Identifiers Following ITU-T Conventions, - [I-D.ietf-mpls-tp-itu-t-identifiers], Section 3. - Uniquely Identifying an Operator - the ICC_Operator_ID" - SYNTAX OCTET STRING (SIZE (1..6)) + draft-ietf-mpls-tp-itu-t-identifiers-08 (work in + progress), February 2013. Section 3" + SYNTAX OCTET STRING (SIZE (0..6)) -- MPLS-TC-EXT-STD-MIB module ends END 11. MPLS Identifier MIB definitions MPLS-ID-STD-MIB DEFINITIONS ::= BEGIN - 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, MplsIccId, MplsNodeId + MplsGlobalId, MplsCcId, MplsIccId, MplsNodeId FROM MPLS-TC-EXT-STD-MIB ; mplsIdStdMIB MODULE-IDENTITY LAST-UPDATED - "201301140000Z" -- January 14, 2013 + "201304130000Z" -- April 13, 2013 ORGANIZATION "Multiprotocol Label Switching (MPLS) Working Group" CONTACT-INFO " Venkatesan Mahalingam Dell Inc, 350 Holger way, San Jose, CA, USA Email: venkat.mahalingams@gmail.com @@ -1128,74 +1140,103 @@ DESCRIPTION "Copyright (c) 2013 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 - "201301140000Z" -- January 14, 2013 + "201304130000Z" -- April 13, 2013 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 } + mplsIdObjects OBJECT IDENTIFIER ::= { mplsIdStdMIB 0 } -- conformance - mplsIdConformance OBJECT IDENTIFIER ::= { mplsIdStdMIB 2 } + mplsIdConformance OBJECT IDENTIFIER ::= { mplsIdStdMIB 1 } -- MPLS common objects mplsIdGlobalId OBJECT-TYPE SYNTAX MplsGlobalId MAX-ACCESS read-write STATUS current DESCRIPTION - "This object allows the operator to assign a unique - operator identifier also called MPLS-TP Global_ID." + operator identifier also called MPLS-TP Global_ID. + If this value is used in mplsTunnelExtNodeConfigGlobalId + for mapping Global_ID::Node_ID with the local identifier + then this object value SHOULD NOT be changed." ::= { mplsIdObjects 1 } - mplsIdIcc OBJECT-TYPE - SYNTAX MplsIccId + mplsIdNodeId OBJECT-TYPE + SYNTAX MplsNodeId MAX-ACCESS read-write STATUS current DESCRIPTION "This object allows the operator or service provider to - assign a unique MPLS-TP ITU-T Carrier Code (ICC) to a - network." + assign a unique MPLS-TP Node_ID. + + The Node_ID is assigned within the scope of + the Global_ID. + If this value is used in mplsTunnelExtNodeConfigNodeId + for mapping Global_ID::Node_ID with the local identifier + then this object value SHOULD NOT be changed." ::= { mplsIdObjects 2 } - mplsIdNodeId OBJECT-TYPE - SYNTAX MplsNodeId + mplsIdCc OBJECT-TYPE + SYNTAX MplsCcId MAX-ACCESS read-write STATUS current DESCRIPTION "This object allows the operator or service provider to - assign a unique MPLS-TP Node_ID. - - The Node_ID is assigned within the scope of - the Global_ID." + assign a unique Country Code (CC). Global uniqueness is + assured by concatenating the ICC with a + Country Code (CC). + If this value is used in mplsTunnelExtNodeConfigCcId + for mapping CC:ICC with the local identifier then this + object value SHOULD NOT be changed." + REFERENCE + "MPLS-TP Identifiers Following ITU-T Conventions, + draft-ietf-mpls-tp-itu-t-identifiers-08 (work in + progress), February 2013. Section 3" ::= { mplsIdObjects 3 } + mplsIdIcc OBJECT-TYPE + SYNTAX MplsIccId + MAX-ACCESS read-write + STATUS current + DESCRIPTION + "This object allows the operator or service provider to + assign a unique MPLS-TP ITU-T Carrier Code (ICC) to a + network. Together, the CC and the ICC form + the ICC_Operator_ID as: CC::ICC. + If this value is used in mplsTunnelExtNodeConfigIccId + for mapping CC::ICC with the local identifier then + this object value SHOULD NOT be changed." + REFERENCE + "MPLS-TP Identifiers Following ITU-T Conventions, + draft-ietf-mpls-tp-itu-t-identifiers-08 (work in + progress), February 2013. Section 3" + ::= { mplsIdObjects 4 } + -- Module compliance. - mplsIdGroups + mplsIdCompliances OBJECT IDENTIFIER ::= { mplsIdConformance 1 } - mplsIdCompliances + mplsIdGroups OBJECT IDENTIFIER ::= { mplsIdConformance 2 } -- Compliance requirement for fully compliant implementations. mplsIdModuleFullCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "Compliance statement for agents that provide full support the MPLS-ID-STD-MIB module." @@ -1203,45 +1244,27 @@ -- The mandatory group has to be implemented by all -- LSRs that originate/terminate MPLS-TP paths. MANDATORY-GROUPS { mplsIdScalarGroup } ::= { mplsIdCompliances 1 } - -- Compliance requirement for read-only implementations. - - mplsIdModuleReadOnlyCompliance MODULE-COMPLIANCE - STATUS current - DESCRIPTION - "Compliance statement for agents that provide full - support the MPLS-ID-STD-MIB module." - - MODULE -- this module - - -- The mandatory group has to be implemented by all - -- LSRs that originate/terminate MPLS-TP paths. - - MANDATORY-GROUPS { - mplsIdScalarGroup - } - - ::= { mplsIdCompliances 2 } - -- Units of conformance. mplsIdScalarGroup OBJECT-GROUP OBJECTS { mplsIdGlobalId, mplsIdNodeId, - mplsIdIcc + mplsIdIcc, + mplsIdCc } STATUS current DESCRIPTION "Scalar object needed to implement MPLS TP path." ::= { mplsIdGroups 1 } -- MPLS-ID-STD-MIB module ends END @@ -1258,21 +1281,21 @@ FROM MPLS-TC-STD-MIB -- [RFC3811] RowPointer FROM SNMPv2-TC -- [RFC2579] mplsXCIndex, mplsXCInSegmentIndex, mplsXCOutSegmentIndex, mplsInterfaceGroup, mplsInSegmentGroup, mplsOutSegmentGroup, mplsXCGroup, mplsPerfGroup, mplsLsrNotificationGroup FROM MPLS-LSR-STD-MIB; -- [RFC3813] mplsLsrExtStdMIB MODULE-IDENTITY LAST-UPDATED - "201301140000Z" -- January 14, 2013 + "201304130000Z" -- April 13, 2013 ORGANIZATION "Multiprotocol Label Switching (MPLS) Working Group" CONTACT-INFO " Venkatesan Mahalingam Dell Inc, 350 Holger way, San Jose, CA, USA Email: venkat.mahalingams@gmail.com Kannan KV Sampath @@ -1296,110 +1319,105 @@ "Copyright (c) 2013 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 - "201301140000Z" -- January 14, 2013 + "201304130000Z" -- April 13, 2013 DESCRIPTION "MPLS LSR specific MIB objects extension" ::= { mplsStdMIB xxx } -- xxx to be replaced with correct value - -- Notifications - mplsLsrExtNotifications OBJECT IDENTIFIER - ::= { mplsLsrExtStdMIB 0 } -- tables, scalars mplsLsrExtObjects OBJECT IDENTIFIER - ::= { mplsLsrExtStdMIB 1 } + ::= { mplsLsrExtStdMIB 0 } -- conformance mplsLsrExtConformance OBJECT IDENTIFIER - ::= { mplsLsrExtStdMIB 2 } + ::= { mplsLsrExtStdMIB 1 } -- MPLS LSR common objects mplsXCExtTable OBJECT-TYPE SYNTAX SEQUENCE OF MplsXCExtEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table sparse augments the mplsXCTable of MPLS-LSR-STD-MIB [RFC3813] to provide MPLS-TP specific information about associated tunnel information" REFERENCE "1. Multiprotocol Label Switching (MPLS) Label Switching - Router (LSR) Management Information Base (MIB), RFC 3813, - Section 5.7. mplsXCTable" + Router (LSR) Management Information Base (MIB), RFC 3813." ::= { mplsLsrExtObjects 1 } mplsXCExtEntry OBJECT-TYPE SYNTAX MplsXCExtEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry in this table extends the cross connect information represented by an entry in the mplsXCTable in MPLS-LSR-STD-MIB [RFC3813] through a sparse augmentation. An entry can be created by a network operator via SNMP SET commands, or in response to signaling protocol events." REFERENCE "1. Multiprotocol Label Switching (MPLS) Label Switching - Router (LSR) Management Information Base (MIB), RFC 3813, - Section 10. mplsXCTable" + Router (LSR) Management Information Base (MIB), RFC 3813." INDEX { mplsXCIndex, mplsXCInSegmentIndex, mplsXCOutSegmentIndex } ::= { mplsXCExtTable 1 } MplsXCExtEntry ::= SEQUENCE { mplsXCExtTunnelPointer RowPointer, mplsXCExtOppositeDirXCPtr RowPointer } mplsXCExtTunnelPointer OBJECT-TYPE SYNTAX RowPointer MAX-ACCESS read-only STATUS current DESCRIPTION "This read-only object indicates the back pointer to - the tunnel entry segment." + the tunnel entry segment. + The only valid value for Tunnel Pointer is + mplsTunnelTable entry." REFERENCE "1. Multiprotocol Label Switching (MPLS) Label Switching - Router (LSR) Management Information Base (MIB), RFC 3813, - Section 10. mplsXCTable" + Router (LSR) Management Information Base (MIB), RFC 3813." ::= { mplsXCExtEntry 1 } mplsXCExtOppositeDirXCPtr OBJECT-TYPE SYNTAX RowPointer MAX-ACCESS read-create STATUS current DESCRIPTION "This object indicates the pointer to the opposite direction XC entry. This object cannot be modified if mplsXCRowStatus for the corresponding entry in the mplsXCTable is active(1)." REFERENCE "1. Multiprotocol Label Switching (MPLS) Label Switching - Router (LSR) Management Information Base (MIB), RFC 3813, - Section 10. mplsXCTable" + Router (LSR) Management Information Base (MIB), RFC 3813." ::= { mplsXCExtEntry 2 } - mplsLsrExtGroups + mplsLsrExtCompliances OBJECT IDENTIFIER ::= { mplsLsrExtConformance 1 } - mplsLsrExtCompliances + mplsLsrExtGroups OBJECT IDENTIFIER ::= { mplsLsrExtConformance 2 } -- Compliance requirement for fully compliant implementations. mplsLsrExtModuleFullCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "Compliance statement for agents that provide full support for MPLS-LSR-EXT-STD-MIB. The mandatory group has to be implemented by all LSRs @@ -1436,87 +1454,90 @@ provide read-only support for MPLS-LSR-EXT-STD-MIB. Such devices can then be monitored but cannot be configured using this MIB module." MODULE MPLS-LSR-STD-MIB MANDATORY-GROUPS { mplsInterfaceGroup, mplsInSegmentGroup, mplsOutSegmentGroup, - mplsXCGroup, mplsPerfGroup } MODULE -- this module - MANDATORY-GROUPS { - mplsXCExtGroup - } - - OBJECT mplsXCExtTunnelPointer - SYNTAX RowPointer - MIN-ACCESS read-only + GROUP mplsXCExtReadOnlyObjectsGroup DESCRIPTION - "The only valid value for Tunnel Pointer is - mplsTunnelTable entry." + "This group is mandatory for devices which support + Opposite direction XC configuration of tunnels." + -- mplsXCExtTable OBJECT mplsXCExtOppositeDirXCPtr - SYNTAX RowPointer MIN-ACCESS read-only DESCRIPTION - "The only valid value for XC Pointer is - mplsXCTable entry." - + "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 } + -- Units of conformance. + mplsXCExtGroup OBJECT-GROUP OBJECTS { mplsXCExtTunnelPointer, mplsXCExtOppositeDirXCPtr } STATUS current DESCRIPTION "This object should be supported in order to access the tunnel entry from XC entry." - ::= { mplsLsrExtGroups 1 } + mplsXCExtReadOnlyObjectsGroup OBJECT-GROUP + OBJECTS { mplsXCExtOppositeDirXCPtr } + STATUS current + DESCRIPTION + "This Object is needed to associate the opposite direction + (forward/reverse) XC entry." + ::= { 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 FROM SNMPv2-SMI -- [RFC2578] MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF -- [RFC2580] TruthValue, RowStatus, RowPointer, StorageType FROM SNMPv2-TC -- [RFC2579] - MplsGlobalId, MplsNodeId, MplsIccId + 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 - "201301140000Z" -- January 14, 2013 + "201304130000Z" -- April 13, 2013 ORGANIZATION "Multiprotocol Label Switching (MPLS) Working Group" CONTACT-INFO " Venkatesan Mahalingam Dell Inc, 350 Holger way, San Jose, CA, USA Email: venkat.mahalingams@gmail.com Kannan KV Sampath @@ -1538,210 +1560,239 @@ DESCRIPTION "Copyright (c) 2013 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 - "201301140000Z" -- January 14, 2013 + "201304130000Z" -- April 13, 2013 DESCRIPTION "MPLS TE MIB objects extension" ::= { mplsStdMIB xxx } -- xxx to be replaced -- with correct value -- Top level components of this MIB module. - -- Notifications - mplsTeExtNotifications OBJECT IDENTIFIER - ::= { mplsTeExtStdMIB 0 } -- tables, scalars mplsTeExtObjects OBJECT IDENTIFIER - ::= { mplsTeExtStdMIB 1 } + ::= { mplsTeExtStdMIB 0 } -- conformance mplsTeExtConformance OBJECT IDENTIFIER - ::= { mplsTeExtStdMIB 2 } + ::= { mplsTeExtStdMIB 1 } -- Start of MPLS Transport Profile Node configuration table mplsTunnelExtNodeConfigTable OBJECT-TYPE SYNTAX SEQUENCE OF MplsTunnelExtNodeConfigEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table allows the operator to map a node or - LSR Identifier (IP compatible [Global_Node_ID] or ICC) - with a local identifier. + LSR Identifier (IP compatible [Global_ID::Node_ID] or + ICC based [CC::ICC]) with a local identifier. This table is created to reuse the existing mplsTunnelTable for MPLS based transport network tunnels also. + Since the MPLS tunnel's Ingress/Egress LSR identifiers' size (Unsigned32) value is not compatible for - MPLS-TP tunnel i.e. Global_Node_Id of size 8 bytes and - ICC of size 6 bytes, there exists a need to map the - Global_Node_ID or ICC with the local identifier of size - 4 bytes (Unsigned32) value in order - to index (Ingress/Egress LSR identifier) - the existing mplsTunnelTable." + MPLS-TP tunnel i.e. Global_ID::Node_ID of size 8 bytes and + CC::ICC of size 8 bytes, there exists a need to map the + Global_ID::Node_ID or CC::ICC with the local identifier of + size 4 bytes (Unsigned32) value in order to index + (Ingress/Egress LSR identifier) the existing + mplsTunnelTable." ::= { mplsTeExtObjects 1 } mplsTunnelExtNodeConfigEntry OBJECT-TYPE SYNTAX MplsTunnelExtNodeConfigEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry in this table represents a mapping identification for the operator or service provider with node or LSR. - As per [RFC6370], this mapping is + As per [RFC6370], IP compatible mapping is + represented as Global_ID::Node_ID. - represented as Global_Node_ID or ICC. + As per [I-D.ietf-mpls-tp-itu-t-identifiers], ICC + compatible mapping is represented as CC::ICC. Note: Each entry in this table should have a unique - Global_ID and Node_ID combination." + [Global_ID and Node_ID] or [CC and ICC] combination." INDEX { mplsTunnelExtNodeConfigLocalId } ::= { mplsTunnelExtNodeConfigTable 1 } MplsTunnelExtNodeConfigEntry ::= SEQUENCE { mplsTunnelExtNodeConfigLocalId MplsExtendedTunnelId, mplsTunnelExtNodeConfigGlobalId MplsGlobalId, mplsTunnelExtNodeConfigNodeId MplsNodeId, + mplsTunnelExtNodeConfigCcId MplsCcId, mplsTunnelExtNodeConfigIccId MplsIccId, + mplsTunnelExtNodeConfigIccValid TruthValue, mplsTunnelExtNodeConfigRowStatus RowStatus, mplsTunnelExtNodeConfigStorageType StorageType } mplsTunnelExtNodeConfigLocalId OBJECT-TYPE SYNTAX MplsExtendedTunnelId MAX-ACCESS not-accessible STATUS current DESCRIPTION "This object is used in accommodating the bigger - size Global_Node_ID and/or ICC with lower size LSR + size Global_ID::Node_ID and/or CC::ICC 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_Node_ID or ICC) from mplsTunnelExtNodeConfigTable. + (Global_ID::Node_ID or CC::ICC) 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 - a unique identifier to map Global_Node_ID and/or ICC. - As this Local Identifier is unique within the node and - the same syntax of this object can be used for MPLS TE + a unique identifier to map Global_ID::Node_ID and/or + CC::ICC. 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 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 value should be zero when - mplsTunnelExtNodeConfigIccId is configured with non-null - value." + This object has no meaning when + mplsTunnelExtNodeConfigIccValid is set true." REFERENCE "MPLS Transport Profile (MPLS-TP) Identifiers [RFC6370] - Section 3. Uniquely Identifying an Operator - - the Global_ID" + Section 3." ::= { mplsTunnelExtNodeConfigEntry 2 } mplsTunnelExtNodeConfigNodeId OBJECT-TYPE SYNTAX MplsNodeId MAX-ACCESS read-create STATUS current DESCRIPTION - "This object indicates the Node_ID within the operator. - This object value should be zero when - mplsTunnelExtNodeConfigIccId is configured with non-null - value." + "This object indicates the Node_ID within the scope + of a Global_ID. This object has no meaning when + mplsTunnelExtNodeConfigIccValid is set true." REFERENCE "MPLS Transport Profile (MPLS-TP) Identifiers [RFC6370] - Section 4, Node and Interface Identifiers" + Section 4." ::= { mplsTunnelExtNodeConfigEntry 3 } + mplsTunnelExtNodeConfigCcId OBJECT-TYPE + SYNTAX MplsCcId + MAX-ACCESS read-create + STATUS current + DESCRIPTION + "This object allows the operator or service provider to + configure a unique MPLS-TP ITU-T Country Code (CC) + either for Ingress ID or Egress ID. + + This object has no meaning when + mplsTunnelExtNodeConfigIccValid is set false." + REFERENCE + "MPLS-TP Identifiers Following ITU-T Conventions, + draft-ietf-mpls-tp-itu-t-identifiers-08 (work in + progress), February 2013. Section 3" + ::= { mplsTunnelExtNodeConfigEntry 4 } + mplsTunnelExtNodeConfigIccId OBJECT-TYPE SYNTAX MplsIccId MAX-ACCESS read-create STATUS current DESCRIPTION "This object allows the operator or service provider to configure a unique MPLS-TP ITU-T Carrier Code (ICC) either for Ingress ID or Egress ID. - This object value should be zero when - mplsTunnelExtNodeConfigGlobalId and - mplsTunnelExtNodeConfigNodeId are assigned with non-zero - value." + This object has no meaning when + mplsTunnelExtNodeConfigIccValid is set false." REFERENCE "MPLS-TP Identifiers Following ITU-T Conventions, - [I-D.ietf-mpls-tp-itu-t-identifiers], August 2012, - Section 3. Uniquely Identifying an Operator - the - ICC_Operator_ID" - ::= { mplsTunnelExtNodeConfigEntry 4 } + draft-ietf-mpls-tp-itu-t-identifiers-08 (work in + progress), February 2013. Section 3" + ::= { mplsTunnelExtNodeConfigEntry 5 } + + mplsTunnelExtNodeConfigIccValid OBJECT-TYPE + SYNTAX TruthValue + MAX-ACCESS read-create + STATUS current + DESCRIPTION + "Denotes whether or not this entry uses + mplsTunnelExtNodeConfigCcId and + mplsTunnelExtNodeConfigIccId for mapping + the ICC based identifiers with the local identifier. + Note that if this variable is set to false then the + mplsTunnelExtNodeConfigGlobalId and + mplsTunnelExtNodeConfigNodeId objects should have + the valid information." + DEFVAL { false } + ::= { mplsTunnelExtNodeConfigEntry 6 } mplsTunnelExtNodeConfigRowStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "This object allows the operator to create, modify, and/or delete a row in this table." - ::= { mplsTunnelExtNodeConfigEntry 5 } + ::= { mplsTunnelExtNodeConfigEntry 7 } mplsTunnelExtNodeConfigStorageType OBJECT-TYPE SYNTAX StorageType MAX-ACCESS read-create STATUS current DESCRIPTION "This variable indicates the storage type for this object. Conceptual rows having the value 'permanent' need not allow write-access to any columnar objects in the row." DEFVAL { volatile } - ::= { mplsTunnelExtNodeConfigEntry 6 } + ::= { mplsTunnelExtNodeConfigEntry 8 } -- End of MPLS Transport Profile Node configuration table -- Start of MPLS Transport Profile Node IP compatible -- mapping table mplsTunnelExtNodeIpMapTable OBJECT-TYPE SYNTAX SEQUENCE OF MplsTunnelExtNodeIpMapEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This read-only table allows the operator to retrieve - the local identifier for a given Global_Node_ID in an IP + 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 identifiers are used to retrieve the tunnel entry. This table returns nothing when the associated entry is not defined in mplsTunnelExtNodeConfigTable." ::= { mplsTeExtObjects 2 } mplsTunnelExtNodeIpMapEntry OBJECT-TYPE @@ -1743,31 +1794,30 @@ This table returns nothing when the associated entry is not defined in mplsTunnelExtNodeConfigTable." ::= { mplsTeExtObjects 2 } mplsTunnelExtNodeIpMapEntry OBJECT-TYPE SYNTAX MplsTunnelExtNodeIpMapEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry in this table represents a mapping of - Global_Node_ID with the local identifier. + Global_ID::Node_ID with the local identifier. An entry in this table is created automatically when the Local identifier is associated with Global_ID and Node_Id in the mplsTunnelExtNodeConfigTable. Note: Each entry in this table should have a unique Global_ID and Node_ID combination." INDEX { mplsTunnelExtNodeIpMapGlobalId, mplsTunnelExtNodeIpMapNodeId - } ::= { mplsTunnelExtNodeIpMapTable 1 } MplsTunnelExtNodeIpMapEntry ::= SEQUENCE { mplsTunnelExtNodeIpMapGlobalId MplsGlobalId, mplsTunnelExtNodeIpMapNodeId MplsNodeId, mplsTunnelExtNodeIpMapLocalId MplsExtendedTunnelId } mplsTunnelExtNodeIpMapGlobalId OBJECT-TYPE @@ -1800,79 +1849,93 @@ -- End MPLS Transport Profile Node IP compatible table -- Start of MPLS Transport Profile Node ICC based table mplsTunnelExtNodeIccMapTable OBJECT-TYPE SYNTAX SEQUENCE OF MplsTunnelExtNodeIccMapEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This read-only table allows the operator to retrieve - the local identifier for a given ICC operator in an ICC + the local identifier for a given CC::ICC 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 identifiers are used to retrieve the tunnel entry. This table returns nothing when the associated entry is not defined in mplsTunnelExtNodeConfigTable." ::= { mplsTeExtObjects 3 } mplsTunnelExtNodeIccMapEntry OBJECT-TYPE SYNTAX MplsTunnelExtNodeIccMapEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION - "An entry in this table represents a mapping of ICC with - the local identifier. + "An entry in this table represents a mapping of CC::ICC + with the local identifier. An entry in this table is created automatically when - the Local identifier is associated with ICC in + the Local identifier is associated with CC::ICC in the mplsTunnelExtNodeConfigTable." - INDEX { mplsTunnelExtNodeIccMapIccId } + INDEX { mplsTunnelExtNodeIccMapCcId, + mplsTunnelExtNodeIccMapIccId } ::= { mplsTunnelExtNodeIccMapTable 1 } MplsTunnelExtNodeIccMapEntry ::= SEQUENCE { + mplsTunnelExtNodeIccMapCcId MplsCcId, mplsTunnelExtNodeIccMapIccId MplsIccId, mplsTunnelExtNodeIccMapLocalId MplsExtendedTunnelId } - mplsTunnelExtNodeIccMapIccId OBJECT-TYPE - SYNTAX MplsIccId + mplsTunnelExtNodeIccMapCcId OBJECT-TYPE + SYNTAX MplsCcId MAX-ACCESS not-accessible STATUS current DESCRIPTION "This object allows the operator or service provider to - configure a unique MPLS-TP ITU-T Carrier Code (ICC) + configure a unique MPLS-TP ITU-T Country Code (CC) either for Ingress or Egress LSR ID. + The CC is a string of two alphabetic characters + represented with upper case letters (i.e., A-Z)." + ::= { mplsTunnelExtNodeIccMapEntry 1 } + + mplsTunnelExtNodeIccMapIccId OBJECT-TYPE + SYNTAX MplsIccId + MAX-ACCESS not-accessible + STATUS current + DESCRIPTION + "This object allows the operator or service provider + to configure a unique MPLS-TP ITU-T Carrier + Code (ICC) either for Ingress or Egress LSR ID. + 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." - ::= { mplsTunnelExtNodeIccMapEntry 1 } + ::= { mplsTunnelExtNodeIccMapEntry 2 } mplsTunnelExtNodeIccMapLocalId OBJECT-TYPE SYNTAX MplsExtendedTunnelId MAX-ACCESS read-only STATUS current DESCRIPTION "This object contains an ICC based local identifier which is defined in mplsTunnelExtNodeConfigTable." - ::= { mplsTunnelExtNodeIccMapEntry 2 } + ::= { mplsTunnelExtNodeIccMapEntry 3 } -- End MPLS Transport Profile Node ICC based table - -- Start of MPLS Tunnel table extension mplsTunnelExtTable OBJECT-TYPE SYNTAX SEQUENCE OF MplsTunnelExtEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table represents extensions to mplsTunnelTable in order to support MPLS-TP tunnels. @@ -1888,28 +1951,27 @@ mplsTunnelTable is reused for forming the LSP_ID as follows, Source Tunnel_Num is mapped with mplsTunnelIndex, Source Node_ID is mapped with mplsTunnelIngressLSRId, Destination Node_ID is mapped with mplsTunnelEgressLSRId LSP_Num is mapped with mplsTunnelInstance. - Source Global_Node_ID and/or ICC and Destination - Global_Node_ID and/or ICC are maintained in the + Source Global_ID::Node_ID and/or CC::ICC and Destination + Global_ID::Node_ID and/or CC::ICC are maintained in the mplsTunnelExtNodeConfigTable and mplsTunnelExtNodeConfigLocalId is used to create an entry in mplsTunnelTable." REFERENCE - "MPLS Transport Profile (MPLS-TP) Identifiers [RFC6370], - Section 3 and 4." + "MPLS Transport Profile (MPLS-TP) Identifiers [RFC6370]." ::= { mplsTeExtObjects 4 } mplsTunnelExtEntry OBJECT-TYPE SYNTAX MplsTunnelExtEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry in this table represents MPLS-TP specific additional tunnel configurations." INDEX { @@ -1937,34 +1999,22 @@ STATUS current DESCRIPTION "This object is applicable only for the bidirectional tunnel that has the forward and reverse LSPs in the same tunnel or in the different tunnels. This object holds the opposite direction tunnel entry if the bidirectional tunnel is setup by configuring two tunnel entries in mplsTunnelTable. - Note that there are two different ways to represent the - opposite direction tunnel entry. One method is to use this - object mplsTunnelExtOppositeDirPtr as RowPointer and make - it point to the other direction tunnel. Other method is to - use the mplsTunnelExtDestTnlIndex and - mplsTunnelExtDestTnlLspIndex instead of using this - mplsTunnelExtOppositeDirPtr. Implementation can choose - either one of the method to represent the opposite - direction tunnel. Duplicate methods are provided to provide - easy ways for different implementations. - The value of zeroDotZero indicates single tunnel entry is used for bidirectional tunnel setup." - DEFVAL { zeroDotZero } ::= { mplsTunnelExtEntry 1 } mplsTunnelExtOppositeDirTnlValid OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-create STATUS current DESCRIPTION "Denotes whether or not this tunnel uses mplsTunnelExtOppositeDirPtr for identifying the opposite @@ -2046,78 +2096,73 @@ ::= { mplsTunnelExtEntry 5 } mplsTunnelExtIngressLSRLocalIdValid OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-create STATUS current DESCRIPTION "This object denotes whether the mplsTunnelIngressLSRId contains the local value, which is used to reference the complete Ingress Global_ID::Node_ID or ICC from - the mplsTunnelExtNodeConfigTable." - REFERENCE - "MPLS-TE-STD-MIB [RFC3812], Section 11. mplsTunnelIngressLSRId - object in mplsTunnelTable. + the mplsTunnelExtNodeConfigTable. If this object is set to FALSE, mplsTunnelExtNodeConfigTable will not contain an entry to reference local identifier with Global_ID::Node_ID or ICC value. This object is set to FALSE for legacy implementations like MPLS TE tunnels where mplsTunnelIngressId itself provides complete Ingress LSRId." + REFERENCE + "MPLS-TE-STD-MIB [RFC3812], Section 11. + mplsTunnelIngressLSRId object in mplsTunnelTable." DEFVAL { false } ::= { mplsTunnelExtEntry 6 } mplsTunnelExtEgressLSRLocalIdValid OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-create STATUS current DESCRIPTION "This object denotes whether the mplsTunnelEgressLSRId contains the local value, which is used to reference the complete Egress Global_ID::Node_ID or ICC from - the mplsTunnelExtNodeConfigTable." - REFERENCE - "MPLS-TE-STD-MIB [RFC3812], Section 11. mplsTunnelEgressLSRId - object in mplsTunnelTable. + the mplsTunnelExtNodeConfigTable. If this object is set to FALSE, mplsTunnelExtNodeConfigTable will not contain an entry to reference local identifier with Global_ID::Node_ID or ICC value. This object is set to FALSE for legacy implementations like MPLS TE tunnels where mplsTunnelEgressId itself provides complete Egress LSRId." + REFERENCE + "MPLS-TE-STD-MIB [RFC3812], Section 11. + mplsTunnelEgressLSRId object in mplsTunnelTable." DEFVAL { false } ::= { mplsTunnelExtEntry 7 } -- End of MPLS Tunnel table extension mplsTunnelExtReversePerfTable OBJECT-TYPE SYNTAX SEQUENCE OF MplsTunnelExtReversePerfEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table extends the mplsTunnelTable 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. - - For links that do not transport packets, these packet - counters cannot be maintained. For such links, attempts - to read the objects in this table will return - noSuchInstance." + mplsTunnelTable." REFERENCE "1. Multiprotocol Label Switching (MPLS) Traffic Engineering (TE)Management Information Base (MIB), - RFC 3812. Section 6.6. mplsTunnelPerfTable" + RFC 3812." ::= { mplsTeExtObjects 5 } mplsTunnelExtReversePerfEntry OBJECT-TYPE SYNTAX MplsTunnelExtReversePerfEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry in this table is created by the LSR for every bidirectional MPLS tunnel where packets are visible to the LSR." @@ -2142,53 +2187,42 @@ MAX-ACCESS read-only STATUS current DESCRIPTION "Number of packets forwarded on the tunnel in the reverse direction if it is bidirectional. This object represents the 32-bit value of the least significant part of the 64-bit value if both mplsTunnelExtReversePerfHCPackets and this object - are returned. - - For links that do not transport packets, this packet - counter cannot be maintained. For such links, this value - will return noSuchInstance." + are returned." ::= { mplsTunnelExtReversePerfEntry 1 } mplsTunnelExtReversePerfHCPackets OBJECT-TYPE SYNTAX Counter64 MAX-ACCESS read-only STATUS current DESCRIPTION "High-capacity counter for number of packets forwarded on the tunnel in the reverse direction if it is - bidirectional. + bidirectional." - For links that do not transport packets, this packet - counter cannot be maintained. For such links, this value - will return noSuchInstance." ::= { mplsTunnelExtReversePerfEntry 2 } mplsTunnelExtReversePerfErrors OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Number of errored packets received on the tunnel in - the reverse direction if it is bidirectional. For links - that do not transport packets, this packet counter cannot - be maintained. For such links, this value will return - noSuchInstance." + the reverse direction if it is bidirectional." ::= { mplsTunnelExtReversePerfEntry 3 } - mplsTunnelExtReversePerfBytes OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Number of bytes forwarded on the tunnel in the reverse direction if it is bidirectional. This object represents the 32-bit value of the least significant part of the 64-bit value if both @@ -2185,50 +2219,40 @@ mplsTunnelExtReversePerfBytes OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Number of bytes forwarded on the tunnel in the reverse direction if it is bidirectional. This object represents the 32-bit value of the least significant part of the 64-bit value if both - mplsTunnelExtReversePerfHCBytes and this object are returned. + mplsTunnelExtReversePerfHCBytes and this object are + returned." - For links that do not transport packets, this packet - counter cannot be maintained. For such links, this value - will return noSuchInstance." ::= { mplsTunnelExtReversePerfEntry 4 } mplsTunnelExtReversePerfHCBytes OBJECT-TYPE SYNTAX Counter64 MAX-ACCESS read-only STATUS current DESCRIPTION "High-capacity counter for number of bytes forwarded on the - tunnel in the reverse direction if it is bidirectional. - - For links that do not transport packets, this packet - counter cannot be maintained. For such links, this value - will return noSuchInstance." + tunnel in the reverse direction if it is bidirectional." ::= { mplsTunnelExtReversePerfEntry 5 } - -- Notifications. - -- Notification objects need to be added here. - -- End of notifications. - -- Module compliance. - mplsTeExtGroups + mplsTeExtCompliances OBJECT IDENTIFIER ::= { mplsTeExtConformance 1 } - mplsTeExtCompliances + mplsTeExtGroups OBJECT IDENTIFIER ::= { mplsTeExtConformance 2 } -- Compliance requirement for fully compliant implementations. mplsTeExtModuleFullCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "Compliance statement for agents that provide full support the MPLS-TE-EXT-STD-MIB module." @@ -2322,73 +2348,127 @@ mplsTunnelExtNodeConfigRowStatus, mplsTunnelExtNodeConfigStorageType, mplsTunnelExtNodeIpMapLocalId } STATUS current DESCRIPTION "Object(s) needed to implement IP compatible tunnels." ::= { mplsTeExtGroups 2 } mplsTunnelExtIccOperatorGroup OBJECT-GROUP - OBJECTS { mplsTunnelExtNodeConfigIccId, + OBJECTS { mplsTunnelExtNodeConfigCcId, + mplsTunnelExtNodeConfigIccId, + mplsTunnelExtNodeConfigIccValid, mplsTunnelExtNodeConfigRowStatus, mplsTunnelExtNodeConfigStorageType, mplsTunnelExtNodeIccMapLocalId } STATUS current DESCRIPTION "Object(s) needed to implement ICC based tunnels." ::= { mplsTeExtGroups 3 } -- MPLS-TE-EXT-STD-MIB module ends END 14. Security Consideration - There is a number of management objects defined in this MIB module - that has a MAX-ACCESS clause of read-write.. 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. + 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. + + There are a number of management objects defined in this MIB module + with a MAX-ACCESS clause of read-write. 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: + + - the tables specified in [RFC3812], [RFC3813] and this document + MIB tables 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: + - the tables specified in [RFC3812], [RFC3813] and this document + MIB tables mplsTunnelExtNodeConfigTable, mplsTunnelExtTable, + mplsXCExtTable and mplsTunnelExtReversePerfTable collectively + show the MPLS-TP tunnel network topology and its performance + 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). + 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. 15. IANA Considerations - To be added in a later version of this document. + As described in [MPLSMGMT] 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]. + +15.1. IANA Considerations for MPLS-TC-EXT-STD-MIB + + IANA is requested to assign an OID { mplsStdMIB OID } to the MPLS-TC- + EXT-STD-MIB module specified in this document. + +15.2. IANA Considerations for MPLS-ID-STD-MIB + IANA is requested to assign an OID { mplsStdMIB IOD } to the MPLS-ID- + STD-MIB module specified in this document. + +15.3. IANA Considerations for MPLS-LSR-EXT-STD-MIB + + IANA is requested to assign an OID { mplsStdMIB OID } to the MPLS- + LSR-EXT-STD-MIB module specified in this document. + +15.4. IANA Considerations for MPLS-TE-EXT-STD-MIB + + IANA is requested to assign an OID { mplsStdMIB OID } to the MPLS-TE- + EXT-STD-MIB module specified in this document. 16. References 16.1. Normative References [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. [RFC2578] McCloghrie, K., Perkins, D., and J. Schoenwaelder, "Structure of Management Information Version 2 (SMIv2)", @@ -2401,20 +2481,28 @@ [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, "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. 16.2. Informative References + [MPLSMGMT] Nadeau, T., Srinivasan, C., and A. Farrel, "Multiprotocol + Label Switching (MPLS) Management Overview", Work in + Progress, September 2003. + + [RFC5226] Narten, T. and H. Alvestrand., "Guidelines for Writing + an IANA Considerations Section in RFCs", BCP 26, + RFC 5226, May 2008. + [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. @@ -2433,41 +2522,42 @@ [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. [I-D.ietf-mpls-tp-itu-t-identifiers] Winter, R., Gray, E., Helvoort, H., and M. Betts, "MPLS-TP Identifiers Following ITU-T - Conventions", draft-ietf-mpls-tp-itu-t-identifiers-07 - (work in progress), August 2012. + Conventions", draft-ietf-mpls-tp-itu-t-identifiers-08 + (work in progress), February 2013 17. Acknowledgments The authors would like to thank Francesco Fondelli, Josh Littlefield, - Agrahara Kiran Koushik, Metrri Jain, Muly Ilan, Joan Cucchiara and - Randy Presuhn for their valuable comments. + Agrahara Kiran Koushik, Metrri Jain, Muly Ilan and Randy Presuhn for + their valuable comments. A special thanks to Joan Cucchiara for + really getting the MIB modules into shape. 18. Authors' Addresses + Venkatesan Mahalingam + Dell Inc. + 350 Holger way, San Jose, CA, 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 Juniper Networks 10 Technology Park Drive, Westford, MA 01886 Email: tnadeau@juniper.net - Venkatesan Mahalingam - Dell Inc. - 350 Holger way, San Jose, CA, USA - Email: venkat.mahalingams@gmail.com - Kannan KV Sampath Redeem India Email: kannankvs@gmail.com