idnits 2.17.1 draft-ietf-mpls-tp-te-mib-11.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (December 18, 2014) is 3417 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) -- Obsolete informational reference (is this intentional?): RFC 5226 (Obsoleted by RFC 8126) Summary: 0 errors (**), 0 flaws (~~), 1 warning (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group 3 INTERNET-DRAFT M.Venkatesan 4 Intended Status: Standards Track Dell Inc. 5 Expires: June 21, 2015 Kannan KV Sampath 6 Redeem 7 Sam K. Aldrin 8 Huawei Technologies 9 Thomas D. Nadeau 10 Brocade 12 December 18, 2014 14 MPLS-TP Traffic Engineering (TE) Management Information Base (MIB) 15 draft-ietf-mpls-tp-te-mib-11.txt 17 Abstract 19 This memo defines a portion of the Management Information Base (MIB) 20 for use with network management protocols in the Internet community. 21 In particular, it describes additional managed objects and textual 22 conventions for Tunnels, Identifiers and Label Switching Router to 23 support Multiprotocol Label Switching (MPLS) MIB modules for 24 transport networks. 26 Status of this Memo 28 This Internet-Draft is submitted to IETF in full conformance with the 29 provisions of BCP 78 and BCP 79. 31 Internet-Drafts are working documents of the Internet Engineering 32 Task Force (IETF), its areas, and its working groups. Note that 33 other groups may also distribute working documents as Internet- 34 Drafts. 36 Internet-Drafts are draft documents valid for a maximum of six months 37 and may be updated, replaced, or obsoleted by other documents at any 38 time. It is inappropriate to use Internet-Drafts as reference 39 material or to cite them other than as "work in progress." 41 The list of current Internet-Drafts can be accessed at 42 http://www.ietf.org/ietf/1id-abstracts.txt. 44 The list of Internet-Draft Shadow Directories can be accessed at 45 http://www.ietf.org/shadow.html. 47 This Internet-Draft will expire on June 21, 2015. 49 Copyright and License Notice 51 Copyright (c) 2014 IETF Trust and the persons identified as the 52 document authors. All rights reserved. 54 This document is subject to BCP 78 and the IETF Trust's Legal 55 Provisions Relating to IETF Documents 56 (http://trustee.ietf.org/license-info) in effect on the date of 57 publication of this document. Please review these documents 58 carefully, as they describe your rights and restrictions with respect 59 to this document. Code Components extracted from this document must 60 include Simplified BSD License text as described in Section 4.e of 61 the Trust Legal Provisions and are provided without warranty as 62 described in the Simplified BSD License. 63 Table of Contents 65 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 66 2. The Internet-Standard Management Framework . . . . . . . . . . 5 67 3. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 68 3.1. Conventions used in this document . . . . . . . . . . . . . 5 69 3.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . 5 70 3.3. Acronyms . . . . . . . . . . . . . . . . . . . . . . . . . 7 71 4. Motivations . . . . . . . . . . . . . . . . . . . . . . . . . . 7 72 5. Feature List . . . . . . . . . . . . . . . . . . . . . . . . . 7 73 6. Outline . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 74 6.1 MIB Module Extensions . . . . . . . . . . . . . . . . . . . 9 75 6.1.1 Summary of MIB Module changes . . . . . . . . . . . . . 9 76 6.2 MPLS-TE-EXT-STD-MIB . . . . . . . . . . . . . . . . . . . . 10 77 6.2.1 mplsTunnelExtNodeConfigTable . . . . . . . . . . . . . . 10 78 6.2.2 mplsTunnelExtNodeIpMapTable . . . . . . . . . . . . . . 11 79 6.2.3 mplsTunnelExtNodeIccMapTable . . . . . . . . . . . . . . 11 80 6.2.4 mplsTunnelExtTable . . . . . . . . . . . . . . . . . . . 11 81 6.3 MPLS-TC-EXT-STD-MIB . . . . . . . . . . . . . . . . . . . . 11 82 6.4 MPLS-ID-STD-MIB . . . . . . . . . . . . . . . . . . . . . . 11 83 6.5 MPLS-LSR-EXT-STD-MIB . . . . . . . . . . . . . . . . . . . . 12 84 6.6 The Use of RowPointer . . . . . . . . . . . . . . . . . . . 12 85 7. MIB Modules Interdependencies . . . . . . . . . . . . . . . . . 13 86 8. Dependencies between MIB Module Tables . . . . . . . . . . . . 14 87 9. Example of MPLS-TP Tunnel Setup . . . . . . . . . . . . . . . . 15 88 9.1. Example of MPLS-TP static co-routed bidirectional tunnel 89 setup . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 90 9.1.1. mplsTunnelEntry . . . . . . . . . . . . . . . . . . . . 16 91 9.1.2. mplsTunnelExtEntry . . . . . . . . . . . . . . . . . . 17 92 9.1.3. Forward direction mplsOutSegmentEntry . . . . . . . . . 17 93 9.1.4. Reverse direction mplsInSegmentEntry . . . . . . . . . 17 94 9.1.5. Forward direction mplsXCEntry . . . . . . . . . . . . . 18 95 9.1.6. Reverse direction mplsXCEntry . . . . . . . . . . . . . 18 96 9.1.7. Forward direction mplsXCExtEntry . . . . . . . . . . . 19 97 9.1.8. Reverse direction mplsXCExtEntry . . . . . . . . . . . 19 98 9.2. Example of MPLS-TP static associated bidirectional tunnel 99 setup . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 100 9.2.1. Forward direction mplsTunnelEntry . . . . . . . . . . . 19 101 9.2.2. Forward direction mplsTunnelExtEntry . . . . . . . . . 20 102 9.2.3. Forward direction mplsOutSegmentTable . . . . . . . . . 20 103 9.2.4. Forward direction mplsXCEntry . . . . . . . . . . . . . 21 104 9.2.5. Forward direction mplsXCExtEntry . . . . . . . . . . . 21 105 9.2.6. Reverse direction mplsTunnelEntry . . . . . . . . . . . 21 106 9.2.7. Reverse direction mplsTunnelExtEntry . . . . . . . . . 22 107 9.2.8. Reverse direction mplsInSegmentEntry . . . . . . . . . 22 108 9.2.9. Reverse direction mplsXCEntry . . . . . . . . . . . . . 23 109 9.2.10. Reverse direction mplsXCExtEntry . . . . . . . . . . . 23 110 9.3. Example of MPLS-TP signaled co-routed bidirectional 111 tunnel setup . . . . . . . . . . . . . . . . . . . . . . . 23 112 9.3.1. mplsTunnelEntry . . . . . . . . . . . . . . . . . . . . 24 113 9.3.2. mplsTunnelExtEntry . . . . . . . . . . . . . . . . . . 24 114 9.3.3. Forward direction mplsOutSegmentEntry . . . . . . . . . 25 115 9.3.4. Reverse direction mplsInSegmentEntry . . . . . . . . . 25 116 9.3.5. Forward direction mplsXCEntry . . . . . . . . . . . . . 25 117 9.3.6. Reverse direction mplsXCEntry . . . . . . . . . . . . . 25 118 9.3.7. Forward direction mplsXCExtEntry . . . . . . . . . . . 25 119 9.3.8. Reverse direction mplsXCExtEntry . . . . . . . . . . . 26 120 10. MPLS Textual Convention Extension MIB definitions . . . . . . 26 121 11. MPLS Identifier MIB definitions . . . . . . . . . . . . . . . 29 122 12. MPLS LSR Extension MIB definitions . . . . . . . . . . . . . . 34 123 13. MPLS Tunnel Extension MIB definitions . . . . . . . . . . . . 39 124 14. Security Consideration . . . . . . . . . . . . . . . . . . . . 56 125 15. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 57 126 15.1. IANA Considerations for MPLS-TC-EXT-STD-MIB . . . . . . . 58 127 15.2. IANA Considerations for MPLS-ID-STD-MIB . . . . . . . . . 58 128 15.3. IANA Considerations for MPLS-LSR-EXT-STD-MIB . . . . . . . 58 129 15.4. IANA Considerations for MPLS-TE-EXT-STD-MIB . . . . . . . 58 130 16. References . . . . . . . . . . . . . . . . . . . . . . . . . . 58 131 16.1. Normative References . . . . . . . . . . . . . . . . . . . 58 132 16.2. Informative References . . . . . . . . . . . . . . . . . 59 133 17. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 60 134 18. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 60 136 1. Introduction 138 This memo defines a portion of the Management Information Base (MIB) for 139 use with network management protocols in the Internet community. In 140 particular, it describes additional textual conventions and managed 141 objects for Tunnels, Identifiers and Label Switching Router to support 142 Multiprotocol Label Switching (MPLS) MIB modules for transport networks. 143 MIB modules defined in this document extend the existing MPLS MIB 144 objects in such a way that they support MPLS-TP but also other MPLS 145 networks as well. Hence, the MPLS-TP name is not included in the MIB 146 module name. 148 As described in the MPLS Traffic Engineering (TE) Management Information 149 Base (MIB) definition [RFC3812], MPLS traffic engineering is concerned 150 with the creation and management of MPLS tunnels. This term is a 151 shorthand for a combination of one or more LSPs linking an ingress and 152 an egress LSR. Several types of point-to-point MPLS tunnels may be 153 constructed between a pair of LSRs A and B: 155 - Unidirectional with a single LSP (say) from A to B. 157 - Associated bidirectional consisting of two separately routed LSPs, 158 one linking A to B and the other linking B to A. Together the pair 159 provide a single logical bidirectional transport path. 161 - Co-routed bidirectional consisting of an associated bidirectional 162 tunnel but with the second LSP from B to A following the reverse 163 of the path of the LSP from A to B, in terms of both nodes and 164 links. 166 Tunnels may be either statically configured by management action or 167 dynamically created using a LSP management protocol. 169 The existing MPLS TE MIB [RFC3812] and the Generalized Multiprotocol 170 Label Switching (GMPLS) Traffic Engineering Management Information Base 171 [RFC4802] address only a subset of the combinations of statically and 172 dynamically configured tunnel types, catering for statically configured 173 unidirectional tunnels together with dynamically configured 174 unidirectional and co-routed bidirectional tunnels. They are also 175 restricted to two end point LSRs identified by IP addresses. 177 The MPLS-TP TE MIB defined in this document extends the MIB modules 178 defined in [RFC3812] to cover all six combinations (that is adding 179 support for statically configured associated and co-routed bidirectional 180 plus dynamically configured associated bidirectional tunnels). It also 181 extends support to end points that are identified other than with IP 182 addresses. 184 This support is provided by a suite of four MIB modules that are to be 185 used in conjunction with the MIB modules defined in [RFC3812] and the 186 companion document [RFC3813] for MPLS Transport Profile (MPLS-TP) tunnel 187 management. 189 At the time of writing, SNMP SET is no longer recommended as a way to 190 configure MPLS networks as was described in [RFC3812]. However, since 191 the MIB modules specified in this document extend and are intended to 192 work in parallel with the MIB modules for MPLS specified in [RFC3812], 193 certain objects defined here are specified with MAX-ACCESS of read-write 194 or read-create so that specifications of the base tables in [RFC3812] 195 and the extensions in this document are consistent. Although the 196 examples described in Section 9 specify means to configure MPLS-TP 197 tunnels in a similar way to the examples in [RFC3812], this should be 198 seen as indicating how the MIB values would be returned in the specified 199 circumstances having been configured by alternative means. 201 2. The Internet-Standard Management Framework 203 For a detailed overview of the documents that describe the current 204 Internet-Standard Management Framework, please refer to section 7 of RFC 205 3410 [RFC3410]. 207 Managed objects are accessed via a virtual information store, termed the 208 Management Information Base or MIB. MIB objects are generally accessed 209 through the Simple Network Management Protocol (SNMP). Objects in the 210 MIB are defined using the mechanisms defined in the Structure of 211 Management Information (SMI). This memo specifies a MIB module that is 212 compliant to the SMIv2, which is described in STD 58 [RFC2578], STD 58 213 [RFC2579] and STD 58 [RFC2580]. 215 3. Overview 217 3.1. Conventions used in this document 219 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 220 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 221 "OPTIONAL" in this document are to be interpreted as described in 222 [RFC2119]. 224 3.2. Terminology 226 This document uses terminology from the Multiprotocol Label Switching 227 Architecture [RFC3031], Multiprotocol Label Switching (MPLS) Traffic 228 Engineering (TE) Management Information Base (MIB) [RFC3812], 229 Multiprotocol Label Switching (MPLS) Label Switching Router (LSR) 230 Management Information Base (MIB) [RFC3813] and MPLS Transport Profile 231 (MPLS-TP) Identifiers [RFC6370]. 233 3.3. Acronyms 235 CC: Country Code 236 ICC: ITU Carrier Code 237 LSP: Label Switching Path 238 LSR: Label Switching Router 239 MPLS-TP: MPLS Transport Profile 240 TE: Traffic Engineering 241 TP: Transport Profile 243 4. Motivations 245 Multiprotocol Label Switching (MPLS) Traffic Engineering (TE) Management 246 Information Base (MIB) [RFC3812] provides support for Traffic 247 Engineering tunnels. In MPLS, the actual transport of packets is 248 provided by Label Switched Paths (LSPs). A transport service may be 249 composed of multiple LSPs. In order to clearly identify the MPLS-TP 250 service, as defined in [RFC6370], we use the term "MPLS-TP Tunnel" or 251 simply "tunnel". However, with MPLS-TP, the characteristics of the 252 tunnels were enhanced. For example, MPLS-TP tunnels, are bidirectional 253 in nature and could be used with non-IP identifiers for the tunnel end 254 points. As the existing MPLS-TE-STD-MIB and GMPLS-TE-STD-MIB were 255 defined mainly to support unidirectional tunnels and signaled co-routed 256 bidirectional tunnel definitions respectively, these existing MIB 257 modules are not sufficient to capture all the characteristics of the 258 tunnels. Hence, enhancing the MIB modules to support MPLS-TP tunnels is 259 required. As most of the attributes of MPLS Traffic Engineering tunnels 260 are also applicable to MPLS-TP tunnels, it is optimal to re-use and 261 extend the existing MIB module definition instead of defining a new MIB 262 module. 264 This document defines four additional MIB modules, namely MPLS-TE-EXT- 265 STD-MIB, MPLS-TC-EXT-STD-MIB, MPLS-ID-STD-MIB and MPLS-LSR-EXT-STD-MIB. 266 As these additional MIB modules are required for MPLS-TP functionality, 267 these are all defined in this document, instead of being documented 268 separately. 270 5. Feature List 272 The MIBs in this document satisfy the following requirements and 273 constraints: 275 The MIB modules, taken together, support statically configured and 276 dynamically signaled point-to-point, co-routed bidirectional and 277 associated bidirectional tunnels. 279 - The MPLS tunnels need not be interfaces, but it is possible 280 to configure an MPLS TP tunnel as an interface. Same ifType 150, 281 as defined in section 8 of [RFC3812], will be used for MPLS-TP 282 tunnels as well. 284 - The mplsTunnelTable [RFC3812] is also to be used for MPLS-TP 285 tunnels. 287 - New MPLS-TP specific textual conventions and identifiers are 288 required. 290 - The mplsTunnelTable is sparsely extended to support MPLS-TP 291 tunnel specific objects. 293 - A node configuration table (mplsTunnelExtNodeConfigTable), as 294 detailed in the below section 6.1.2, is used to translate 295 the Global_ID::Node_ID or ICC_Operator_ID::Node_ID to 296 the local identifier in order to index mplsTunnelTable. 298 - The mplsXCTable is sparsely extended to support MPLS-TP 299 XC(Cross Connect) specific objects. 301 - The MIB module supports persistent, as well as non-persistent 302 tunnels. 304 6. Outline 306 Traffic Engineering support for the MPLS-TP tunnels requires the set up 307 of the co-routed or associated bidirectional tunnel. The tables and MIB 308 modules that are mentioned in the below subsections support the 309 functionality described in documents [RFC5654] and [RFC6370]. These 310 tables support both IP compatible and ITU Carrier Code (ICC) based 311 tunnel configurations. 313 The below Figure 1 depicts how the table references are followed in this 314 MIB. 316 Tunnel1-->XC1<-------------- 317 ^ ^ | | | 318 | | | |-->InSeg1 | 319 | | | |-->OutSeg1 | 320 | | v | 321 | ------XCext1 | 322 | | | 323 V v | 324 Tunnel2-->XC1 | 325 ^ | | | 326 | | |-->InSeg2 | 327 | | |-->OutSeg2 | 328 | v | 329 ------XCext2------------ 331 Figure 1: Table references of MIB modules 333 6.1 MIB Module Extensions 335 Four MIB modules are extended to support MPLS-TP tunnels, namely, 336 MPLS-TE-EXT-STD-MIB, MPLS-TC-EXT-STD-MIB, MPLS-ID-STD-MIB and MPLS- 337 LSR-EXT-STD-MIB. Following section provides the summary of changes. 339 6.1.1 Summary of MIB Module changes 341 - Node configuration table (mplsTunnelExtNodeConfigTable) for 342 setting the local identifier for Tunnel Ingress and Egress 343 identifiers. 345 - Node IP map table (mplsTunnelExtNodeIpMapTable) for querying 346 the local identifier for a given Global_ID and Node_ID. 348 - Node ICC map table (mplsTunnelExtNodeIccMapTable) for querying 349 the local identifier for a given ICC_Operator_ID and Node_ID. 351 - Tunnel extension table (mplsTunnelExtTable) for setting up 352 MPLS-TP tunnels with sparse extension of mplsTunnelTable. 354 - Textual conventions and object definitions for MPLS-TP Tunnels 356 - Cross connect extension table (mplsXCExtTable) for setting up 357 the MPLS-TP LSPs. 359 These tables are described in the subsequent sections. 361 6.2 MPLS-TE-EXT-STD-MIB 363 The TE MIB module extensions and details of the tables are described 364 in the following sections. 366 6.2.1 mplsTunnelExtNodeConfigTable 368 The mplsTunnelExtNodeConfigTable is used to assign a local identifier 369 for a given ICC_Operator_ID::Node_ID or Global_ID::Node_ID 370 combination as defined in [RFC6923] and [RFC6370] respectively. The 371 CC is a string of two characters, each being an uppercase Basic Latin 372 alphabetic (i.e., A-Z). The ICC is a string of one to six characters, 373 each an upper case Basic Latin alphabetic (i.e., A-Z) or numeric 374 (i.e., 0-9). All of the characters are encoded using [T.50] as 375 described in [RFC6370]. 377 In the IP compatible mode, Global_ID::Node_ID, is used to uniquely 378 identify a node. For each ICC_Operator_ID::Node_ID or 379 Global_ID::Node_ID, there is a unique entry in the table representing 380 a node. As the regular TE tunnels use IP address as LSR ID, the 381 local identifier should be below the first valid IP address, which is 382 16777216[1.0.0.0]. Every node is assigned a local identifier within a 383 range of 0 to 16777215. This local identifier is used for indexing 384 into mplsTunnelTable as mplsTunnelIngressLSRId and 385 mplsTunnelEgressLSRId. 387 For IP compatible environment, MPLS-TP tunnel is indexed by Tunnel 388 Index, Tunnel Instance, Source Global_ID, Source Node_ID, Destination 389 Global_ID and Destination Node_ID. 391 For ICC based environment, MPLS-TP tunnel is indexed by Tunnel Index, 392 Tunnel Instance, Source CC, Source ICC, Source Node_ID, Destination 393 CC, Destination ICC and Destination Node_ID. 395 As mplsTunnelTable is indexed by mplsTunnelIndex, 396 mplsTunnelInstance, mplsTunnelIngressLSRId, and 397 mplsTunnelEgressLSRId, the MPLS-TP tunnel identifiers cannot be 398 used directly. 400 The mplsTunnelExtNodeConfigTable will be used to store an entry for 401 ICC_Operator_ID::Node_ID or Global_ID::Node_ID with a local 402 identifier to be used as LSR ID in mplsTunnelTable. 404 6.2.2 mplsTunnelExtNodeIpMapTable 406 The read-only mplsTunnelExtNodeIpMapTable is used to query the local 407 identifier assigned and stored in mplsTunnelExtNodeConfigTable for 408 a given Global_ID::Node_ID. In order to query the local identifier, 409 in the IP compatible mode, this table is indexed with 410 Global_ID::Node_ID. In the IP compatible mode for a TP tunnel, 411 Global_ID::Node_ID is used. 413 A separate query is made to get the local identifier of both 414 Ingress and Egress Global_ID::Node_ID identifiers. These local 415 identifiers are used as mplsTunnelIngressLSRId and 416 mplsTunnelEgressLSRId, while indexing mplsTunnelTable. 418 6.2.3 mplsTunnelExtNodeIccMapTable 420 The read-only mplsTunnelExtNodeIccMapTable is used to query the local 421 identifier assigned and stored in the mplsTunnelExtNodeConfigTable 422 for a given ICC_Operator_ID::Node_ID. 424 A separate query is made to get the local identifier of both 425 Ingress and Egress ICC_Operator_ID::Node_ID. These local identifiers 426 are used as mplsTunnelIngressLSRId and mplsTunnelEgressLSRId, 427 while indexing mplsTunnelTable. 429 6.2.4 mplsTunnelExtTable 431 This table sparsely extends the mplsTunnelTable in order to support 432 MPLS-TP tunnels with additional objects. All the additional 433 attributes specific to supporting TP tunnel are contained in this 434 extended table and could be accessed with the mplsTunnelTable 435 indices. 437 The gmplsTunnelReversePerfTable [RFC4802] should be used to provide 438 per-tunnel packet performance information for the reverse direction 439 of a bidirectional tunnel. It can be seen as supplementing the 440 mplsTunnelPerfTable, which augments the mplsTunnelTable. 442 6.3 MPLS-TC-EXT-STD-MIB 444 This MIB module contains textual Conventions for LSPs of MPLS based 445 transport networks. 447 6.4 MPLS-ID-STD-MIB 448 This MIB module contains generic object definitions for MPLS Traffic 449 Engineering in transport networks. 451 6.5 MPLS-LSR-EXT-STD-MIB 453 This MIB module contains generic object definitions (Cross connect 454 extension table - mplsXCExtTable, for setting up the MPLS-TP LSPs 455 with sparse extension of mplsXCTable) for MPLS LSRs in transport 456 networks. 458 6.6 The Use of RowPointer 460 This document follows the RowPointer usage as described in the 461 section 10 of [RFC3812]. 463 A new RowPointer object, mplsTunnelExtOppositeDirPtr, is added to 464 mplsTunnelExtTable of MPLS-TE-EXT-STD-MIB MIB module. This RowPointer 465 object points to the opposite direction tunnel entry. 467 Two additional RowPointers objects, mplsXCExtTunnelPointer and 468 mplsXCExtOppositeDirXCPtr are added to mplsXCExtTable of MPLS-LSR- 469 EXT-STD-MIB. The RowPointer mplsXCExtTunnelPointer is read-only 470 object used to indicate the back pointer to the tunnel entry. The 471 RowPointer mplsXCExtOppositeDirXCPtr object points to the opposite 472 direction XC entry. 474 If these RowPointer returns zeroDotZero, it implies that there is no 475 entry associated with the RowPointer object. 477 7. MIB Modules Interdependencies 479 This section provides an overview of the relationship between the 480 MPLS-TP TE MIB module and other MPLS MIB modules. 482 The arrows in the following diagram show a 'depends on' 483 relationship. A relationship "MIB module A depends on MIB module B" 484 means that MIB module A uses an object, object identifier, or 485 textual convention defined in MIB module B, or that MIB module A 486 contains a pointer (index or RowPointer) to an object in 487 MIB module B. 489 MPLS-TC-EXT-STD-MIB 490 ^ 491 | 492 | 493 +<---- MPLS-ID-STD-MIB 494 ^ 495 | | 496 +<---- MPLS-TE-EXT-STD-MIB 497 | | 498 | V 499 | MPLS-TE-STD-MIB 500 | | 501 | | 502 | V 503 | MPLS-LSR-STD-MIB 504 | ^ 505 | | 506 | | 507 +------MPLS-LSR-EXT-STD-MIB 509 Figure 2: MIB modules interdependencies 511 Thus: 513 - All the new MPLS extension MIB modules depend on 514 MPLS-TC-EXT-STD-MIB. 516 - MPLS-ID-STD-MIB contains references to objects in 517 MPLS-TE-STD-MIB [RFC3812]. 519 - MPLS-TE-EXT-STD-MIB contains references to objects in 520 MPLS-TE-STD-MIB [RFC3812]. 522 - MPLS-LSR-EXT-STD-MIB contains references to objects in 523 MPLS-LSR-STD-MIB [RFC3813]. 525 The mplsTunnelExtTable sparsely extends the mplsTunnelTable of 526 MPLS-TE-STD-MIB [RFC3812]. This helps in associating the reverse 527 direction tunnel information. 529 The mplsXCExtTable sparsely extends the mplsXCTable of 530 MPLS-LSR-STD-MIB [RFC3813]. This helps in pointing back to the tunnel 531 entry for easy tunnel access from XC entry. 533 Note that all of the MIB modules shown above in the figure also 534 have a dependency on MPLS-TC-STD-MIB. 536 8. Dependencies between MIB Module Tables 538 The tables in MPLS-TE-EXT-STD-MIB are related as shown on the diagram 539 below. The arrows indicate a reference from one table to another. 541 mplsTunnelExtNodeConfigTable 542 ^ ^ ^ 543 | | | 544 | | | 545 | | | 546 | | +----------------------+ 547 | | | 548 | mplsTunnelExtNodeIpMapTable mplsTunnelExtNodeIccMapTable 549 | 550 | mplsXCExtTable 551 | | ^ 552 | +---------+ | 553 | | | 554 | | | 555 | V V 556 mplsTunnelTable ---->mplsXCTable 557 ^ 558 | 559 | 560 | 561 mplsTunnelExtTable 563 Figure 3: Dependencies between MIB module tables 565 An existing mplsTunnelTable uses the mplsTunnelExtNodeConfigTable 566 table to map the Global_ID::Node_ID and/or ICC_Operator_ID::Node_ID 567 with the local number in order to accommodate in the existing tunnel 568 table's ingress/egress LSR-id. 570 New mplsTunnelExtTable table provides the reverse direction LSP 571 information for the existing tunnel table in order to achieve 572 bidirectional LSPs. 574 mplsXCExtTable sparsely extends the mplsLsrXCTable to provide 575 backward reference to tunnel entry. 577 9. Example of MPLS-TP Tunnel Setup 579 In this section, we provide an example to configure MPLS-TP 580 bidirectional tunnels with IP tunnel identifiers. This example 581 provides the usage of MPLS-TP Tunnel MIB along with the extended MIB 582 modules introduced in this document. 584 Do note that a MPLS-TP tunnel could be setup statically as well as 585 signaled via control plane. This example considers accessing MIB 586 objects on a head-end for a static and signaled MPLS-TP tunnels. This 587 section shows the configuration of the forward and reverse direction 588 MPLS-TP LSPs that run between East and West and vice-versa. Only 589 objects relevant to MPLS-TP tunnels are illustrated here. 591 In mplsTunnelExtNodeConfigTable: 593 { 594 -- Non-IP Ingress LSR-Id (Index to the table) 596 mplsTunnelExtNodeConfigLocalId = 1, 598 mplsTunnelExtNodeConfigGlobalId = 1234, 599 mplsTunnelExtNodeConfigNodeId = 10, 600 -- Mandatory parameters needed to activate the row go here 601 mplsTunnelExtNodeConfigRowStatus = createAndGo (4) 603 -- Non-IP Egress LSR-Id (Index to the table) 604 mplsTunnelExtNodeConfigLocalId = 2, 605 mplsTunnelExtNodeConfigGlobalId = 1234, 606 mplsTunnelExtNodeConfigNodeId = 20, 607 -- Mandatory parameters needed to activate the row go here 608 mplsTunnelExtNodeConfigRowStatus = createAndGo (4) 609 } 611 This will create an entry in the mplsTunnelExtNodeConfigTable for a 612 Global_ID::Node_ID. A separate entry is made for both Ingress LSR 613 and Egress LSR. 615 The following read-only mplsTunnelExtNodeIpMapTable table is 616 populated automatically upon creating an entry in 617 mplsTunnelExtNodeConfigTable and this table is used to retrieve 618 the local identifier for the given Global_ID::Node_ID. 620 In mplsTunnelExtNodeIpMapTable: 622 { 623 -- Global_ID (Index to the table) 624 mplsTunnelExtNodeIpMapGlobalId = 1234, 625 -- Node Identifier (Index to the table) 626 mplsTunnelExtNodeIpMapNodeId = 10, 627 mplsTunnelExtNodeIpMapLocalId = 1 629 -- Global_ID (Index to the table) 630 mplsTunnelExtNodeIpMapGlobalId = 1234, 631 -- Node Identifier (Index to the table) 632 mplsTunnelExtNodeIpMapNodeId = 20, 633 mplsTunnelExtNodeIpMapLocalId = 2 634 } 636 9.1. Example of MPLS-TP static co-routed bidirectional tunnel setup 638 The following denotes the co-routed bidirectional tunnel "head" 639 entry. 641 9.1.1. mplsTunnelEntry 643 In mplsTunnelTable: 645 { 646 mplsTunnelIndex = 1, 647 mplsTunnelInstance = 1, 648 -- Local map number created in mplsTunnelExtNodeConfigTable for 649 -- Ingress LSR-Id 650 mplsTunnelIngressLSRId = 1, 652 -- Local map number created in mplsTunnelExtNodeConfigTable for 653 -- Egress LSR-Id 654 mplsTunnelEgressLSRId = 2, 655 mplsTunnelName = "TP co-routed bidirectional LSP", 656 mplsTunnelDescr = "East to West", 657 mplsTunnelIsIf = true (1), 658 -- RowPointer MUST point to the first accessible column 659 mplsTunnelXCPointer = 660 mplsXCLspId.4.0.0.0.1.1.0.4.0.0.0.1, 661 mplsTunnelSignallingProto = none (1), 662 mplsTunnelSetupPrio = 0, 663 mplsTunnelHoldingPrio = 0, 664 mplsTunnelSessionAttributes = 0, 665 mplsTunnelLocalProtectInUse = false (0), 666 -- RowPointer MUST point to the first accessible column 667 mplsTunnelResourcePointer = mplsTunnelResourceMaxRate.5, 668 mplsTunnelInstancePriority = 1, 669 mplsTunnelHopTableIndex = 1, 670 mplsTunnelIncludeAnyAffinity = 0, 671 mplsTunnelIncludeAllAffinity = 0, 672 mplsTunnelExcludeAnyAffinity = 0, 673 mplsTunnelRole = head (1), 674 -- Mandatory parameters needed to activate the row go here 675 mplsTunnelRowStatus = createAndGo (4) 676 } 678 9.1.2. mplsTunnelExtEntry 680 -- An MPLS extension table 681 In mplsTunnelExtTable: 682 { 683 -- This opposite direction tunnel pointer may point to 0.0 684 -- if co-routed bidirectional tunnel is managed by single tunnel 685 -- entry 686 mplsTunnelExtOppositeDirTnlPtr = 0.0 687 -- Set both the Ingress and Egress LocalId objects to TRUE as 688 -- this tunnel entry uses the local identifiers. 689 mplsTunnelExtIngressLSRLocalIdValid = true, 690 mplsTunnelExtEgressLSRLocalIdValid = true 692 } 694 We must next create the appropriate in-segment and out-segment 695 entries. These are done in [RFC3813] using the mplsInSegmentTable and 696 mplsOutSegmentTable. 698 9.1.3. Forward direction mplsOutSegmentEntry 700 For the forward direction, 702 In mplsOutSegmentTable: 703 { 704 mplsOutSegmentIndex = 0x0000001, 705 mplsOutSegmentInterface = 13, -- outgoing interface 706 mplsOutSegmentPushTopLabel = true(1), 707 mplsOutSegmentTopLabel = 22, -- outgoing label 709 -- RowPointer MUST point to the first accessible column. 710 mplsOutSegmentTrafficParamPtr = 0.0, 711 mplsOutSegmentRowStatus = createAndGo (4) 712 } 714 9.1.4. Reverse direction mplsInSegmentEntry 716 For the reverse direction, 718 In mplsInSegmentTable: 719 { 720 mplsInSegmentIndex = 0x0000001 721 mplsInSegmentLabel = 21, -- incoming label 722 mplsInSegmentNPop = 1, 723 mplsInSegmentInterface = 13, -- incoming interface 725 -- RowPointer MUST point to the first accessible column. 726 mplsInSegmentTrafficParamPtr = 0.0, 727 mplsInSegmentRowStatus = createAndGo (4) 728 } 730 Next, two cross-connect entries are created in the mplsXCTable of the 731 MPLS-LSR-STD-MIB [RFC3813], thereby associating the newly created 732 segments together. 734 9.1.5. Forward direction mplsXCEntry 736 In mplsXCTable: 737 { 738 mplsXCIndex = 0x01, 739 mplsXCInSegmentIndex = 0x00000000, 740 mplsXCOutSegmentIndex = 0x00000001, 741 mplsXCLspId = 0x0102 -- unique ID 743 -- only a single outgoing label 744 mplsXCLabelStackIndex = 0x00, 745 mplsXCRowStatus = createAndGo(4) 747 } 749 9.1.6. Reverse direction mplsXCEntry 751 In mplsXCTable: 752 { 753 mplsXCIndex = 0x01, 754 mplsXCInSegmentIndex = 0x00000001, 755 mplsXCOutSegmentIndex = 0x00000000, 756 mplsXCLspId = 0x0102 -- unique ID 757 -- only a single outgoing label 758 mplsXCLabelStackIndex = 0x00, 759 mplsXCRowStatus = createAndGo(4) 760 } 762 This table entry is extended by entry in the 763 mplsXCExtTable. Note that the nature of the 'extends' 764 relationship is a sparse augmentation so that the entry in the 765 mplsXCExtTable has the same index values as the entry in 766 the mplsXCTable. 768 9.1.7. Forward direction mplsXCExtEntry 770 In mplsXCExtTable (0x01, 0x00000000, 0x00000001) 771 { 772 -- Back pointer from XC table to Tunnel table 773 mplsXCExtTunnelPointer = mplsTunnelName.1.1.1.2 774 mplsXCExtOppositeDirXCPtr = 775 mplsXCLspId.4.0.0.0.1.4.0.0.0.1.1.0 776 } 778 9.1.8. Reverse direction mplsXCExtEntry 780 Next for the reverse direction: 782 In mplsXCExtTable (0x01, 0x00000001, 0x00000000) 783 { 784 -- Back pointer from XC table to Tunnel table 785 mplsXCExtTunnelPointer = mplsTunnelName.1.1.1.2 786 mplsXCExtOppositeDirXCPtr = 787 mplsXCLspId.4.0.0.0.1.1.0.4.0.0.0.1 788 } 790 9.2. Example of MPLS-TP static associated bidirectional tunnel setup 792 The MPLS-TP associated bidirectional tunnel is implemented by two 793 different unidirectional tunnels [Forward and Reverse LSPs] and these 794 are associated together using mplsTunnelExtTable. Two different 795 tunnel entries to provide the forward and reverse directions MAY be 796 used for co-routed bidirectional tunnels as well. 798 The following denotes the associated bidirectional forward tunnel 799 "head" entry: 801 9.2.1. Forward direction mplsTunnelEntry 803 In mplsTunnelTable: 805 { 806 mplsTunnelIndex = 1, 807 mplsTunnelInstance = 1, 808 -- Local map number created in mplsTunnelExtNodeConfigTable for 809 -- Ingress LSR-Id 810 mplsTunnelIngressLSRId = 1, 812 -- Local map number created in mplsTunnelExtNodeConfigTable for 813 -- Egress LSR-Id 814 mplsTunnelEgressLSRId = 2, 815 mplsTunnelName = "TP associated bidirectional 816 forward LSP", 817 mplsTunnelDescr = "East to West", 818 mplsTunnelIsIf = true (1), 819 -- RowPointer MUST point to the first accessible column 820 mplsTunnelXCPointer = 821 mplsXCLspId.4.0.0.0.1.1.0.4.0.0.0.1, 822 mplsTunnelSignallingProto = none (1), 823 mplsTunnelSetupPrio = 0, 824 mplsTunnelHoldingPrio = 0, 825 mplsTunnelSessionAttributes = 0, 826 mplsTunnelLocalProtectInUse = false (0), 827 -- RowPointer MUST point to the first accessible column 828 mplsTunnelResourcePointer = mplsTunnelResourceMaxRate.5, 829 mplsTunnelInstancePriority = 1, 830 mplsTunnelHopTableIndex = 1, 831 mplsTunnelIncludeAnyAffinity = 0, 833 mplsTunnelIncludeAllAffinity = 0, 834 mplsTunnelExcludeAnyAffinity = 0, 835 mplsTunnelRole = head (1), 836 -- Mandatory parameters needed to activate the row go here 837 mplsTunnelRowStatus = createAndGo (4) 838 } 840 9.2.2. Forward direction mplsTunnelExtEntry 842 For Associated bidirectional forward LSP, 843 In mplsTunnelExtTable: 844 { 845 mplsTunnelExtOppositeDirPtr = mplsTunnelName.2.1.2.1 846 -- Set both the Ingress and Egress LocalId objects to TRUE as 847 -- this tunnel entry uses the local identifiers. 848 mplsTunnelExtIngressLSRLocalIdValid = true, 849 mplsTunnelExtEgressLSRLocalIdValid = true 850 } 852 9.2.3. Forward direction mplsOutSegmentTable 854 For the forward direction. 856 In mplsOutSegmentTable: 857 { 858 mplsOutSegmentIndex = 0x0000001, 859 mplsOutSegmentInterface = 13, -- outgoing interface 860 mplsOutSegmentPushTopLabel = true(1), 861 mplsOutSegmentTopLabel = 22, -- outgoing label 862 -- RowPointer MUST point to the first accessible column. 863 mplsOutSegmentTrafficParamPtr = 0.0, 864 mplsOutSegmentRowStatus = createAndGo (4) 865 } 867 9.2.4. Forward direction mplsXCEntry 869 In mplsXCTable: 870 { 871 mplsXCIndex = 0x01, 872 mplsXCInSegmentIndex = 0x00000000, 873 mplsXCOutSegmentIndex = 0x00000001, 874 mplsXCLspId = 0x0102 -- unique ID 875 -- only a single outgoing label 876 mplsXCLabelStackIndex = 0x00, 877 mplsXCRowStatus = createAndGo(4) 879 } 881 9.2.5. Forward direction mplsXCExtEntry 883 In mplsXCExtTable (0x01, 0x00000000, 0x00000001) 884 { 885 -- Back pointer from XC table to Tunnel table 886 mplsXCExtTunnelPointer = mplsTunnelName.1.1.1.2 887 mplsXCExtOppositeDirXCPtr = 888 mplsXCLspId.4.0.0.0.1.4.0.0.0.1.1.0 889 } 891 9.2.6. Reverse direction mplsTunnelEntry 893 The following denotes the configured associated bidirectional reverse 894 tunnel "tail" entry: 896 In mplsTunnelTable: 898 { 899 mplsTunnelIndex = 2, 900 mplsTunnelInstance = 1, 901 -- Local map number created in mplsTunnelExtNodeConfigTable for 902 -- Ingress LSR-Id 903 mplsTunnelIngressLSRId = 2, 904 -- Local map number created in mplsTunnelExtNodeConfigTable for 905 -- Egress LSR-Id 906 mplsTunnelEgressLSRId = 1, 907 mplsTunnelName = "TP associated bidirectional 908 reverse LSP", 909 mplsTunnelDescr = "West to East", 910 mplsTunnelIsIf = true (1), 911 -- RowPointer MUST point to the first accessible column 912 mplsTunnelXCPointer = 913 mplsXCLspId.4.0.0.0.1.4.0.0.0.1.1.0, 914 mplsTunnelSignallingProto = none (1), 915 mplsTunnelSetupPrio = 0, 916 mplsTunnelHoldingPrio = 0, 917 mplsTunnelSessionAttributes = 0, 918 mplsTunnelLocalProtectInUse = false (0), 920 -- RowPointer MUST point to the first accessible column 921 mplsTunnelResourcePointer = mplsTunnelResourceMaxRate.5, 922 mplsTunnelInstancePriority = 1, 923 mplsTunnelHopTableIndex = 1, 924 mplsTunnelIncludeAnyAffinity = 0, 925 mplsTunnelIncludeAllAffinity = 0, 926 mplsTunnelExcludeAnyAffinity = 0, 927 mplsTunnelRole = head (1), 928 -- Mandatory parameters needed to activate the row go here 930 mplsTunnelRowStatus = createAndGo (4) 931 } 933 9.2.7. Reverse direction mplsTunnelExtEntry 935 For Associated bidirectional reverse LSP, 936 In mplsTunnelExtTable: 937 { 938 mplsTunnelExtOppositeDirPtr = mplsTunnelName.1.1.1.2 939 -- Set both the Ingress and Egress LocalId objects to TRUE as 940 -- this tunnel entry uses the local identifiers. 941 mplsTunnelExtIngressLSRLocalIdValid = true, 942 mplsTunnelExtEgressLSRLocalIdValid = true 943 } 945 9.2.8. Reverse direction mplsInSegmentEntry 947 We must next create the appropriate in-segment and out-segment 948 entries. These are done in [RFC3813] using the mplsInSegmentTable and 949 mplsOutSegmentTable. 951 In mplsInSegmentTable: 952 { 953 mplsInSegmentIndex = 0x0000001 954 mplsInSegmentLabel = 21, -- incoming label 955 mplsInSegmentNPop = 1, 956 mplsInSegmentInterface = 13, -- incoming interface 957 -- RowPointer MUST point to the first accessible column. 958 mplsInSegmentTrafficParamPtr = 0.0, 959 mplsInSegmentRowStatus = createAndGo (4) 960 } 962 Next, two cross-connect entries are created in the mplsXCTable of the 963 MPLS-LSR-STD-MIB [RFC3813], thereby associating the newly created 964 segments together. 966 9.2.9. Reverse direction mplsXCEntry 968 In mplsXCTable: 969 { 970 mplsXCIndex = 0x01, 971 mplsXCInSegmentIndex = 0x00000001, 972 mplsXCOutSegmentIndex = 0x00000000, 973 mplsXCLspId = 0x0102 -- unique ID 974 -- only a single outgoing label 975 mplsXCLabelStackIndex = 0x00, 977 mplsXCRowStatus = createAndGo(4) 978 } 980 This table entry is extended by entry in the 981 mplsXCExtTable. Note that the nature of the 'extends' 982 relationship is a sparse augmentation so that the entry in the 983 mplsXCExtTable has the same index values as the entry in 984 the mplsXCTable. 986 9.2.10. Reverse direction mplsXCExtEntry 988 Next for the reverse direction: 990 In mplsXCExtTable (0x01, 0x00000001, 0x00000000) 991 { 992 -- Back pointer from XC table to Tunnel table 993 mplsXCExtTunnelPointer = mplsTunnelName.2.1.2.1 994 mplsXCExtOppositeDirXCPtr = 995 mplsXCLspId.4.0.0.0.1.1.0.4.0.0.0.1 996 } 998 9.3. Example of MPLS-TP signaled co-routed bidirectional tunnel setup 1000 The following denotes the co-routed bidirectional tunnel "head" entry 1001 and in intermediate and tail-end nodes, the tunnel table and its 1002 associated tables are created by the local management subsystem 1003 (e.g. agent) when the MPLS TP tunnel is signaled successfully. 1005 Refer [RFC3812] and [RFC4802] for signaled tunnel table 1006 configuration examples. 1008 9.3.1. mplsTunnelEntry 1010 In mplsTunnelTable: 1012 { 1013 mplsTunnelIndex = 1, 1014 mplsTunnelInstance = 0, 1015 -- Local map number created in mplsTunnelExtNodeConfigTable for 1016 -- Ingress LSR-Id, for the intermediate and tail-end nodes, 1017 -- the local management entity is expected to pick a first available 1018 -- local identifier which is not used in mplsTunnelTable. 1019 mplsTunnelIngressLSRId = 1, 1021 -- Local map number created in mplsTunnelExtNodeConfigTable for 1022 -- Egress LSR-Id 1023 mplsTunnelEgressLSRId = 2, 1024 mplsTunnelName = "TP co-routed bidirectional LSP", 1025 mplsTunnelDescr = "East to West", 1026 mplsTunnelIsIf = true (1), 1028 -- RowPointer MUST point to the first accessible column 1029 mplsTunnelXCPointer = 1030 mplsXCLspId.4.0.0.0.1.1.0.4.0.0.0.1, 1031 mplsTunnelSignallingProto = none (1), 1032 mplsTunnelSetupPrio = 0, 1033 mplsTunnelHoldingPrio = 0, 1034 mplsTunnelSessionAttributes = 0, 1035 mplsTunnelLocalProtectInUse = false (0), 1036 -- RowPointer MUST point to the first accessible column 1037 mplsTunnelResourcePointer = mplsTunnelResourceMaxRate.5, 1038 mplsTunnelInstancePriority = 1, 1039 mplsTunnelHopTableIndex = 1, 1040 mplsTunnelIncludeAnyAffinity = 0, 1041 mplsTunnelIncludeAllAffinity = 0, 1042 mplsTunnelExcludeAnyAffinity = 0, 1043 mplsTunnelRole = head (1), 1044 -- Mandatory parameters needed to activate the row go here 1045 mplsTunnelRowStatus = createAndGo (4) 1046 } 1048 9.3.2. mplsTunnelExtEntry 1050 -- An MPLS extension table 1051 In mplsTunnelExtTable: 1052 { 1053 -- This opposite direction tunnel pointer may point to 0.0 1054 -- if co-routed bidirectional tunnel is managed by single tunnel 1055 -- entry 1056 mplsTunnelExtOppositeDirTnlPtr = 0.0 1057 -- Set both the Ingress and Egress LocalId objects to TRUE as 1058 -- this tunnel entry uses the local identifiers. 1059 mplsTunnelExtIngressLSRLocalIdValid = true, 1060 mplsTunnelExtEgressLSRLocalIdValid = true 1061 } 1063 We must next create the appropriate in-segment and out-segment 1064 entries. These are done in [RFC3813] using the mplsInSegmentTable and 1065 mplsOutSegmentTable. 1067 9.3.3. Forward direction mplsOutSegmentEntry 1069 The forward direction mplsOutSegmentTable will be populated 1070 automatically based on the information received from the signaling 1071 protocol. 1073 9.3.4. Reverse direction mplsInSegmentEntry 1075 The reverse direction mplsOutSegmentTable will be populated 1076 automatically based on the information received from the signaling 1077 protocol. 1079 Next, two cross-connect entries are created in the mplsXCTable of the 1080 MPLS-LSR-STD-MIB [RFC3813], thereby associating the newly created 1081 segments together. 1083 9.3.5. Forward direction mplsXCEntry 1085 The forward direction mplsXCEntry will be populated as soon as the 1086 forward path label information is available. 1088 9.3.6. Reverse direction mplsXCEntry 1090 The reverse direction mplsXCEntry will be populated as soon as the 1091 reverse path label information is available. 1093 This table entry is extended by entry in the mplsXCExtTable. Note 1094 that the nature of the 'extends' relationship is a sparse 1095 augmentation so that the entry in the mplsXCExtTable has the same 1096 index values as the entry in the mplsXCTable. 1098 9.3.7. Forward direction mplsXCExtEntry 1100 Once the forward path information is negotiated using signaling 1101 protocol, the forward direction mplsXCExtEntry will be created for 1102 associating the opposite direction XC entry and tunnel table entry. 1104 9.3.8. Reverse direction mplsXCExtEntry 1106 Once the reverse path information is negotiated using signaling 1107 protocol, the reverse direction mplsXCExtEntry will be created for 1108 associating the opposite direction XC entry and tunnel table entry. 1110 10. MPLS Textual Convention Extension MIB definitions 1112 MPLS-TC-EXT-STD-MIB DEFINITIONS ::= BEGIN 1114 IMPORTS 1115 MODULE-IDENTITY, Unsigned32 1116 FROM SNMPv2-SMI -- [RFC2578] 1118 TEXTUAL-CONVENTION 1119 FROM SNMPv2-TC -- [RFC2579] 1121 mplsStdMIB 1122 FROM MPLS-TC-STD-MIB -- [RFC3811] 1124 ; 1126 mplsTcExtStdMIB MODULE-IDENTITY 1128 LAST-UPDATED 1129 "201412180000Z" -- December 18, 2014 1130 ORGANIZATION 1131 "Multiprotocol Label Switching (MPLS) Working Group" 1132 CONTACT-INFO 1133 " 1134 Venkatesan Mahalingam 1135 Dell Inc, 1136 5450 Great America Parkway, 1137 Santa Clara, CA 95054, USA 1138 Email: venkat.mahalingams@gmail.com 1140 Kannan KV Sampath 1141 Redeem, 1142 India 1143 Email: kannankvs@gmail.com 1145 Sam Aldrin 1146 Huawei Technologies 1147 2330 Central Express Way, 1148 Santa Clara, CA 95051, USA 1150 Email: aldrin.ietf@gmail.com 1152 Thomas D. Nadeau 1153 Email: tnadeau@lucidvision.com 1154 " 1155 DESCRIPTION 1156 "Copyright (c) 2014 IETF Trust and the persons identified 1157 as the document authors. All rights reserved. 1159 This MIB module contains Textual Conventions for LSPs of MPLS 1160 based transport networks." 1162 -- Revision history. 1164 REVISION 1166 "201412180000Z" -- December 18, 2014 1167 DESCRIPTION 1168 "MPLS Textual Convention Extensions" 1170 ::= { mplsStdMIB www } -- www to be replaced with correct value 1172 MplsGlobalId ::= TEXTUAL-CONVENTION 1173 STATUS current 1174 DESCRIPTION 1175 "This object contains the Textual Convention for IP based 1176 operator unique identifier (Global_ID), the Global_ID can 1177 contain the 2-octet or 4-octet value of the operator's 1178 Autonomous System Number (ASN). 1180 When the Global_ID is derived from a 2-octet AS number, 1181 the two high-order octets of this 4-octet identifier 1182 MUST be set to zero(0x00). Further ASN 0 is reserved. 1183 The size of the Global_ID string MUST be zero if 1184 the Global_ID is invalid. 1186 Note that a Global_ID of zero is limited to entities 1187 contained within a single operator and MUST NOT be used 1188 across an Network-to-Network Interface (NNI). A non-zero 1189 Global_ID MUST be derived from an ASN owned by 1190 the operator." 1191 REFERENCE 1192 "MPLS Transport Profile (MPLS-TP) Identifiers, [RFC6370] 1193 Section 3" 1194 SYNTAX OCTET STRING (SIZE (4)) 1196 MplsCcId ::= TEXTUAL-CONVENTION 1197 STATUS current 1198 DESCRIPTION 1199 "The CC (Country Code) is a string of two characters, each 1200 being an uppercase Basic Latin alphabetic (i.e., A-Z). 1201 The characters are encoded using ITU-T Recommendation T.50. 1202 The size of the CC string MUST be zero if the CC identifier 1203 is invalid." 1204 REFERENCE 1205 "MPLS-TP Identifiers Following ITU-T Conventions, 1206 RFC 6923, Section 3. 1207 International Reference Alphabet (IRA) (Formerly 1208 International Alphabet No. 5 or IA5) - Information 1209 technology - 7-bit coded character set for information 1210 exchange, ITU-T Recommendation T.50, September 1992. " 1211 SYNTAX OCTET STRING (SIZE (0|2)) 1213 MplsIccId ::= TEXTUAL-CONVENTION 1214 STATUS current 1215 DESCRIPTION 1216 "The ICC is a string of one to six characters, each 1217 an upper case Basic Latin alphabetic (i.e., A-Z) or 1218 numeric (i.e., 0-9). The characters are encoded 1219 using ITU-T Recommendation T.50. The size of 1220 the ICC string MUST be zero if the ICC identifier 1221 is invalid." 1222 REFERENCE 1223 "MPLS-TP Identifiers Following ITU-T Conventions, 1224 RFC6923, Section 3. 1225 International Reference Alphabet (IRA) (Formerly 1226 International Alphabet No. 5 or IA5) - Information 1227 technology - 7-bit coded character set for information 1228 exchange, ITU-T Recommendation T.50, September 1992. " 1229 SYNTAX OCTET STRING (SIZE (0|1..6)) 1231 MplsNodeId ::= TEXTUAL-CONVENTION 1232 DISPLAY-HINT "d" 1233 STATUS current 1234 DESCRIPTION 1235 "The Node_ID is assigned within the scope of 1236 the Global_ID/ICC_Operator_ID. 1238 When IPv4 addresses are in use, the value of this object 1239 can be derived from the LSR's IPv4 loop back address. 1240 When IPv6 addresses are in use, the value of this object 1241 can be a 32-bit value unique within the scope of 1242 a Global_ID. 1244 Note that, when IP reachability is not needed, the 32-bit 1245 Node_ID is not required to have any association 1246 with the IPv4 address space. The value of 0 indicates 1247 the invalid Node identifier." 1248 REFERENCE 1249 "MPLS Transport Profile (MPLS-TP) Identifiers, [RFC6370] 1250 Section 4" 1251 SYNTAX Unsigned32 (0|1..4294967295) 1253 -- MPLS-TC-EXT-STD-MIB module ends 1254 END 1256 11. MPLS Identifier MIB definitions 1258 MPLS-ID-STD-MIB DEFINITIONS ::= BEGIN 1260 IMPORTS 1261 MODULE-IDENTITY, OBJECT-TYPE 1262 FROM SNMPv2-SMI -- [RFC2578] 1263 MODULE-COMPLIANCE, OBJECT-GROUP 1264 FROM SNMPv2-CONF -- [RFC2580] 1265 mplsStdMIB 1266 FROM MPLS-TC-STD-MIB -- [RFC3811] 1267 MplsGlobalId, MplsCcId, MplsIccId, MplsNodeId 1268 FROM MPLS-TC-EXT-STD-MIB 1269 ; 1271 mplsIdStdMIB MODULE-IDENTITY 1272 LAST-UPDATED 1273 "201412120000Z" -- December 12, 2014 1274 ORGANIZATION 1275 "Multiprotocol Label Switching (MPLS) Working Group" 1277 CONTACT-INFO 1278 " 1279 Venkatesan Mahalingam 1280 Dell Inc, 1281 5450 Great America Parkway, 1282 Santa Clara, CA 95054, USA 1283 Email: venkat.mahalingams@gmail.com 1285 Kannan KV Sampath 1287 Redeem, 1288 India 1289 Email: kannankvs@gmail.com 1291 Sam Aldrin 1292 Huawei Technologies 1293 2330 Central Express Way, 1294 Santa Clara, CA 95051, USA 1295 Email: aldrin.ietf@gmail.com 1297 Thomas D. Nadeau 1298 Email: tnadeau@lucidvision.com 1299 " 1300 DESCRIPTION 1301 "Copyright (c) 2014 IETF Trust and the persons identified 1302 as the document authors. All rights reserved. 1304 This MIB module contains generic object definitions for 1305 MPLS Traffic Engineering in transport networks." 1307 -- Revision history. 1309 REVISION 1310 "201412120000Z" -- December 12, 2014 1311 DESCRIPTION 1312 "This MIB modules defines the MIB objects for MPLS-TP 1313 identifiers" 1315 ::= { mplsStdMIB xxx } -- xxx to be replaced with correct value 1317 -- notifications 1318 mplsIdNotifications OBJECT IDENTIFIER ::= { mplsIdStdMIB 0 } 1319 -- tables, scalars 1320 mplsIdObjects OBJECT IDENTIFIER ::= { mplsIdStdMIB 1 } 1321 -- conformance 1322 mplsIdConformance OBJECT IDENTIFIER ::= { mplsIdStdMIB 2 } 1324 -- MPLS common objects 1326 mplsIdGlobalId OBJECT-TYPE 1327 SYNTAX MplsGlobalId 1328 MAX-ACCESS read-write 1329 STATUS current 1330 DESCRIPTION 1331 "This object allows the operator or service provider to 1332 assign a unique operator identifier also called MPLS-TP 1333 Global_ID. 1334 If this value is used in mplsTunnelExtNodeConfigGlobalId 1335 for mapping Global_ID::Node_ID with the local identifier 1336 then this object value MUST NOT be changed." 1337 ::= { mplsIdObjects 1 } 1339 mplsIdNodeId OBJECT-TYPE 1340 SYNTAX MplsNodeId 1341 MAX-ACCESS read-write 1342 STATUS current 1343 DESCRIPTION 1344 "This object allows the operator or service provider to 1345 assign a unique MPLS-TP Node_ID. The Node_ID is assigned 1346 within the scope of the Global_ID/ICC_Operator_ID. 1347 If this value is used in mplsTunnelExtNodeConfigNodeId 1348 for mapping Global_ID::Node_ID with the local identifier 1349 then this object value SHOULD NOT be changed. 1350 If this value is used in mplsTunnelExtNodeConfigNodeId 1351 for mapping ICC_Operator_ID::Node_ID with the local 1352 identifier then this object value MUST NOT be changed." 1353 ::= { mplsIdObjects 2 } 1355 mplsIdCc OBJECT-TYPE 1356 SYNTAX MplsCcId 1357 MAX-ACCESS read-write 1358 STATUS current 1359 DESCRIPTION 1360 "This object allows the operator or service provider to 1361 assign a Country Code (CC) to the node. Global 1362 uniqueness of ICC is assured by concatenating the ICC 1363 with a Country Code (CC). 1364 If this value is used in mplsTunnelExtNodeConfigCcId 1365 for mapping ICC_Operator_ID::Node_ID with the local 1366 identifier then this object value MUST NOT be changed." 1367 REFERENCE 1368 "MPLS-TP Identifiers Following ITU-T Conventions, 1369 [RFC6923] Section 3" 1370 ::= { mplsIdObjects 3 } 1372 mplsIdIcc OBJECT-TYPE 1373 SYNTAX MplsIccId 1374 MAX-ACCESS read-write 1375 STATUS current 1376 DESCRIPTION 1377 "This object allows the operator or service provider to 1378 assign a unique MPLS-TP ITU-T Carrier Code (ICC) to 1379 the node. Together, the CC and the ICC form 1380 the ICC_Operator_ID as CC::ICC. 1381 If this value is used in mplsTunnelExtNodeConfigIccId 1382 for mapping ICC_Operator_ID::Node_ID with the local 1383 identifier then this object value MUST NOT be changed." 1384 REFERENCE 1385 "MPLS-TP Identifiers Following ITU-T Conventions, 1386 [RFC6923] Section 3" 1388 ::= { mplsIdObjects 4 } 1390 -- Module compliance. 1392 mplsIdCompliances 1393 OBJECT IDENTIFIER ::= { mplsIdConformance 1 } 1395 mplsIdGroups 1396 OBJECT IDENTIFIER ::= { mplsIdConformance 2 } 1398 -- Compliance requirement for fully compliant implementations. 1400 mplsIdModuleFullCompliance MODULE-COMPLIANCE 1401 STATUS current 1402 DESCRIPTION 1403 "Compliance statement for agents that provide full 1404 support of the MPLS-ID-STD-MIB module." 1406 MODULE -- this module 1408 -- The mandatory group has to be implemented by all LSRs that 1409 -- originate, terminate, or act as transit for MPLS-TP tunnels. 1411 GROUP mplsIdIpOperatorGroup 1412 DESCRIPTION 1413 "This group is mandatory for devices which support 1414 IP based identifier configuration." 1416 GROUP mplsIdIccOperatorGroup 1417 DESCRIPTION 1418 "This group is mandatory for devices which support 1419 ICC based identifier configuration." 1421 ::= { mplsIdCompliances 1 } 1423 -- Compliance requirement for read-only implementations. 1425 mplsIdModuleReadOnlyCompliance MODULE-COMPLIANCE 1426 STATUS current 1427 DESCRIPTION 1428 "Compliance statement for agents that only provide 1429 read-only support for the MPLS-ID-STD-MIB module." 1431 MODULE -- this module 1433 GROUP mplsIdIpOperatorGroup 1434 DESCRIPTION 1435 "This group is mandatory for devices which support 1436 IP based identifier configuration." 1438 GROUP mplsIdIccOperatorGroup 1439 DESCRIPTION 1440 "This group is mandatory for devices which support 1441 ICC based identifier configuration." 1443 OBJECT mplsIdGlobalId 1444 MIN-ACCESS read-only 1445 DESCRIPTION 1446 "Write access is not required." 1448 OBJECT mplsIdNodeId 1449 MIN-ACCESS read-only 1450 DESCRIPTION 1451 "Write access is not required." 1453 OBJECT mplsIdCc 1454 MIN-ACCESS read-only 1455 DESCRIPTION 1456 "Write access is not required." 1458 OBJECT mplsIdIcc 1459 MIN-ACCESS read-only 1460 DESCRIPTION 1461 "Write access is not required." 1463 ::= { mplsIdCompliances 2 } 1465 -- Units of conformance. 1467 mplsIdIpOperatorGroup OBJECT-GROUP 1468 OBJECTS { mplsIdGlobalId, 1469 mplsIdNodeId 1470 } 1471 STATUS current 1472 DESCRIPTION 1473 "The objects in this group are optional for ICC based 1474 node." 1475 ::= { mplsIdGroups 1 } 1477 mplsIdIccOperatorGroup OBJECT-GROUP 1478 OBJECTS { mplsIdNodeId, 1479 mplsIdCc, 1480 mplsIdIcc 1482 } 1483 STATUS current 1484 DESCRIPTION 1485 "The objects in this group are optional for IP based 1486 node." 1487 ::= { mplsIdGroups 2 } 1489 -- MPLS-ID-STD-MIB module ends 1490 END 1492 12. MPLS LSR Extension MIB definitions 1494 MPLS-LSR-EXT-STD-MIB DEFINITIONS ::= BEGIN 1496 IMPORTS 1497 MODULE-IDENTITY, OBJECT-TYPE 1498 FROM SNMPv2-SMI -- [RFC2578] 1499 MODULE-COMPLIANCE, OBJECT-GROUP 1500 FROM SNMPv2-CONF -- [RFC2580] 1501 mplsStdMIB 1502 FROM MPLS-TC-STD-MIB -- [RFC3811] 1503 RowPointer 1504 FROM SNMPv2-TC -- [RFC2579] 1505 mplsXCIndex, mplsXCInSegmentIndex, mplsXCOutSegmentIndex, 1506 mplsInterfaceGroup, mplsInSegmentGroup, mplsOutSegmentGroup, 1507 mplsXCGroup, mplsLsrNotificationGroup 1508 FROM MPLS-LSR-STD-MIB; -- [RFC3813] 1510 mplsLsrExtStdMIB MODULE-IDENTITY 1511 LAST-UPDATED 1512 "201412120000Z" -- December 12, 2014 1513 ORGANIZATION 1514 "Multiprotocol Label Switching (MPLS) Working Group" 1515 CONTACT-INFO 1516 " 1517 Venkatesan Mahalingam 1518 Dell Inc, 1519 5450 Great America Parkway, 1520 Santa Clara, CA 95054, USA 1521 Email: venkat.mahalingams@gmail.com 1523 Kannan KV Sampath 1524 Redeem, 1525 India 1526 Email: kannankvs@gmail.com 1528 Sam Aldrin 1529 Huawei Technologies 1530 2330 Central Express Way, 1531 Santa Clara, CA 95051, USA 1533 Email: aldrin.ietf@gmail.com 1535 Thomas D. Nadeau 1536 Email: tnadeau@lucidvision.com 1537 " 1538 DESCRIPTION 1539 "Copyright (c) 2014 IETF Trust and the persons identified 1540 as the document authors. All rights reserved. 1542 This MIB module contains generic object definitions for 1543 MPLS LSR in transport networks." 1545 -- Revision history. 1547 REVISION 1548 "201412120000Z" -- December 12, 2014 1549 DESCRIPTION 1550 "MPLS LSR specific MIB objects extension" 1552 ::= { mplsStdMIB yyy } -- yyy to be replaced with correct value 1554 -- notifications 1555 mplsLsrExtNotifications OBJECT IDENTIFIER ::= { mplsLsrExtStdMIB 0 } 1557 -- tables, scalars 1558 mplsLsrExtObjects OBJECT IDENTIFIER 1559 ::= { mplsLsrExtStdMIB 1 } 1560 -- conformance 1561 mplsLsrExtConformance OBJECT IDENTIFIER 1562 ::= { mplsLsrExtStdMIB 2 } 1564 -- MPLS LSR common objects 1565 mplsXCExtTable OBJECT-TYPE 1566 SYNTAX SEQUENCE OF MplsXCExtEntry 1567 MAX-ACCESS not-accessible 1568 STATUS current 1569 DESCRIPTION 1570 "This table sparse augments the mplsXCTable of 1571 MPLS-LSR-STD-MIB [RFC3813] to provide MPLS-TP specific 1572 information about associated tunnel information" 1573 REFERENCE 1574 "1. Multiprotocol Label Switching (MPLS) Label Switching 1575 Router (LSR) Management Information Base (MIB), RFC 3813." 1576 ::= { mplsLsrExtObjects 1 } 1577 mplsXCExtEntry OBJECT-TYPE 1578 SYNTAX MplsXCExtEntry 1579 MAX-ACCESS not-accessible 1581 STATUS current 1582 DESCRIPTION 1584 "An entry in this table sparsely extends the cross connect 1585 information represented by an entry in 1586 the mplsXCTable in MPLS-LSR-STD-MIB [RFC3813] through 1587 a sparse augmentation. An entry can be created by 1588 a network operator via SNMP SET commands, or in 1589 response to signaling protocol events." 1590 REFERENCE 1591 "1. Multiprotocol Label Switching (MPLS) Label Switching 1592 Router (LSR) Management Information Base (MIB), RFC 3813." 1594 INDEX { mplsXCIndex, mplsXCInSegmentIndex, 1595 mplsXCOutSegmentIndex } 1596 ::= { mplsXCExtTable 1 } 1598 MplsXCExtEntry ::= SEQUENCE { 1599 mplsXCExtTunnelPointer RowPointer, 1600 mplsXCExtOppositeDirXCPtr RowPointer 1601 } 1603 mplsXCExtTunnelPointer OBJECT-TYPE 1604 SYNTAX RowPointer 1605 MAX-ACCESS read-only 1606 STATUS current 1607 DESCRIPTION 1608 "This read-only object indicates the back pointer to 1609 the tunnel entry segment. 1610 The only valid value for Tunnel Pointer is 1611 mplsTunnelTable entry." 1612 REFERENCE 1613 "1. Multiprotocol Label Switching (MPLS) Label Switching 1614 Router (LSR) Management Information Base (MIB), RFC 3813." 1615 ::= { mplsXCExtEntry 1 } 1617 mplsXCExtOppositeDirXCPtr OBJECT-TYPE 1618 SYNTAX RowPointer 1619 MAX-ACCESS read-create 1620 STATUS current 1621 DESCRIPTION 1622 "This object indicates the pointer to the opposite 1623 direction XC entry. This object cannot be modified if 1624 mplsXCRowStatus for the corresponding entry in the 1625 mplsXCTable is active(1). If this pointer is not set or 1626 removed, mplsXCOperStatus should be set to down(2)." 1627 REFERENCE 1628 "1. Multiprotocol Label Switching (MPLS) Label Switching 1629 Router (LSR) Management Information Base (MIB), RFC 3813." 1630 ::= { mplsXCExtEntry 2 } 1632 mplsLsrExtCompliances 1633 OBJECT IDENTIFIER ::= { mplsLsrExtConformance 1 } 1635 mplsLsrExtGroups 1636 OBJECT IDENTIFIER ::= { mplsLsrExtConformance 2 } 1638 -- Compliance requirement for fully compliant implementations. 1640 mplsLsrExtModuleFullCompliance MODULE-COMPLIANCE 1641 STATUS current 1642 DESCRIPTION 1643 "Compliance statement for agents that provide full support 1644 for MPLS-LSR-EXT-STD-MIB. 1645 The mandatory group has to be implemented by all LSRs 1646 that originate, terminate, or act as transit for 1647 TE-LSPs/tunnels. 1648 In addition, depending on the type of tunnels supported, 1649 other groups become mandatory as explained below." 1651 MODULE MPLS-LSR-STD-MIB -- The MPLS-LSR-STD-MIB, RFC3813 1653 MANDATORY-GROUPS { 1654 mplsInSegmentGroup, 1655 mplsOutSegmentGroup, 1656 mplsXCGroup, 1657 mplsLsrNotificationGroup 1658 } 1660 MODULE -- this module 1662 MANDATORY-GROUPS { 1663 mplsXCExtGroup 1664 } 1666 ::= { mplsLsrExtCompliances 1 } 1668 -- Compliance requirement for implementations that provide 1669 -- read-only access. 1671 mplsLsrExtModuleReadOnlyCompliance MODULE-COMPLIANCE 1672 STATUS current 1673 DESCRIPTION 1674 "Compliance requirement for implementations that only 1675 provide read-only support for MPLS-LSR-EXT-STD-MIB. 1676 Such devices can then be monitored but cannot be 1677 configured using this MIB module." 1679 MODULE MPLS-LSR-STD-MIB 1681 MANDATORY-GROUPS { 1682 mplsInterfaceGroup, 1683 mplsInSegmentGroup, 1684 mplsOutSegmentGroup 1685 } 1687 MODULE -- this module 1689 GROUP mplsXCExtReadOnlyObjectsGroup 1690 DESCRIPTION 1691 "This group is mandatory for devices which support 1692 opposite direction XC configuration of tunnels." 1694 -- mplsXCExtTable 1695 OBJECT mplsXCExtOppositeDirXCPtr 1696 MIN-ACCESS read-only 1697 DESCRIPTION 1698 "Write access is not required. 1699 This object indicates the pointer to the opposite 1700 direction XC entry. The only valid value for XC 1701 Pointer is mplsXCTable entry." 1702 ::= { mplsLsrExtCompliances 2 } 1704 -- Units of conformance. 1706 mplsXCExtGroup OBJECT-GROUP 1707 OBJECTS { 1708 mplsXCExtTunnelPointer, 1709 mplsXCExtOppositeDirXCPtr 1710 } 1711 STATUS current 1712 DESCRIPTION 1713 "This object should be supported in order to access 1714 the tunnel entry from XC entry." 1715 ::= { mplsLsrExtGroups 1 } 1716 mplsXCExtReadOnlyObjectsGroup OBJECT-GROUP 1717 OBJECTS { 1718 mplsXCExtTunnelPointer, 1719 mplsXCExtOppositeDirXCPtr 1720 } 1721 STATUS current 1722 DESCRIPTION 1723 "This Object is needed to associate the opposite direction 1724 (forward/reverse) XC entry." 1725 ::= { mplsLsrExtGroups 2 } 1727 -- MPLS-LSR-EXT-STD-MIB module ends 1728 END 1730 13. MPLS Tunnel Extension MIB definitions 1732 MPLS-TE-EXT-STD-MIB DEFINITIONS ::= BEGIN 1734 IMPORTS 1735 MODULE-IDENTITY, OBJECT-TYPE 1736 FROM SNMPv2-SMI -- [RFC2578] 1737 MODULE-COMPLIANCE, OBJECT-GROUP 1738 FROM SNMPv2-CONF -- [RFC2580] 1739 TruthValue, RowStatus, RowPointer, StorageType 1740 FROM SNMPv2-TC -- [RFC2579] 1741 IndexIntegerNextFree 1742 FROM DIFFSERV-MIB -- [RFC3289] 1743 MplsGlobalId, MplsNodeId, MplsCcId, MplsIccId 1744 FROM MPLS-TC-EXT-STD-MIB 1745 mplsStdMIB, MplsTunnelIndex, MplsTunnelInstanceIndex, 1746 MplsExtendedTunnelId 1747 FROM MPLS-TC-STD-MIB -- [RFC3811] 1748 mplsTunnelIndex, mplsTunnelInstance, mplsTunnelIngressLSRId, 1749 mplsTunnelEgressLSRId 1750 FROM MPLS-TE-STD-MIB -- [RFC3812] 1751 ; 1753 mplsTeExtStdMIB MODULE-IDENTITY 1754 LAST-UPDATED 1755 "201412120000Z" -- December 12, 2014 1756 ORGANIZATION 1757 "Multiprotocol Label Switching (MPLS) Working Group" 1758 CONTACT-INFO 1759 " 1760 Venkatesan Mahalingam 1761 Dell Inc, 1762 5450 Great America Parkway, 1763 Santa Clara, CA 95054, USA 1764 Email: venkat.mahalingams@gmail.com 1766 Kannan KV Sampath 1767 Redeem, 1768 India 1769 Email: kannankvs@gmail.com 1771 Sam Aldrin 1772 Huawei Technologies 1773 2330 Central Express Way, 1774 Santa Clara, CA 95051, USA 1775 Email: aldrin.ietf@gmail.com 1777 Thomas D. Nadeau 1778 Email: tnadeau@lucidvision.com 1779 " 1780 DESCRIPTION 1781 "Copyright (c) 2014 IETF Trust and the persons identified 1782 as the document authors. All rights reserved. 1784 This MIB module contains generic object definitions for 1785 MPLS Traffic Engineering in transport networks." 1787 -- Revision history. 1789 REVISION 1790 "201412120000Z" -- December 12, 2014 1792 DESCRIPTION 1793 "MPLS TE MIB objects extension" 1795 ::= { mplsStdMIB zzz } -- zzz to be replaced 1796 -- with correct value 1798 -- Top level components of this MIB module. 1800 -- tables, scalars 1801 mplsTeExtObjects OBJECT IDENTIFIER 1802 ::= { mplsTeExtStdMIB 0 } 1803 -- conformance 1804 mplsTeExtConformance OBJECT IDENTIFIER 1805 ::= { mplsTeExtStdMIB 1 } 1807 -- Start of MPLS Transport Profile Node configuration table 1808 mplsTunnelExtNodeConfigLocalIdNext OBJECT-TYPE 1809 SYNTAX IndexIntegerNextFree (0..16777215) 1810 MAX-ACCESS read-only 1811 STATUS current 1812 DESCRIPTION 1813 "This object contains an unused value for 1814 mplsTunnelExtNodeConfigLocalId, or a zero to indicate 1815 that none exist. Negative values are not allowed, 1816 as they do not correspond to valid values of 1817 mplsTunnelExtNodeConfigLocalId." 1818 ::= { mplsTeExtObjects 1 } 1820 mplsTunnelExtNodeConfigTable OBJECT-TYPE 1821 SYNTAX SEQUENCE OF MplsTunnelExtNodeConfigEntry 1822 MAX-ACCESS not-accessible 1823 STATUS current 1824 DESCRIPTION 1825 "This table allows the operator to map a node or 1826 LSR Identifier (IP compatible [Global_ID::Node_ID] or 1827 ICC based [ICC_Operator_ID::Node_ID]) with a local 1828 identifier. 1830 This table is created to reuse the existing 1831 mplsTunnelTable for MPLS based transport network 1832 tunnels also. 1834 Since the MPLS tunnel's Ingress/Egress LSR identifiers' 1835 size (Unsigned32) value is not compatible for 1836 MPLS-TP tunnel i.e. Global_ID::Node_ID of size 8 bytes and 1837 ICC_Operator_ID::Node_ID of size 12 bytes, there exists a 1838 need to map the Global_ID::Node_ID or ICC_Operator_ID::Node_ID 1839 with the local identifier of size 4 bytes (Unsigned32) value 1840 in order to index (Ingress/Egress LSR identifier) 1841 the existing mplsTunnelTable." 1843 ::= { mplsTeExtObjects 2 } 1845 mplsTunnelExtNodeConfigEntry OBJECT-TYPE 1846 SYNTAX MplsTunnelExtNodeConfigEntry 1847 MAX-ACCESS not-accessible 1848 STATUS current 1849 DESCRIPTION 1850 "An entry in this table represents a mapping 1851 identification for the operator or service provider 1852 with node or LSR. 1854 As per [RFC6370], IP compatible mapping is represented 1855 as Global_ID::Node_ID. 1857 As per [RFC6923], the CC and the ICC form the ICC_Operator_ID 1858 as CC::ICC and ICC compatible mapping is represented 1859 as ICC_Operator_ID::Node_ID. 1861 Note: Each entry in this table should have a unique 1862 [Global_ID and Node_ID] or [CC::ICC and Node_ID] combination." 1863 INDEX { mplsTunnelExtNodeConfigLocalId } 1864 ::= { mplsTunnelExtNodeConfigTable 1 } 1866 MplsTunnelExtNodeConfigEntry ::= SEQUENCE { 1867 mplsTunnelExtNodeConfigLocalId MplsExtendedTunnelId, 1868 mplsTunnelExtNodeConfigGlobalId MplsGlobalId, 1869 mplsTunnelExtNodeConfigCcId MplsCcId, 1870 mplsTunnelExtNodeConfigIccId MplsIccId, 1871 mplsTunnelExtNodeConfigNodeId MplsNodeId, 1872 mplsTunnelExtNodeConfigIccValid TruthValue, 1873 mplsTunnelExtNodeConfigStorageType StorageType, 1874 mplsTunnelExtNodeConfigRowStatus RowStatus 1876 } 1878 mplsTunnelExtNodeConfigLocalId OBJECT-TYPE 1879 SYNTAX MplsExtendedTunnelId 1880 MAX-ACCESS not-accessible 1881 STATUS current 1882 DESCRIPTION 1883 "This object is used in accommodating the bigger 1884 size Global_ID::Node_ID and/or the ICC_Operator_ID::Node_ID 1885 with lower size LSR identifier in order to index 1886 the mplsTunnelTable. 1888 The Local Identifier is configured between 0 and 16777215, 1889 as valid IP address range starts from 16777216(01.00.00.00). 1890 This range is chosen to determine whether the 1891 mplsTunnelTable's Ingress/Egress LSR-id is an IP address or 1892 Local identifier. If the configured range is not an 1893 IP address, the operator is expected to retrieve the 1894 complete information (Global_ID::Node_ID or 1895 ICC_Operator_ID::Node_ID) from 1896 mplsTunnelExtNodeConfigTable. 1897 This way, existing mplsTunnelTable is reused for 1898 bidirectional tunnel extensions for MPLS based transport 1899 networks. 1901 The Local Identifier allows the operator to assign 1902 a unique identifier to map Global_ID::Node_ID and/or 1903 ICC_Operator_ID::Node_ID. As this Local Identifier is unique 1904 within the node and the same syntax of this object can be 1905 used for MPLS-TE tunnel also, it is up to the operator/local 1906 management entity to choose non-conflicting value for 1907 indexing the MPLS and MPLS-TP tunnel entries." 1908 ::= { mplsTunnelExtNodeConfigEntry 1 } 1910 mplsTunnelExtNodeConfigGlobalId OBJECT-TYPE 1911 SYNTAX MplsGlobalId 1912 MAX-ACCESS read-create 1913 STATUS current 1914 DESCRIPTION 1915 "This object indicates the Global Operator Identifier. 1916 This object has no meaning when 1917 mplsTunnelExtNodeConfigIccValid is set true." 1918 REFERENCE 1919 "MPLS Transport Profile (MPLS-TP) Identifiers [RFC6370] 1920 Section 3." 1921 ::= { mplsTunnelExtNodeConfigEntry 2 } 1923 mplsTunnelExtNodeConfigCcId OBJECT-TYPE 1924 SYNTAX MplsCcId 1925 MAX-ACCESS read-create 1926 STATUS current 1927 DESCRIPTION 1928 "This object allows the operator or service provider to 1929 configure a unique MPLS-TP ITU-T Country Code (CC) 1930 either for Ingress ID or Egress ID. 1932 This object has no meaning when 1933 mplsTunnelExtNodeConfigIccValid is set false." 1934 REFERENCE 1935 "MPLS-TP Identifiers Following ITU-T Conventions, 1936 [RFC6923] Section 3" 1937 ::= { mplsTunnelExtNodeConfigEntry 3 } 1939 mplsTunnelExtNodeConfigIccId OBJECT-TYPE 1940 SYNTAX MplsIccId 1941 MAX-ACCESS read-create 1942 STATUS current 1943 DESCRIPTION 1944 "This object allows the operator or service provider to 1945 configure a unique MPLS-TP ITU-T Carrier Code (ICC) 1946 either for Ingress ID or Egress ID. 1948 This object has no meaning when 1949 mplsTunnelExtNodeConfigIccValid is set false." 1950 REFERENCE 1951 "MPLS-TP Identifiers Following ITU-T Conventions, 1953 [RFC6923] Section 3" 1954 ::= { mplsTunnelExtNodeConfigEntry 4 } 1956 mplsTunnelExtNodeConfigNodeId OBJECT-TYPE 1957 SYNTAX MplsNodeId 1958 MAX-ACCESS read-create 1959 STATUS current 1960 DESCRIPTION 1961 "This object indicates the Node_ID within the scope 1962 of a Global_ID or ICC_Operator_ID." 1963 REFERENCE 1964 "MPLS Transport Profile (MPLS-TP) Identifiers [RFC6370] 1965 Section 4." 1966 ::= { mplsTunnelExtNodeConfigEntry 5 } 1968 mplsTunnelExtNodeConfigIccValid OBJECT-TYPE 1969 SYNTAX TruthValue 1970 MAX-ACCESS read-create 1971 STATUS current 1972 DESCRIPTION 1973 "Denotes whether or not this entry uses 1974 mplsTunnelExtNodeConfigCcId, 1975 mplsTunnelExtNodeConfigIccId and 1976 mplsTunnelExtNodeConfigNodeId for mapping 1977 the ICC based identifiers with the local identifier. 1978 Note that if this variable is set to false then the 1979 mplsTunnelExtNodeConfigGlobalId and 1980 mplsTunnelExtNodeConfigNodeId objects should have 1981 the valid information." 1982 DEFVAL { false } 1983 ::= { mplsTunnelExtNodeConfigEntry 6 } 1985 mplsTunnelExtNodeConfigStorageType OBJECT-TYPE 1986 SYNTAX StorageType 1987 MAX-ACCESS read-create 1988 STATUS current 1989 DESCRIPTION 1990 "This variable indicates the storage type for this 1991 object. 1992 Conceptual rows having the value 'permanent' 1993 need not allow write-access to any columnar 1994 objects in the row." 1995 DEFVAL { volatile } 1996 ::= { mplsTunnelExtNodeConfigEntry 7 } 1998 mplsTunnelExtNodeConfigRowStatus OBJECT-TYPE 1999 SYNTAX RowStatus 2000 MAX-ACCESS read-create 2001 STATUS current 2002 DESCRIPTION 2003 "This object allows the operator to create, modify, 2004 and/or delete a row in this table." 2005 ::= { mplsTunnelExtNodeConfigEntry 8 } 2007 -- End of MPLS Transport Profile Node configuration table 2009 -- Start of MPLS Transport Profile Node IP compatible 2010 -- mapping table 2012 mplsTunnelExtNodeIpMapTable OBJECT-TYPE 2013 SYNTAX SEQUENCE OF MplsTunnelExtNodeIpMapEntry 2015 MAX-ACCESS not-accessible 2016 STATUS current 2017 DESCRIPTION 2018 "This read-only table allows the operator to retrieve 2019 the local identifier for a given Global_ID::Node_ID in an IP 2020 compatible operator environment. 2022 This table MAY be used in on-demand and/or proactive 2024 OAM operations to get the Ingress/Egress LSR identifier 2025 (Local Identifier) from Src-Global_Node_ID 2026 or Dst-Global_Node_ID. The Ingress and Egress LSR 2027 identifiers are used to retrieve the tunnel entry. 2029 This table returns nothing when the associated entry 2030 is not defined in mplsTunnelExtNodeConfigTable." 2031 ::= { mplsTeExtObjects 3 } 2033 mplsTunnelExtNodeIpMapEntry OBJECT-TYPE 2034 SYNTAX MplsTunnelExtNodeIpMapEntry 2035 MAX-ACCESS not-accessible 2036 STATUS current 2037 DESCRIPTION 2038 "An entry in this table represents a mapping of 2039 Global_ID::Node_ID with the local identifier. 2041 An entry in this table is created automatically when 2042 the Local identifier is associated with Global_ID and 2043 Node_Id in the mplsTunnelExtNodeConfigTable. 2045 Note: Each entry in this table should have a unique 2046 Global_ID and Node_ID combination." 2047 INDEX { mplsTunnelExtNodeIpMapGlobalId, 2048 mplsTunnelExtNodeIpMapNodeId 2049 } 2050 ::= { mplsTunnelExtNodeIpMapTable 1 } 2052 MplsTunnelExtNodeIpMapEntry ::= SEQUENCE { 2053 mplsTunnelExtNodeIpMapGlobalId MplsGlobalId, 2054 mplsTunnelExtNodeIpMapNodeId MplsNodeId, 2055 mplsTunnelExtNodeIpMapLocalId MplsExtendedTunnelId 2056 } 2058 mplsTunnelExtNodeIpMapGlobalId OBJECT-TYPE 2059 SYNTAX MplsGlobalId 2060 MAX-ACCESS not-accessible 2061 STATUS current 2062 DESCRIPTION 2063 "This object indicates the Global_ID." 2064 ::= { mplsTunnelExtNodeIpMapEntry 1 } 2066 mplsTunnelExtNodeIpMapNodeId OBJECT-TYPE 2067 SYNTAX MplsNodeId 2068 MAX-ACCESS not-accessible 2069 STATUS current 2070 DESCRIPTION 2071 "This object indicates the Node_ID within the 2073 operator." 2074 ::= { mplsTunnelExtNodeIpMapEntry 2 } 2076 mplsTunnelExtNodeIpMapLocalId OBJECT-TYPE 2077 SYNTAX MplsExtendedTunnelId 2078 MAX-ACCESS read-only 2079 STATUS current 2080 DESCRIPTION 2081 "This object contains an IP compatible local identifier 2082 which is defined in mplsTunnelExtNodeConfigTable." 2083 ::= { mplsTunnelExtNodeIpMapEntry 3 } 2085 -- End MPLS Transport Profile Node IP compatible table 2087 -- Start of MPLS Transport Profile Node ICC based table 2089 mplsTunnelExtNodeIccMapTable OBJECT-TYPE 2090 SYNTAX SEQUENCE OF MplsTunnelExtNodeIccMapEntry 2091 MAX-ACCESS not-accessible 2092 STATUS current 2093 DESCRIPTION 2094 "This read-only table allows the operator to retrieve 2095 the local identifier for a given ICC_Operator_ID::Node_ID 2096 in an ICC operator environment. 2098 This table MAY be used in on-demand and/or proactive 2099 OAM operations to get the Ingress/Egress LSR 2100 identifier (Local Identifier) from Src-ICC 2101 or Dst-ICC. The Ingress and Egress LSR 2102 identifiers are used to retrieve the tunnel entry. 2103 This table returns nothing when the associated entry 2104 is not defined in mplsTunnelExtNodeConfigTable." 2105 ::= { mplsTeExtObjects 4 } 2107 mplsTunnelExtNodeIccMapEntry OBJECT-TYPE 2108 SYNTAX MplsTunnelExtNodeIccMapEntry 2109 MAX-ACCESS not-accessible 2110 STATUS current 2111 DESCRIPTION 2112 "An entry in this table represents a mapping of 2113 ICC_Operator_ID::Node_ID with the local identifier. 2115 An entry in this table is created automatically when 2116 the Local identifier is associated with 2117 ICC_Operator_ID::Node_ID in 2118 the mplsTunnelExtNodeConfigTable." 2119 INDEX { mplsTunnelExtNodeIccMapCcId, 2120 mplsTunnelExtNodeIccMapIccId, 2121 mplsTunnelExtNodeIccMapNodeId } 2122 ::= { mplsTunnelExtNodeIccMapTable 1 } 2124 MplsTunnelExtNodeIccMapEntry ::= SEQUENCE { 2125 mplsTunnelExtNodeIccMapCcId MplsCcId, 2126 mplsTunnelExtNodeIccMapIccId MplsIccId, 2127 mplsTunnelExtNodeIccMapNodeId MplsNodeId, 2128 mplsTunnelExtNodeIccMapLocalId MplsExtendedTunnelId 2129 } 2131 mplsTunnelExtNodeIccMapCcId OBJECT-TYPE 2132 SYNTAX MplsCcId 2133 MAX-ACCESS not-accessible 2134 STATUS current 2135 DESCRIPTION 2136 "This object allows the operator or service provider to 2137 configure a unique MPLS-TP ITU-T Country Code (CC) 2138 either for Ingress or Egress LSR ID. 2140 The CC is a string of two alphabetic characters 2141 represented with upper case letters (i.e., A-Z)." 2142 ::= { mplsTunnelExtNodeIccMapEntry 1 } 2143 mplsTunnelExtNodeIccMapIccId OBJECT-TYPE 2144 SYNTAX MplsIccId 2145 MAX-ACCESS not-accessible 2146 STATUS current 2147 DESCRIPTION 2148 "This object allows the operator or service provider 2149 to configure a unique MPLS-TP ITU-T Carrier 2150 Code (ICC) either for Ingress or Egress LSR ID. 2152 The ICC is a string of one to six characters, each 2153 character being either alphabetic (i.e. A-Z) or 2154 numeric (i.e. 0-9) characters. Alphabetic characters 2155 in the ICC should be represented with upper case 2156 letters." 2157 ::= { mplsTunnelExtNodeIccMapEntry 2 } 2159 mplsTunnelExtNodeIccMapNodeId OBJECT-TYPE 2160 SYNTAX MplsNodeId 2161 MAX-ACCESS not-accessible 2162 STATUS current 2163 DESCRIPTION 2164 "This object indicates the Node_ID within the 2165 ICC based operator." 2166 ::= { mplsTunnelExtNodeIccMapEntry 3} 2168 mplsTunnelExtNodeIccMapLocalId OBJECT-TYPE 2169 SYNTAX MplsExtendedTunnelId 2170 MAX-ACCESS read-only 2171 STATUS current 2172 DESCRIPTION 2173 "This object contains an ICC based local identifier 2174 which is defined in mplsTunnelExtNodeConfigTable." 2175 ::= { mplsTunnelExtNodeIccMapEntry 4 } 2177 -- End MPLS Transport Profile Node ICC based table 2179 -- Start of MPLS Tunnel table extension 2181 mplsTunnelExtTable OBJECT-TYPE 2182 SYNTAX SEQUENCE OF MplsTunnelExtEntry 2183 MAX-ACCESS not-accessible 2184 STATUS current 2185 DESCRIPTION 2186 "This table represents extensions to mplsTunnelTable 2187 in order to support MPLS-TP tunnels. 2189 As per MPLS-TP Identifiers [RFC6370], LSP_ID for IP based 2190 co-routed bidirectional tunnel, 2191 A1-{Global_ID::Node_ID::Tunnel_Num}::Z9-{Global_ID:: 2192 Node_ID::Tunnel_Num}::LSP_Num 2194 LSP_ID for IP based associated bidirectional tunnel, 2195 A1-{Global_ID::Node_ID::Tunnel_Num::LSP_Num}:: 2196 Z9-{Global_ID::Node_ID::Tunnel_Num::LSP_Num} 2198 mplsTunnelTable is reused for forming the LSP_ID 2199 as follows, 2201 Source Tunnel_Num is mapped with mplsTunnelIndex, 2202 Source Node_ID is mapped with 2203 mplsTunnelIngressLSRId, Destination Node_ID is 2204 mapped with mplsTunnelEgressLSRId LSP_Num is mapped with 2205 mplsTunnelInstance. 2207 Source Global_ID::Node_ID and/or ICC_Operator_ID::Node_ID and 2208 Destination Global_ID::Node_ID and/or ICC_Operator_ID::Node-ID 2209 are maintained in the mplsTunnelExtNodeConfigTable and 2210 mplsTunnelExtNodeConfigLocalId is used to create an entry 2211 in mplsTunnelTable." 2212 REFERENCE 2213 "MPLS Transport Profile (MPLS-TP) Identifiers [RFC6370]." 2214 ::= { mplsTeExtObjects 5 } 2216 mplsTunnelExtEntry OBJECT-TYPE 2217 SYNTAX MplsTunnelExtEntry 2218 MAX-ACCESS not-accessible 2219 STATUS current 2220 DESCRIPTION 2221 "An entry in this table represents MPLS-TP 2222 specific additional tunnel configurations." 2223 INDEX { 2224 mplsTunnelIndex, 2225 mplsTunnelInstance, 2226 mplsTunnelIngressLSRId, 2227 mplsTunnelEgressLSRId 2228 } 2229 ::= { mplsTunnelExtTable 1 } 2231 MplsTunnelExtEntry ::= SEQUENCE { 2232 mplsTunnelExtOppositeDirPtr RowPointer, 2233 mplsTunnelExtOppositeDirTnlValid TruthValue, 2234 mplsTunnelExtDestTnlIndex MplsTunnelIndex, 2235 mplsTunnelExtDestTnlLspIndex MplsTunnelInstanceIndex, 2236 mplsTunnelExtDestTnlValid TruthValue, 2237 mplsTunnelExtIngressLSRLocalIdValid TruthValue, 2238 mplsTunnelExtEgressLSRLocalIdValid TruthValue 2240 } 2242 mplsTunnelExtOppositeDirPtr OBJECT-TYPE 2243 SYNTAX RowPointer 2244 MAX-ACCESS read-create 2245 STATUS current 2246 DESCRIPTION 2247 "This object points to the opposite direction tunnel entry." 2248 ::= { mplsTunnelExtEntry 1 } 2250 mplsTunnelExtOppositeDirTnlValid OBJECT-TYPE 2251 SYNTAX TruthValue 2252 MAX-ACCESS read-create 2253 STATUS current 2254 DESCRIPTION 2255 "Denotes whether or not this tunnel uses 2256 mplsTunnelExtOppositeDirPtr for identifying the opposite 2257 direction tunnel information. Note that if this variable 2258 is set to true then the mplsTunnelExtOppositeDirPtr should 2259 point to the first accessible row of the valid opposite 2260 direction tunnel." 2261 DEFVAL { false } 2262 ::= { mplsTunnelExtEntry 2 } 2264 mplsTunnelExtDestTnlIndex OBJECT-TYPE 2265 SYNTAX MplsTunnelIndex 2266 MAX-ACCESS read-create 2267 STATUS current 2268 DESCRIPTION 2269 "This object is applicable only for the bidirectional 2270 tunnel that has the forward and reverse LSPs in the 2271 different tunnel entries. 2273 The values of this object and the 2274 mplsTunnelExtDestTnlLspIndex object together can be used 2275 to identify an opposite direction LSP i.e. if the 2276 mplsTunnelIndex and mplsTunnelInstance hold the value 2277 for forward LSP, this object and 2278 mplsTunnelExtDestTnlLspIndex can be used to retrieve 2279 the reverse direction LSP and vice versa. 2281 This object and mplsTunnelExtDestTnlLspIndex values 2282 provide the first two indices of tunnel entry and 2283 the remaining indices can be derived as follows, 2284 the Ingress and Egress Identifiers should be 2285 swapped in order to index the other direction tunnel." 2286 ::= { mplsTunnelExtEntry 3 } 2288 mplsTunnelExtDestTnlLspIndex OBJECT-TYPE 2289 SYNTAX MplsTunnelInstanceIndex 2290 MAX-ACCESS read-create 2291 STATUS current 2292 DESCRIPTION 2293 "This object is applicable only for the bidirectional 2294 tunnel that has the forward and reverse LSPs in the 2295 different tunnel entries. This object holds 2296 the instance index of the opposite direction tunnel." 2297 ::= { mplsTunnelExtEntry 4 } 2299 mplsTunnelExtDestTnlValid OBJECT-TYPE 2300 SYNTAX TruthValue 2301 MAX-ACCESS read-create 2302 STATUS current 2303 DESCRIPTION 2304 "Denotes whether or not this tunnel uses 2305 mplsTunnelExtDestTnlIndex and 2306 mplsTunnelExtDestTnlLspIndex for identifying 2307 the opposite direction tunnel information. Note that if 2308 this variable is set to true then the 2309 mplsTunnelExtDestTnlIndex and 2310 mplsTunnelExtDestTnlLspIndex objects should have 2311 the valid opposite direction tunnel indices." 2312 DEFVAL { false } 2313 ::= { mplsTunnelExtEntry 5 } 2315 mplsTunnelExtIngressLSRLocalIdValid OBJECT-TYPE 2316 SYNTAX TruthValue 2317 MAX-ACCESS read-create 2318 STATUS current 2319 DESCRIPTION 2320 "This object denotes whether the mplsTunnelIngressLSRId 2321 contains the local value, which is used to reference 2322 the complete Ingress Global_ID::Node_ID or ICC_Operator_ID 2323 from the mplsTunnelExtNodeConfigTable. 2325 If this object is set to FALSE, mplsTunnelExtNodeConfigTable 2326 will not contain an entry to reference local identifier with 2327 Global_ID::Node_ID or ICC_Operator_ID::Node_ID value. 2329 This object is set to FALSE for legacy implementations like 2330 MPLS TE tunnels where mplsTunnelIngressId itself provides 2331 complete Ingress LSRId." 2332 REFERENCE 2333 "MPLS-TE-STD-MIB [RFC3812], Section 11. 2334 mplsTunnelIngressLSRId object in mplsTunnelTable." 2335 DEFVAL { false } 2336 ::= { mplsTunnelExtEntry 6 } 2338 mplsTunnelExtEgressLSRLocalIdValid OBJECT-TYPE 2339 SYNTAX TruthValue 2340 MAX-ACCESS read-create 2341 STATUS current 2342 DESCRIPTION 2343 "This object denotes whether the mplsTunnelEgressLSRId 2344 contains the local value, which is used to reference 2345 the complete Egress Global_ID::Node_ID or 2346 ICC_Operator_ID::Node_ID from 2347 the mplsTunnelExtNodeConfigTable. 2349 If this object is set to FALSE, mplsTunnelExtNodeConfigTable 2350 will not contain an entry to reference local identifier with 2351 Global_ID::Node_ID or ICC_Operator_ID::Node_ID value. 2353 This object is set to FALSE for legacy implementations like 2354 MPLS TE tunnels where mplsTunnelEgressId itself provides 2355 complete Egress LSRId." 2356 REFERENCE 2357 "MPLS-TE-STD-MIB [RFC3812], Section 11. 2358 mplsTunnelEgressLSRId object in mplsTunnelTable." 2359 DEFVAL { false } 2360 ::= { mplsTunnelExtEntry 7 } 2362 -- End of MPLS Tunnel table extension 2364 -- Module compliance. 2366 mplsTeExtCompliances 2367 OBJECT IDENTIFIER ::= { mplsTeExtConformance 1 } 2369 mplsTeExtGroups 2370 OBJECT IDENTIFIER ::= { mplsTeExtConformance 2 } 2372 -- Compliance requirement for fully compliant implementations. 2374 mplsTeExtModuleFullCompliance MODULE-COMPLIANCE 2375 STATUS current 2376 DESCRIPTION 2377 "Compliance statement for agents that provide full 2378 support the MPLS-TE-EXT-STD-MIB module." 2380 MODULE -- this module 2382 -- The mandatory group has to be implemented by all 2383 -- LSRs that originate/terminate MPLS-TP tunnels. 2385 -- In addition, depending on the type of tunnels 2386 -- supported, other groups become mandatory as 2388 -- explained below. 2390 MANDATORY-GROUPS { 2391 mplsTunnelExtGroup 2392 } 2394 GROUP mplsTunnelExtIpOperatorGroup 2395 DESCRIPTION 2396 "This group is mandatory for devices which support 2397 configuration of IP based identifier tunnels." 2399 GROUP mplsTunnelExtIccOperatorGroup 2400 DESCRIPTION 2401 "This group is mandatory for devices which support 2402 configuration of ICC based tunnels." 2404 ::= { mplsTeExtCompliances 1 } 2406 -- Compliance requirement for read-only implementations. 2408 mplsTeExtModuleReadOnlyCompliance MODULE-COMPLIANCE 2409 STATUS current 2410 DESCRIPTION 2411 "Compliance statement for agents that only provide 2412 read-only support for MPLS-TE-EXT-STD-MIB module." 2414 MODULE -- this module 2416 MANDATORY-GROUPS { 2417 mplsTunnelExtGroup 2418 } 2420 GROUP mplsTunnelExtIpOperatorGroup 2421 DESCRIPTION 2422 "This group is mandatory for devices which support 2423 configuration of IP based identifier tunnels." 2425 GROUP mplsTunnelExtIccOperatorGroup 2426 DESCRIPTION 2427 "This group is mandatory for devices which support 2428 configuration of ICC based tunnels." 2430 -- mplsTunnelExtTable 2432 OBJECT mplsTunnelExtOppositeDirPtr 2433 MIN-ACCESS read-only 2434 DESCRIPTION 2435 "Write access is not required." 2437 OBJECT mplsTunnelExtOppositeDirTnlValid 2438 MIN-ACCESS read-only 2439 DESCRIPTION 2440 "Write access is not required." 2442 OBJECT mplsTunnelExtDestTnlIndex 2443 MIN-ACCESS read-only 2444 DESCRIPTION 2445 "Write access is not required." 2447 OBJECT mplsTunnelExtDestTnlLspIndex 2448 MIN-ACCESS read-only 2449 DESCRIPTION 2450 "Write access is not required." 2452 OBJECT mplsTunnelExtDestTnlValid 2453 MIN-ACCESS read-only 2454 DESCRIPTION 2455 "Write access is not required." 2457 OBJECT mplsTunnelExtIngressLSRLocalIdValid 2458 MIN-ACCESS read-only 2459 DESCRIPTION 2460 "Write access is not required." 2462 OBJECT mplsTunnelExtEgressLSRLocalIdValid 2463 MIN-ACCESS read-only 2464 DESCRIPTION 2465 "Write access is not required." 2467 OBJECT mplsTunnelExtNodeConfigGlobalId 2468 MIN-ACCESS read-only 2469 DESCRIPTION 2470 "Write access is not required." 2472 OBJECT mplsTunnelExtNodeConfigNodeId 2473 MIN-ACCESS read-only 2474 DESCRIPTION 2475 "Write access is not required." 2477 OBJECT mplsTunnelExtNodeConfigStorageType 2478 MIN-ACCESS read-only 2479 DESCRIPTION 2480 "Write access is not required." 2482 OBJECT mplsTunnelExtNodeConfigRowStatus 2483 SYNTAX RowStatus { active(1) } 2484 MIN-ACCESS read-only 2485 DESCRIPTION 2486 "Write access is not required." 2488 OBJECT mplsTunnelExtNodeConfigCcId 2489 MIN-ACCESS read-only 2490 DESCRIPTION 2491 "Write access is not required." 2493 OBJECT mplsTunnelExtNodeConfigIccId 2494 MIN-ACCESS read-only 2495 DESCRIPTION 2496 "Write access is not required." 2498 OBJECT mplsTunnelExtNodeConfigIccValid 2499 MIN-ACCESS read-only 2500 DESCRIPTION 2501 "Write access is not required." 2503 ::= { mplsTeExtCompliances 2 } 2505 -- Units of conformance. 2507 mplsTunnelExtGroup OBJECT-GROUP 2508 OBJECTS { 2509 mplsTunnelExtOppositeDirPtr, 2510 mplsTunnelExtOppositeDirTnlValid, 2511 mplsTunnelExtDestTnlIndex, 2512 mplsTunnelExtDestTnlLspIndex, 2513 mplsTunnelExtDestTnlValid, 2514 mplsTunnelExtIngressLSRLocalIdValid, 2515 mplsTunnelExtEgressLSRLocalIdValid 2516 } 2518 STATUS current 2519 DESCRIPTION 2520 "Necessary, but not sufficient, set of objects to 2521 implement tunnels. In addition, depending on the 2522 operating environment, the following groups are 2523 mandatory." 2524 ::= { mplsTeExtGroups 1 } 2526 mplsTunnelExtIpOperatorGroup OBJECT-GROUP 2527 OBJECTS { mplsTunnelExtNodeConfigLocalIdNext, 2528 mplsTunnelExtNodeConfigGlobalId, 2529 mplsTunnelExtNodeConfigNodeId, 2530 mplsTunnelExtNodeIpMapLocalId, 2531 mplsTunnelExtNodeConfigStorageType, 2532 mplsTunnelExtNodeConfigRowStatus 2533 } 2534 STATUS current 2535 DESCRIPTION 2536 "Object(s) needed to implement IP compatible tunnels." 2537 ::= { mplsTeExtGroups 2 } 2539 mplsTunnelExtIccOperatorGroup OBJECT-GROUP 2540 OBJECTS { mplsTunnelExtNodeConfigLocalIdNext, 2541 mplsTunnelExtNodeConfigCcId, 2542 mplsTunnelExtNodeConfigIccId, 2543 mplsTunnelExtNodeConfigNodeId, 2544 mplsTunnelExtNodeConfigIccValid, 2545 mplsTunnelExtNodeIccMapLocalId, 2546 mplsTunnelExtNodeConfigStorageType, 2547 mplsTunnelExtNodeConfigRowStatus 2548 } 2549 STATUS current 2550 DESCRIPTION 2551 "Object(s) needed to implement ICC based tunnels." 2552 ::= { mplsTeExtGroups 3 } 2554 -- MPLS-TE-EXT-STD-MIB module ends 2555 END 2557 14. Security Consideration 2559 This document follows the security consideration mentioned in the 2560 section 12 of [RFC3812]. These security considerations are also 2561 applicable to the MIB objects and tables defined in this draft, which 2562 are identified as below. 2564 - The common objects mplsIdGlobalId, mplsIdNodeId, mplsIdCc, and 2565 mplsIdIcc are used to define the identity of an MPLS-TP node for 2566 OAM purposes. If write-access is allowed to these objects it 2567 offers the possibility for incorrect values to be entered that 2568 will confuse the information returned by OAM functions and 2569 possibly prevent OAM from operating correctly. Furthermore, 2570 there is the possibility of inducing one node to impersonate 2571 another with confusing results. 2573 - mplsTunnelExtNodeConfigTable, mplsTunnelExtTable and 2574 mplsXCExtTable collectively contain objects to provision MPLS-TP 2575 tunnels, tunnel hops, and tunnel resources. 2577 Some of the readable objects in this MIB module (i.e., objects with a 2578 MAX-ACCESS other than not-accessible) may be considered sensitive or 2579 vulnerable in some network environments. It is thus important to 2580 control even GET and/or NOTIFY access to these objects and possibly 2581 to even encrypt the values of these objects when sending them over 2582 the network via SNMP. These are the tables and objects and their 2583 sensitivity/vulnerability: 2585 - mplsTunnelExtNodeConfigTable, mplsTunnelExtTable, 2586 and mplsXCExtTable collectively show the MPLS-TP tunnel network 2587 topology characteristics. If an Administrator does not want to 2588 reveal this information, then these tables should be considered 2589 sensitive/vulnerable. 2591 SNMP versions prior to SNMPv3 did not include adequate security. Even 2592 if the network itself is secure (for example by using IPsec), there 2593 is no control as to who on the secure network is allowed to access 2594 and GET/SET (read/change/create/delete) the objects in this MIB 2595 module. 2597 Implementations SHOULD provide the security features described by the 2598 SNMPv3 framework (see [RFC3410]), and implementations claiming 2599 compliance to the SNMPv3 standard MUST include full support for 2600 authentication and privacy via the User-based Security Model (USM) 2601 [RFC3414] with the AES cipher algorithm [RFC3826]. Implementations 2602 MAY also provide support for the Transport Security Model (TSM) 2603 [RFC5591] in combination with a secure transport such as SSH 2604 [RFC5592] or TLS/DTLS [RFC6353]. 2606 Further, deployment of SNMP versions prior to SNMPv3 is NOT 2607 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 2608 enable cryptographic security. It is then a customer/operator 2609 responsibility to ensure that the SNMP entity giving access to an 2610 instance of this MIB module is properly configured to give access to 2611 the objects only to those principals (users) that have legitimate 2612 rights to indeed GET or SET (change/create/delete) them. 2614 15. IANA Considerations 2616 As described in [RFC4221], [RFC6639] and as requested in the MPLS-TC- 2617 STD-MIB [RFC3811], MPLS related standards track MIB modules should be 2618 rooted under the mplsStdMIB subtree. There are 4 MPLS MIB Modules 2619 contained in this document, each of the following "IANA 2620 Considerations" subsections requests IANA for a new assignment under 2621 the mplsStdMIB subtree. New assignments can only be made via a 2622 Standards Action as specified in [RFC5226]. 2624 15.1. IANA Considerations for MPLS-TC-EXT-STD-MIB 2626 IANA is requested to assign an OID { mplsStdMIB OID } to the MPLS-TC- 2627 EXT-STD-MIB module specified in this document. 2629 15.2. IANA Considerations for MPLS-ID-STD-MIB 2630 IANA is requested to assign an OID { mplsStdMIB OID } to the MPLS-ID- 2631 STD-MIB module specified in this document. 2633 15.3. IANA Considerations for MPLS-LSR-EXT-STD-MIB 2635 IANA is requested to assign an OID { mplsStdMIB OID } to the MPLS- 2636 LSR-EXT-STD-MIB module specified in this document. 2638 15.4. IANA Considerations for MPLS-TE-EXT-STD-MIB 2640 IANA is requested to assign an OID { mplsStdMIB OID } to the MPLS-TE- 2641 EXT-STD-MIB module specified in this document. 2643 16. References 2645 16.1. Normative References 2647 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 2648 Requirement Levels", BCP 14, RFC 2119, March 1997. 2650 [RFC2578] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 2651 "Structure of Management Information Version 2 (SMIv2)", 2652 STD 58, RFC 2578, April 1999. 2654 [RFC2579] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 2655 "Textual Conventions for SMIv2", STD 58, RFC 2579, April 2656 1999. 2658 [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 2659 "Conformance Statements for SMIv2", STD 58, RFC 2580, 2660 April 1999. 2662 [RFC3031] Rosen, E., Viswanathan, A., and R. Callon, "Multiprotocol 2663 Label Switching Architecture", RFC 3031, January 2001. 2665 [RFC3289] Baker, F., Chan, K., and A. Smith, "Management 2666 Information Base for the Differentiated Services 2667 Architecture", RFC 3289, May 2002. 2669 [RFC3811] Nadeau, T., Ed., and J. Cucchiara, Ed., "Definitions of 2670 Textual Conventions (TCs) for Multiprotocol Label 2671 Switching (MPLS) Management", RFC 3811, June 2004. 2673 [RFC3812] Srinivasan, C., Viswanathan, A., and T. Nadeau, 2674 "Multiprotocol Label Switching (MPLS) Traffic Engineering 2675 (TE) Management Information Base (MIB)", RFC 3812, June 2676 2004. 2678 [RFC3813] Srinivasan, C., Viswanathan, A., and T. Nadeau, 2679 "Multiprotocol Label Switching (MPLS) Label Switching 2680 (LSR) Router Management Information Base (MIB)", RFC 3813, 2681 June 2004. 2683 [RFC4802] Nadeau, T., Ed., and A. Farrel, Ed., "Generalized 2684 Multiprotocol Label Switching (GMPLS) Traffic Engineering 2685 Management Information Base", RFC 4802, February 2007. 2687 [RFC6370] Bocci, M., Swallow, G., and E. Gray, "MPLS Transport 2688 Profile (MPLS-TP) Identifiers", RFC 6370, September 2011. 2690 [RFC6923] Winter, R., Gray, E., Helvoort, H., and M. Betts, "MPLS-TP 2691 Identifiers Following ITU-T Conventions", RFC 6923, May 2692 2013 2694 [T.50] "International Reference Alphabet (IRA) (Formerly 2695 International Alphabet No. 5 or IA5) - Information 2696 technology - 7-bit coded character set for information 2697 exchange", ITU-T Recommendation T.50, September 1992. 2699 16.2. Informative References 2701 [RFC3410] J. Case, R. Mundy, D. pertain, B.Stewart, "Introduction 2702 and Applicability Statement for Internet Standard 2703 Management Framework", RFC 3410, December 2002. 2705 [RFC3414] Blumenthal, U. and B. Wijnen, "User-based Security Model 2706 (USM) for version 3 of the Simple Network Management 2707 Protocol (SNMPv3)", STD 62, RFC 3414, December 2002. 2709 [RFC3826] Blumenthal, U., F. Maino and K. McCloghrie, "The Advanced 2710 Encryption Standard (AES) Cipher Algorithm in the SNMP 2711 User-based Security Model", RFC 3826, June 2004. 2713 [RFC4221] Nadeau, T., Srinivasan, C., and A. Farrel, "Multiprotocol 2714 Label Switching (MPLS) Management Overview", RFC 4221, 2715 November 2005. 2717 [RFC5226] Narten, T. and H. Alvestrand., "Guidelines for Writing an 2718 IANA Considerations Section in RFCs", BCP 26, RFC 5226, 2719 May 2008. 2721 [RFC5591] Harrington, D. and W. Hardaker, "Transport Security Model 2722 for the Simple Network Management Protocol (SNMP)", 2723 RFC 5591, June 2009. 2725 [RFC5592] Harrington, D., Salowey, J., and W. Hardaker, "Secure 2726 Shell Transport Model for the Simple Network Management 2727 Protocol (SNMP)", RFC 5592, June 2009. 2729 [RFC5654] Niven-Jenkins, B., Ed., Brungard, D., Ed., Betts, M., 2730 Ed.,Sprecher, N., and S. Ueno, "Requirements of an MPLS 2731 Transport Profile", RFC 5654, September 2009. 2733 [RFC6353] Hardaker, W., "Transport Layer Security (TLS) Transport 2734 Model for the Simple Network Management Protocol (SNMP)", 2735 STD 78, RFC 6353, July 2011. 2737 [RFC6639] Venkatesan, M., King, D., "Multiprotocol Label Switching 2738 Transport Profile (MPLS-TP) MIB-Based Management 2739 Overview", RFC 6639, June 2012 2741 17. Acknowledgments 2743 The authors would like to thank Francesco Fondelli, Josh Littlefield, 2744 Agrahara Kiran Koushik, Metrri Jain, Muly Ilan, Randy Presuhn, Elwyn 2745 Davies, Tom Taylor and Pete Resnick for their valuable review and 2746 comments. A special thanks to Joan Cucchiara and Adrian Farrel for 2747 really getting the MIB modules into shape. 2749 18. Authors' Addresses 2751 Venkatesan Mahalingam 2752 Dell Inc. 2753 5450 Great America Parkway, 2754 Santa Clara, CA 95054, USA 2755 Email: venkat.mahalingams@gmail.com 2757 Sam Aldrin 2758 Huawei Technologies 2759 2330 Central Express Way, 2760 Santa Clara, CA 95051, USA 2761 Email: aldrin.ietf@gmail.com 2763 Thomas D. Nadeau 2764 Brocade 2765 Email: tnadeau@lucidvision.com 2767 Kannan KV Sampath 2768 Redeem 2769 India 2770 Email: kannankvs@gmail.com