idnits 2.17.1 draft-ietf-mpls-tp-te-mib-00.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 seems to use 'NOT RECOMMENDED' as an RFC 2119 keyword, but does not include the phrase in its RFC 2119 key words list. -- The document date (June 17, 2011) is 4695 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) == Missing Reference: 'RFC4802' is mentioned on line 154, but not defined == Missing Reference: 'RFC 3812' is mentioned on line 300, but not defined == Missing Reference: 'RFC 3813' is mentioned on line 991, but not defined == Outdated reference: A later version (-07) exists of draft-ietf-mpls-tp-identifiers-03 Summary: 0 errors (**), 0 flaws (~~), 6 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 Kannan KV Sampath 5 Expires: December 17, 2011 Aricent 6 Sam K. Aldrin 7 Huawei Technologies 8 Thomas D. Nadeau 9 CA Technologies 11 June 17, 2011 13 MPLS-TP Traffic Engineering (TE) Management Information Base (MIB) 14 draft-ietf-mpls-tp-te-mib-00.txt 16 Abstract 18 This memo defines a portion of the Management Information Base (MIB) 19 for use with network management protocols in the Internet community. 20 In particular, it describes managed objects of Tunnels, Identifiers, 21 Label Switch Router and Textual conventions for Multiprotocol Label 22 Switching (MPLS) based Transport Profile (TP). 24 Status of this Memo 26 This Internet-Draft is submitted to IETF in full conformance with the 27 provisions of BCP 78 and BCP 79. 29 Internet-Drafts are working documents of the Internet Engineering 30 Task Force (IETF), its areas, and its working groups. Note that 31 other groups may also distribute working documents as Internet- 32 Drafts. 34 Internet-Drafts are draft documents valid for a maximum of six months 35 and may be updated, replaced, or obsoleted by other documents at any 36 time. It is inappropriate to use Internet-Drafts as reference 37 material or to cite them other than as "work in progress." 39 The list of current Internet-Drafts can be accessed at 40 http://www.ietf.org/ietf/1id-abstracts.txt. 42 The list of Internet-Draft Shadow Directories can be accessed at 43 http://www.ietf.org/shadow.html. 45 This Internet-Draft will expire on December 17, 2011. 47 Copyright and License Notice 49 Copyright (c) 2011 IETF Trust and the persons identified as the 50 document authors. All rights reserved. 52 This document is subject to BCP 78 and the IETF Trust's Legal 53 Provisions Relating to IETF Documents 54 (http://trustee.ietf.org/license-info) in effect on the date of 55 publication of this document. Please review these documents 56 carefully, as they describe your rights and restrictions with respect 57 to this document. Code Components extracted from this document must 58 include Simplified BSD License text as described in Section 4.e of 59 the Trust Legal Provisions and are provided without warranty as 60 described in the Simplified BSD License. 62 Table of Contents 64 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 65 2. The Internet-Standard Management Framework . . . . . . . . . . 3 66 3. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 67 3.1 Conventions used in this document . . . . . . . . . . . . . 3 68 3.2 Terminology . . . . . . . . . . . . . . . . . . . . . . . . 3 69 3.3 Acronyms . . . . . . . . . . . . . . . . . . . . . . . . . . 3 70 4. Motivations . . . . . . . . . . . . . . . . . . . . . . . . . . 4 71 5. Feature List . . . . . . . . . . . . . . . . . . . . . . . . . 4 72 6. Brief description of MIB Objects . . . . . . . . . . . . . . . 4 73 6.1. mplsNodeConfigTable . . . . . . . . . . . . . . . . . . . 5 74 6.2. mplsNodeIpMapTable . . . . . . . . . . . . . . . . . . . . 5 75 6.3. mplsNodeIccMapTable . . . . . . . . . . . . . . . . . . . 6 76 6.4.mplsTunnelExtTable . . . . . . . . . . . . . . . . . . . . . 6 77 7. MIB Module Interdependencies . . . . . . . . . . . . . . . . . 6 78 8. Dependencies between MIB Module Tables . . . . . . . . . . . . 8 79 9. Example of MPLS-TP tunnel setup . . . . . . . . . . . . . . . . 8 80 10. MPLS Textual Convention Extension MIB definitions . . . . . . 13 81 11. MPLS Identifier MIB definitions . . . . . . . . . . . . . . . 16 82 12. MPLS LSR Extension MIB definitions . . . . . . . . . . . . . . 20 83 13. MPLS Tunnel Extension MIB definitions . . . . . . . . . . . . 24 84 14. Security Consideration . . . . . . . . . . . . . . . . . . . . 36 85 15. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 37 86 16. References . . . . . . . . . . . . . . . . . . . . . . . . . . 37 87 16.1 Normative References . . . . . . . . . . . . . . . . . . . 37 88 16.2 Informative References . . . . . . . . . . . . . . . . . . 38 89 17. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 38 90 18. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 38 92 1 Introduction 94 This memo defines a portion of the Management Information Base (MIB) 95 for use with network management protocols in the Internet community. 96 In particular, it describes managed objects of Tunnels, Identifiers, 97 Label Switch Router and Textual conventions for Multiprotocol Label 98 Switching (MPLS) based Transport Profile (TP). 100 This MIB module should be used in conjunction with the MPLS traffic 101 Engineering MIB [RFC3812] and companion document MPLS Label Switch 102 Router MIB [RFC3813] for MPLS based traffic engineering configuration 103 and management. 105 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 106 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 107 document are to be interpreted as described in BCP 14, RFC2119. 109 2. The Internet-Standard Management Framework 111 For a detailed overview of the documents that describe the current 112 Internet-Standard Management Framework, please refer to section 7 of 113 RFC3410 [RFC3410]. 115 Managed objects are accessed via a virtual information store, termed 116 the Management Information Base or MIB. MIB objects are generally 117 accessed through the Simple Network Management Protocol (SNMP). 118 Objects in the MIB are defined using the mechanisms defined in the 119 Structure of Management Information (SMI). This memo specifies a MIB 120 module that is compliant to the SMIv2, which is described in STD 58, 121 RFC2578, STD 58, RFC2579 and STD58, RFC2580. 123 3. Overview 125 3.1 Conventions used in this document 127 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 128 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 129 document are to be interpreted as described in RFC-2119 [RFC2119]. 131 3.2 Terminology 133 This document uses terminology from the MPLS architecture document 134 [RFC3031], MPLS Traffic Engineering Management information [RFC3812], 135 MPLS Label Switch Router MIB [RFC3813] and MPLS-TP Identifiers 136 document [TPIDS]. 138 3.3 Acronyms 139 GMPLS: Generalized Multi-Protocol Label Switching 140 ICC: ITU Carrier Code 141 IP: Internet Protocol 142 LSP: Label Switching Path 143 LSR: Label Switching Router 144 MIB: Management Information Base 145 MPLS: Multi-Protocol Label Switching 146 MPLS-TP: MPLS Transport Profile 147 OSPF: Open Shortest Path First 148 PW: Pseudowire 149 TE: Traffic Engineering 150 TP: Transport Profile 152 4. Motivations 154 The existing MPLS TE [RFC3812] and GMPLS MIBs [RFC4802] do not 155 support the transport network requirements of NON-IP based management 156 and static bidirectional tunnels. 158 5. Feature List 160 The MPLS transport profile MIB module is designed to satisfy the 161 following requirements and constraints: 163 The MIB module supports point-to-point, co-routed bi-directional 164 associated bi-directional tunnels. 166 - The MPLS tunnels need not be interfaces, but it is possible 167 to configure a TP tunnel as an interface. 169 - The mplsTunnelTable [RFC3812] to be also used for MPLS-TP 170 tunnels 172 - The mplsTunnelTable is extended to support MPLS-TP specific 173 objects. 175 - A node configuration table (mplsNodeConfigTable) is used to 176 translate the Global_Node_ID or ICC to the local identifier 177 in order to index mplsTunnelTable. 179 - The MIB module supports persistent, as well as non-persistent 180 tunnels. 182 6. Brief description of MIB Objects 184 The objects described in this section support the functionality 185 described in documents [RFC5654] and [TPIDS]. The tables support 186 both IP compatible and ICC based tunnel configurations. 188 6.1. mplsNodeConfigTable 190 The mplsNodeConfigTable is used to assign a local identifier for a 191 given ICC or Global_Node_ID combination as defined in [TPIDS]. 192 An ICC is a string of one to six characters, each character being 193 either alphabetic (i.e. A-Z) or numeric (i.e. 0-9) characters. 194 Alphabetic characters in the ICC should be represented 195 with upper case letters. In the IP compatible mode, 196 Global_Node_ID, is used to uniquely identify a node. 198 Each ICC or Global_Node_ID contains one unique entry in the 199 table representing a node. Every node is assigned a local identifier 200 within a range of 0 to 16777215. This local identifier is used for 201 indexing into mplsTunnelTable as mplsTunnelIngressLSRId and 202 mplsTunnelEgressLSRId. 204 For IP compatible environment, MPLS-TP tunnel is indexed by Tunnel 205 Index, Tunnel Instance, Source Global_ID, Source Node_ID, 206 Destination Global_ID and Destination Node_ID. 208 For ICC based environment, MPLS-TP tunnel is indexed by Tunnel 209 Index, Tunnel Instance, Source ICC and Destination ICC. 211 As mplsTunnelTable is indexed by mplsTunnelIndex, 212 mplsTunnelInstance, mplsTunnelIngressLSRId, and 213 mplsTunnelEgressLSRId, the MPLS-TP tunnel identifiers cannot be 214 used directly. 216 The mplsNodeConfigTable will be used to store an entry for ICC or 217 Global_Node_ID with a local identifier to be used as LSR ID 218 in mplsTunnelTable. As the regular TE tunnels use IP address as LSR 219 ID, the local identifier should be below the first valid IP address, 220 which is 16777216[1.0.0.0]. 222 6.2. mplsNodeIpMapTable 224 The read-only mplsNodeIpMaptable is used to query the local 225 identifier assigned and stored in mplsNodeConfigTable for a given 226 Global_Node_ID. In order to query the local identifier, 227 in the IP compatible mode, this table is indexed with Global_Node_ID. 228 In the IP compatible mode for a TP tunnel, Global_Node_ID 229 is used. 231 A separate query is made to get the local identifier of both 232 Ingress and Egress Global_Node_ID identifiers. These local 233 identifiers are used as mplsTunnelIngressLSRId and 234 mplsTunnelEgressLSRId, while indexing mplsTunnelTable. 236 6.3. mplsNodeIccMapTable 238 The read-only mplsNodeIccMapTable is used to query the local 239 identifier assigned and stored in the mplsNodeConfigTable 240 for a given ICC. 242 A separate query is made to get the local identifier of both 243 Ingress and Egress ICC. These local identifiers are used as 244 mplsTunnelIngressLSRId and mplsTunnelEgressLSRId, 245 while indexing mplsTunnelTable. 247 6.4.mplsTunnelExtTable 249 mplsTunnelExtTable extends the mplsTunnelTable to add MPLS-TP tunnel 250 specific additional objects. All the additional attributes specific 251 to TP tunnel are contained in this extended table and could be 252 accessed with the mplsTunnelTable indices. 254 7. MIB Module Interdependencies 256 This section provides an overview of the relationship between the 257 MPLS-TP TE MIB module and other MPLS MIB modules. 259 The arrows in the following diagram show a 'depends on' 260 relationship. A relationship "MIB module A depends on MIB module B" 261 means that MIB module A uses an object, object identifier, or 262 textual convention defined in MIB module B, or that MIB module A 263 contains a pointer (index or RowPointer) to an object in 264 MIB module B. 266 MPLS-TC-EXT-STD-MIB 267 ^ 268 | 269 | 270 +<---- MPLS-ID-STD-MIB 271 ^ 272 | | 273 +<---- MPLS-TE-EXT-STD-MIB 274 | | 275 | V 276 | MPLS-TE-STD-MIB 277 | | 278 | | 279 | V 280 | MPLS-LSR-STD-MIB 281 | ^ 282 | | 283 | | 284 +------MPLS-LSR-EXT-STD-MIB 286 Thus: 288 - All the new MPLS extension MIB modules depend on 289 MPLS-TC-EXT-STD-MIB. 291 - MPLS-TE-STD-MIB [RFC3812] contains references to objects in 292 MPLS-ID-STD-MIB. 294 - MPLS-TE-EXT-STD-MIB contains references to objects in 295 MPLS-TE-STD-MIB [RFC3812]. 297 - MPLS-LSR-EXT-STD-MIB contains references to objects in 298 MPLS-LSR-STD-MIB [RFC3813]. 300 MPLS-TE-STD-MIB [RFC 3812] is extended by MPLS-TE-EXT-STD-MIB 301 mib module for associating the reverse direction tunnel 302 information. 304 Note that the nature of the 'extends' relationship 305 is a sparse augmentation so that the entry in the 306 mplsTunnelExtTable has the same index values as the in the 307 mplsTunnelTable. 309 MPLS-LSR-STD-MIB [RFC 3813] is extended by MPLS-LSR-EXT-STD-MIB 310 mib module for pointing back to the tunnel entry for easy tunnel 311 access from XC entry. 313 Note that the nature of the 'extends' relationship 314 is a sparse augmentation so that the entry in the 315 mplsXCExtTable has the same index values as the in the mplsXCTable. 317 8. Dependencies between MIB Module Tables 319 The tables in MPLS-TE-EXT-STD-MIB are related as shown on the diagram 320 below. The arrows indicate a reference from one table to another. 322 mplsNodeConfigTable 323 ^ mplsXCExtTable 324 | | ^ 325 | +---------+ | 326 | | | 327 | V V 328 mplsTunnelTable ---->mplsXCTable 329 ^ 330 | 331 | 332 mplsTunnelExtTable 334 An existing mplsTunnelTable uses the new mplsNodeConfigTable table 335 to map the Global_Node_ID and/or ICC with the local number in order 336 to accommodate in the existing tunnel table's ingress/egress LSR-id. 338 New mplsTunnelExtTable table provides the reverse direction LSP 339 information for the existing tunnel table in order to achieve 340 bidirectional LSPs. 342 mplsXCExtTable is extended from mplsLsrXCTable to provide 343 backward reference to tunnel entry. 345 9. Example of MPLS-TP tunnel setup 347 In this section, we provide an example of the IP based MPLS-TP 348 co-routed bidirectional tunnel setup. This example provides 349 the usage of MPLS-TP Tunnel MIB along with the extended new MIB 350 modules introduced in this document. 352 Do note that a MPLS-TP tunnel could be setup statically as well as 353 signaled via control plane. This example considers configuration 354 on a head-end LSR to setup a static MPLS-TP tunnel. Only relevant 355 objects which are applicable for MPLS-TP tunnel are illustrated here. 357 In mplsNodeConfigTable: 359 { 360 -- Non-IP Ingress LSR-Id (Index to the table) 361 mplsNodeConfigLocalId = 1, 362 mplsNodeConfigGlobalId = 1234, 363 mplsNodeConfigNodeId = 10, 364 -- Mandatory parameters needed to activate the row go here 365 mplsNodeConfigRowStatus = createAndGo (4) 367 -- Non-IP Egress LSR-Id (Index to the table) 368 mplsNodeConfigLocalId = 2, 369 mplsNodeConfigGlobalId = 1234, 370 mplsNodeConfigNodeId = 20, 371 -- Mandatory parameters needed to activate the row go here 372 mplsNodeConfigRowStatus = createAndGo (4) 373 } 375 This will create an entry in the mplsNodeConfigTable for a 376 Global_Node_ID. A separate entry is made for both Ingress LSR 377 and Egress LSR. 379 The following read-only mplsNodeIpMapTable table is populated 380 automatically upon creating an entry in mplsNodeConfigTable and 381 this table is used to retrieve the local identifier for the given 382 Global_Node_ID. 384 In mplsNodeIpMapTable: 386 { 387 -- Global_ID (Index to the table) 388 mplsNodeIpMapGlobalId = 1234, 389 -- Node Identifier (Index to the table) 390 mplsNodeIpMapNodeId = 10, 391 mplsNodeIpMapLocalId = 1 393 -- Global_ID (Index to the table) 394 mplsNodeIpMapGlobalId = 1234, 395 -- Node Identifier (Index to the table) 396 mplsNodeIpMapNodeId = 20, 397 mplsNodeIpMapLocalId = 2 398 } 400 The following denotes the configured tunnel "head" entry: 402 In mplsTunnelTable: 404 { 405 mplsTunnelIndex = 1, 406 mplsTunnelInstance = 1, 407 -- Local map number created in mplsNodeConfigTable for Ingress 408 LSR-Id 409 mplsTunnelIngressLSRId = 1, 411 -- Local map number created in mplsNodeConfigTable for Egress 412 LSR-Id 413 mplsTunnelEgressLSRId = 2, 414 mplsTunnelName = "TP forward LSP", 415 mplsTunnelDescr = "East to West", 416 mplsTunnelIsIf = true (1), 417 -- RowPointer MUST point to the first accessible column 418 mplsTunnelXCPointer = 419 mplsXCLspId.4.0.0.0.1.1.0.4.0.0.0.12, 420 mplsTunnelSignallingProto = none (1), 421 mplsTunnelSetupPrio = 0, 422 mplsTunnelHoldingPrio = 0, 423 mplsTunnelSessionAttributes = 0, 424 mplsTunnelLocalProtectInUse = false (0), 425 -- RowPointer MUST point to the first accessible column 426 mplsTunnelResourcePointer = mplsTunnelResourceMaxRate.5, 427 mplsTunnelInstancePriority = 1, 428 mplsTunnelHopTableIndex = 1, 429 mplsTunnelIncludeAnyAffinity = 0, 430 mplsTunnelIncludeAllAffinity = 0, 431 mplsTunnelExcludeAnyAffinity = 0, 432 mplsTunnelRole = head (1), 433 -- Mandatory parameters needed to activate the row go here 434 mplsTunnelRowStatus = createAndGo (4) 435 } 437 In mplsTunnelTable: 439 { 440 mplsTunnelIndex = 1, 441 mplsTunnelInstance = 2, 442 -- Local map number created in mplsNodeConfigTable for Ingress 443 LSR-Id 444 mplsTunnelIngressLSRId = 1, 445 -- Local map number created in mplsNodeConfigTable for Egress 446 LSR-Id 447 mplsTunnelEgressLSRId = 2, 448 mplsTunnelName = "TP reverse LSP", 449 mplsTunnelDescr = "West to East", 450 mplsTunnelIsIf = true (1), 451 -- RowPointer MUST point to the first accessible column 452 mplsTunnelXCPointer = 453 mplsXCLspId.4.0.0.0.1.4.0.0.0.16.1.0, 454 mplsTunnelSignallingProto = none (1), 455 mplsTunnelSetupPrio = 0, 456 mplsTunnelHoldingPrio = 0, 457 mplsTunnelSessionAttributes = 0, 458 mplsTunnelLocalProtectInUse = false (0), 460 -- RowPointer MUST point to the first accessible column 461 mplsTunnelResourcePointer = mplsTunnelResourceMaxRate.5, 462 mplsTunnelInstancePriority = 1, 463 mplsTunnelHopTableIndex = 1, 464 mplsTunnelIncludeAnyAffinity = 0, 465 mplsTunnelIncludeAllAffinity = 0, 466 mplsTunnelExcludeAnyAffinity = 0, 467 mplsTunnelRole = head (1), 468 -- Mandatory parameters needed to activate the row go here 469 mplsTunnelRowStatus = createAndGo (4) 470 } 472 Now the TP specific Tunnel parameters are configured in 473 the extended Tunnel table 475 In mplsTunnelExtTable: 476 { 477 Index = same as one used for mplsTunnelTable, 478 -- As per [TPIDS] LSP_ID is defined as follows, 479 -- For corouted bidirectional tunnel 480 -- LSP_ID => East-Global_Node_ID::East-Tunnel_Num:: 481 -- West-Global_Node_ID::West-Tunnel_Num::LSP_Num 482 -- LSP_ID of this tunnel: 1234_10::1::1234_20::1::0 483 -- Where, 484 -- LSP_Num - 0 indicates the configured head end tunnel. 486 -- West tunnel number is assigned in the destination 487 -- tunnel index, 488 -- single LSP number is common for both forward and reverse 489 -- directions, as the single tunnel head entry originates 490 -- both the forward and reverse LSPs. 491 -- mplsTunnelExtDestTnlIndex = West-Tunnel_Num 492 -- mplsTunnelExtDestTnlLspIndex = LSP_Num 494 mplsTunnelExtDestTnlIndex = 1, 495 mplsTunnelExtDestTnlLspIndex = 0 497 -- For associated bidirectional tunnel 498 -- LSP_ID => East-Global_Node_ID::East-Tunnel_Num:: 499 -- East-LSP_Num::West-Global_Node_ID:: 500 -- West-Tunnel_Num::West-LSP_Num 501 -- West tunnel number is assigned in the destination 502 -- tunnel index, since the head end tunnel is different for 503 -- both the forward and reverse direction LSPs, 504 -- Destination LSP index points the reverse direction LSP 505 -- in a different tunnel. 506 -- mplsTunnelExtDestTnlIndex = West-Tunnel_Num 507 -- mplsTunnelExtDestTnlLspIndex = West-LSP_Num 509 } 511 We must next create the appropriate in-segment and out-segment 512 entries. These are done in [RFC3813] using the mplsInSegmentTable 513 and mplsOutSegmentTable. 515 For the forward direction. 517 In mplsOutSegmentTable: 518 { 519 mplsOutSegmentIndex = 0x00000012, 520 mplsOutSegmentInterface = 13, -- outgoing interface 521 mplsOutSegmentPushTopLabel = true(1), 522 mplsOutSegmentTopLabel = 22, -- outgoing label 524 -- RowPointer MUST point to the first accessible column. 525 mplsOutSegmentTrafficParamPtr = 0.0, 526 mplsOutSegmentRowStatus = createAndGo (4) 527 } 529 For the reverse direction. 531 In mplsInSegmentTable: 532 { 533 mplsInSegmentIndex = 0x00000016 534 mplsInSegmentLabel = 21, -- incoming label 535 mplsInSegmentNPop = 1, 536 mplsInSegmentInterface = 13, -- incoming interface 538 -- RowPointer MUST point to the first accessible column. 539 mplsInSegmentTrafficParamPtr = 0.0, 540 mplsInSegmentRowStatus = createAndGo (4) 541 } 543 Next, two cross-connect entries are created in the mplsXCTable of 544 the MPLS-LSR-STD-MIB [RFC3813], thereby associating the newly 545 created segments together. 547 In mplsXCTable: 548 { 549 mplsXCIndex = 0x01, 550 mplsXCInSegmentIndex = 0x00000000, 551 mplsXCOutSegmentIndex = 0x00000012, 552 mplsXCLspId = 0x0102 -- unique ID 553 -- only a single outgoing label 554 mplsXCLabelStackIndex = 0x00, 555 mplsXCRowStatus = createAndGo(4) 557 } 559 In mplsXCTable: 560 { 561 mplsXCIndex = 0x01, 562 mplsXCInSegmentIndex = 0x00000016, 563 mplsXCOutSegmentIndex = 0x00000000, 564 mplsXCLspId = 0x0102 -- unique ID 565 -- only a single outgoing label 566 mplsXCLabelStackIndex = 0x00, 567 mplsXCRowStatus = createAndGo(4) 568 } 570 This table entry is extended by entry in the 571 mplsXCExtTable. Note that the nature of the 'extends' 572 relationship is a sparse augmentation so that the entry in the 573 mplsXCExtTable has the same index values as the entry in 574 the mplsXCTable. 576 First for the forward direction: 578 In mplsXCExtTable 579 { 580 -- Back pointer from XC table to Tunnel table 581 mplsXCExtTunnelPointer = mplsTunnelName.1.1.1.2 582 } 584 Next for the reverse direction: 586 In mplsXCExtTable 587 { 588 -- Back pointer from XC table to Tunnel table 589 mplsXCExtTunnelPointer = mplsTunnelName.1.2.1.2 590 } 592 10. MPLS Textual Convention Extension MIB definitions 594 MPLS-TC-EXT-STD-MIB DEFINITIONS ::= BEGIN 596 IMPORTS 597 MODULE-IDENTITY, Unsigned32 598 FROM SNMPv2-SMI -- [RFC2578] 600 TEXTUAL-CONVENTION 601 FROM SNMPv2-TC -- [RFC2579] 603 mplsStdMIB 604 FROM MPLS-TC-STD-MIB -- [RFC3811] 606 ; 608 mplsTcExtStdMIB MODULE-IDENTITY 610 LAST-UPDATED 611 "201106160000Z" -- June 16, 2011 612 ORGANIZATION 613 "Multiprotocol Label Switching (MPLS) Working Group" 614 CONTACT-INFO 615 " 616 Venkatesan Mahalingam 617 Aricent, 618 India 619 Email: venkatesan.mahalingam@aricent.com 621 Kannan KV Sampath 622 Aricent, 623 India 624 Email: Kannan.Sampath@aricent.com 626 Sam Aldrin 627 Huawei Technologies 628 2330 Central Express Way, 629 Santa Clara, CA 95051, USA 630 Email: aldrin.ietf@gmail.com 632 Thomas D. Nadeau 633 CA Technologies 634 273 Corporate Drive, Portsmouth, NH, USA 635 Email: thomas.nadeau@ca.com 636 " 637 DESCRIPTION 638 "Copyright (c) 2011 IETF Trust and the persons identified 639 as the document authors. All rights reserved. 641 This MIB module contains Textual Conventions for 642 MPLS based transport networks." 644 -- Revision history. 646 REVISION 647 "201106160000Z" -- June 16, 2011 648 DESCRIPTION 649 "MPLS Textual Convention Extensions" 651 ::= { mplsStdMIB xxx } -- xxx to be replaced with correct value 653 MplsGlobalId ::= TEXTUAL-CONVENTION 654 STATUS current 655 DESCRIPTION 656 "This object contains the Textual Convention of IP based 657 operator unique identifier (Global_ID), the Global_ID 659 can contain the 2-octet or 4-octet value of the operator's 660 Autonomous System Number (ASN). 662 It is expected that the Global_ID will be derived from 663 the globally unique ASN of the autonomous system hosting 664 the PEs containing the actual AIIs. 665 The presence of a Global_ID based on the operator's 666 ASN ensures that the AII will be globally unique. 668 When the Global_ID is derived from a 2-octet AS number, 669 the two high-order octets of this 4-octet identifier 670 MUST be set to zero. 671 Further ASN 0 is reserved. A Global_ID of zero means that 672 no Global_ID is present. Note that a Global_ID of zero 673 is limited to entities contained within a single operator 674 and MUST NOT be used across an NNI. 675 A non-zero Global_ID MUST be derived from an ASN owned by 676 the operator." 677 SYNTAX OCTET STRING (SIZE (4)) 679 MplsNodeId ::= TEXTUAL-CONVENTION 680 DISPLAY-HINT "d" 681 STATUS current 682 DESCRIPTION 683 "The Node_ID is assigned within the scope of the Global_ID. 684 The value 0(or 0.0.0.0 in dotted decimal notation) is 685 reserved and MUST NOT be used. 687 When IPv4 addresses are in use, the value of this object 688 can be derived from the LSR's /32 IPv4 loop back address. 690 Note that, when IP reach ability is not needed, the 32-bit 691 Node_ID is not required to have any association 692 with the IPv4 address space." 693 SYNTAX Unsigned32 695 MplsIccId ::= TEXTUAL-CONVENTION 696 STATUS current 697 DESCRIPTION 698 "The ICC is a string of one to six characters, each 699 character being either alphabetic (i.e. A-Z) or 700 numeric (i.e. 0-9) characters. 701 Alphabetic characters in the ICC SHOULD be represented 702 with upper case letters." 703 SYNTAX OCTET STRING (SIZE (1..6)) 705 MplsLocalId ::= TEXTUAL-CONVENTION 706 DISPLAY-HINT "d" 707 STATUS current 708 DESCRIPTION 709 "This textual convention is used in accommodating the bigger 710 size Global_Node_ID and/or ICC with lower size LSR identifier 711 in order to index the mplsTunnelTable. 713 The Local Identifier is configured between 1 and 16777215, 714 as valid IP address range starts from 16777216 (01.00.00.00). 715 This range is chosen to identify the mplsTunnelTable's 716 Ingress/Egress LSR-id is IP address or Local identifier, 717 if the configured range is not IP address, administrator is 718 expected to retrieve the complete information (Global_Node_ID 719 or ICC) from mplsNodeConfigTable. This way, existing 720 mplsTunnelTable is reused for bidirectional tunnel extensions 721 for MPLS based transport networks. 723 This Local Identifier allows the administrator to assign 724 a unique identifier to map Global_Node_ID and/or ICC." 725 SYNTAX Unsigned32(1..16777215) 727 -- MPLS-TC-EXT-STD-MIB module ends 728 END 730 11. MPLS Identifier MIB definitions 732 MPLS-ID-STD-MIB DEFINITIONS ::= BEGIN 734 IMPORTS 735 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE 736 FROM SNMPv2-SMI -- [RFC2578] 737 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 738 FROM SNMPv2-CONF -- [RFC2580] 739 mplsStdMIB 740 FROM MPLS-TC-STD-MIB -- [RFC3811] 741 MplsGlobalId, MplsIccId, MplsNodeId 742 FROM MPLS-TC-EXT-STD-MIB 743 ; 745 mplsIdStdMIB MODULE-IDENTITY 746 LAST-UPDATED 747 "201106160000Z" -- June 16, 2011 748 ORGANIZATION 749 "Multiprotocol Label Switching (MPLS) Working Group" 751 CONTACT-INFO 752 " 753 Venkatesan Mahalingam 754 Aricent, 755 India 757 Email: venkatesan.mahalingam@aricent.com 759 Kannan KV Sampath 760 Aricent, 761 India 762 Email: Kannan.Sampath@aricent.com 764 Sam Aldrin 765 Huawei Technologies 766 2330 Central Express Way, 767 Santa Clara, CA 95051, USA 768 Email: aldrin.ietf@gmail.com 770 Thomas D. Nadeau 771 CA Technologies 772 273 Corporate Drive, Portsmouth, NH, USA 773 Email: thomas.nadeau@ca.com 774 " 775 DESCRIPTION 776 "Copyright (c) 2011 IETF Trust and the persons identified 777 as the document authors. All rights reserved. 779 This MIB module contains generic object definitions for 780 MPLS Traffic Engineering in transport networks." 782 -- Revision history. 784 REVISION 785 "201106160000Z" -- June 16, 2011 786 DESCRIPTION 787 "MPLS identifiers mib object extension" 789 ::= { mplsStdMIB xxx } -- xxx to be replaced with correct value 791 -- traps 792 mplsIdNotifications OBJECT IDENTIFIER ::= { mplsIdStdMIB 0 } 793 -- tables, scalars 794 mplsIdObjects OBJECT IDENTIFIER ::= { mplsIdStdMIB 1 } 795 -- conformance 796 mplsIdConformance OBJECT IDENTIFIER ::= { mplsIdStdMIB 2 } 797 -- MPLS common objects 799 mplsGlobalId OBJECT-TYPE 800 SYNTAX MplsGlobalId 801 MAX-ACCESS read-write 802 STATUS current 803 DESCRIPTION 805 "This object allows the administrator to assign a unique 806 operator identifier also called MPLS-TP Global_ID." 807 REFERENCE 808 "MPLS-TP Identifiers [TPIDS]." 809 ::= { mplsIdObjects 1 } 811 mplsIcc OBJECT-TYPE 812 SYNTAX MplsIccId 813 MAX-ACCESS read-write 814 STATUS current 815 DESCRIPTION 816 "This object allows the operator or service provider to 817 assign a unique MPLS-TP ITU-T Carrier Code (ICC) to a 818 network." 819 REFERENCE 820 "MPLS-TP Identifiers [TPIDS]." 821 ::= { mplsIdObjects 2 } 823 mplsNodeId OBJECT-TYPE 824 SYNTAX MplsNodeId 825 MAX-ACCESS read-write 826 STATUS current 827 DESCRIPTION 828 "This object allows the operator or service provider to 829 assign a unique MPLS-TP Node_ID. 831 The Node_ID is assigned within the scope of the 832 Global_ID." 834 REFERENCE 835 "MPLS-TP Identifiers [TPIDS]." 836 ::= { mplsIdObjects 3 } 838 -- Module compliance. 840 mplsIdGroups 841 OBJECT IDENTIFIER ::= { mplsIdConformance 1 } 843 mplsIdCompliances 844 OBJECT IDENTIFIER ::= { mplsIdConformance 2 } 846 -- Compliance requirement for fully compliant implementations. 848 mplsIdModuleFullCompliance MODULE-COMPLIANCE 849 STATUS current 850 DESCRIPTION 851 "Compliance statement for agents that provide full 852 support the MPLS-ID-STD-MIB module." 854 MODULE -- this module 856 -- The mandatory group has to be implemented by all 857 -- LSRs that originate/terminate MPLS-TP paths. 859 MANDATORY-GROUPS { 860 mplsIdScalarGroup 861 } 863 ::= { mplsIdCompliances 1 } 865 -- Compliance requirement for read-only implementations. 867 mplsIdModuleReadOnlyCompliance MODULE-COMPLIANCE 868 STATUS current 869 DESCRIPTION 870 "Compliance statement for agents that provide full 871 support the MPLS-ID-STD-MIB module." 873 MODULE -- this module 875 -- The mandatory group has to be implemented by all 876 -- LSRs that originate/terminate MPLS-TP paths. 878 MANDATORY-GROUPS { 879 mplsIdScalarGroup 880 } 882 ::= { mplsIdCompliances 2 } 884 -- Units of conformance. 886 mplsIdScalarGroup OBJECT-GROUP 887 OBJECTS { mplsGlobalId, 888 mplsNodeId, 889 mplsIcc 891 } 892 STATUS current 893 DESCRIPTION 894 "Scalar object needed to implement MPLS TP path." 895 ::= { mplsIdGroups 1 } 897 -- MPLS-ID-STD-MIB module ends 898 END 900 12. MPLS LSR Extension MIB definitions 902 MPLS-LSR-EXT-STD-MIB DEFINITIONS ::= BEGIN 904 IMPORTS 905 MODULE-IDENTITY, OBJECT-TYPE 906 FROM SNMPv2-SMI -- [RFC2578] 907 MODULE-COMPLIANCE, OBJECT-GROUP 908 FROM SNMPv2-CONF -- [RFC2580] 909 mplsStdMIB 910 FROM MPLS-TC-STD-MIB -- [RFC3811] 911 RowPointer 912 FROM SNMPv2-TC -- [RFC2579] 913 mplsXCIndex, mplsXCInSegmentIndex, mplsXCOutSegmentIndex, 914 mplsInSegmentGroup, mplsOutSegmentGroup, mplsXCGroup, 915 mplsPerfGroup, mplsLsrNotificationGroup 916 FROM MPLS-LSR-STD-MIB; -- [RFC3813] 918 mplsLsrExtStdMIB MODULE-IDENTITY 919 LAST-UPDATED 920 "201106160000Z" -- June 16, 2011 921 ORGANIZATION 922 "Multiprotocol Label Switching (MPLS) Working Group" 923 CONTACT-INFO 924 " 925 Venkatesan Mahalingam 926 Aricent, 927 India 928 Email: venkatesan.mahalingam@aricent.com 930 Kannan KV Sampath 931 Aricent, 932 India 933 Email: Kannan.Sampath@aricent.com 935 Sam Aldrin 936 Huawei Technologies 937 2330 Central Express Way, 938 Santa Clara, CA 95051, USA 940 Email: aldrin.ietf@gmail.com 942 Thomas D. Nadeau 943 CA Technologies 944 273 Corporate Drive, Portsmouth, NH, USA 945 Email: thomas.nadeau@ca.com 946 " 947 DESCRIPTION 948 "Copyright (c) 2011 IETF Trust and the persons identified 949 as the document authors. All rights reserved. 951 This MIB module contains generic object definitions for 952 MPLS LSR in transport networks." 954 -- Revision history. 956 REVISION 957 "201106160000Z" -- June 16, 2011 958 DESCRIPTION 959 "MPLS LSR specific mib objects extension" 961 ::= { mplsStdMIB xxx } -- xxx to be replaced with correct value 963 -- traps 964 mplsLsrExtNotifications OBJECT IDENTIFIER ::= { mplsLsrExtStdMIB 0 } 965 -- tables, scalars 966 mplsLsrExtObjects OBJECT IDENTIFIER ::= { mplsLsrExtStdMIB 1 } 967 -- conformance 968 mplsLsrExtConformance OBJECT IDENTIFIER ::= { mplsLsrExtStdMIB 2 } 970 -- MPLS LSR common objects 971 mplsXCExtTable OBJECT-TYPE 972 SYNTAX SEQUENCE OF MplsXCExtEntry 973 MAX-ACCESS not-accessible 974 STATUS current 975 DESCRIPTION 976 "This table sparse augments the mplsXCTable of 977 MPLS-LSR-STD-MIB [RFC 3813] to provide MPLS-TP specific 978 information about associated tunnel information" 979 REFERENCE 980 "1. Multiprotocol Label Switching (MPLS) Label Switching 981 Router (LSR) Management Information Base (MIB), RFC 3813." 982 ::= { mplsLsrExtObjects 1 } 984 mplsXCExtEntry OBJECT-TYPE 985 SYNTAX MplsXCExtEntry 986 MAX-ACCESS not-accessible 987 STATUS current 988 DESCRIPTION 989 "An entry in this table extends the cross connect 990 information represented by an entry in 991 the mplsXCTable in MPLS-LSR-STD-MIB [RFC 3813] through 992 a sparse augmentation. An entry can be created by a network 993 administrator via SNMP SET commands, or in 994 response to signaling protocol events." 995 REFERENCE 996 "1. Multiprotocol Label Switching (MPLS) Label Switching 997 Router (LSR) Management Information Base (MIB), RFC 3813." 998 INDEX { mplsXCIndex, mplsXCInSegmentIndex, 999 mplsXCOutSegmentIndex } 1000 ::= { mplsXCExtTable 1 } 1002 MplsXCExtEntry ::= SEQUENCE { 1003 mplsXCExtTunnelPointer RowPointer 1004 } 1006 mplsXCExtTunnelPointer OBJECT-TYPE 1007 SYNTAX RowPointer 1008 MAX-ACCESS read-create 1009 STATUS current 1010 DESCRIPTION 1011 "This object indicates the back pointer to the tunnel entry 1012 segment. This object cannot be modified if 1013 mplsXCRowStatus for the corresponding entry in the 1014 mplsXCTable is active(1)." 1015 REFERENCE 1016 "1. Multiprotocol Label Switching (MPLS) Label Switching 1017 Router (LSR) Management Information Base (MIB), RFC 3813." 1018 ::= { mplsXCExtEntry 1 } 1020 mplsLsrExtGroups 1021 OBJECT IDENTIFIER ::= { mplsLsrExtConformance 1 } 1022 mplsLsrExtCompliances 1023 OBJECT IDENTIFIER ::= { mplsLsrExtConformance 2 } 1025 -- Compliance requirement for fully compliant implementations. 1027 mplsLsrExtModuleFullCompliance MODULE-COMPLIANCE 1028 STATUS current 1029 DESCRIPTION 1030 "Compliance statement for agents that provide full support 1031 for MPLS-LSR-EXT-STD-MIB. 1033 The mandatory group has to be implemented by all LSRs that 1034 originate, terminate, or act as transit for TE-LSPs/tunnels. 1036 In addition, depending on the type of tunnels supported, 1037 other groups become mandatory as explained below." 1039 MODULE MPLS-LSR-STD-MIB -- The MPLS-LSR-STD-MIB, RFC3813 1041 MANDATORY-GROUPS { 1042 mplsInSegmentGroup, 1043 mplsOutSegmentGroup, 1044 mplsXCGroup, 1045 mplsPerfGroup, 1046 mplsLsrNotificationGroup 1047 } 1049 MODULE -- this module 1051 MANDATORY-GROUPS { 1052 mplsXCExtGroup 1053 } 1055 OBJECT mplsXCExtTunnelPointer 1056 SYNTAX RowPointer 1057 MIN-ACCESS read-only 1058 DESCRIPTION 1059 "The only valid value for Tunnel Pointer is mplsTunnelTable 1060 entry." 1062 ::= { mplsLsrExtCompliances 1 } 1064 -- Compliance requirement for implementations that provide read-only 1065 -- access. 1067 mplsLsrExtModuleReadOnlyCompliance MODULE-COMPLIANCE 1068 STATUS current 1069 DESCRIPTION 1070 "Compliance requirement for implementations that only provide 1071 read-only support for MPLS-LSR-EXT-STD-MIB. Such devices can 1072 then be monitored but cannot be configured using this 1073 MIB module." 1075 MODULE MPLS-LSR-STD-MIB 1077 MANDATORY-GROUPS { 1078 mplsInterfaceGroup, 1079 mplsInSegmentGroup, 1080 mplsOutSegmentGroup, 1081 mplsXCGroup, 1082 mplsPerfGroup 1083 } 1085 MODULE -- this module 1087 MANDATORY-GROUPS { 1088 mplsXCExtGroup 1089 } 1091 OBJECT mplsXCExtTunnelPointer 1092 SYNTAX RowPointer 1093 MIN-ACCESS read-only 1094 DESCRIPTION 1095 "The only valid value for Tunnel Pointer is mplsTunnelTable 1096 entry." 1098 ::= { mplsLsrExtCompliances 2 } 1100 mplsXCExtGroup OBJECT-GROUP 1101 OBJECTS { 1102 mplsXCExtTunnelPointer 1103 } 1104 STATUS current 1105 DESCRIPTION 1106 "This object should be supported in order to access 1107 the tunnel entry from XC entry." 1108 ::= { mplsLsrExtGroups 1 } 1110 -- MPLS-LSR-EXT-STD-MIB module ends 1111 END 1113 13. MPLS Tunnel Extension MIB definitions 1115 MPLS-TE-EXT-STD-MIB DEFINITIONS ::= BEGIN 1117 IMPORTS 1118 MODULE-IDENTITY, OBJECT-TYPE, Unsigned32, Gauge32, 1119 NOTIFICATION-TYPE 1120 FROM SNMPv2-SMI -- [RFC2578] 1121 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 1122 FROM SNMPv2-CONF -- [RFC2580] 1123 RowStatus, StorageType 1124 FROM SNMPv2-TC -- [RFC2579] 1125 MplsLocalId, MplsGlobalId, MplsNodeId, MplsIccId 1126 FROM MPLS-TC-EXT-STD-MIB 1128 mplsStdMIB, MplsTunnelIndex, MplsTunnelInstanceIndex 1129 FROM MPLS-TC-STD-MIB -- [RFC3811] 1130 mplsTunnelIndex, mplsTunnelInstance, mplsTunnelIngressLSRId, 1131 mplsTunnelEgressLSRId 1132 FROM MPLS-TE-STD-MIB -- [RFC3812] 1133 ; 1135 mplsTeExtStdMIB MODULE-IDENTITY 1136 LAST-UPDATED 1137 "201106160000Z" -- June 16, 2011 1138 ORGANIZATION 1139 "Multiprotocol Label Switching (MPLS) Working Group" 1140 CONTACT-INFO 1141 " 1142 Venkatesan Mahalingam 1143 Aricent, 1144 India 1145 Email: venkatesan.mahalingam@aricent.com 1147 Kannan KV Sampath 1148 Aricent, 1150 India 1151 Email: Kannan.Sampath@aricent.com 1153 Sam Aldrin 1154 Huawei Technologies 1155 2330 Central Express Way, 1156 Santa Clara, CA 95051, USA 1157 Email: aldrin.ietf@gmail.com 1159 Thomas D. Nadeau 1160 CA Technologies 1161 273 Corporate Drive, Portsmouth, NH, USA 1162 Email: thomas.nadeau@ca.com 1163 " 1164 DESCRIPTION 1165 "Copyright (c) 2011 IETF Trust and the persons identified 1166 as the document authors. All rights reserved. 1168 This MIB module contains generic object definitions for 1169 MPLS Traffic Engineering in transport networks." 1171 -- Revision history. 1173 REVISION 1174 "201106160000Z" -- June 16, 2011 1176 DESCRIPTION 1177 "MPLS TE mib objects extension" 1179 ::= { mplsStdMIB xxx } -- xxx to be replaced with correct value 1181 -- Top level components of this MIB module. 1183 -- traps 1184 mplsTeExtNotifications OBJECT IDENTIFIER ::= { mplsTeExtStdMIB 0 } 1185 -- tables, scalars 1186 mplsTeExtObjects OBJECT IDENTIFIER ::= { mplsTeExtStdMIB 1 } 1187 -- conformance 1188 mplsTeExtConformance OBJECT IDENTIFIER ::= { mplsTeExtStdMIB 2 } 1190 -- Start of MPLS Transport Profile Node configuration table 1191 mplsNodeConfigTable OBJECT-TYPE 1192 SYNTAX SEQUENCE OF MplsNodeConfigEntry 1193 MAX-ACCESS not-accessible 1194 STATUS current 1195 DESCRIPTION 1196 "This table allows the administrator to map a node or LSR 1197 Identifier (IP compatible [Global_Node_ID] or ICC) with 1198 a local identifier. 1200 This table is created to reuse the existing 1201 mplsTunnelTable for MPLS based transport network 1202 tunnels also. 1203 Since the MPLS tunnel's Ingress/Egress LSR identifiers' 1204 size (Unsigned32) value is not compatible for 1205 MPLS-TP tunnel i.e. Global_Node_Id of size 8 bytes and 1206 ICC of size 6 bytes, there exists a need to map the 1207 Global_Node_ID or ICC with the local identifier of size 1208 4 bytes (Unsigned32) value in order 1209 to index (Ingress/Egress LSR identifier) 1210 the existing mplsTunnelTable." 1211 ::= { mplsTeExtObjects 1 } 1213 mplsNodeConfigEntry OBJECT-TYPE 1214 SYNTAX MplsNodeConfigEntry 1215 MAX-ACCESS not-accessible 1216 STATUS current 1217 DESCRIPTION 1218 "An entry in this table represents a mapping 1219 identification for the operator or service provider 1220 with node or LSR. 1222 As per [TPIDS], this mapping is 1223 represented as Global_Node_ID or ICC. 1225 Note: Each entry in this table should have a unique 1226 Global_ID and Node_ID combination." 1227 INDEX { mplsNodeConfigLocalId } 1228 ::= { mplsNodeConfigTable 1 } 1230 MplsNodeConfigEntry ::= SEQUENCE { 1231 mplsNodeConfigLocalId MplsLocalId, 1232 mplsNodeConfigGlobalId MplsGlobalId, 1233 mplsNodeConfigNodeId MplsNodeId, 1234 mplsNodeConfigIccId MplsIccId, 1235 mplsNodeConfigRowStatus RowStatus, 1236 mplsNodeConfigStorageType StorageType 1238 } 1240 mplsNodeConfigLocalId OBJECT-TYPE 1241 SYNTAX MplsLocalId 1242 MAX-ACCESS not-accessible 1243 STATUS current 1244 DESCRIPTION 1245 "This object allows the administrator to assign a unique 1246 local identifier to map Global_Node_ID or ICC." 1247 ::= { mplsNodeConfigEntry 1 } 1249 mplsNodeConfigGlobalId OBJECT-TYPE 1250 SYNTAX MplsGlobalId 1251 MAX-ACCESS read-write 1252 STATUS current 1253 DESCRIPTION 1254 "This object indicates the Global Operator Identifier. 1255 This object value should be zero when 1256 mplsNodeConfigIccId is configured with non-null value." 1257 REFERENCE 1258 "MPLS-TP Identifiers [TPIDS]." 1259 ::= { mplsNodeConfigEntry 2 } 1261 mplsNodeConfigNodeId OBJECT-TYPE 1262 SYNTAX MplsNodeId 1263 MAX-ACCESS read-write 1264 STATUS current 1265 DESCRIPTION 1266 "This object indicates the Node_ID within the operator. 1267 This object value should be zero when mplsNodeConfigIccId 1268 is configured with non-null value." 1269 REFERENCE 1270 "MPLS-TP Identifiers [TPIDS]." 1271 ::= { mplsNodeConfigEntry 3 } 1273 mplsNodeConfigIccId OBJECT-TYPE 1274 SYNTAX MplsIccId 1275 MAX-ACCESS read-write 1276 STATUS current 1277 DESCRIPTION 1278 "This object allows the operator or service provider to 1279 configure a unique MPLS-TP ITU-T Carrier Code (ICC) 1280 either for Ingress ID or Egress ID. 1282 This object value should be zero when 1283 mplsNodeConfigGlobalId and mplsNodeConfigNodeId are 1284 assigned with non-zero value." 1285 REFERENCE 1286 "MPLS-TP Identifiers [TPIDS]." 1287 ::= { mplsNodeConfigEntry 4 } 1289 mplsNodeConfigRowStatus OBJECT-TYPE 1290 SYNTAX RowStatus 1291 MAX-ACCESS read-create 1292 STATUS current 1293 DESCRIPTION 1294 "This object allows the administrator to create, modify, 1295 and/or delete a row in this table." 1296 ::= { mplsNodeConfigEntry 5 } 1298 mplsNodeConfigStorageType OBJECT-TYPE 1299 SYNTAX StorageType 1300 MAX-ACCESS read-create 1301 STATUS current 1302 DESCRIPTION 1303 "This variable indicates the storage type for this 1304 object. 1305 Conceptual rows having the value 'permanent' 1306 need not allow write-access to any columnar 1307 objects in the row." 1308 DEFVAL { volatile } 1309 ::= { mplsNodeConfigEntry 6 } 1311 -- End of MPLS Transport Profile Node configuration table 1313 -- Start of MPLS Transport Profile Node IP compatible mapping table 1315 mplsNodeIpMapTable OBJECT-TYPE 1316 SYNTAX SEQUENCE OF MplsNodeIpMapEntry 1317 MAX-ACCESS not-accessible 1318 STATUS current 1319 DESCRIPTION 1320 "This read-only table allows the administrator to retrieve 1321 the local identifier for a given Global_Node_ID in an IP 1322 compatible operator environment. 1324 This table MAY be used in on-demand and/or proactive 1325 OAM operations to get the Ingress/Egress LSR 1326 identifier (Local Identifier) from Src-Global_Node_ID 1327 or Dst-Global_Node_ID and the Ingress and Egress LSR 1328 identifiers are used to retrieve the tunnel entry. 1330 This table returns nothing when the associated entry 1331 is not defined in mplsNodeConfigTable." 1332 ::= { mplsTeExtObjects 2 } 1334 mplsNodeIpMapEntry OBJECT-TYPE 1335 SYNTAX MplsNodeIpMapEntry 1336 MAX-ACCESS not-accessible 1337 STATUS current 1338 DESCRIPTION 1339 "An entry in this table represents a mapping of 1340 Global_Node_ID with the local identifier. 1342 An entry in this table is created automatically when 1343 the Local identifier is associated with Global_ID and 1344 Node_Id in the mplsNodeConfigTable. 1346 Note: Each entry in this table should have a unique 1347 Global_ID and Node_ID combination." 1348 INDEX { mplsNodeIpMapGlobalId, 1349 mplsNodeIpMapNodeId 1350 } 1351 ::= { mplsNodeIpMapTable 1 } 1353 MplsNodeIpMapEntry ::= SEQUENCE { 1354 mplsNodeIpMapGlobalId MplsGlobalId, 1355 mplsNodeIpMapNodeId MplsNodeId, 1356 mplsNodeIpMapLocalId MplsLocalId 1357 } 1359 mplsNodeIpMapGlobalId OBJECT-TYPE 1360 SYNTAX MplsGlobalId 1361 MAX-ACCESS not-accessible 1362 STATUS current 1363 DESCRIPTION 1364 "This object indicates the Global_ID." 1365 ::= { mplsNodeIpMapEntry 1 } 1367 mplsNodeIpMapNodeId OBJECT-TYPE 1368 SYNTAX MplsNodeId 1369 MAX-ACCESS not-accessible 1370 STATUS current 1371 DESCRIPTION 1372 "This object indicates the Node_ID within the 1373 operator." 1374 ::= { mplsNodeIpMapEntry 2 } 1376 mplsNodeIpMapLocalId OBJECT-TYPE 1377 SYNTAX MplsLocalId 1378 MAX-ACCESS read-only 1379 STATUS current 1380 DESCRIPTION 1381 "This object contains an IP compatible local identifier 1382 which is defined in mplsNodeConfigTable." 1383 ::= { mplsNodeIpMapEntry 3 } 1385 -- End MPLS Transport Profile Node IP compatible table 1387 -- Start of MPLS Transport Profile Node ICC based table 1389 mplsNodeIccMapTable OBJECT-TYPE 1390 SYNTAX SEQUENCE OF MplsNodeIccMapEntry 1391 MAX-ACCESS not-accessible 1392 STATUS current 1393 DESCRIPTION 1394 "This read-only table allows the administrator to retrieve 1395 the local identifier for a given ICC operator in an ICC 1396 operator environment. 1398 This table MAY be used in on-demand and/or proactive 1399 OAM operations to get the Ingress/Egress LSR 1400 identifier (Local Identifier) from Src-ICC 1401 or Dst-ICC and the Ingress and Egress LSR 1402 identifiers are used to retrieve the tunnel entry. 1404 This table returns nothing when the associated entry 1405 is not defined in mplsNodeConfigTable." 1406 ::= { mplsTeExtObjects 3 } 1408 mplsNodeIccMapEntry OBJECT-TYPE 1409 SYNTAX MplsNodeIccMapEntry 1410 MAX-ACCESS not-accessible 1411 STATUS current 1412 DESCRIPTION 1413 "An entry in this table represents a mapping of ICC with 1414 the local identifier. 1416 An entry in this table is created automatically when 1417 the Local identifier is associated with ICC in 1418 the mplsNodeConfigTable." 1419 INDEX { mplsNodeIccMapIccId } 1420 ::= { mplsNodeIccMapTable 1 } 1422 MplsNodeIccMapEntry ::= SEQUENCE { 1423 mplsNodeIccMapIccId MplsIccId, 1424 mplsNodeIccMapLocalId MplsLocalId 1425 } 1427 mplsNodeIccMapIccId OBJECT-TYPE 1428 SYNTAX MplsIccId 1429 MAX-ACCESS not-accessible 1430 STATUS current 1431 DESCRIPTION 1432 "This object allows the operator or service provider to 1433 configure a unique MPLS-TP ITU-T Carrier Code (ICC) 1434 either for Ingress or Egress LSR ID. 1436 The ICC is a string of one to six characters, each 1437 character being either alphabetic (i.e. A-Z) or 1438 numeric (i.e. 0-9) characters. Alphabetic characters in 1439 the ICC should be represented with upper case letters." 1440 ::= { mplsNodeIccMapEntry 1 } 1442 mplsNodeIccMapLocalId OBJECT-TYPE 1443 SYNTAX MplsLocalId 1444 MAX-ACCESS read-only 1445 STATUS current 1446 DESCRIPTION 1447 "This object contains an ICC based local identifier 1448 which is defined in mplsNodeConfigTable." 1449 ::= { mplsNodeIccMapEntry 2 } 1451 -- End MPLS Transport Profile Node ICC based table 1453 -- Start of MPLS Tunnel table extension 1455 mplsTunnelExtTable OBJECT-TYPE 1456 SYNTAX SEQUENCE OF MplsTunnelExtEntry 1457 MAX-ACCESS not-accessible 1458 STATUS current 1459 DESCRIPTION 1460 "This table represents MPLS-TP specific extensions to 1461 mplsTunnelTable. 1463 As per MPLS-TP Identifiers [TPIDS] draft, LSP_ID is 1465 Src-Global_Node_ID::Src-Tunnel_Num::Dst-Global_Node_ID:: 1466 Dst-Tunnel_Num::LSP_Num for IP operator and 1468 Src-ICC::Src-Tunnel_Num::Dst-ICC::Dst-Tunnel_Num::LSP_Num 1469 for ICC operator, 1471 mplsTunnelTable is reused for forming the LSP_ID 1472 as follows, 1474 Source Tunnel_Num is mapped with mplsTunnelIndex, 1475 Source Node_ID is mapped with 1476 mplsTunnelIngressLSRId, Destination Node_ID is 1477 mapped with mplsTunnelEgressLSRId LSP_Num is mapped with 1478 mplsTunnelInstance. 1480 Source Global_Node_ID and/or ICC and Destination 1481 Global_Node_ID and/or ICC are maintained in the 1482 mplsNodeConfigTable and mplsNodeConfigLocalId is 1483 used to create an entry in mplsTunnelTable." 1484 REFERENCE 1485 "MPLS-TP Identifiers [TPIDS]." 1486 ::= { mplsTeExtObjects 4 } 1488 mplsTunnelExtEntry OBJECT-TYPE 1489 SYNTAX MplsTunnelExtEntry 1491 MAX-ACCESS not-accessible 1492 STATUS current 1493 DESCRIPTION 1494 "An entry in this table represents MPLS-TP 1495 specific additional tunnel configurations." 1496 INDEX { 1497 mplsTunnelIndex, 1498 mplsTunnelInstance, 1499 mplsTunnelIngressLSRId, 1500 mplsTunnelEgressLSRId 1501 } 1502 ::= { mplsTunnelExtTable 1 } 1504 MplsTunnelExtEntry ::= SEQUENCE { 1505 mplsTunnelExtDestTnlIndex MplsTunnelIndex, 1506 mplsTunnelExtDestTnlLspIndex MplsTunnelInstanceIndex 1507 } 1509 mplsTunnelExtDestTnlIndex OBJECT-TYPE 1510 SYNTAX MplsTunnelIndex 1511 MAX-ACCESS read-create 1512 STATUS current 1513 DESCRIPTION 1514 "This object is applicable only for the bidirectional 1515 tunnel that has the forward and reverse LSPs in the 1516 same tunnel or in the different tunnels. 1518 This object holds the same value as that of the 1519 mplsTunnelIndex of mplsTunnelEntry if the forward and 1520 reverse LSPs are in the same tunnel. Otherwise, 1521 this object holds the value of the other direction 1522 associated LSP's mplsTunnelIndex from a different tunnel. 1524 The values of this object and the 1525 mplsTunnelExtDestTnlLspIndex object together can be used 1526 to identify an opposite direction LSP i.e. if the 1527 mplsTunnelIndex and mplsTunnelInstance hold the value for 1528 forward LSP, this object and mplsTunnelExtDestTnlLspIndex 1529 can be used to retrieve the reverse direction LSP and 1530 vice versa. 1532 This object and mplsTunnelExtDestTnlLspIndex values 1533 provide the first two indices of tunnel entry and 1534 the remaining indices can be derived as follows, 1535 if both the forward and reverse LSPs are present in 1536 the same tunnel, the opposite direction LSP's Ingress and 1537 Egress Identifier will be same for both the LSPs, 1538 else the Ingress and Egress Identifiers should be 1539 swapped in order to index the other direction tunnel. 1541 The value of zero for this object is invalid." 1542 ::= { mplsTunnelExtEntry 1 } 1544 mplsTunnelExtDestTnlLspIndex OBJECT-TYPE 1545 SYNTAX MplsTunnelInstanceIndex 1546 MAX-ACCESS read-create 1547 STATUS current 1548 DESCRIPTION 1549 "This object is applicable only for the bidirectional 1550 tunnel that has the forward and reverse LSPs in the 1551 same tunnel or in the different tunnels. 1553 This object should contain different value if both the 1554 forward and reverse LSPs present in the same tunnel. 1556 This object can contain same value or different values if 1557 the forward and reverse LSPs present in the different 1558 tunnels. 1560 The value of zero for this object is valid for the 1561 configured tunnel." 1562 ::= { mplsTunnelExtEntry 2 } 1564 -- End of MPLS Tunnel table extension 1566 -- Notifications. 1567 -- Notifications objects need to be added here. 1568 -- End of notifications. 1570 -- Module compliance. 1572 mplsTeExtGroups 1573 OBJECT IDENTIFIER ::= { mplsTeExtConformance 1 } 1575 mplsTeExtCompliances 1576 OBJECT IDENTIFIER ::= { mplsTeExtConformance 2 } 1578 -- Compliance requirement for fully compliant implementations. 1580 mplsTeExtModuleFullCompliance MODULE-COMPLIANCE 1581 STATUS current 1582 DESCRIPTION 1583 "Compliance statement for agents that provide full 1584 support the MPLS-TE-EXT-STD-MIB module." 1586 MODULE -- this module 1588 -- The mandatory group has to be implemented by all 1589 -- LSRs that originate/terminate MPLS-TP tunnels. 1590 -- In addition, depending on the type of tunnels 1591 -- supported, other groups become mandatory as 1592 -- explained below. 1594 MANDATORY-GROUPS { 1595 mplsTunnelExtGroup 1596 } 1598 GROUP mplsTunnelExtIpOperatorGroup 1599 DESCRIPTION 1600 "This group is mandatory for devices which support 1601 configuration of IP based identifier tunnels." 1603 GROUP mplsTunnelExtIccOperatorGroup 1604 DESCRIPTION 1605 "This group is mandatory for devices which support 1606 configuration of ICC based tunnels." 1608 ::= { mplsTeExtCompliances 1 } 1610 -- Compliance requirement for read-only implementations. 1612 mplsTeExtModuleReadOnlyCompliance MODULE-COMPLIANCE 1613 STATUS current 1614 DESCRIPTION 1615 "Compliance statement for agents that provide full 1616 support the MPLS-TE-EXT-STD-MIB module." 1618 MODULE -- this module 1620 -- The mandatory group has to be implemented by all 1621 -- LSRs that originate/terminate MPLS-TP tunnels. 1622 -- In addition, depending on the type of tunnels 1623 -- supported, other groups become mandatory as 1624 -- explained below. 1626 MANDATORY-GROUPS { 1627 mplsTunnelExtGroup 1628 } 1630 GROUP mplsTunnelExtIpOperatorGroup 1631 DESCRIPTION 1632 "This group is mandatory for devices which support 1633 configuration of IP based identifier tunnels." 1635 GROUP mplsTunnelExtIccOperatorGroup 1637 DESCRIPTION 1638 "This group is mandatory for devices which support 1639 configuration of ICC based tunnels." 1641 ::= { mplsTeExtCompliances 2 } 1643 -- Units of conformance. 1645 mplsTunnelExtGroup OBJECT-GROUP 1646 OBJECTS { 1647 mplsTunnelExtDestTnlIndex, 1648 mplsTunnelExtDestTnlLspIndex 1649 } 1650 STATUS current 1651 DESCRIPTION 1652 "Necessary, but not sufficient, set of objects to 1653 implement tunnels. In addition, depending on the 1654 operating environment, the following groups are 1655 mandatory." 1656 ::= { mplsTeExtGroups 1 } 1658 mplsTunnelExtIpOperatorGroup OBJECT-GROUP 1659 OBJECTS { mplsNodeConfigGlobalId, 1660 mplsNodeConfigNodeId, 1661 mplsNodeConfigRowStatus, 1662 mplsNodeConfigStorageType, 1663 mplsNodeIpMapLocalId 1664 } 1665 STATUS current 1666 DESCRIPTION 1667 "Object(s) needed to implement IP compatible tunnels." 1668 ::= { mplsTeExtGroups 2 } 1670 mplsTunnelExtIccOperatorGroup OBJECT-GROUP 1671 OBJECTS { mplsNodeConfigIccId, 1672 mplsNodeConfigRowStatus, 1673 mplsNodeConfigStorageType, 1674 mplsNodeIccMapLocalId 1675 } 1676 STATUS current 1677 DESCRIPTION 1678 "Object(s) needed to implement ICC based tunnels." 1679 ::= { mplsTeExtGroups 3 } 1681 -- MPLS-TE-EXT-STD-MIB module ends 1682 END 1684 14. Security Consideration 1686 There is a number of management objects defined in this MIB module 1687 that has a MAX-ACCESS clause of read-write.. Such objects may be 1688 considered sensitive or vulnerable in some network environments. 1689 The support for SET operations in a non-secure environment without 1690 proper protection can have a negative effect on network 1691 operations. 1693 Some of the readable objects in this MIB module (i.e., objects 1694 with a MAX-ACCESS other than not-accessible) may be considered 1695 sensitive or vulnerable in some network environments. 1696 It is thus important to control even GET and/or NOTIFY access to 1697 these objects and possibly to even encrypt the values of these 1698 objects when sending them over the network via SNMP. These are 1699 the tables and objects and their sensitivity/vulnerability: 1701 SNMP versions prior to SNMPv3 did not include adequate security. 1702 Even if the network itself is secure (for example by using IPsec), 1703 even then, there is no control as to who on the secure network is 1704 allowed to access and GET/SET (read/change/create/delete) 1705 the objects in this MIB module. 1707 It is RECOMMENDED that implementers consider the security 1708 features as provided by the SNMPv3 framework (see [RFC3410], 1709 section 8), including full supports for the SNMPv3 cryptographic 1710 mechanisms (for authentication and privacy). 1712 Further, deployment of SNMP versions prior to SNMPv3 is NOT 1713 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 1714 enable cryptographic security. It is then a customer/operator 1715 responsibility to ensure that the SNMP entity giving access to an 1716 instance of this MIB module is properly configured to give 1717 access to the objects only to those principles (users) that 1718 have legitimate rights to indeed GET or SET (change/create/delete) 1719 them. 1721 15. IANA Considerations 1723 To be added in a later version of this document. 1725 16. References 1727 16.1 Normative References 1729 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1730 Requirement Levels", BCP 14, RFC 2119, March 1997. 1732 [RFC2578] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 1733 "Structure of Management Information Version 2 (SMIv2)", 1734 STD 58, RFC 2578, April 1999. 1736 [RFC2579] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 1737 "Textual Conventions for SMIv2", STD 58, RFC 2579, April 1738 1999. 1740 [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 1741 "Conformance Statements for SMIv2", STD 58, RFC 2580, 1742 April 1999. 1744 [RFC3031] Rosen, E., Viswanathan, A., and R. Callon, "Multiprotocol 1745 Label Switching Architecture", RFC 3031, January 2001. 1747 16.2 Informative References 1749 [RFC3812] Srinivasan, C., Viswanathan, A., and T. Nadeau, 1750 "Multiprotocol Label Switching (MPLS) Traffic Engineering 1751 (TE) Management Information Base (MIB)", RFC 3812, June 1752 2004. 1754 [RFC3813] Srinivasan, C., Viswanathan, A., and T. Nadeau, 1755 "Multiprotocol Label Switching (MPLS) Label Switching 1756 (LSR) Router Management Information Base (MIB)", RFC 3813, 1757 June 2004. 1759 [RFC3410] J. Case, R. Mundy, D. pertain, B.Stewart, "Introduction 1760 and Applicability Statement for Internet Standard 1761 Management Framework", RFC 3410, December 2002. 1763 [RFC3811] Nadeau, T., Ed., and J. Cucchiara, Ed., "Definitions of 1764 Textual Conventions (TCs) for Multiprotocol Label 1765 Switching (MPLS) Management", RFC 3811, June 2004. 1767 [RFC5654] Niven-Jenkins, B., Ed., Brungard, D., Ed., Betts, M., Ed., 1768 Sprecher, N., and S. Ueno, "Requirements of an MPLS 1769 Transport Profile", RFC 5654, September 2009. 1771 [TPIDS] M. Bocci, et al, "MPLS-TP Identifiers", 1772 draft-ietf-mpls-tp-identifiers-03, October 25, 2010 1774 17. Acknowledgments 1776 To be added in a later version of this document. 1778 18. Authors' Addresses 1780 Sam Aldrin 1781 Huawei Technologies 1782 2330 Central Express Way, 1783 Santa Clara, CA 95051, USA 1784 Email: aldrin.ietf@gmail.com 1786 Thomas D. Nadeau 1787 CA Technologies 1788 273 Corporate Drive, Portsmouth, NH, USA 1789 Email: thomas.nadeau@ca.com 1791 Venkatesan Mahalingam 1792 Aricent 1793 India 1794 Email: venkatesan.mahalingam@aricent.com 1796 Kannan KV Sampath 1797 Aricent 1798 India 1799 Email: Kannan.Sampath@aricent.com