MPLS-TP Traffic Engineering (TE) Management Information Base (MIB)
draft-ietf-mpls-tp-te-mib-08
The information below is for an old version of the document.
| Document | Type |
This is an older version of an Internet-Draft that was ultimately published as RFC 7453.
|
|
|---|---|---|---|
| Authors | Venkatesan Mahalingam , Kannan KV Sampath , Sam Aldrin , Thomas Nadeau | ||
| Last updated | 2014-05-06 | ||
| Replaces | draft-vkst-mpls-tp-te-mib | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Formats | |||
| Reviews | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | WG Document | |
| Document shepherd | Young Lee | ||
| Shepherd write-up | Show Last changed 2013-11-04 | ||
| IESG | IESG state | Became RFC 7453 (Proposed Standard) | |
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | Adrian Farrel | ||
| Send notices to | mpls-chairs@tools.ietf.org, draft-ietf-mpls-tp-te-mib@tools.ietf.org |
draft-ietf-mpls-tp-te-mib-08
INTERNET DRAFT MPLS-TP MIB May 6, 2014 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 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 Kannan KV Sampath Redeem, India Email: kannankvs@gmail.com Sam Aldrin Huawei Technologies 2330 Central Express Way, Santa Clara, CA 95051, USA Email: aldrin.ietf@gmail.com Thomas D. Nadeau Email: tnadeau@lucidvision.com " 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 Venkatesan, et al. Expires November 7, 2014 [Page 36] INTERNET DRAFT MPLS-TP MIB May 6, 2014 MPLS Traffic Engineering in transport networks." -- Revision history. REVISION "201405050000Z" -- May 05, 2014 DESCRIPTION "MPLS TE MIB objects extension" ::= { mplsStdMIB xxx } -- xxx 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 } -- Start of MPLS Transport Profile Node configuration table mplsTunnelExtNodeConfigLocalIdNext OBJECT-TYPE SYNTAX IndexIntegerNextFree (0..16777215) MAX-ACCESS read-only STATUS current DESCRIPTION "This object contains an unused value for mplsTunnelExtNodeConfigLocalId, or a zero to indicate that none exist. Negative values are not allowed, as they do not correspond to valid values of mplsTunnelExtNodeConfigLocalId." ::= { mplsTeExtObjects 1 } 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_ID::Node_ID] or ICC based [ICC_Operator_ID::Node_ID]) with a local identifier. Venkatesan, et al. Expires November 7, 2014 [Page 37] INTERNET DRAFT MPLS-TP MIB May 6, 2014 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_ID::Node_ID of size 8 bytes and ICC_Operator_ID::Node_ID of size 12 bytes, there exists a need to map the Global_ID::Node_ID or ICC_Operator_ID::Node_ID with the local identifier of size 4 bytes (Unsigned32) value in order to index (Ingress/Egress LSR identifier) the existing mplsTunnelTable." ::= { mplsTeExtObjects 2 } 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], IP compatible mapping is represented as Global_ID::Node_ID. As per [RFC6923], the CC and the ICC form the ICC_Operator_ID as CC::ICC and ICC compatible mapping is represented as ICC_Operator_ID::Node_ID. Note: Each entry in this table should have a unique [Global_ID and Node_ID] or [CC::ICC and Node_ID] combination." INDEX { mplsTunnelExtNodeConfigLocalId } ::= { mplsTunnelExtNodeConfigTable 1 } MplsTunnelExtNodeConfigEntry ::= SEQUENCE { mplsTunnelExtNodeConfigLocalId MplsExtendedTunnelId, mplsTunnelExtNodeConfigGlobalId MplsGlobalId, mplsTunnelExtNodeConfigCcId MplsCcId, mplsTunnelExtNodeConfigIccId MplsIccId, mplsTunnelExtNodeConfigNodeId MplsNodeId, mplsTunnelExtNodeConfigIccValid TruthValue, mplsTunnelExtNodeConfigStorageType StorageType, mplsTunnelExtNodeConfigRowStatus RowStatus } Venkatesan, et al. Expires November 7, 2014 [Page 38] INTERNET DRAFT MPLS-TP MIB May 6, 2014 mplsTunnelExtNodeConfigLocalId OBJECT-TYPE SYNTAX MplsExtendedTunnelId 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 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_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 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 mplsTunnelExtNodeConfigIccValid is set true." REFERENCE "MPLS Transport Profile (MPLS-TP) Identifiers [RFC6370] Section 3." ::= { mplsTunnelExtNodeConfigEntry 2 } mplsTunnelExtNodeConfigCcId OBJECT-TYPE SYNTAX MplsCcId MAX-ACCESS read-create Venkatesan, et al. Expires November 7, 2014 [Page 39] INTERNET DRAFT MPLS-TP MIB May 6, 2014 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, [RFC6923] Section 3" ::= { mplsTunnelExtNodeConfigEntry 3 } 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 has no meaning when mplsTunnelExtNodeConfigIccValid is set false." REFERENCE "MPLS-TP Identifiers Following ITU-T Conventions, [RFC6923] Section 3" ::= { mplsTunnelExtNodeConfigEntry 4 } mplsTunnelExtNodeConfigNodeId OBJECT-TYPE SYNTAX MplsNodeId MAX-ACCESS read-create STATUS current DESCRIPTION "This object indicates the Node_ID within the scope of a Global_ID or ICC_Operator_ID." REFERENCE "MPLS Transport Profile (MPLS-TP) Identifiers [RFC6370] Section 4." ::= { mplsTunnelExtNodeConfigEntry 5 } mplsTunnelExtNodeConfigIccValid OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-create STATUS current DESCRIPTION "Denotes whether or not this entry uses mplsTunnelExtNodeConfigCcId, Venkatesan, et al. Expires November 7, 2014 [Page 40] INTERNET DRAFT MPLS-TP MIB May 6, 2014 mplsTunnelExtNodeConfigIccId and mplsTunnelExtNodeConfigNodeId 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 } 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 7 } 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 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_ID::Node_ID in an IP compatible operator environment. Venkatesan, et al. Expires November 7, 2014 [Page 41] INTERNET DRAFT MPLS-TP MIB May 6, 2014 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 3 } mplsTunnelExtNodeIpMapEntry OBJECT-TYPE SYNTAX MplsTunnelExtNodeIpMapEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry in this table represents a mapping of 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 SYNTAX MplsGlobalId MAX-ACCESS not-accessible STATUS current DESCRIPTION "This object indicates the Global_ID." ::= { mplsTunnelExtNodeIpMapEntry 1 } mplsTunnelExtNodeIpMapNodeId OBJECT-TYPE SYNTAX MplsNodeId MAX-ACCESS not-accessible STATUS current Venkatesan, et al. Expires November 7, 2014 [Page 42] INTERNET DRAFT MPLS-TP MIB May 6, 2014 DESCRIPTION "This object indicates the Node_ID within the operator." ::= { mplsTunnelExtNodeIpMapEntry 2 } mplsTunnelExtNodeIpMapLocalId OBJECT-TYPE SYNTAX MplsExtendedTunnelId MAX-ACCESS read-only STATUS current DESCRIPTION "This object contains an IP compatible local identifier which is defined in mplsTunnelExtNodeConfigTable." ::= { mplsTunnelExtNodeIpMapEntry 3 } -- 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_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 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 "An entry in this table represents a mapping of ICC_Operator_ID::Node_ID with the local identifier. An entry in this table is created automatically when the Local identifier is associated with ICC_Operator_ID::Node_ID in Venkatesan, et al. Expires November 7, 2014 [Page 43] INTERNET DRAFT MPLS-TP MIB May 6, 2014 the mplsTunnelExtNodeConfigTable." INDEX { mplsTunnelExtNodeIccMapCcId, mplsTunnelExtNodeIccMapIccId, mplsTunnelExtNodeIccMapNodeId } ::= { mplsTunnelExtNodeIccMapTable 1 } MplsTunnelExtNodeIccMapEntry ::= SEQUENCE { mplsTunnelExtNodeIccMapCcId MplsCcId, mplsTunnelExtNodeIccMapIccId MplsIccId, mplsTunnelExtNodeIccMapNodeId MplsNodeId, mplsTunnelExtNodeIccMapLocalId MplsExtendedTunnelId } 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 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 2 } mplsTunnelExtNodeIccMapNodeId OBJECT-TYPE SYNTAX MplsNodeId MAX-ACCESS not-accessible STATUS current DESCRIPTION Venkatesan, et al. Expires November 7, 2014 [Page 44] INTERNET DRAFT MPLS-TP MIB May 6, 2014 "This object indicates the Node_ID within the ICC based operator." ::= { mplsTunnelExtNodeIccMapEntry 3} 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 4 } -- 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. As per MPLS-TP Identifiers [RFC6370], LSP_ID for IP based co-routed bidirectional tunnel, A1-{Global_ID::Node_ID::Tunnel_Num}::Z9-{Global_ID:: Node_ID::Tunnel_Num}::LSP_Num LSP_ID for IP based associated bidirectional tunnel, A1-{Global_ID::Node_ID::Tunnel_Num::LSP_Num}:: Z9-{Global_ID::Node_ID::Tunnel_Num::LSP_Num} 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_ID::Node_ID and/or ICC_Operator_ID::Node_ID and Destination Global_ID::Node_ID and/or ICC_Operator_ID::Node-ID are maintained in the mplsTunnelExtNodeConfigTable and Venkatesan, et al. Expires November 7, 2014 [Page 45] INTERNET DRAFT MPLS-TP MIB May 6, 2014 mplsTunnelExtNodeConfigLocalId is used to create an entry in mplsTunnelTable." REFERENCE "MPLS Transport Profile (MPLS-TP) Identifiers [RFC6370]." ::= { mplsTeExtObjects 5 } 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 { mplsTunnelIndex, mplsTunnelInstance, mplsTunnelIngressLSRId, mplsTunnelEgressLSRId } ::= { mplsTunnelExtTable 1 } MplsTunnelExtEntry ::= SEQUENCE { mplsTunnelExtOppositeDirPtr RowPointer, mplsTunnelExtOppositeDirTnlValid TruthValue, mplsTunnelExtDestTnlIndex MplsTunnelIndex, mplsTunnelExtDestTnlLspIndex MplsTunnelInstanceIndex, mplsTunnelExtDestTnlValid TruthValue, mplsTunnelExtIngressLSRLocalIdValid TruthValue, mplsTunnelExtEgressLSRLocalIdValid TruthValue } mplsTunnelExtOppositeDirPtr OBJECT-TYPE SYNTAX RowPointer MAX-ACCESS read-create STATUS current DESCRIPTION "This object points to the opposite direction tunnel entry." ::= { 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 direction tunnel information. Note that if this variable Venkatesan, et al. Expires November 7, 2014 [Page 46] INTERNET DRAFT MPLS-TP MIB May 6, 2014 is set to true then the mplsTunnelExtOppositeDirPtr should point to the first accessible row of the valid opposite direction tunnel." DEFVAL { false } ::= { mplsTunnelExtEntry 2 } mplsTunnelExtDestTnlIndex OBJECT-TYPE SYNTAX MplsTunnelIndex MAX-ACCESS read-create STATUS current DESCRIPTION "This object is applicable only for the bidirectional tunnel that has the forward and reverse LSPs in the different tunnel entries. The values of this object and the mplsTunnelExtDestTnlLspIndex object together can be used to identify an opposite direction LSP i.e. if the mplsTunnelIndex and mplsTunnelInstance hold the value for forward LSP, this object and mplsTunnelExtDestTnlLspIndex can be used to retrieve the reverse direction LSP and vice versa. This object and mplsTunnelExtDestTnlLspIndex values provide the first two indices of tunnel entry and the remaining indices can be derived as follows, the Ingress and Egress Identifiers should be swapped in order to index the other direction tunnel." ::= { mplsTunnelExtEntry 3 } mplsTunnelExtDestTnlLspIndex OBJECT-TYPE SYNTAX MplsTunnelInstanceIndex MAX-ACCESS read-create STATUS current DESCRIPTION "This object is applicable only for the bidirectional tunnel that has the forward and reverse LSPs in the different tunnel entries. This object holds the instance index of the opposite direction tunnel." ::= { mplsTunnelExtEntry 4 } mplsTunnelExtDestTnlValid OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-create STATUS current DESCRIPTION "Denotes whether or not this tunnel uses mplsTunnelExtDestTnlIndex and Venkatesan, et al. Expires November 7, 2014 [Page 47] INTERNET DRAFT MPLS-TP MIB May 6, 2014 mplsTunnelExtDestTnlLspIndex for identifying the opposite direction tunnel information. Note that if this variable is set to true then the mplsTunnelExtDestTnlIndex and mplsTunnelExtDestTnlLspIndex objects should have the valid opposite direction tunnel indices." DEFVAL { false } ::= { 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_Operator_ID from 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_Operator_ID::Node_ID 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_Operator_ID::Node_ID from 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_Operator_ID::Node_ID value. This object is set to FALSE for legacy implementations like Venkatesan, et al. Expires November 7, 2014 [Page 48] INTERNET DRAFT MPLS-TP MIB May 6, 2014 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 -- Module compliance. mplsTeExtCompliances OBJECT IDENTIFIER ::= { mplsTeExtConformance 1 } 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." MODULE -- this module -- The mandatory group has to be implemented by all -- LSRs that originate/terminate MPLS-TP tunnels. -- In addition, depending on the type of tunnels -- supported, other groups become mandatory as -- explained below. MANDATORY-GROUPS { mplsTunnelExtGroup } GROUP mplsTunnelExtIpOperatorGroup DESCRIPTION "This group is mandatory for devices which support configuration of IP based identifier tunnels." GROUP mplsTunnelExtIccOperatorGroup DESCRIPTION "This group is mandatory for devices which support configuration of ICC based tunnels." Venkatesan, et al. Expires November 7, 2014 [Page 49] INTERNET DRAFT MPLS-TP MIB May 6, 2014 ::= { mplsTeExtCompliances 1 } -- Compliance requirement for read-only implementations. mplsTeExtModuleReadOnlyCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "Compliance statement for agents that only provide read-only support for MPLS-TE-EXT-STD-MIB module." MODULE -- this module MANDATORY-GROUPS { mplsTunnelExtGroup } GROUP mplsTunnelExtIpOperatorGroup DESCRIPTION "This group is mandatory for devices which support configuration of IP based identifier tunnels." GROUP mplsTunnelExtIccOperatorGroup DESCRIPTION "This group is mandatory for devices which support configuration of ICC based tunnels." -- mplsTunnelExtTable OBJECT mplsTunnelExtOppositeDirPtr MIN-ACCESS read-only DESCRIPTION "Write access is not required." OBJECT mplsTunnelExtOppositeDirTnlValid MIN-ACCESS read-only DESCRIPTION "Write access is not required." OBJECT mplsTunnelExtDestTnlIndex MIN-ACCESS read-only DESCRIPTION "Write access is not required." OBJECT mplsTunnelExtDestTnlLspIndex MIN-ACCESS read-only DESCRIPTION "Write access is not required." Venkatesan, et al. Expires November 7, 2014 [Page 50] INTERNET DRAFT MPLS-TP MIB May 6, 2014 OBJECT mplsTunnelExtDestTnlValid MIN-ACCESS read-only DESCRIPTION "Write access is not required." OBJECT mplsTunnelExtIngressLSRLocalIdValid MIN-ACCESS read-only DESCRIPTION "Write access is not required." OBJECT mplsTunnelExtEgressLSRLocalIdValid MIN-ACCESS read-only DESCRIPTION "Write access is not required." OBJECT mplsTunnelExtNodeConfigGlobalId MIN-ACCESS read-only DESCRIPTION "Write access is not required." OBJECT mplsTunnelExtNodeConfigNodeId MIN-ACCESS read-only DESCRIPTION "Write access is not required." OBJECT mplsTunnelExtNodeConfigStorageType MIN-ACCESS read-only DESCRIPTION "Write access is not required." OBJECT mplsTunnelExtNodeConfigRowStatus SYNTAX RowStatus { active(1) } MIN-ACCESS read-only DESCRIPTION "Write access is not required." OBJECT mplsTunnelExtNodeConfigCcId MIN-ACCESS read-only DESCRIPTION "Write access is not required." OBJECT mplsTunnelExtNodeConfigIccId MIN-ACCESS read-only DESCRIPTION "Write access is not required." OBJECT mplsTunnelExtNodeConfigIccValid MIN-ACCESS read-only Venkatesan, et al. Expires November 7, 2014 [Page 51] INTERNET DRAFT MPLS-TP MIB May 6, 2014 DESCRIPTION "Write access is not required." ::= { mplsTeExtCompliances 2 } -- Units of conformance. mplsTunnelExtGroup OBJECT-GROUP OBJECTS { mplsTunnelExtOppositeDirPtr, mplsTunnelExtOppositeDirTnlValid, mplsTunnelExtDestTnlIndex, mplsTunnelExtDestTnlLspIndex, mplsTunnelExtDestTnlValid, mplsTunnelExtIngressLSRLocalIdValid, mplsTunnelExtEgressLSRLocalIdValid } STATUS current DESCRIPTION "Necessary, but not sufficient, set of objects to implement tunnels. In addition, depending on the operating environment, the following groups are mandatory." ::= { mplsTeExtGroups 1 } mplsTunnelExtIpOperatorGroup OBJECT-GROUP OBJECTS { mplsTunnelExtNodeConfigLocalIdNext, mplsTunnelExtNodeConfigGlobalId, mplsTunnelExtNodeConfigNodeId, mplsTunnelExtNodeIpMapLocalId, mplsTunnelExtNodeConfigStorageType, mplsTunnelExtNodeConfigRowStatus } STATUS current DESCRIPTION "Object(s) needed to implement IP compatible tunnels." ::= { mplsTeExtGroups 2 } mplsTunnelExtIccOperatorGroup OBJECT-GROUP OBJECTS { mplsTunnelExtNodeConfigLocalIdNext, mplsTunnelExtNodeConfigCcId, mplsTunnelExtNodeConfigIccId, mplsTunnelExtNodeConfigNodeId, mplsTunnelExtNodeConfigIccValid, mplsTunnelExtNodeIccMapLocalId, Venkatesan, et al. Expires November 7, 2014 [Page 52] INTERNET DRAFT MPLS-TP MIB May 6, 2014 mplsTunnelExtNodeConfigStorageType, mplsTunnelExtNodeConfigRowStatus } 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. 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: - 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: Venkatesan, et al. Expires November 7, 2014 [Page 53] INTERNET DRAFT MPLS-TP MIB May 6, 2014 - the tables specified in [RFC3812], [RFC3813] and this document MIB tables 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. 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]. 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 OID } to the MPLS-ID- STD-MIB module specified in this document. 15.3. IANA Considerations for MPLS-LSR-EXT-STD-MIB Venkatesan, et al. Expires November 7, 2014 [Page 54] INTERNET DRAFT MPLS-TP MIB May 6, 2014 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)", STD 58, RFC 2578, April 1999. [RFC2579] McCloghrie, K., Perkins, D., and J. Schoenwaelder, "Textual Conventions for SMIv2", STD 58, RFC 2579, April 1999. [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. [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 Venkatesan, et al. Expires November 7, 2014 [Page 55] INTERNET DRAFT MPLS-TP MIB May 6, 2014 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. [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. 18. Authors' Addresses Venkatesan Mahalingam Dell Inc. 5450 Great America Parkway, Santa Clara, CA 95054, USA Email: venkat.mahalingams@gmail.com Venkatesan, et al. Expires November 7, 2014 [Page 56] INTERNET DRAFT MPLS-TP MIB May 6, 2014 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 Kannan KV Sampath Redeem India Email: kannankvs@gmail.com Venkatesan, et al. Expires November 7, 2014 [Page 57]