idnits 2.17.1 draft-ietf-mpls-tp-te-mib-05.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 (January 14, 2013) is 4112 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) == Outdated reference: A later version (-08) exists of draft-ietf-mpls-tp-itu-t-identifiers-07 Summary: 0 errors (**), 0 flaws (~~), 2 warnings (==), 1 comment (--). 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: July 18, 2013 Kannan KV Sampath 6 Redeem 7 Sam K. Aldrin 8 Huawei Technologies 9 Thomas D. Nadeau 10 Juniper Networks 12 January 14, 2013 14 MPLS-TP Traffic Engineering (TE) Management Information Base (MIB) 15 draft-ietf-mpls-tp-te-mib-05.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 managed objects of Tunnels, Identifiers, 22 Label Switch Router and Textual conventions for Multiprotocol Label 23 Switching (MPLS) based Transport Profile (TP). 25 Status of this Memo 27 This Internet-Draft is submitted to IETF in full conformance with the 28 provisions of BCP 78 and BCP 79. 30 Internet-Drafts are working documents of the Internet Engineering 31 Task Force (IETF), its areas, and its working groups. Note that 32 other groups may also distribute working documents as Internet- 33 Drafts. 35 Internet-Drafts are draft documents valid for a maximum of six months 36 and may be updated, replaced, or obsoleted by other documents at any 37 time. It is inappropriate to use Internet-Drafts as reference 38 material or to cite them other than as "work in progress." 40 The list of current Internet-Drafts can be accessed at 41 http://www.ietf.org/ietf/1id-abstracts.txt. 43 The list of Internet-Draft Shadow Directories can be accessed at 44 http://www.ietf.org/shadow.html. 46 This Internet-Draft will expire on July 18, 2013. 48 Copyright and License Notice 50 Copyright (c) 2013 IETF Trust and the persons identified as the 51 document authors. All rights reserved. 53 This document is subject to BCP 78 and the IETF Trust's Legal 54 Provisions Relating to IETF Documents 55 (http://trustee.ietf.org/license-info) in effect on the date of 56 publication of this document. Please review these documents 57 carefully, as they describe your rights and restrictions with respect 58 to this document. Code Components extracted from this document must 59 include Simplified BSD License text as described in Section 4.e of 60 the Trust Legal Provisions and are provided without warranty as 61 described in the Simplified BSD License. 63 Table of Contents 65 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 66 2. The Internet-Standard Management Framework . . . . . . . . . . 4 67 3. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 68 3.1. Conventions used in this document . . . . . . . . . . . . . 4 69 3.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . 4 70 3.3. Acronyms . . . . . . . . . . . . . . . . . . . . . . . . . 5 71 4. Motivations . . . . . . . . . . . . . . . . . . . . . . . . . . 5 72 5. Feature List . . . . . . . . . . . . . . . . . . . . . . . . . 5 73 6. Brief description of MIB Objects . . . . . . . . . . . . . . . 5 74 6.1. mplsTunnelExtNodeConfigTable . . . . . . . . . . . . . . . 6 75 6.2. mplsTunnelExtNodeIpMapTable . . . . . . . . . . . . . . . . 6 76 6.3. mplsTunnelExtNodeIccMapTable . . . . . . . . . . . . . . . 7 77 6.4. mplsTunnelExtTable . . . . . . . . . . . . . . . . . . . . 7 78 6.5. mplsTunnelExtReversePerfTable . . . . . . . . . . . . . . . 7 79 7. MIB Module Interdependencies . . . . . . . . . . . . . . . . . 7 80 8. Dependencies between MIB Module Tables . . . . . . . . . . . . 9 81 9. Example of MPLS-TP Tunnel Setup . . . . . . . . . . . . . . . . 9 82 9.1. Example of MPLS-TP static co-routed bidirectional tunnel 83 setup . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 84 9.1.1. mplsTunnelEntry . . . . . . . . . . . . . . . . . . . . 10 85 9.1.2. mplsTunnelExtEntry . . . . . . . . . . . . . . . . . . 11 86 9.1.3. Forward direction mplsOutSegmentEntry . . . . . . . . . 12 87 9.1.4. Reverse direction mplsInSegmentEntry . . . . . . . . . 12 88 9.1.5. Forward direction mplsXCEntry . . . . . . . . . . . . . 12 89 9.1.6. Reverse direction mplsXCEntry . . . . . . . . . . . . . 13 90 9.1.7. Forward direction mplsXCExtEntry . . . . . . . . . . . 13 91 9.1.8. Reverse direction mplsXCExtEntry . . . . . . . . . . . 13 92 9.1.9. mplsTunnelExtReversePerfTable . . . . . . . . . . . . . 13 94 9.2. Example of MPLS-TP static associated bidirectional tunnel 95 setup . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 96 9.2.1. Forward direction mplsTunnelEntry . . . . . . . . . . . 14 97 9.2.2. Forward direction mplsTunnelExtEntry . . . . . . . . . 15 98 9.2.3. Forward direction mplsOutSegmentTable . . . . . . . . . 15 99 9.2.4. Forward direction mplsXCEntry . . . . . . . . . . . . . 15 100 9.2.5. Forward direction mplsXCExtEntry . . . . . . . . . . . 16 101 9.2.6. Reverse direction mplsTunnelEntry . . . . . . . . . . . 16 102 9.2.7. Reverse direction mplsTunnelExtEntry . . . . . . . . . 17 103 9.2.8. Reverse direction mplsInSegmentEntry . . . . . . . . . 17 104 9.2.9. Reverse direction mplsXCEntry . . . . . . . . . . . . . 17 105 9.2.10. Reverse direction mplsXCExtEntry . . . . . . . . . . . 18 106 9.3. Example of MPLS-TP signaling co-routed bidirectional 107 tunnel setup . . . . . . . . . . . . . . . . . . . . . . . 18 108 9.3.1. mplsTunnelEntry . . . . . . . . . . . . . . . . . . . . 18 109 9.3.2. mplsTunnelExtEntry . . . . . . . . . . . . . . . . . . 19 110 9.3.3. Forward direction mplsOutSegmentEntry . . . . . . . . . 19 111 9.3.4. Reverse direction mplsInSegmentEntry . . . . . . . . . 19 112 9.3.5. Forward direction mplsXCEntry . . . . . . . . . . . . . 20 113 9.3.6. Reverse direction mplsXCEntry . . . . . . . . . . . . . 20 114 9.3.7. Forward direction mplsXCExtEntry . . . . . . . . . . . 20 115 9.3.8. Reverse direction mplsXCExtEntry . . . . . . . . . . . 20 116 9.3.9. mplsTunnelExtReversePerfTable . . . . . . . . . . . . . 20 117 10. MPLS Textual Convention Extension MIB definitions . . . . . . 20 118 11. MPLS Identifier MIB definitions . . . . . . . . . . . . . . . 23 119 12. MPLS LSR Extension MIB definitions . . . . . . . . . . . . . . 27 120 13. MPLS Tunnel Extension MIB definitions . . . . . . . . . . . . 31 121 14. Security Consideration . . . . . . . . . . . . . . . . . . . . 49 122 15. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 50 123 16. References . . . . . . . . . . . . . . . . . . . . . . . . . . 50 124 16.1. Normative References . . . . . . . . . . . . . . . . . . . 50 125 16.2. Informative References . . . . . . . . . . . . . . . . . 50 126 17. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 51 127 18. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 51 129 1. Introduction 131 This memo defines a portion of the Management Information Base (MIB) for 132 use with network management protocols in the Internet community. In 133 particular, it describes managed objects of Tunnels, Identifiers, Label 134 Switch Router and Textual conventions for Multiprotocol Label Switching 135 (MPLS) based Transport Profile (TP). This draft extends the existing 136 MPLS MIB objects for both MPLS-TP and Non-MPLS-TP operations, so the 137 MPLS-TP name is not included in the MIB module name. 139 The existing Multiprotocol Label Switching (MPLS) Traffic Engineering 140 (TE) Management Information Base (MIB) [RFC3812] and Generalized 141 Multiprotocol Label Switching (GMPLS) Traffic Engineering Management 142 Information Base [RFC4802] do not support the transport network 143 requirements of NON-IP based management and static bidirectional 144 tunnels. This MIB module should be used in conjunction with [RFC3812] 145 and companion document [RFC3813] for MPLS based traffic engineering 146 configuration and management. 148 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 149 "SHOULD", "SHOULD NOT", "MAY", and "OPTIONAL" in this document are to be 150 interpreted as described in BCP 14, RFC2119. 152 2. The Internet-Standard Management Framework 154 For a detailed overview of the documents that describe the current 155 Internet-Standard Management Framework, please refer to section 7 of 156 RFC3410 [RFC3410]. 158 Managed objects are accessed via a virtual information store, termed the 159 Management Information Base or MIB. MIB objects are generally accessed 160 through the Simple Network Management Protocol (SNMP). Objects in the 161 MIB are defined using the mechanisms defined in the Structure of 162 Management Information (SMI). This memo specifies a MIB module that is 163 compliant to the SMIv2, which is described in STD 58, RFC2578, STD 58, 164 RFC2579 and STD58, RFC2580. 166 3. Overview 168 3.1. Conventions used in this document 170 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 171 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 172 document are to be interpreted as described in [RFC2119]. 174 3.2. Terminology 175 This document uses terminology from the Multiprotocol Label Switching 176 Architecture [RFC3031], Multiprotocol Label Switching (MPLS) Traffic 177 Engineering (TE) Management Information Base (MIB) [RFC3812], 178 Multiprotocol Label Switching (MPLS) Label Switching Router (LSR) 179 Management Information Base (MIB) [RFC3813] and MPLS Transport Profile 180 (MPLS-TP) Identifiers [RFC6370]. 182 3.3. Acronyms 184 GMPLS: Generalized Multi-Protocol Label Switching 185 ICC: ITU Carrier Code 186 IP: Internet Protocol 187 LSP: Label Switching Path 188 LSR: Label Switching Router 189 MIB: Management Information Base 190 MPLS: Multi-Protocol Label Switching 191 MPLS-TP: MPLS Transport Profile 192 OSPF: Open Shortest Path First 193 PW: Pseudowire 194 TE: Traffic Engineering 195 TP: Transport Profile 197 4. Motivations 199 Multiprotocol Label Switching (MPLS) Traffic Engineering (TE) Management 200 Information Base (MIB) [RFC3812] provides support for Traffic 201 Engineering tunnels. However, with MPLS-TP, the characteristics of 202 Tunnels were enhanced. For example, MPLS-TP tunnels are bidirectional in 203 nature and could be used in non-IP environment. As the existing MPLS-TE- 204 STD-MIB is not sufficient to capture all the characteristics of the 205 tunnels, enhancing the MIB to support MPLS TP tunnels is required. As 206 most of the attributes of MPLS Traffic Engineering tunnels are also 207 applicable to MPLS-TP tunnels, it is optimal to re-use the existing MIB 208 definition instead of a new MIB. 210 This MIB also defines three other MIB modules within this document. As 211 these new MIB modules are small in size, MPLS-TC-EXT-STD-MIB, MPLS-ID- 212 STD-MIB and MPLS-LSR-EXT-STD-MIB are retained in the same document, 213 instead of a separate document. 215 5. Feature List 217 The MPLS transport profile MIB module is designed to satisfy the 218 following requirements and constraints: 220 The MIB module supports static and signaling point-to-point, co-routed 221 bi-directional and associated bi-directional tunnels. 223 - The MPLS tunnels need not be interfaces, but it is possible 224 to configure a TP tunnel as an interface. 226 - The mplsTunnelTable [RFC3812] to be also used for MPLS-TP 227 tunnels 229 - The mplsTunnelTable is extended to support MPLS-TP specific 230 objects. 232 - A node configuration table (mplsTunnelExtNodeConfigTable) 233 is used to translate the Global_Node_ID or ICC to the local 234 identifier in order to index mplsTunnelTable. 236 - The MIB module supports persistent, as well as non-persistent 237 tunnels. 239 6. Brief description of MIB Objects 241 The objects described in this section support the functionality 242 described in documents [RFC5654] and [RFC6370]. The tables support 243 both IP compatible and ICC based tunnel configurations. 245 6.1. mplsTunnelExtNodeConfigTable 247 The mplsTunnelExtNodeConfigTable is used to assign a local identifier 248 for a given ICC or Global_Node_ID combination as defined in 249 [RFC6370]. An ICC is a string of one to six characters, each 250 character being either alphabetic (i.e. A-Z) or numeric (i.e. 0-9) 251 characters. Alphabetic characters in the ICC should be represented 252 with upper case letters. In the IP compatible mode, 253 Global_Node_ID, is used to uniquely identify a node. 255 Each ICC or Global_Node_ID contains one unique entry in the 256 table representing a node. Every node is assigned a local identifier 257 within a range of 0 to 16777215. This local identifier is used for 258 indexing into mplsTunnelTable as mplsTunnelIngressLSRId and 259 mplsTunnelEgressLSRId. 261 For IP compatible environment, MPLS-TP tunnel is indexed by Tunnel 262 Index, Tunnel Instance, Source Global_ID, Source Node_ID, Destination 263 Global_ID and Destination Node_ID. 265 For ICC based environment, MPLS-TP tunnel is indexed by Tunnel Index, 266 Tunnel Instance, Source ICC and Destination ICC. 268 As mplsTunnelTable is indexed by mplsTunnelIndex, 269 mplsTunnelInstance, mplsTunnelIngressLSRId, and 270 mplsTunnelEgressLSRId, the MPLS-TP tunnel identifiers cannot be 271 used directly. 273 The mplsTunnelExtNodeConfigTable will be used to store an entry for 274 ICC or Global_Node_ID with a local identifier to be used as LSR ID in 275 mplsTunnelTable. As the regular TE tunnels use IP address as LSR ID, 276 the local identifier should be below the first valid IP address, 277 which is 16777216[1.0.0.0]. 279 6.2. mplsTunnelExtNodeIpMapTable 281 The read-only mplsTunnelExtNodeIpMaptable is used to query the local 282 identifier assigned and stored in mplsTunnelExtNodeConfigTable for 283 a given Global_Node_ID. In order to query the local identifier, 284 in the IP compatible mode, this table is indexed with Global_Node_ID. 285 In the IP compatible mode for a TP tunnel, Global_Node_ID 286 is used. 288 A separate query is made to get the local identifier of both 289 Ingress and Egress Global_Node_ID identifiers. These local 290 identifiers are used as mplsTunnelIngressLSRId and 291 mplsTunnelEgressLSRId, while indexing mplsTunnelTable. 293 6.3. mplsTunnelExtNodeIccMapTable 295 The read-only mplsTunnelExtNodeIccMapTable is used to query the local 296 identifier assigned and stored in the mplsTunnelExtNodeConfigTable 297 for a given ICC. 299 A separate query is made to get the local identifier of both 300 Ingress and Egress ICC. These local identifiers are used as 301 mplsTunnelIngressLSRId and mplsTunnelEgressLSRId, 302 while indexing mplsTunnelTable. 304 6.4. mplsTunnelExtTable 306 mplsTunnelExtTable extends the mplsTunnelTable in order to support 307 MPLS-TP tunnels with additional objects. All the additional 308 attributes specific to supporting TP tunnel are contained in this 309 extended table and could be accessed with the mplsTunnelTable 310 indices. 312 6.5. mplsTunnelExtReversePerfTable 314 This table augments the mplsTunnelTable to provide per-tunnel packet 315 performance information for the reverse direction of a bidirectional 316 tunnel. It can be seen as supplementing the mplsTunnelPerfTable, 317 which augments the mplsTunnelTable. 319 7. MIB Module Interdependencies 321 This section provides an overview of the relationship between the 322 MPLS-TP TE MIB module and other MPLS MIB modules. 324 The arrows in the following diagram show a 'depends on' 325 relationship. A relationship "MIB module A depends on MIB module B" 326 means that MIB module A uses an object, object identifier, or 327 textual convention defined in MIB module B, or that MIB module A 328 contains a pointer (index or RowPointer) to an object in 329 MIB module B. 331 MPLS-TC-EXT-STD-MIB 332 ^ 333 | 334 | 335 +<---- MPLS-ID-STD-MIB 336 ^ 337 | | 338 +<---- MPLS-TE-EXT-STD-MIB 339 | | 340 | V 341 | MPLS-TE-STD-MIB 342 | | 343 | | 344 | V 345 | MPLS-LSR-STD-MIB 346 | ^ 347 | | 348 | | 349 +------MPLS-LSR-EXT-STD-MIB 351 Thus: 353 - All the new MPLS extension MIB modules depend on 354 MPLS-TC-EXT-STD-MIB. 356 - MPLS-ID-STD-MIB contains references to objects in 357 MPLS-TE-STD-MIB [RFC3812]. 359 - MPLS-TE-EXT-STD-MIB contains references to objects in 360 MPLS-TE-STD-MIB [RFC3812]. 362 - MPLS-LSR-EXT-STD-MIB contains references to objects in 363 MPLS-LSR-STD-MIB [RFC3813]. 365 MPLS-TE-STD-MIB [RFC3812] is extended by MPLS-TE-EXT-STD-MIB 366 MIB module for associating the reverse direction tunnel 367 information. 369 Note that the nature of the 'extends' relationship 370 is a sparse augmentation so that the entry in the 371 mplsTunnelExtTable has the same index values as the in the 372 mplsTunnelTable. 374 MPLS-LSR-STD-MIB [RFC3813] is extended by MPLS-LSR-EXT-STD-MIB 375 MIB module for pointing back to the tunnel entry for easy tunnel 376 access from XC entry. 378 Note that the nature of the 'extends' relationship 379 is a sparse augmentation so that the entry in the 380 mplsXCExtTable has the same index values as the in the mplsXCTable. 382 8. Dependencies between MIB Module Tables 384 The tables in MPLS-TE-EXT-STD-MIB are related as shown on the diagram 385 below. The arrows indicate a reference from one table to another. 387 mplsTunnelExtNodeConfigTable 388 ^ mplsXCExtTable 389 | | ^ 390 | +---------+ | 391 | | | 392 | V V 393 mplsTunnelTable ---->mplsXCTable 394 ^ 395 | 396 | 397 mplsTunnelExtTable 399 An existing mplsTunnelTable uses the mplsTunnelExtNodeConfigTable 400 table to map the Global_Node_ID and/or ICC with the local number in 401 order to accommodate in the existing tunnel table's ingress/egress 402 LSR-id. 404 New mplsTunnelExtTable table provides the reverse direction LSP 405 information for the existing tunnel table in order to achieve 406 bidirectional LSPs. 408 mplsXCExtTable is extended from mplsLsrXCTable to provide 409 backward reference to tunnel entry. 411 9. Example of MPLS-TP Tunnel Setup 412 In this section, we provide an example of the IP based MPLS-TP 413 bidirectional tunnel setup. This example provides the usage of 414 MPLS-TP Tunnel MIB along with the extended new MIB modules introduced 415 in this document. 417 Do note that a MPLS-TP tunnel could be setup statically as well as 418 signaled via control plane. This example considers accessing MIB 419 objects on a head-end for a static and signaling MPLS-TP tunnels. 420 Only relevant objects which are applicable for MPLS-TP tunnel are 421 illustrated here. 423 In mplsTunnelExtNodeConfigTable: 425 { 426 -- Non-IP Ingress LSR-Id (Index to the table) 427 mplsTunnelExtNodeConfigLocalId = 1, 429 mplsTunnelExtNodeConfigGlobalId = 1234, 430 mplsTunnelExtNodeConfigNodeId = 10, 431 -- Mandatory parameters needed to activate the row go here 432 mplsTunnelExtNodeConfigRowStatus = createAndGo (4) 434 -- Non-IP Egress LSR-Id (Index to the table) 435 mplsTunnelExtNodeConfigLocalId = 2, 436 mplsTunnelExtNodeConfigGlobalId = 1234, 437 mplsTunnelExtNodeConfigNodeId = 20, 438 -- Mandatory parameters needed to activate the row go here 439 mplsTunnelExtNodeConfigRowStatus = createAndGo (4) 440 } 442 This will create an entry in the mplsTunnelExtNodeConfigTable for a 443 Global_Node_ID. A separate entry is made for both Ingress LSR 444 and Egress LSR. 446 The following read-only mplsTunnelExtNodeIpMapTable table is 447 populated automatically upon creating an entry in 448 mplsTunnelExtNodeConfigTable and this table is used to retrieve 449 the local identifier for the given Global_Node_ID. 451 In mplsTunnelExtNodeIpMapTable: 453 { 454 -- Global_ID (Index to the table) 455 mplsTunnelExtNodeIpMapGlobalId = 1234, 456 -- Node Identifier (Index to the table) 457 mplsTunnelExtNodeIpMapNodeId = 10, 458 mplsTunnelExtNodeIpMapLocalId = 1 460 -- Global_ID (Index to the table) 461 mplsTunnelExtNodeIpMapGlobalId = 1234, 462 -- Node Identifier (Index to the table) 463 mplsTunnelExtNodeIpMapNodeId = 20, 464 mplsTunnelExtNodeIpMapLocalId = 2 465 } 467 9.1. Example of MPLS-TP static co-routed bidirectional tunnel setup 469 The following denotes the configured co-routed bidirectional 470 tunnel "head" entry: 472 9.1.1. mplsTunnelEntry 474 In mplsTunnelTable: 476 { 477 mplsTunnelIndex = 1, 478 mplsTunnelInstance = 1, 479 -- Local map number created in mplsTunnelExtNodeConfigTable for 480 -- Ingress LSR-Id 481 mplsTunnelIngressLSRId = 1, 483 -- Local map number created in mplsTunnelExtNodeConfigTable for 484 -- Egress LSR-Id 485 mplsTunnelEgressLSRId = 2, 486 mplsTunnelName = "TP co-routed bidirectional LSP", 487 mplsTunnelDescr = "East to West", 488 mplsTunnelIsIf = true (1), 489 -- RowPointer MUST point to the first accessible column 490 mplsTunnelXCPointer = 491 mplsXCLspId.4.0.0.0.1.1.0.4.0.0.0.1, 492 mplsTunnelSignallingProto = none (1), 493 mplsTunnelSetupPrio = 0, 494 mplsTunnelHoldingPrio = 0, 495 mplsTunnelSessionAttributes = 0, 496 mplsTunnelLocalProtectInUse = false (0), 497 -- RowPointer MUST point to the first accessible column 498 mplsTunnelResourcePointer = mplsTunnelResourceMaxRate.5, 499 mplsTunnelInstancePriority = 1, 500 mplsTunnelHopTableIndex = 1, 501 mplsTunnelIncludeAnyAffinity = 0, 502 mplsTunnelIncludeAllAffinity = 0, 503 mplsTunnelExcludeAnyAffinity = 0, 504 mplsTunnelRole = head (1), 505 -- Mandatory parameters needed to activate the row go here 506 mplsTunnelRowStatus = createAndGo (4) 507 } 509 9.1.2. mplsTunnelExtEntry 511 -- An MPLS extension table 512 In mplsTunnelExtTable: 513 { 514 -- This opposite direction tunnel pointer MAY be point to 0.0 515 -- if co-routed bidirectional tunnel is managed by single tunnel 516 -- entry 517 mplsTunnelExtOppositeDirTnlPtr = 0.0 518 -- Set both the Ingress and Egress LocalId objects to TRUE as 519 -- this tunnel entry uses the local identifiers. 520 mplsTunnelExtIngressLSRLocalIdValid = true, 521 mplsTunnelExtEgressLSRLocalIdValid = true 523 } 524 We must next create the appropriate in-segment and out-segment 525 entries. These are done in [RFC3813] using the mplsInSegmentTable and 526 mplsOutSegmentTable. 528 9.1.3. Forward direction mplsOutSegmentEntry 530 For the forward direction. 532 In mplsOutSegmentTable: 533 { 534 mplsOutSegmentIndex = 0x0000001, 535 mplsOutSegmentInterface = 13, -- outgoing interface 536 mplsOutSegmentPushTopLabel = true(1), 537 mplsOutSegmentTopLabel = 22, -- outgoing label 539 -- RowPointer MUST point to the first accessible column. 540 mplsOutSegmentTrafficParamPtr = 0.0, 541 mplsOutSegmentRowStatus = createAndGo (4) 542 } 544 9.1.4. Reverse direction mplsInSegmentEntry 546 For the reverse direction. 548 In mplsInSegmentTable: 549 { 550 mplsInSegmentIndex = 0x0000001 551 mplsInSegmentLabel = 21, -- incoming label 552 mplsInSegmentNPop = 1, 553 mplsInSegmentInterface = 13, -- incoming interface 555 -- RowPointer MUST point to the first accessible column. 556 mplsInSegmentTrafficParamPtr = 0.0, 557 mplsInSegmentRowStatus = createAndGo (4) 558 } 560 Next, two cross-connect entries are created in the mplsXCTable of the 561 MPLS-LSR-STD-MIB [RFC3813], thereby associating the newly created 562 segments together. 564 9.1.5. Forward direction mplsXCEntry 566 In mplsXCTable: 567 { 568 mplsXCIndex = 0x01, 569 mplsXCInSegmentIndex = 0x00000000, 570 mplsXCOutSegmentIndex = 0x00000001, 571 mplsXCLspId = 0x0102 -- unique ID 572 -- only a single outgoing label 573 mplsXCLabelStackIndex = 0x00, 574 mplsXCRowStatus = createAndGo(4) 576 } 578 9.1.6. Reverse direction mplsXCEntry 580 In mplsXCTable: 581 { 582 mplsXCIndex = 0x01, 583 mplsXCInSegmentIndex = 0x00000001, 584 mplsXCOutSegmentIndex = 0x00000000, 585 mplsXCLspId = 0x0102 -- unique ID 586 -- only a single outgoing label 587 mplsXCLabelStackIndex = 0x00, 588 mplsXCRowStatus = createAndGo(4) 589 } 591 This table entry is extended by entry in the 592 mplsXCExtTable. Note that the nature of the 'extends' 593 relationship is a sparse augmentation so that the entry in the 594 mplsXCExtTable has the same index values as the entry in 595 the mplsXCTable. 597 9.1.7. Forward direction mplsXCExtEntry 599 In mplsXCExtTable (0x01, 0x00000000, 0x00000001) 600 { 601 -- Back pointer from XC table to Tunnel table 602 mplsXCExtTunnelPointer = mplsTunnelName.1.1.1.2 603 mplsXCExtOppositeDirXCPtr = 604 mplsXCLspId.4.0.0.0.1.4.0.0.0.1.1.0 605 } 607 9.1.8. Reverse direction mplsXCExtEntry 609 Next for the reverse direction: 611 In mplsXCExtTable (0x01, 0x00000001, 0x00000000) 612 { 613 -- Back pointer from XC table to Tunnel table 614 mplsXCExtTunnelPointer = mplsTunnelName.1.1.1.2 615 mplsXCExtOppositeDirXCPtr = 616 mplsXCLspId.4.0.0.0.1.1.0.4.0.0.0.1 617 } 619 9.1.9. mplsTunnelExtReversePerfTable 620 The mplsTunnelExtReversePerfTable SHOULD be populated incase 621 the single tunnel entry is used for co-routed bidirectional tunnel 622 setup. The mplsTunnelPerfTable will have the forward direction 623 LSP performance counters and mplsTunnelExtReversePerfTable will have 624 the reverse direction LSP performance counters. 626 9.2. Example of MPLS-TP static associated bidirectional tunnel setup 628 The MPLS-TP associated bidirectional tunnel has two different 629 direction tunnels[Forward and Reverse LSPs] and these are 630 associated together using mplsTunnelExtTable. Two different 631 tunnel entries for both forward and reverse direction MAY be used 632 for co-routed bidirectional tunnel as well. 634 The following denotes the configured associated bidirectional forward 635 tunnel "head" entry: 637 9.2.1. Forward direction mplsTunnelEntry 639 In mplsTunnelTable: 641 { 642 mplsTunnelIndex = 1, 643 mplsTunnelInstance = 1, 644 -- Local map number created in mplsTunnelExtNodeConfigTable for 645 -- Ingress LSR-Id 646 mplsTunnelIngressLSRId = 1, 648 -- Local map number created in mplsTunnelExtNodeConfigTable for 649 -- Egress LSR-Id 650 mplsTunnelEgressLSRId = 2, 651 mplsTunnelName = "TP associated bi-directional 652 forward LSP", 653 mplsTunnelDescr = "East to West", 654 mplsTunnelIsIf = true (1), 655 -- RowPointer MUST point to the first accessible column 656 mplsTunnelXCPointer = 657 mplsXCLspId.4.0.0.0.1.1.0.4.0.0.0.1, 658 mplsTunnelSignallingProto = none (1), 659 mplsTunnelSetupPrio = 0, 660 mplsTunnelHoldingPrio = 0, 661 mplsTunnelSessionAttributes = 0, 662 mplsTunnelLocalProtectInUse = false (0), 663 -- RowPointer MUST point to the first accessible column 664 mplsTunnelResourcePointer = mplsTunnelResourceMaxRate.5, 665 mplsTunnelInstancePriority = 1, 666 mplsTunnelHopTableIndex = 1, 667 mplsTunnelIncludeAnyAffinity = 0, 668 mplsTunnelIncludeAllAffinity = 0, 669 mplsTunnelExcludeAnyAffinity = 0, 670 mplsTunnelRole = head (1), 671 -- Mandatory parameters needed to activate the row go here 672 mplsTunnelRowStatus = createAndGo (4) 673 } 675 9.2.2. Forward direction mplsTunnelExtEntry 677 For Associated bidirectional forward LSP, 678 In mplsTunnelExtTable: 679 { 680 mplsTunnelExtOppositeDirPtr = mplsTunnelName.2.1.2.1 681 -- Set both the Ingress and Egress LocalId objects to TRUE as 682 -- this tunnel entry uses the local identifiers. 683 mplsTunnelExtIngressLSRLocalIdValid = true, 684 mplsTunnelExtEgressLSRLocalIdValid = true 685 } 687 9.2.3. Forward direction mplsOutSegmentTable 689 For the forward direction. 691 In mplsOutSegmentTable: 692 { 693 mplsOutSegmentIndex = 0x0000001, 694 mplsOutSegmentInterface = 13, -- outgoing interface 695 mplsOutSegmentPushTopLabel = true(1), 696 mplsOutSegmentTopLabel = 22, -- outgoing label 698 -- RowPointer MUST point to the first accessible column. 699 mplsOutSegmentTrafficParamPtr = 0.0, 700 mplsOutSegmentRowStatus = createAndGo (4) 701 } 703 9.2.4. Forward direction mplsXCEntry 705 In mplsXCTable: 706 { 707 mplsXCIndex = 0x01, 708 mplsXCInSegmentIndex = 0x00000000, 709 mplsXCOutSegmentIndex = 0x00000001, 710 mplsXCLspId = 0x0102 -- unique ID 711 -- only a single outgoing label 712 mplsXCLabelStackIndex = 0x00, 713 mplsXCRowStatus = createAndGo(4) 715 } 717 9.2.5. Forward direction mplsXCExtEntry 719 In mplsXCExtTable (0x01, 0x00000000, 0x00000001) 720 { 721 -- Back pointer from XC table to Tunnel table 722 mplsXCExtTunnelPointer = mplsTunnelName.1.1.1.2 723 mplsXCExtOppositeDirXCPtr = 724 mplsXCLspId.4.0.0.0.1.4.0.0.0.1.1.0 725 } 727 9.2.6. Reverse direction mplsTunnelEntry 729 The following denotes the configured associated bidirectional reverse 730 tunnel "tail" entry: 732 In mplsTunnelTable: 734 { 735 mplsTunnelIndex = 2, 736 mplsTunnelInstance = 1, 737 -- Local map number created in mplsTunnelExtNodeConfigTable for 738 -- Ingress LSR-Id 739 mplsTunnelIngressLSRId = 2, 740 -- Local map number created in mplsTunnelExtNodeConfigTable for 741 -- Egress LSR-Id 742 mplsTunnelEgressLSRId = 1, 743 mplsTunnelName = "TP associated bi-directional 744 reverse LSP", 745 mplsTunnelDescr = "West to East", 746 mplsTunnelIsIf = true (1), 747 -- RowPointer MUST point to the first accessible column 748 mplsTunnelXCPointer = 749 mplsXCLspId.4.0.0.0.1.4.0.0.0.1.1.0, 750 mplsTunnelSignallingProto = none (1), 751 mplsTunnelSetupPrio = 0, 752 mplsTunnelHoldingPrio = 0, 753 mplsTunnelSessionAttributes = 0, 754 mplsTunnelLocalProtectInUse = false (0), 756 -- RowPointer MUST point to the first accessible column 757 mplsTunnelResourcePointer = mplsTunnelResourceMaxRate.5, 758 mplsTunnelInstancePriority = 1, 759 mplsTunnelHopTableIndex = 1, 760 mplsTunnelIncludeAnyAffinity = 0, 761 mplsTunnelIncludeAllAffinity = 0, 762 mplsTunnelExcludeAnyAffinity = 0, 763 mplsTunnelRole = head (1), 764 -- Mandatory parameters needed to activate the row go here 765 mplsTunnelRowStatus = createAndGo (4) 766 } 768 9.2.7. Reverse direction mplsTunnelExtEntry 770 For Associated bidirectional reverse LSP, 771 In mplsTunnelExtTable: 772 { 773 mplsTunnelExtOppositeDirPtr = mplsTunnelName.1.1.1.2 774 -- Set both the Ingress and Egress LocalId objects to TRUE as 775 -- this tunnel entry uses the local identifiers. 776 mplsTunnelExtIngressLSRLocalIdValid = true, 777 mplsTunnelExtEgressLSRLocalIdValid = true 778 } 780 9.2.8. Reverse direction mplsInSegmentEntry 782 We must next create the appropriate in-segment and out-segment 783 entries. These are done in [RFC3813] using the mplsInSegmentTable and 784 mplsOutSegmentTable. 786 In mplsInSegmentTable: 787 { 788 mplsInSegmentIndex = 0x0000001 789 mplsInSegmentLabel = 21, -- incoming label 790 mplsInSegmentNPop = 1, 791 mplsInSegmentInterface = 13, -- incoming interface 793 -- RowPointer MUST point to the first accessible column. 794 mplsInSegmentTrafficParamPtr = 0.0, 795 mplsInSegmentRowStatus = createAndGo (4) 796 } 798 Next, two cross-connect entries are created in the mplsXCTable of the 799 MPLS-LSR-STD-MIB [RFC3813], thereby associating the newly created 800 segments together. 802 9.2.9. Reverse direction mplsXCEntry 804 In mplsXCTable: 805 { 806 mplsXCIndex = 0x01, 807 mplsXCInSegmentIndex = 0x00000001, 808 mplsXCOutSegmentIndex = 0x00000000, 809 mplsXCLspId = 0x0102 -- unique ID 810 -- only a single outgoing label 811 mplsXCLabelStackIndex = 0x00, 812 mplsXCRowStatus = createAndGo(4) 813 } 815 This table entry is extended by entry in the 816 mplsXCExtTable. Note that the nature of the 'extends' 817 relationship is a sparse augmentation so that the entry in the 818 mplsXCExtTable has the same index values as the entry in 819 the mplsXCTable. 821 9.2.10. Reverse direction mplsXCExtEntry 823 Next for the reverse direction: 825 In mplsXCExtTable (0x01, 0x00000001, 0x00000000) 826 { 827 -- Back pointer from XC table to Tunnel table 828 mplsXCExtTunnelPointer = mplsTunnelName.2.1.2.1 829 mplsXCExtOppositeDirXCPtr = 830 mplsXCLspId.4.0.0.0.1.1.0.4.0.0.0.1 831 } 833 9.3. Example of MPLS-TP signaling co-routed bidirectional tunnel setup 835 The following denotes the configured co-routed bidirectional 836 tunnel "head" entry and in intermediate and tail-end nodes, 837 the tunnel table and its associated tables are created 838 by the local management subsystem (e.g. agent) when the MPLS TP 839 tunnel is signaled successfully. Refer [RFC3812] and [RFC4802] 840 for signaling tunnel table configuration examples. 842 9.3.1. mplsTunnelEntry 844 In mplsTunnelTable: 846 { 847 mplsTunnelIndex = 1, 848 mplsTunnelInstance = 0, 849 -- Local map number created in mplsTunnelExtNodeConfigTable for 850 -- Ingress LSR-Id, for the intermediate and tail-end nodes, 851 -- the local management entity is expected to pick a first available 852 -- local identifier which is not used in mplsTunnelTable. 853 mplsTunnelIngressLSRId = 1, 855 -- Local map number created in mplsTunnelExtNodeConfigTable for 856 -- Egress LSR-Id 857 mplsTunnelEgressLSRId = 2, 858 mplsTunnelName = "TP co-routed bidirectional LSP", 859 mplsTunnelDescr = "East to West", 860 mplsTunnelIsIf = true (1), 862 -- RowPointer MUST point to the first accessible column 863 mplsTunnelXCPointer = 864 mplsXCLspId.4.0.0.0.1.1.0.4.0.0.0.1, 865 mplsTunnelSignallingProto = none (1), 866 mplsTunnelSetupPrio = 0, 867 mplsTunnelHoldingPrio = 0, 868 mplsTunnelSessionAttributes = 0, 869 mplsTunnelLocalProtectInUse = false (0), 870 -- RowPointer MUST point to the first accessible column 871 mplsTunnelResourcePointer = mplsTunnelResourceMaxRate.5, 872 mplsTunnelInstancePriority = 1, 873 mplsTunnelHopTableIndex = 1, 874 mplsTunnelIncludeAnyAffinity = 0, 875 mplsTunnelIncludeAllAffinity = 0, 876 mplsTunnelExcludeAnyAffinity = 0, 877 mplsTunnelRole = head (1), 878 -- Mandatory parameters needed to activate the row go here 879 mplsTunnelRowStatus = createAndGo (4) 880 } 882 9.3.2. mplsTunnelExtEntry 884 -- An MPLS extension table 885 In mplsTunnelExtTable: 886 { 887 -- This opposite direction tunnel pointer MAY be point to 0.0 888 -- if co-routed bidirectional tunnel is managed by single tunnel 889 -- entry 890 mplsTunnelExtOppositeDirTnlPtr = 0.0 891 -- Set both the Ingress and Egress LocalId objects to TRUE as 892 -- this tunnel entry uses the local identifiers. 893 mplsTunnelExtIngressLSRLocalIdValid = true, 894 mplsTunnelExtEgressLSRLocalIdValid = true 895 } 897 We must next create the appropriate in-segment and out-segment 898 entries. These are done in [RFC3813] using the mplsInSegmentTable and 899 mplsOutSegmentTable. 901 9.3.3. Forward direction mplsOutSegmentEntry 903 The forward direction mplsOutSegmentTable will be populated 904 automatically based on the information received from the signaling 905 protocol. 907 9.3.4. Reverse direction mplsInSegmentEntry 908 The reverse direction mplsOutSegmentTable will be populated 909 automatically based on the information received from the signaling 910 protocol. 912 Next, two cross-connect entries are created in the mplsXCTable of the 913 MPLS-LSR-STD-MIB [RFC3813], thereby associating the newly created 914 segments together. 916 9.3.5. Forward direction mplsXCEntry 918 The forward direction mplsXCEntry will be populated as soon as the 919 forward path label information is available. 921 9.3.6. Reverse direction mplsXCEntry 923 The reverse direction mplsXCEntry will be populated as soon as the 924 reverse path label information is available. 926 This table entry is extended by entry in the mplsXCExtTable. Note 927 that the nature of the 'extends' relationship is a sparse 928 augmentation so that the entry in the mplsXCExtTable has the same 929 index values as the entry in the mplsXCTable. 931 9.3.7. Forward direction mplsXCExtEntry 933 Once the forward path information is negotiated using signaling 934 protocol, the forward direction mplsXCExtEntry will be created for 935 associating the opposite direction XC entry and tunnel table entry. 937 9.3.8. Reverse direction mplsXCExtEntry 939 Once the reverse path information is negotiated using signaling 940 protocol, the reverse direction mplsXCExtEntry will be created for 941 associating the opposite direction XC entry and tunnel table entry. 943 9.3.9. mplsTunnelExtReversePerfTable 945 The mplsTunnelExtReversePerfTable SHOULD be populated incase the 946 single tunnel entry is used for co-routed bidirectional tunnel setup. 947 The mplsTunnelPerfTable will have the forward direction LSP 948 performance counters and mplsTunnelExtReversePerfTable will have the 949 reverse direction LSP performance counters. 951 10. MPLS Textual Convention Extension MIB definitions 952 MPLS-TC-EXT-STD-MIB DEFINITIONS ::= BEGIN 954 IMPORTS 955 MODULE-IDENTITY, Unsigned32 956 FROM SNMPv2-SMI -- [RFC2578] 958 TEXTUAL-CONVENTION 959 FROM SNMPv2-TC -- [RFC2579] 961 mplsStdMIB 962 FROM MPLS-TC-STD-MIB -- [RFC3811] 964 ; 966 mplsTcExtStdMIB MODULE-IDENTITY 968 LAST-UPDATED 969 "201301140000Z" -- January 14, 2013 970 ORGANIZATION 971 "Multiprotocol Label Switching (MPLS) Working Group" 972 CONTACT-INFO 973 " 974 Venkatesan Mahalingam 975 Dell Inc, 976 350 Holger way, San Jose, CA, USA 977 Email: venkat.mahalingams@gmail.com 979 Kannan KV Sampath 980 Redeem, 981 India 982 Email: kannankvs@gmail.com 984 Sam Aldrin 985 Huawei Technologies 986 2330 Central Express Way, 987 Santa Clara, CA 95051, USA 988 Email: aldrin.ietf@gmail.com 990 Thomas D. Nadeau 991 Juniper Networks 992 10 Technology Park Drive, 993 Westford, MA 01886 994 Email: tnadeau@juniper.net 995 " 996 DESCRIPTION 997 "Copyright (c) 2013 IETF Trust and the persons identified 998 as the document authors. All rights reserved. 1000 This MIB module contains Textual Conventions for 1001 MPLS based transport networks." 1003 -- Revision history. 1005 REVISION 1007 "201301140000Z" -- January 14, 2013 1008 DESCRIPTION 1009 "MPLS Textual Convention Extensions" 1011 ::= { mplsStdMIB xxx } -- xxx to be replaced with correct value 1013 MplsGlobalId ::= TEXTUAL-CONVENTION 1015 STATUS current 1016 DESCRIPTION 1017 "This object contains the Textual Convention of IP based 1018 operator unique identifier (Global_ID), the Global_ID can 1019 contain the 2-octet or 4-octet value of the operator's 1020 Autonomous System Number (ASN). 1022 It is expected that the Global_ID will be derived from 1023 the globally unique ASN of the autonomous system hosting 1024 the PEs containing the actual AIIs. 1025 The presence of a Global_ID based on the operator's 1026 ASN ensures that the AII will be globally unique. 1028 When the Global_ID is derived from a 2-octet AS number, 1030 the two high-order octets of this 4-octet identifier 1031 MUST be set to zero. 1032 Further ASN 0 is reserved. A Global_ID of zero means 1033 that no Global_ID is present. Note that a Global_ID of 1034 zero is limited to entities contained within a single 1035 operator and MUST NOT be used across an NNI. 1036 A non-zero Global_ID MUST be derived from an ASN owned by 1037 the operator." 1038 REFERENCE 1039 "MPLS Transport Profile (MPLS-TP) Identifiers, [RFC6370] 1040 Section 3 Uniquely Identifying an Operator - the Global_ID" 1041 SYNTAX OCTET STRING (SIZE (4)) 1043 MplsNodeId ::= TEXTUAL-CONVENTION 1044 DISPLAY-HINT "d" 1045 STATUS current 1046 DESCRIPTION 1047 "The Node_ID is assigned within the scope of the Global_ID. 1048 The value 0(or 0.0.0.0 in dotted decimal notation) is 1049 reserved and MUST NOT be used. 1051 When IPv4 addresses are in use, the value of this object 1052 can be derived from the LSR's IPv4 loop back address. 1053 When IPv6 addresses are in use, the value of this object 1054 can be a 32-bit value unique within the scope of 1055 a Global_ID. 1057 Note that, when IP reach ability is not needed, the 32-bit 1058 Node_ID is not required to have any association 1059 with the IPv4 address space." 1060 REFERENCE 1061 "MPLS Transport Profile (MPLS-TP) Identifiers, [RFC6370], 1062 Section 4. Node and Interface Identifiers" 1063 SYNTAX Unsigned32 -- the default range: (0..4294967295) 1065 MplsIccId ::= TEXTUAL-CONVENTION 1066 STATUS current 1067 DESCRIPTION 1068 "The ICC is a string of one to six characters, each 1069 character being either alphabetic (i.e. A-Z) or 1070 numeric (i.e. 0-9) characters. 1071 Alphabetic characters in the ICC SHOULD be represented 1072 with upper case letters." 1073 REFERENCE 1074 "MPLS-TP Identifiers Following ITU-T Conventions, 1075 [I-D.ietf-mpls-tp-itu-t-identifiers], Section 3. 1076 Uniquely Identifying an Operator - the ICC_Operator_ID" 1077 SYNTAX OCTET STRING (SIZE (1..6)) 1079 -- MPLS-TC-EXT-STD-MIB module ends 1080 END 1082 11. MPLS Identifier MIB definitions 1084 MPLS-ID-STD-MIB DEFINITIONS ::= BEGIN 1086 IMPORTS 1087 MODULE-IDENTITY, OBJECT-TYPE 1088 FROM SNMPv2-SMI -- [RFC2578] 1089 MODULE-COMPLIANCE, OBJECT-GROUP 1090 FROM SNMPv2-CONF -- [RFC2580] 1091 mplsStdMIB 1092 FROM MPLS-TC-STD-MIB -- [RFC3811] 1093 MplsGlobalId, MplsIccId, MplsNodeId 1094 FROM MPLS-TC-EXT-STD-MIB 1095 ; 1097 mplsIdStdMIB MODULE-IDENTITY 1098 LAST-UPDATED 1099 "201301140000Z" -- January 14, 2013 1100 ORGANIZATION 1101 "Multiprotocol Label Switching (MPLS) Working Group" 1103 CONTACT-INFO 1104 " 1105 Venkatesan Mahalingam 1106 Dell Inc, 1107 350 Holger way, San Jose, CA, USA 1108 Email: venkat.mahalingams@gmail.com 1110 Kannan KV Sampath 1112 Redeem, 1113 India 1114 Email: kannankvs@gmail.com 1116 Sam Aldrin 1117 Huawei Technologies 1118 2330 Central Express Way, 1119 Santa Clara, CA 95051, USA 1120 Email: aldrin.ietf@gmail.com 1122 Thomas D. Nadeau 1123 Juniper Networks 1124 10 Technology Park Drive, 1125 Westford, MA 01886 1126 Email: tnadeau@juniper.net 1127 " 1128 DESCRIPTION 1129 "Copyright (c) 2013 IETF Trust and the persons identified 1130 as the document authors. All rights reserved. 1132 This MIB module contains generic object definitions for 1133 MPLS Traffic Engineering in transport networks." 1135 -- Revision history. 1137 REVISION 1138 "201301140000Z" -- January 14, 2013 1139 DESCRIPTION 1140 "This MIB modules defines the MIB objects for MPLS-TP 1141 identifiers" 1143 ::= { mplsStdMIB xxx } -- xxx to be replaced with correct value 1145 -- Notifications 1146 mplsIdNotifications OBJECT IDENTIFIER ::= { mplsIdStdMIB 0 } 1147 -- tables, scalars 1148 mplsIdObjects OBJECT IDENTIFIER ::= { mplsIdStdMIB 1 } 1149 -- conformance 1150 mplsIdConformance OBJECT IDENTIFIER ::= { mplsIdStdMIB 2 } 1152 -- MPLS common objects 1154 mplsIdGlobalId OBJECT-TYPE 1155 SYNTAX MplsGlobalId 1156 MAX-ACCESS read-write 1157 STATUS current 1158 DESCRIPTION 1160 "This object allows the operator to assign a unique 1161 operator identifier also called MPLS-TP Global_ID." 1162 ::= { mplsIdObjects 1 } 1164 mplsIdIcc OBJECT-TYPE 1165 SYNTAX MplsIccId 1166 MAX-ACCESS read-write 1167 STATUS current 1168 DESCRIPTION 1169 "This object allows the operator or service provider to 1170 assign a unique MPLS-TP ITU-T Carrier Code (ICC) to a 1171 network." 1172 ::= { mplsIdObjects 2 } 1174 mplsIdNodeId OBJECT-TYPE 1175 SYNTAX MplsNodeId 1176 MAX-ACCESS read-write 1177 STATUS current 1178 DESCRIPTION 1179 "This object allows the operator or service provider to 1180 assign a unique MPLS-TP Node_ID. 1182 The Node_ID is assigned within the scope of 1183 the Global_ID." 1184 ::= { mplsIdObjects 3 } 1186 -- Module compliance. 1188 mplsIdGroups 1189 OBJECT IDENTIFIER ::= { mplsIdConformance 1 } 1191 mplsIdCompliances 1192 OBJECT IDENTIFIER ::= { mplsIdConformance 2 } 1194 -- Compliance requirement for fully compliant implementations. 1196 mplsIdModuleFullCompliance MODULE-COMPLIANCE 1197 STATUS current 1198 DESCRIPTION 1199 "Compliance statement for agents that provide full 1200 support the MPLS-ID-STD-MIB module." 1202 MODULE -- this module 1204 -- The mandatory group has to be implemented by all 1205 -- LSRs that originate/terminate MPLS-TP paths. 1207 MANDATORY-GROUPS { 1208 mplsIdScalarGroup 1209 } 1211 ::= { mplsIdCompliances 1 } 1213 -- Compliance requirement for read-only implementations. 1215 mplsIdModuleReadOnlyCompliance MODULE-COMPLIANCE 1216 STATUS current 1217 DESCRIPTION 1218 "Compliance statement for agents that provide full 1219 support the MPLS-ID-STD-MIB module." 1221 MODULE -- this module 1223 -- The mandatory group has to be implemented by all 1224 -- LSRs that originate/terminate MPLS-TP paths. 1226 MANDATORY-GROUPS { 1227 mplsIdScalarGroup 1228 } 1230 ::= { mplsIdCompliances 2 } 1232 -- Units of conformance. 1234 mplsIdScalarGroup OBJECT-GROUP 1235 OBJECTS { mplsIdGlobalId, 1236 mplsIdNodeId, 1237 mplsIdIcc 1239 } 1240 STATUS current 1241 DESCRIPTION 1242 "Scalar object needed to implement MPLS TP path." 1243 ::= { mplsIdGroups 1 } 1245 -- MPLS-ID-STD-MIB module ends 1246 END 1248 12. MPLS LSR Extension MIB definitions 1250 MPLS-LSR-EXT-STD-MIB DEFINITIONS ::= BEGIN 1252 IMPORTS 1253 MODULE-IDENTITY, OBJECT-TYPE 1254 FROM SNMPv2-SMI -- [RFC2578] 1255 MODULE-COMPLIANCE, OBJECT-GROUP 1256 FROM SNMPv2-CONF -- [RFC2580] 1257 mplsStdMIB 1258 FROM MPLS-TC-STD-MIB -- [RFC3811] 1259 RowPointer 1260 FROM SNMPv2-TC -- [RFC2579] 1261 mplsXCIndex, mplsXCInSegmentIndex, mplsXCOutSegmentIndex, 1262 mplsInterfaceGroup, mplsInSegmentGroup, mplsOutSegmentGroup, 1263 mplsXCGroup, mplsPerfGroup, mplsLsrNotificationGroup 1264 FROM MPLS-LSR-STD-MIB; -- [RFC3813] 1266 mplsLsrExtStdMIB MODULE-IDENTITY 1267 LAST-UPDATED 1268 "201301140000Z" -- January 14, 2013 1269 ORGANIZATION 1270 "Multiprotocol Label Switching (MPLS) Working Group" 1271 CONTACT-INFO 1272 " 1273 Venkatesan Mahalingam 1274 Dell Inc, 1275 350 Holger way, San Jose, CA, USA 1276 Email: venkat.mahalingams@gmail.com 1278 Kannan KV Sampath 1279 Redeem, 1280 India 1281 Email: kannankvs@gmail.com 1283 Sam Aldrin 1284 Huawei Technologies 1285 2330 Central Express Way, 1286 Santa Clara, CA 95051, USA 1288 Email: aldrin.ietf@gmail.com 1290 Thomas D. Nadeau 1291 Juniper Networks 1292 10 Technology Park Drive, Westford, MA 01886 1293 Email: tnadeau@juniper.net 1294 " 1295 DESCRIPTION 1296 "Copyright (c) 2013 IETF Trust and the persons identified 1297 as the document authors. All rights reserved. 1299 This MIB module contains generic object definitions for 1301 MPLS LSR in transport networks." 1303 -- Revision history. 1305 REVISION 1306 "201301140000Z" -- January 14, 2013 1307 DESCRIPTION 1308 "MPLS LSR specific MIB objects extension" 1310 ::= { mplsStdMIB xxx } -- xxx to be replaced with correct value 1312 -- Notifications 1313 mplsLsrExtNotifications OBJECT IDENTIFIER 1314 ::= { mplsLsrExtStdMIB 0 } 1315 -- tables, scalars 1316 mplsLsrExtObjects OBJECT IDENTIFIER 1317 ::= { mplsLsrExtStdMIB 1 } 1318 -- conformance 1319 mplsLsrExtConformance OBJECT IDENTIFIER 1320 ::= { mplsLsrExtStdMIB 2 } 1322 -- MPLS LSR common objects 1323 mplsXCExtTable OBJECT-TYPE 1324 SYNTAX SEQUENCE OF MplsXCExtEntry 1325 MAX-ACCESS not-accessible 1326 STATUS current 1327 DESCRIPTION 1328 "This table sparse augments the mplsXCTable of 1329 MPLS-LSR-STD-MIB [RFC3813] to provide MPLS-TP specific 1330 information about associated tunnel information" 1331 REFERENCE 1332 "1. Multiprotocol Label Switching (MPLS) Label Switching 1333 Router (LSR) Management Information Base (MIB), RFC 3813, 1334 Section 5.7. mplsXCTable" 1335 ::= { mplsLsrExtObjects 1 } 1337 mplsXCExtEntry OBJECT-TYPE 1338 SYNTAX MplsXCExtEntry 1339 MAX-ACCESS not-accessible 1341 STATUS current 1342 DESCRIPTION 1344 "An entry in this table extends the cross connect 1345 information represented by an entry in 1346 the mplsXCTable in MPLS-LSR-STD-MIB [RFC3813] through 1347 a sparse augmentation. An entry can be created by 1348 a network operator via SNMP SET commands, or in 1349 response to signaling protocol events." 1350 REFERENCE 1351 "1. Multiprotocol Label Switching (MPLS) Label Switching 1352 Router (LSR) Management Information Base (MIB), RFC 3813, 1353 Section 10. mplsXCTable" 1355 INDEX { mplsXCIndex, mplsXCInSegmentIndex, 1356 mplsXCOutSegmentIndex } 1357 ::= { mplsXCExtTable 1 } 1359 MplsXCExtEntry ::= SEQUENCE { 1360 mplsXCExtTunnelPointer RowPointer, 1361 mplsXCExtOppositeDirXCPtr RowPointer 1362 } 1364 mplsXCExtTunnelPointer OBJECT-TYPE 1365 SYNTAX RowPointer 1366 MAX-ACCESS read-only 1367 STATUS current 1368 DESCRIPTION 1369 "This read-only object indicates the back pointer to 1370 the tunnel entry segment." 1371 REFERENCE 1372 "1. Multiprotocol Label Switching (MPLS) Label Switching 1373 Router (LSR) Management Information Base (MIB), RFC 3813, 1374 Section 10. mplsXCTable" 1375 ::= { mplsXCExtEntry 1 } 1377 mplsXCExtOppositeDirXCPtr OBJECT-TYPE 1378 SYNTAX RowPointer 1379 MAX-ACCESS read-create 1380 STATUS current 1381 DESCRIPTION 1382 "This object indicates the pointer to the opposite 1383 direction XC entry. This object cannot be modified if 1384 mplsXCRowStatus for the corresponding entry in the 1385 mplsXCTable is active(1)." 1386 REFERENCE 1387 "1. Multiprotocol Label Switching (MPLS) Label Switching 1388 Router (LSR) Management Information Base (MIB), RFC 3813, 1389 Section 10. mplsXCTable" 1390 ::= { mplsXCExtEntry 2 } 1392 mplsLsrExtGroups 1393 OBJECT IDENTIFIER ::= { mplsLsrExtConformance 1 } 1395 mplsLsrExtCompliances 1396 OBJECT IDENTIFIER ::= { mplsLsrExtConformance 2 } 1398 -- Compliance requirement for fully compliant implementations. 1400 mplsLsrExtModuleFullCompliance MODULE-COMPLIANCE 1401 STATUS current 1402 DESCRIPTION 1403 "Compliance statement for agents that provide full support 1404 for MPLS-LSR-EXT-STD-MIB. 1405 The mandatory group has to be implemented by all LSRs 1406 that originate, terminate, or act as transit for 1407 TE-LSPs/tunnels. 1408 In addition, depending on the type of tunnels supported, 1409 other groups become mandatory as explained below." 1411 MODULE MPLS-LSR-STD-MIB -- The MPLS-LSR-STD-MIB, RFC3813 1413 MANDATORY-GROUPS { 1414 mplsInSegmentGroup, 1415 mplsOutSegmentGroup, 1416 mplsXCGroup, 1417 mplsPerfGroup, 1418 mplsLsrNotificationGroup 1419 } 1421 MODULE -- this module 1423 MANDATORY-GROUPS { 1424 mplsXCExtGroup 1425 } 1427 ::= { mplsLsrExtCompliances 1 } 1429 -- Compliance requirement for implementations that provide 1430 -- read-only access. 1432 mplsLsrExtModuleReadOnlyCompliance MODULE-COMPLIANCE 1433 STATUS current 1434 DESCRIPTION 1435 "Compliance requirement for implementations that only 1436 provide read-only support for MPLS-LSR-EXT-STD-MIB. 1437 Such devices can then be monitored but cannot be 1438 configured using this MIB module." 1440 MODULE MPLS-LSR-STD-MIB 1442 MANDATORY-GROUPS { 1443 mplsInterfaceGroup, 1444 mplsInSegmentGroup, 1445 mplsOutSegmentGroup, 1446 mplsXCGroup, 1447 mplsPerfGroup 1448 } 1450 MODULE -- this module 1452 MANDATORY-GROUPS { 1453 mplsXCExtGroup 1454 } 1456 OBJECT mplsXCExtTunnelPointer 1457 SYNTAX RowPointer 1458 MIN-ACCESS read-only 1459 DESCRIPTION 1460 "The only valid value for Tunnel Pointer is 1461 mplsTunnelTable entry." 1463 OBJECT mplsXCExtOppositeDirXCPtr 1464 SYNTAX RowPointer 1465 MIN-ACCESS read-only 1466 DESCRIPTION 1467 "The only valid value for XC Pointer is 1468 mplsXCTable entry." 1470 ::= { mplsLsrExtCompliances 2 } 1472 mplsXCExtGroup OBJECT-GROUP 1473 OBJECTS { 1474 mplsXCExtTunnelPointer, 1475 mplsXCExtOppositeDirXCPtr 1476 } 1477 STATUS current 1478 DESCRIPTION 1479 "This object should be supported in order to access 1480 the tunnel entry from XC entry." 1482 ::= { mplsLsrExtGroups 1 } 1484 -- MPLS-LSR-EXT-STD-MIB module ends 1485 END 1487 13. MPLS Tunnel Extension MIB definitions 1489 MPLS-TE-EXT-STD-MIB DEFINITIONS ::= BEGIN 1491 IMPORTS 1492 MODULE-IDENTITY, OBJECT-TYPE, Counter32, 1493 Counter64, zeroDotZero 1495 FROM SNMPv2-SMI -- [RFC2578] 1496 MODULE-COMPLIANCE, OBJECT-GROUP 1497 FROM SNMPv2-CONF -- [RFC2580] 1498 TruthValue, RowStatus, RowPointer, StorageType 1499 FROM SNMPv2-TC -- [RFC2579] 1500 MplsGlobalId, MplsNodeId, MplsIccId 1501 FROM MPLS-TC-EXT-STD-MIB 1502 mplsStdMIB, MplsTunnelIndex, MplsTunnelInstanceIndex, 1503 MplsExtendedTunnelId 1504 FROM MPLS-TC-STD-MIB -- [RFC3811] 1505 mplsTunnelIndex, mplsTunnelInstance, mplsTunnelIngressLSRId, 1506 mplsTunnelEgressLSRId 1507 FROM MPLS-TE-STD-MIB -- [RFC3812] 1508 ; 1510 mplsTeExtStdMIB MODULE-IDENTITY 1511 LAST-UPDATED 1512 "201301140000Z" -- January 14, 2013 1513 ORGANIZATION 1514 "Multiprotocol Label Switching (MPLS) Working Group" 1515 CONTACT-INFO 1516 " 1517 Venkatesan Mahalingam 1518 Dell Inc, 1519 350 Holger way, San Jose, CA, USA 1520 Email: venkat.mahalingams@gmail.com 1522 Kannan KV Sampath 1523 Redeem, 1524 India 1525 Email: kannankvs@gmail.com 1527 Sam Aldrin 1528 Huawei Technologies 1529 2330 Central Express Way, 1530 Santa Clara, CA 95051, USA 1531 Email: aldrin.ietf@gmail.com 1533 Thomas D. Nadeau 1534 Juniper Networks 1535 10 Technology Park Drive, Westford, MA 01886 1536 Email: tnadeau@juniper.net 1537 " 1538 DESCRIPTION 1539 "Copyright (c) 2013 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 Traffic Engineering in transport networks." 1545 -- Revision history. 1547 REVISION 1548 "201301140000Z" -- January 14, 2013 1550 DESCRIPTION 1551 "MPLS TE MIB objects extension" 1553 ::= { mplsStdMIB xxx } -- xxx to be replaced 1554 -- with correct value 1556 -- Top level components of this MIB module. 1558 -- Notifications 1559 mplsTeExtNotifications OBJECT IDENTIFIER 1560 ::= { mplsTeExtStdMIB 0 } 1561 -- tables, scalars 1562 mplsTeExtObjects OBJECT IDENTIFIER 1563 ::= { mplsTeExtStdMIB 1 } 1564 -- conformance 1565 mplsTeExtConformance OBJECT IDENTIFIER 1566 ::= { mplsTeExtStdMIB 2 } 1568 -- Start of MPLS Transport Profile Node configuration table 1569 mplsTunnelExtNodeConfigTable OBJECT-TYPE 1570 SYNTAX SEQUENCE OF MplsTunnelExtNodeConfigEntry 1571 MAX-ACCESS not-accessible 1572 STATUS current 1573 DESCRIPTION 1574 "This table allows the operator to map a node or 1575 LSR Identifier (IP compatible [Global_Node_ID] or ICC) 1576 with a local identifier. 1578 This table is created to reuse the existing 1579 mplsTunnelTable for MPLS based transport network 1580 tunnels also. 1581 Since the MPLS tunnel's Ingress/Egress LSR identifiers' 1582 size (Unsigned32) value is not compatible for 1583 MPLS-TP tunnel i.e. Global_Node_Id of size 8 bytes and 1584 ICC of size 6 bytes, there exists a need to map the 1585 Global_Node_ID or ICC with the local identifier of size 1586 4 bytes (Unsigned32) value in order 1587 to index (Ingress/Egress LSR identifier) 1588 the existing mplsTunnelTable." 1590 ::= { mplsTeExtObjects 1 } 1592 mplsTunnelExtNodeConfigEntry OBJECT-TYPE 1593 SYNTAX MplsTunnelExtNodeConfigEntry 1594 MAX-ACCESS not-accessible 1595 STATUS current 1596 DESCRIPTION 1598 "An entry in this table represents a mapping 1599 identification for the operator or service provider 1600 with node or LSR. 1602 As per [RFC6370], this mapping is 1604 represented as Global_Node_ID or ICC. 1606 Note: Each entry in this table should have a unique 1607 Global_ID and Node_ID combination." 1608 INDEX { mplsTunnelExtNodeConfigLocalId } 1609 ::= { mplsTunnelExtNodeConfigTable 1 } 1611 MplsTunnelExtNodeConfigEntry ::= SEQUENCE { 1612 mplsTunnelExtNodeConfigLocalId MplsExtendedTunnelId, 1613 mplsTunnelExtNodeConfigGlobalId MplsGlobalId, 1614 mplsTunnelExtNodeConfigNodeId MplsNodeId, 1615 mplsTunnelExtNodeConfigIccId MplsIccId, 1616 mplsTunnelExtNodeConfigRowStatus RowStatus, 1617 mplsTunnelExtNodeConfigStorageType StorageType 1619 } 1621 mplsTunnelExtNodeConfigLocalId OBJECT-TYPE 1622 SYNTAX MplsExtendedTunnelId 1623 MAX-ACCESS not-accessible 1624 STATUS current 1625 DESCRIPTION 1626 "This object is used in accommodating the bigger 1627 size Global_Node_ID and/or ICC with lower size LSR 1628 identifier in order to index the mplsTunnelTable. 1630 The Local Identifier is configured between 0 and 16777215, 1631 as valid IP address range starts from 16777216(01.00.00.00). 1632 This range is chosen to identify the mplsTunnelTable's 1633 Ingress/Egress LSR-id is IP address or Local identifier, 1634 if the configured range is not IP address, operator is 1635 expected to retrieve the complete information 1636 (Global_Node_ID or ICC) from mplsTunnelExtNodeConfigTable. 1637 This way, existing mplsTunnelTable is reused for 1638 bidirectional tunnel extensions for MPLS based transport 1639 networks. 1641 This Local Identifier allows the operator to assign 1642 a unique identifier to map Global_Node_ID and/or ICC. 1643 As this Local Identifier is unique within the node and 1644 the same syntax of this object can be used for MPLS TE 1645 tunnel also, it is up to the operator/local management 1646 entity to choose the non-conflicting value for indexing 1647 the MPLS and MPLS-TP tunnel entries." 1648 ::= { mplsTunnelExtNodeConfigEntry 1 } 1650 mplsTunnelExtNodeConfigGlobalId OBJECT-TYPE 1651 SYNTAX MplsGlobalId 1652 MAX-ACCESS read-create 1653 STATUS current 1654 DESCRIPTION 1655 "This object indicates the Global Operator Identifier. 1656 This object value should be zero when 1657 mplsTunnelExtNodeConfigIccId is configured with non-null 1658 value." 1659 REFERENCE 1660 "MPLS Transport Profile (MPLS-TP) Identifiers [RFC6370] 1661 Section 3. Uniquely Identifying an Operator - 1662 the Global_ID" 1663 ::= { mplsTunnelExtNodeConfigEntry 2 } 1665 mplsTunnelExtNodeConfigNodeId OBJECT-TYPE 1666 SYNTAX MplsNodeId 1667 MAX-ACCESS read-create 1668 STATUS current 1669 DESCRIPTION 1670 "This object indicates the Node_ID within the operator. 1671 This object value should be zero when 1672 mplsTunnelExtNodeConfigIccId is configured with non-null 1673 value." 1674 REFERENCE 1675 "MPLS Transport Profile (MPLS-TP) Identifiers [RFC6370] 1676 Section 4, Node and Interface Identifiers" 1677 ::= { mplsTunnelExtNodeConfigEntry 3 } 1679 mplsTunnelExtNodeConfigIccId OBJECT-TYPE 1680 SYNTAX MplsIccId 1681 MAX-ACCESS read-create 1682 STATUS current 1683 DESCRIPTION 1684 "This object allows the operator or service provider to 1685 configure a unique MPLS-TP ITU-T Carrier Code (ICC) 1686 either for Ingress ID or Egress ID. 1688 This object value should be zero when 1689 mplsTunnelExtNodeConfigGlobalId and 1690 mplsTunnelExtNodeConfigNodeId are assigned with non-zero 1691 value." 1692 REFERENCE 1693 "MPLS-TP Identifiers Following ITU-T Conventions, 1694 [I-D.ietf-mpls-tp-itu-t-identifiers], August 2012, 1695 Section 3. Uniquely Identifying an Operator - the 1696 ICC_Operator_ID" 1697 ::= { mplsTunnelExtNodeConfigEntry 4 } 1699 mplsTunnelExtNodeConfigRowStatus OBJECT-TYPE 1700 SYNTAX RowStatus 1701 MAX-ACCESS read-create 1702 STATUS current 1703 DESCRIPTION 1704 "This object allows the operator to create, modify, 1705 and/or delete a row in this table." 1706 ::= { mplsTunnelExtNodeConfigEntry 5 } 1708 mplsTunnelExtNodeConfigStorageType OBJECT-TYPE 1709 SYNTAX StorageType 1710 MAX-ACCESS read-create 1711 STATUS current 1712 DESCRIPTION 1713 "This variable indicates the storage type for this 1714 object. 1715 Conceptual rows having the value 'permanent' 1716 need not allow write-access to any columnar 1717 objects in the row." 1718 DEFVAL { volatile } 1719 ::= { mplsTunnelExtNodeConfigEntry 6 } 1721 -- End of MPLS Transport Profile Node configuration table 1723 -- Start of MPLS Transport Profile Node IP compatible 1724 -- mapping table 1726 mplsTunnelExtNodeIpMapTable OBJECT-TYPE 1727 SYNTAX SEQUENCE OF MplsTunnelExtNodeIpMapEntry 1729 MAX-ACCESS not-accessible 1730 STATUS current 1731 DESCRIPTION 1732 "This read-only table allows the operator to retrieve 1733 the local identifier for a given Global_Node_ID in an IP 1734 compatible operator environment. 1736 This table MAY be used in on-demand and/or proactive 1738 OAM operations to get the Ingress/Egress LSR identifier 1739 (Local Identifier) from Src-Global_Node_ID 1740 or Dst-Global_Node_ID and the Ingress and Egress LSR 1741 identifiers are used to retrieve the tunnel entry. 1743 This table returns nothing when the associated entry 1744 is not defined in mplsTunnelExtNodeConfigTable." 1745 ::= { mplsTeExtObjects 2 } 1747 mplsTunnelExtNodeIpMapEntry OBJECT-TYPE 1748 SYNTAX MplsTunnelExtNodeIpMapEntry 1749 MAX-ACCESS not-accessible 1750 STATUS current 1751 DESCRIPTION 1752 "An entry in this table represents a mapping of 1753 Global_Node_ID with the local identifier. 1755 An entry in this table is created automatically when 1756 the Local identifier is associated with Global_ID and 1757 Node_Id in the mplsTunnelExtNodeConfigTable. 1759 Note: Each entry in this table should have a unique 1760 Global_ID and Node_ID combination." 1761 INDEX { mplsTunnelExtNodeIpMapGlobalId, 1762 mplsTunnelExtNodeIpMapNodeId 1764 } 1765 ::= { mplsTunnelExtNodeIpMapTable 1 } 1767 MplsTunnelExtNodeIpMapEntry ::= SEQUENCE { 1768 mplsTunnelExtNodeIpMapGlobalId MplsGlobalId, 1769 mplsTunnelExtNodeIpMapNodeId MplsNodeId, 1770 mplsTunnelExtNodeIpMapLocalId MplsExtendedTunnelId 1771 } 1773 mplsTunnelExtNodeIpMapGlobalId OBJECT-TYPE 1774 SYNTAX MplsGlobalId 1775 MAX-ACCESS not-accessible 1776 STATUS current 1777 DESCRIPTION 1778 "This object indicates the Global_ID." 1779 ::= { mplsTunnelExtNodeIpMapEntry 1 } 1781 mplsTunnelExtNodeIpMapNodeId OBJECT-TYPE 1782 SYNTAX MplsNodeId 1783 MAX-ACCESS not-accessible 1784 STATUS current 1785 DESCRIPTION 1786 "This object indicates the Node_ID within the 1788 operator." 1789 ::= { mplsTunnelExtNodeIpMapEntry 2 } 1791 mplsTunnelExtNodeIpMapLocalId OBJECT-TYPE 1792 SYNTAX MplsExtendedTunnelId 1793 MAX-ACCESS read-only 1794 STATUS current 1795 DESCRIPTION 1796 "This object contains an IP compatible local identifier 1797 which is defined in mplsTunnelExtNodeConfigTable." 1798 ::= { mplsTunnelExtNodeIpMapEntry 3 } 1800 -- End MPLS Transport Profile Node IP compatible table 1802 -- Start of MPLS Transport Profile Node ICC based table 1804 mplsTunnelExtNodeIccMapTable OBJECT-TYPE 1805 SYNTAX SEQUENCE OF MplsTunnelExtNodeIccMapEntry 1806 MAX-ACCESS not-accessible 1807 STATUS current 1808 DESCRIPTION 1809 "This read-only table allows the operator to retrieve 1810 the local identifier for a given ICC operator in an ICC 1811 operator environment. 1813 This table MAY be used in on-demand and/or proactive 1814 OAM operations to get the Ingress/Egress LSR 1815 identifier (Local Identifier) from Src-ICC 1816 or Dst-ICC and the Ingress and Egress LSR 1817 identifiers are used to retrieve the tunnel entry. 1818 This table returns nothing when the associated entry 1819 is not defined in mplsTunnelExtNodeConfigTable." 1820 ::= { mplsTeExtObjects 3 } 1822 mplsTunnelExtNodeIccMapEntry OBJECT-TYPE 1823 SYNTAX MplsTunnelExtNodeIccMapEntry 1824 MAX-ACCESS not-accessible 1825 STATUS current 1826 DESCRIPTION 1827 "An entry in this table represents a mapping of ICC with 1828 the local identifier. 1830 An entry in this table is created automatically when 1831 the Local identifier is associated with ICC in 1832 the mplsTunnelExtNodeConfigTable." 1833 INDEX { mplsTunnelExtNodeIccMapIccId } 1834 ::= { mplsTunnelExtNodeIccMapTable 1 } 1836 MplsTunnelExtNodeIccMapEntry ::= SEQUENCE { 1837 mplsTunnelExtNodeIccMapIccId MplsIccId, 1838 mplsTunnelExtNodeIccMapLocalId MplsExtendedTunnelId 1839 } 1841 mplsTunnelExtNodeIccMapIccId OBJECT-TYPE 1842 SYNTAX MplsIccId 1843 MAX-ACCESS not-accessible 1844 STATUS current 1845 DESCRIPTION 1846 "This object allows the operator or service provider to 1847 configure a unique MPLS-TP ITU-T Carrier Code (ICC) 1848 either for Ingress or Egress LSR ID. 1850 The ICC is a string of one to six characters, each 1851 character being either alphabetic (i.e. A-Z) or 1852 numeric (i.e. 0-9) characters. Alphabetic characters 1853 in the ICC should be represented with upper case 1854 letters." 1855 ::= { mplsTunnelExtNodeIccMapEntry 1 } 1857 mplsTunnelExtNodeIccMapLocalId OBJECT-TYPE 1858 SYNTAX MplsExtendedTunnelId 1859 MAX-ACCESS read-only 1860 STATUS current 1861 DESCRIPTION 1862 "This object contains an ICC based local identifier 1863 which is defined in mplsTunnelExtNodeConfigTable." 1865 ::= { mplsTunnelExtNodeIccMapEntry 2 } 1867 -- End MPLS Transport Profile Node ICC based table 1869 -- Start of MPLS Tunnel table extension 1871 mplsTunnelExtTable OBJECT-TYPE 1872 SYNTAX SEQUENCE OF MplsTunnelExtEntry 1873 MAX-ACCESS not-accessible 1874 STATUS current 1875 DESCRIPTION 1876 "This table represents extensions to mplsTunnelTable 1877 in order to support MPLS-TP tunnels. 1879 As per MPLS-TP Identifiers [RFC6370], LSP_ID for IP based 1880 co-routed bidirectional tunnel, 1882 A1-{Global_ID::Node_ID::Tunnel_Num}::Z9-{Global_ID:: 1883 Node_ID::Tunnel_Num}::LSP_Num 1885 LSP_ID for IP based associated bidirectional tunnel, 1886 A1-{Global_ID::Node_ID::Tunnel_Num::LSP_Num}:: 1887 Z9-{Global_ID::Node_ID::Tunnel_Num::LSP_Num} 1889 mplsTunnelTable is reused for forming the LSP_ID 1890 as follows, 1892 Source Tunnel_Num is mapped with mplsTunnelIndex, 1893 Source Node_ID is mapped with 1894 mplsTunnelIngressLSRId, Destination Node_ID is 1895 mapped with mplsTunnelEgressLSRId LSP_Num is mapped with 1896 mplsTunnelInstance. 1898 Source Global_Node_ID and/or ICC and Destination 1899 Global_Node_ID and/or ICC are maintained in the 1900 mplsTunnelExtNodeConfigTable and 1901 mplsTunnelExtNodeConfigLocalId is used to create an entry 1902 in mplsTunnelTable." 1903 REFERENCE 1904 "MPLS Transport Profile (MPLS-TP) Identifiers [RFC6370], 1905 Section 3 and 4." 1906 ::= { mplsTeExtObjects 4 } 1908 mplsTunnelExtEntry OBJECT-TYPE 1909 SYNTAX MplsTunnelExtEntry 1910 MAX-ACCESS not-accessible 1911 STATUS current 1912 DESCRIPTION 1913 "An entry in this table represents MPLS-TP 1914 specific additional tunnel configurations." 1915 INDEX { 1916 mplsTunnelIndex, 1917 mplsTunnelInstance, 1918 mplsTunnelIngressLSRId, 1919 mplsTunnelEgressLSRId 1920 } 1921 ::= { mplsTunnelExtTable 1 } 1923 MplsTunnelExtEntry ::= SEQUENCE { 1924 mplsTunnelExtOppositeDirPtr RowPointer, 1925 mplsTunnelExtOppositeDirTnlValid TruthValue, 1926 mplsTunnelExtDestTnlIndex MplsTunnelIndex, 1927 mplsTunnelExtDestTnlLspIndex MplsTunnelInstanceIndex, 1928 mplsTunnelExtDestTnlValid TruthValue, 1929 mplsTunnelExtIngressLSRLocalIdValid TruthValue, 1930 mplsTunnelExtEgressLSRLocalIdValid TruthValue 1932 } 1934 mplsTunnelExtOppositeDirPtr OBJECT-TYPE 1935 SYNTAX RowPointer 1936 MAX-ACCESS read-create 1937 STATUS current 1938 DESCRIPTION 1939 "This object is applicable only for the bidirectional 1940 tunnel that has the forward and reverse LSPs in the 1941 same tunnel or in the different tunnels. 1943 This object holds the opposite direction tunnel entry 1944 if the bidirectional tunnel is setup by configuring two 1945 tunnel entries in mplsTunnelTable. 1947 Note that there are two different ways to represent the 1948 opposite direction tunnel entry. One method is to use this 1949 object mplsTunnelExtOppositeDirPtr as RowPointer and make 1950 it point to the other direction tunnel. Other method is to 1951 use the mplsTunnelExtDestTnlIndex and 1952 mplsTunnelExtDestTnlLspIndex instead of using this 1953 mplsTunnelExtOppositeDirPtr. Implementation can choose 1954 either one of the method to represent the opposite 1955 direction tunnel. Duplicate methods are provided to provide 1956 easy ways for different implementations. 1958 The value of zeroDotZero indicates single tunnel entry 1959 is used for bidirectional tunnel setup." 1961 DEFVAL { zeroDotZero } 1962 ::= { mplsTunnelExtEntry 1 } 1964 mplsTunnelExtOppositeDirTnlValid OBJECT-TYPE 1965 SYNTAX TruthValue 1966 MAX-ACCESS read-create 1967 STATUS current 1968 DESCRIPTION 1969 "Denotes whether or not this tunnel uses 1970 mplsTunnelExtOppositeDirPtr for identifying the opposite 1971 direction tunnel information. Note that if this variable 1972 is set to true then the mplsTunnelExtOppositeDirPtr should 1973 point to the first accessible row of the opposite 1974 direction tunnel." 1975 DEFVAL { false } 1976 ::= { mplsTunnelExtEntry 2 } 1978 mplsTunnelExtDestTnlIndex OBJECT-TYPE 1979 SYNTAX MplsTunnelIndex 1980 MAX-ACCESS read-create 1981 STATUS current 1982 DESCRIPTION 1983 "This object is applicable only for the bidirectional 1984 tunnel that has the forward and reverse LSPs in the 1985 same tunnel or in the different tunnels. 1987 This object holds the same value as that of the 1988 mplsTunnelIndex of mplsTunnelEntry if the forward and 1989 reverse LSPs are in the same tunnel. Otherwise, 1990 this object holds the value of the other direction 1991 associated LSP's mplsTunnelIndex from a different 1993 tunnel. 1995 The values of this object and the 1996 mplsTunnelExtDestTnlLspIndex object together can be used 1997 to identify an opposite direction LSP i.e. if the 1998 mplsTunnelIndex and mplsTunnelInstance hold the value 1999 for forward LSP, this object and 2000 mplsTunnelExtDestTnlLspIndex can be used to retrieve 2001 the reverse direction LSP and vice versa. 2003 This object and mplsTunnelExtDestTnlLspIndex values 2004 provide the first two indices of tunnel entry and 2005 the remaining indices can be derived as follows, 2006 if both the forward and reverse LSPs are present in 2007 the same tunnel, the opposite direction LSP's Ingress 2008 and Egress Identifier will be same for both the LSPs, 2009 else the Ingress and Egress Identifiers should be 2010 swapped in order to index the other direction tunnel." 2012 ::= { mplsTunnelExtEntry 3 } 2014 mplsTunnelExtDestTnlLspIndex OBJECT-TYPE 2015 SYNTAX MplsTunnelInstanceIndex 2016 MAX-ACCESS read-create 2017 STATUS current 2018 DESCRIPTION 2019 "This object is applicable only for the bidirectional 2020 tunnel that has the forward and reverse LSPs in the 2021 same tunnel or in the different tunnels. 2023 This object should contain different value if both the 2024 forward and reverse LSPs present in the same tunnel. 2026 This object can contain same value or different values 2027 if the forward and reverse LSPs present in the different 2028 tunnels." 2030 ::= { mplsTunnelExtEntry 4 } 2032 mplsTunnelExtDestTnlValid OBJECT-TYPE 2033 SYNTAX TruthValue 2034 MAX-ACCESS read-create 2035 STATUS current 2036 DESCRIPTION 2037 "Denotes whether or not this tunnel uses 2038 mplsTunnelExtDestTnlIndex and 2039 mplsTunnelExtDestTnlLspIndex for identifying 2040 the opposite direction tunnel information. Note that if 2041 this variable is set to true then the 2042 mplsTunnelExtDestTnlIndex and 2043 mplsTunnelExtDestTnlLspIndex objects should have 2044 the valid opposite direction tunnel indices." 2045 DEFVAL { false } 2046 ::= { mplsTunnelExtEntry 5 } 2048 mplsTunnelExtIngressLSRLocalIdValid OBJECT-TYPE 2049 SYNTAX TruthValue 2050 MAX-ACCESS read-create 2051 STATUS current 2052 DESCRIPTION 2053 "This object denotes whether the mplsTunnelIngressLSRId 2054 contains the local value, which is used to reference 2055 the complete Ingress Global_ID::Node_ID or ICC from 2056 the mplsTunnelExtNodeConfigTable." 2057 REFERENCE 2058 "MPLS-TE-STD-MIB [RFC3812], Section 11. mplsTunnelIngressLSRId 2059 object in mplsTunnelTable. 2061 If this object is set to FALSE, mplsTunnelExtNodeConfigTable 2062 will not contain an entry to reference local identifier with 2063 Global_ID::Node_ID or ICC value. 2065 This object is set to FALSE for legacy implementations like 2066 MPLS TE tunnels where mplsTunnelIngressId itself provides 2067 complete Ingress LSRId." 2068 DEFVAL { false } 2069 ::= { mplsTunnelExtEntry 6 } 2071 mplsTunnelExtEgressLSRLocalIdValid OBJECT-TYPE 2072 SYNTAX TruthValue 2073 MAX-ACCESS read-create 2074 STATUS current 2075 DESCRIPTION 2076 "This object denotes whether the mplsTunnelEgressLSRId 2077 contains the local value, which is used to reference 2078 the complete Egress Global_ID::Node_ID or ICC from 2079 the mplsTunnelExtNodeConfigTable." 2080 REFERENCE 2081 "MPLS-TE-STD-MIB [RFC3812], Section 11. mplsTunnelEgressLSRId 2082 object in mplsTunnelTable. 2084 If this object is set to FALSE, mplsTunnelExtNodeConfigTable 2085 will not contain an entry to reference local identifier with 2086 Global_ID::Node_ID or ICC value. 2088 This object is set to FALSE for legacy implementations like 2089 MPLS TE tunnels where mplsTunnelEgressId itself provides 2090 complete Egress LSRId." 2091 DEFVAL { false } 2092 ::= { mplsTunnelExtEntry 7 } 2094 -- End of MPLS Tunnel table extension 2095 mplsTunnelExtReversePerfTable OBJECT-TYPE 2096 SYNTAX SEQUENCE OF MplsTunnelExtReversePerfEntry 2097 MAX-ACCESS not-accessible 2098 STATUS current 2099 DESCRIPTION 2100 "This table extends the mplsTunnelTable to provide 2101 per-tunnel packet performance information for the reverse 2102 direction of a bidirectional tunnel. It can be seen as 2103 supplementing the mplsTunnelPerfTable, which augments the 2104 mplsTunnelTable. 2106 For links that do not transport packets, these packet 2107 counters cannot be maintained. For such links, attempts 2108 to read the objects in this table will return 2109 noSuchInstance." 2110 REFERENCE 2111 "1. Multiprotocol Label Switching (MPLS) Traffic 2112 Engineering (TE)Management Information Base (MIB), 2113 RFC 3812. Section 6.6. mplsTunnelPerfTable" 2114 ::= { mplsTeExtObjects 5 } 2116 mplsTunnelExtReversePerfEntry OBJECT-TYPE 2117 SYNTAX MplsTunnelExtReversePerfEntry 2118 MAX-ACCESS not-accessible 2119 STATUS current 2120 DESCRIPTION 2121 "An entry in this table is created by the LSR for every 2122 bidirectional MPLS tunnel where packets are visible to the 2123 LSR." 2124 INDEX { 2125 mplsTunnelIndex, 2126 mplsTunnelInstance, 2127 mplsTunnelIngressLSRId, 2128 mplsTunnelEgressLSRId 2129 } 2130 ::= { mplsTunnelExtReversePerfTable 1 } 2132 MplsTunnelExtReversePerfEntry ::= SEQUENCE { 2133 mplsTunnelExtReversePerfPackets Counter32, 2134 mplsTunnelExtReversePerfHCPackets Counter64, 2135 mplsTunnelExtReversePerfErrors Counter32, 2136 mplsTunnelExtReversePerfBytes Counter32, 2137 mplsTunnelExtReversePerfHCBytes Counter64 2138 } 2140 mplsTunnelExtReversePerfPackets OBJECT-TYPE 2141 SYNTAX Counter32 2142 MAX-ACCESS read-only 2144 STATUS current 2145 DESCRIPTION 2146 "Number of packets forwarded on the tunnel in the reverse 2147 direction if it is bidirectional. 2149 This object represents the 32-bit value of the least 2150 significant part of the 64-bit value if both 2151 mplsTunnelExtReversePerfHCPackets and this object 2152 are returned. 2154 For links that do not transport packets, this packet 2155 counter cannot be maintained. For such links, this value 2156 will return noSuchInstance." 2157 ::= { mplsTunnelExtReversePerfEntry 1 } 2159 mplsTunnelExtReversePerfHCPackets OBJECT-TYPE 2160 SYNTAX Counter64 2161 MAX-ACCESS read-only 2162 STATUS current 2163 DESCRIPTION 2164 "High-capacity counter for number of packets forwarded on 2165 the tunnel in the reverse direction if it is 2166 bidirectional. 2168 For links that do not transport packets, this packet 2169 counter cannot be maintained. For such links, this value 2170 will return noSuchInstance." 2171 ::= { mplsTunnelExtReversePerfEntry 2 } 2173 mplsTunnelExtReversePerfErrors OBJECT-TYPE 2174 SYNTAX Counter32 2175 MAX-ACCESS read-only 2176 STATUS current 2177 DESCRIPTION 2178 "Number of errored packets received on the tunnel in 2179 the reverse direction if it is bidirectional. For links 2180 that do not transport packets, this packet counter cannot 2181 be maintained. For such links, this value will return 2182 noSuchInstance." 2183 ::= { mplsTunnelExtReversePerfEntry 3 } 2185 mplsTunnelExtReversePerfBytes OBJECT-TYPE 2186 SYNTAX Counter32 2187 MAX-ACCESS read-only 2188 STATUS current 2189 DESCRIPTION 2190 "Number of bytes forwarded on the tunnel in the reverse 2191 direction if it is bidirectional. 2193 This object represents the 32-bit value of the least 2194 significant part of the 64-bit value if both 2195 mplsTunnelExtReversePerfHCBytes and this object are returned. 2197 For links that do not transport packets, this packet 2198 counter cannot be maintained. For such links, this value 2199 will return noSuchInstance." 2200 ::= { mplsTunnelExtReversePerfEntry 4 } 2202 mplsTunnelExtReversePerfHCBytes OBJECT-TYPE 2203 SYNTAX Counter64 2204 MAX-ACCESS read-only 2205 STATUS current 2206 DESCRIPTION 2207 "High-capacity counter for number of bytes forwarded on the 2208 tunnel in the reverse direction if it is bidirectional. 2210 For links that do not transport packets, this packet 2211 counter cannot be maintained. For such links, this value 2212 will return noSuchInstance." 2213 ::= { mplsTunnelExtReversePerfEntry 5 } 2215 -- Notifications. 2216 -- Notification objects need to be added here. 2217 -- End of notifications. 2219 -- Module compliance. 2221 mplsTeExtGroups 2222 OBJECT IDENTIFIER ::= { mplsTeExtConformance 1 } 2224 mplsTeExtCompliances 2225 OBJECT IDENTIFIER ::= { mplsTeExtConformance 2 } 2227 -- Compliance requirement for fully compliant implementations. 2229 mplsTeExtModuleFullCompliance MODULE-COMPLIANCE 2230 STATUS current 2231 DESCRIPTION 2232 "Compliance statement for agents that provide full 2233 support the MPLS-TE-EXT-STD-MIB module." 2235 MODULE -- this module 2237 -- The mandatory group has to be implemented by all 2238 -- LSRs that originate/terminate MPLS-TP tunnels. 2239 -- In addition, depending on the type of tunnels 2240 -- supported, other groups become mandatory as 2241 -- explained below. 2243 MANDATORY-GROUPS { 2244 mplsTunnelExtGroup 2245 } 2247 GROUP mplsTunnelExtIpOperatorGroup 2249 DESCRIPTION 2250 "This group is mandatory for devices which support 2251 configuration of IP based identifier tunnels." 2253 GROUP mplsTunnelExtIccOperatorGroup 2255 DESCRIPTION 2256 "This group is mandatory for devices which support 2257 configuration of ICC based tunnels." 2259 ::= { mplsTeExtCompliances 1 } 2261 -- Compliance requirement for read-only implementations. 2263 mplsTeExtModuleReadOnlyCompliance MODULE-COMPLIANCE 2264 STATUS current 2265 DESCRIPTION 2266 "Compliance statement for agents that provide full 2267 support the MPLS-TE-EXT-STD-MIB module." 2269 MODULE -- this module 2271 -- The mandatory group has to be implemented by all 2272 -- LSRs that originate/terminate MPLS-TP tunnels. 2273 -- In addition, depending on the type of tunnels 2274 -- supported, other groups become mandatory as 2275 -- explained below. 2277 MANDATORY-GROUPS { 2278 mplsTunnelExtGroup 2279 } 2281 GROUP mplsTunnelExtIpOperatorGroup 2282 DESCRIPTION 2283 "This group is mandatory for devices which support 2284 configuration of IP based identifier tunnels." 2286 GROUP mplsTunnelExtIccOperatorGroup 2287 DESCRIPTION 2288 "This group is mandatory for devices which support 2289 configuration of ICC based tunnels." 2291 ::= { mplsTeExtCompliances 2 } 2293 -- Units of conformance. 2295 mplsTunnelExtGroup OBJECT-GROUP 2296 OBJECTS { 2297 mplsTunnelExtOppositeDirPtr, 2298 mplsTunnelExtOppositeDirTnlValid, 2299 mplsTunnelExtDestTnlIndex, 2300 mplsTunnelExtDestTnlLspIndex, 2301 mplsTunnelExtDestTnlValid, 2302 mplsTunnelExtIngressLSRLocalIdValid, 2303 mplsTunnelExtEgressLSRLocalIdValid, 2304 mplsTunnelExtReversePerfPackets, 2305 mplsTunnelExtReversePerfHCPackets, 2306 mplsTunnelExtReversePerfErrors, 2307 mplsTunnelExtReversePerfBytes, 2308 mplsTunnelExtReversePerfHCBytes 2309 } 2311 STATUS current 2312 DESCRIPTION 2313 "Necessary, but not sufficient, set of objects to 2314 implement tunnels. In addition, depending on the 2315 operating environment, the following groups are 2316 mandatory." 2317 ::= { mplsTeExtGroups 1 } 2319 mplsTunnelExtIpOperatorGroup OBJECT-GROUP 2320 OBJECTS { mplsTunnelExtNodeConfigGlobalId, 2321 mplsTunnelExtNodeConfigNodeId, 2322 mplsTunnelExtNodeConfigRowStatus, 2323 mplsTunnelExtNodeConfigStorageType, 2324 mplsTunnelExtNodeIpMapLocalId 2325 } 2326 STATUS current 2327 DESCRIPTION 2328 "Object(s) needed to implement IP compatible tunnels." 2329 ::= { mplsTeExtGroups 2 } 2331 mplsTunnelExtIccOperatorGroup OBJECT-GROUP 2332 OBJECTS { mplsTunnelExtNodeConfigIccId, 2333 mplsTunnelExtNodeConfigRowStatus, 2334 mplsTunnelExtNodeConfigStorageType, 2335 mplsTunnelExtNodeIccMapLocalId 2336 } 2337 STATUS current 2338 DESCRIPTION 2339 "Object(s) needed to implement ICC based tunnels." 2340 ::= { mplsTeExtGroups 3 } 2342 -- MPLS-TE-EXT-STD-MIB module ends 2343 END 2345 14. Security Consideration 2347 There is a number of management objects defined in this MIB module 2348 that has a MAX-ACCESS clause of read-write.. Such objects may be 2349 considered sensitive or vulnerable in some network environments. 2350 The support for SET operations in a non-secure environment without 2351 proper protection can have a negative effect on network 2352 operations. 2354 Some of the readable objects in this MIB module (i.e., objects 2355 with a MAX-ACCESS other than not-accessible) may be considered 2356 sensitive or vulnerable in some network environments. 2357 It is thus important to control even GET and/or NOTIFY access to 2358 these objects and possibly to even encrypt the values of these 2359 objects when sending them over the network via SNMP. These are 2360 the tables and objects and their sensitivity/vulnerability: 2362 SNMP versions prior to SNMPv3 did not include adequate security. 2363 Even if the network itself is secure (for example by using IPsec), 2364 even then, there is no control as to who on the secure network is 2365 allowed to access and GET/SET (read/change/create/delete) 2366 the objects in this MIB module. 2368 It is recommended that implementers consider the security features 2369 as provided by the SNMPv3 framework (see [RFC3410], section 8), 2370 including full supports for the SNMPv3 cryptographic mechanisms 2371 (for authentication and privacy). 2373 Further, deployment of SNMP versions prior to SNMPv3 is not 2374 recommended. Instead, it is recommended to deploy SNMPv3 and to 2375 enable cryptographic security. It is then a customer/operator 2376 responsibility to ensure that the SNMP entity giving access to an 2377 instance of this MIB module is properly configured to give 2378 access to the objects only to those principles (users) that 2379 have legitimate rights to indeed GET or SET (change/create/delete) 2380 them. 2382 15. IANA Considerations 2384 To be added in a later version of this document. 2386 16. References 2388 16.1. Normative References 2390 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 2391 Requirement Levels", BCP 14, RFC 2119, March 1997. 2393 [RFC2578] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 2394 "Structure of Management Information Version 2 (SMIv2)", 2395 STD 58, RFC 2578, April 1999. 2397 [RFC2579] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 2398 "Textual Conventions for SMIv2", STD 58, RFC 2579, April 2399 1999. 2401 [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 2403 "Conformance Statements for SMIv2", STD 58, RFC 2580, 2404 April 1999. 2406 [RFC3031] Rosen, E., Viswanathan, A., and R. Callon, "Multiprotocol 2407 Label Switching Architecture", RFC 3031, January 2001. 2409 16.2. Informative References 2411 [RFC3812] Srinivasan, C., Viswanathan, A., and T. Nadeau, 2412 "Multiprotocol Label Switching (MPLS) Traffic Engineering 2413 (TE) Management Information Base (MIB)", RFC 3812, June 2414 2004. 2416 [RFC3813] Srinivasan, C., Viswanathan, A., and T. Nadeau, 2417 "Multiprotocol Label Switching (MPLS) Label Switching 2418 (LSR) Router Management Information Base (MIB)", RFC 3813, 2419 June 2004. 2421 [RFC3410] J. Case, R. Mundy, D. pertain, B.Stewart, "Introduction 2422 and Applicability Statement for Internet Standard 2423 Management Framework", RFC 3410, December 2002. 2425 [RFC3811] Nadeau, T., Ed., and J. Cucchiara, Ed., "Definitions of 2426 Textual Conventions (TCs) for Multiprotocol Label 2427 Switching (MPLS) Management", RFC 3811, June 2004. 2429 [RFC4802] Nadeau, T., Ed., and A. Farrel, Ed., "Generalized 2430 Multiprotocol Label Switching (GMPLS) Traffic 2431 Engineering Management Information Base", RFC 2432 4802, February 2007. 2433 [RFC5654] Niven-Jenkins, B., Ed., Brungard, D., Ed., Betts, M., Ed., 2434 Sprecher, N., and S. Ueno, "Requirements of an MPLS 2435 Transport Profile", RFC 5654, September 2009. 2437 [RFC6370] Bocci, M., Swallow, G., and E. Gray, "MPLS Transport 2438 Profile (MPLS-TP) Identifiers", RFC 6370, September 2439 2011. 2441 [I-D.ietf-mpls-tp-itu-t-identifiers] Winter, R., Gray, E., Helvoort, 2442 H., and M. Betts, "MPLS-TP Identifiers Following ITU-T 2443 Conventions", draft-ietf-mpls-tp-itu-t-identifiers-07 2444 (work in progress), August 2012. 2446 17. Acknowledgments 2448 The authors would like to thank Francesco Fondelli, Josh Littlefield, 2449 Agrahara Kiran Koushik, Metrri Jain, Muly Ilan, Joan Cucchiara and 2450 Randy Presuhn for their valuable comments. 2452 18. Authors' Addresses 2454 Sam Aldrin 2455 Huawei Technologies 2456 2330 Central Express Way, 2457 Santa Clara, CA 95051, USA 2458 Email: aldrin.ietf@gmail.com 2460 Thomas D. Nadeau 2461 Juniper Networks 2462 10 Technology Park Drive, Westford, MA 01886 2463 Email: tnadeau@juniper.net 2465 Venkatesan Mahalingam 2466 Dell Inc. 2467 350 Holger way, San Jose, CA, USA 2468 Email: venkat.mahalingams@gmail.com 2470 Kannan KV Sampath 2471 Redeem 2472 India 2473 Email: kannankvs@gmail.com