idnits 2.17.1 draft-ietf-mpls-tp-oam-id-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 (June 15, 2014) is 3596 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) No issues found here. Summary: 0 errors (**), 0 flaws (~~), 1 warning (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group 3 INTERNET-DRAFT Sam Aldrin 4 Intended Status: Standards Track Huawei Technologies 5 Expires: December 17, 2014 M.Venkatesan 6 Dell Inc. 7 Kannan KV Sampath 8 Redeem 9 Thomas D. Nadeau 10 Brocade 12 June 15, 2014 14 MPLS-TP Operations, Administration, and Management (OAM) Identifiers 15 Management Information Base (MIB) 16 draft-ietf-mpls-tp-oam-id-mib-05 18 Abstract 20 This memo defines a portion of the Management Information Base (MIB) 21 for use with network management protocols in the Internet community. 22 In particular, it describes Operations, Administration, and 23 Management (OAM) identifiers related managed objects for 24 Multiprotocol Label Switching (MPLS) based Transport Profile (TP). 26 Status of this Memo 28 This Internet-Draft is submitted to IETF in full conformance with the 29 provisions of BCP 78 and BCP 79. 31 Internet-Drafts are working documents of the Internet Engineering 32 Task Force (IETF), its areas, and its working groups. Note that 33 other groups may also distribute working documents as Internet- 34 Drafts. 36 Internet-Drafts are draft documents valid for a maximum of six months 37 and may be updated, replaced, or obsoleted by other documents at any 38 time. It is inappropriate to use Internet-Drafts as reference 39 material or to cite them other than as "work in progress." 41 The list of current Internet-Drafts can be accessed at 42 http://www.ietf.org/ietf/1id-abstracts.txt. 44 The list of Internet-Draft Shadow Directories can be accessed at 45 http://www.ietf.org/shadow.html. 47 This Internet-Draft will expire on December 17, 2014. 49 Copyright and License Notice 51 Copyright (c) 2014 IETF Trust and the persons identified as the 52 document authors. All rights reserved. 54 This document is subject to BCP 78 and the IETF Trust's Legal 55 Provisions Relating to IETF Documents 56 (http://trustee.ietf.org/license-info) in effect on the date of 57 publication of this document. Please review these documents 58 carefully, as they describe your rights and restrictions with respect 59 to this document. Code Components extracted from this document must 60 include Simplified BSD License text as described in Section 4.e of 61 the Trust Legal Provisions and are provided without warranty as 62 described in the Simplified BSD License. 64 Table of Contents 66 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 67 2. The Internet-Standard Management Framework . . . . . . . . . . 3 68 3. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 69 3.1 Conventions used in this document . . . . . . . . . . . . . 3 70 3.2 Terminology . . . . . . . . . . . . . . . . . . . . . . . . 3 71 3.3 Acronyms . . . . . . . . . . . . . . . . . . . . . . . . . . 3 72 4. Feature List . . . . . . . . . . . . . . . . . . . . . . . . . 4 73 5. Brief description of MIB Objects . . . . . . . . . . . . . . . 4 74 5.1. mplsOamIdMegTable . . . . . . . . . . . . . . . . . . . . 4 75 5.2. mplsOamIdMeTable . . . . . . . . . . . . . . . . . . . . . 5 76 6. MPLS OAM identifier configuration for MPLS tunnel example . . . 5 77 7. MPLS OAM Identifiers MIB definitions . . . . . . . . . . . . . 6 78 8. Security Consideration . . . . . . . . . . . . . . . . . . . . 25 79 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 25 80 10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 26 81 10.1 Normative References . . . . . . . . . . . . . . . . . . . 26 82 10.2 Informative References . . . . . . . . . . . . . . . . . . 26 83 11. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 27 84 12. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 27 86 1 Introduction 88 This memo defines a portion of the Management Information Base (MIB) 89 for use with network management protocols in the Internet community. 90 In particular, it describes managed objects for modeling a 91 Multiprotocol Label Switching (MPLS) [RFC3031] based transport 92 profile. 94 This MIB module should be used for performing the OAM operations for 95 MPLS LSPs, Pseudowires and Sections. 97 2. The Internet-Standard Management Framework 99 For a detailed overview of the documents that describe the current 100 Internet-Standard Management Framework, please refer to section 7 of 101 RFC3410 [RFC3410]. 103 Managed objects are accessed via a virtual information store, termed 104 the Management Information Base or MIB. MIB objects are generally 105 accessed through the Simple Network Management Protocol (SNMP). 106 Objects in the MIB are defined using the mechanisms defined in the 107 Structure of Management Information (SMI). This memo specifies a MIB 108 module that is compliant to the SMIv2, which is described in STD 58, 109 RFC2578, STD 58, RFC2579 and STD58, RFC2580. 111 3. Overview 113 3.1 Conventions used in this document 115 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 116 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 117 "OPTIONAL" in this document are to be interpreted as described in 118 RFC-2119 [RFC2119]. 120 3.2 Terminology 122 This document uses terminology from the Multiprotocol Label Switching 123 Architecture [RFC3031], Multiprotocol Label Switching (MPLS) Traffic 124 Engineering (TE)Management Information Base (MIB)[RFC3812], 125 Multiprotocol Label Switching (MPLS) Label Switching Router (LSR) 126 Management Information Base (MIB)[RFC3813], Operations, 127 Administration, and Maintenance Framework for MPLS-Based Transport 128 Networks [RFC6371], MPLS Transport Profile (MPLS-TP) Identifiers 129 [RFC6370], MPLS-TP Identifiers Following ITU-T Conventions [RFC6923], 130 and OAM in MPLS Transport Networks [RFC5860]. 132 3.3 Acronyms 133 ICC: ITU Carrier Code 134 IP: Internet Protocol 136 LSP: Label Switching Path 137 LSR: Label Switching Router 138 MIB: Management Information Base 139 ME: Maintenance Entity 140 MEG: Maintenance Entity Group 141 MEP: Maintenance Entity Group End Point 142 MIP: Maintenance Entity Group Intermediate Point 143 MPLS: Multi-Protocol Label Switching 144 MPLS-TP: MPLS Transport Profile 145 PW: Pseudowire 146 TE: Traffic Engineering 147 TP: Transport Profile 149 4. Feature List 151 The MPLS transport profile OAM identifiers MIB module is designed 152 to satisfy the following requirements and constraints: 154 - The MIB module supports configuration of OAM identifiers for 155 point-to-point, co-routed bidirectional, associated 156 bidirectional MPLS tunnels and MPLS Pseudowires. 158 5. Brief description of MIB Objects 160 The objects described in this section support the functionality 161 described in documents [RFC5654] and [RFC6370]. The tables support 162 both IP compatible and ICC based OAM identifiers configurations 163 for MPLS Tunnels and Pseudowires. 165 5.1. mplsOamIdMegTable 167 The mplsOamIdMegTable is used to manage one or more 168 Maintenance Entities (MEs) that belongs to the same transport path. 170 When a new entry is created with mplsOamIdMegOperatorType set to 171 ipCompatible (1), then as per [RFC6370] (MEG_ID for LSP 172 is LSP_ID and MEG_ID for PW is PW_Path_ID), MEP_ID can be 173 automatically formed. 175 For ICC based transport path, the user is expected to configure 176 the ICC identifier explicitly in this table for MPLS tunnels 177 and pseudowires. 179 5.2. mplsOamIdMeTable 181 The mplsOamIdMeTable defines a relationship between two points 182 (source and sink) of a transport path to which maintenance and 183 monitoring operations apply. The two points that define 184 a maintenance entity are called Maintenance Entity Group 185 End Points (MEPs). 187 In between MEPs, there are zero or more intermediate points, 188 called Maintenance Entity Group Intermediate Points (MIPs). 189 MEPs and MIPs are associated with the MEG and can be shared by 190 more than one ME in a MEG. 192 6. MPLS OAM identifier configuration for MPLS tunnel example 194 In this section, we provide an example of the OAM identifier 195 configuration for an MPLS co-routed bidirectional tunnel. 197 This example provides usage of a MEG and ME tables for management and 198 monitoring operations of an MPLS tunnel. 200 This example considers the OAM identifiers configuration on a 201 head-end LSR to manage and monitor a MPLS tunnel. 202 Only relevant objects which are applicable for IP based OAM 203 identifiers of co-routed MPLS tunnel are illustrated here. 205 In mplsOamIdMegTable: 207 { 208 -- MEG index (Index to the table) 209 mplsOamIdMegIndex = 1, 210 mplsOamIdMegName = "MEG1", 211 mplsOamIdMegOperatorType = ipCompatible (1), 212 mplsOamIdMegServicePointerType = lsp (1), 213 mplsOamIdMegMpLocation = perNode(1), 214 -- Mandatory parameters needed to activate the row go here 215 mplsOamIdMegRowStatus = createAndGo (4), 216 mplsOamIdMegPathFlow 217 = coRoutedBidirectionalPointToPoint (2) 218 } 220 This will create an entry in the mplsOamIdMegTable to manage and 221 monitor the MPLS tunnel. 223 The following ME table is used to associate the path information 224 to a MEG. 226 In mplsOamIdMeTable: 228 { 229 -- ME index (Index to the table) 230 mplsOamIdMeIndex = 1, 232 -- MP index (Index to the table) 233 mplsOamIdMeMpIndex = 1, 234 mplsOamIdMeName = "ME1", 235 mplsOamIdMeMpIfIndex = 0, 236 -- Source MEP id is derived from the IP compatible MPLS tunnel 237 mplsOamIdMeSourceMepIndex = 0, 238 -- Source MEP id is derived from the IP compatible MPLS tunnel 239 mplsOamIdMeSinkMepIndex = 0, 240 mplsOamIdMeMpType = mep (1), 241 mplsOamIdMeMepDirection = down (2), 242 mplsOamIdMeProactiveOamPhbTCValue = 0, 243 mplsOamIdMeOnDemandOamPhbTCValue = 0, 244 -- RowPointer MUST point to the first accessible column of an 245 -- MPLS tunnel 246 mplsOamIdMeServicePointer = mplsTunnelName.1.1.10.20, 247 -- Mandatory parameters needed to activate the row go here 248 mplsOamIdMeRowStatus = createAndGo (4) 249 } 251 7. MPLS OAM Identifiers MIB definitions 253 MPLS-OAM-ID-STD-MIB DEFINITIONS ::= BEGIN 255 IMPORTS 256 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, 257 Unsigned32, zeroDotZero 258 FROM SNMPv2-SMI -- [RFC2578] 259 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 260 FROM SNMPv2-CONF -- [RFC2580] 261 RowStatus, RowPointer, StorageType, 262 TEXTUAL-CONVENTION 263 FROM SNMPv2-TC -- [RFC2579] 264 SnmpAdminString 265 FROM SNMP-FRAMEWORK-MIB -- [RFC3411] 266 IndexIntegerNextFree 267 FROM DIFFSERV-MIB -- [RFC3289] 268 mplsStdMIB 269 FROM MPLS-TC-STD-MIB -- [RFC3811] 270 InterfaceIndexOrZero, ifGeneralInformationGroup, 271 ifCounterDiscontinuityGroup 272 FROM IF-MIB; -- [RFC2863] 274 mplsOamIdStdMIB MODULE-IDENTITY 275 LAST-UPDATED 276 "201406150000Z" -- June 15, 2014 277 ORGANIZATION 278 "Multiprotocol Label Switching (MPLS) Working Group" 279 CONTACT-INFO 280 " 281 Sam Aldrin 282 Huawei Technologies, co. 283 2330 Central Express Way, 285 Santa Clara, CA 95051, USA 286 Email: aldrin.ietf@gmail.com 288 Thomas D. Nadeau 289 Email: tnadeau@lucidvision.com 291 Venkatesan Mahalingam 292 Dell Inc. 293 5450 Great America Parkway, 294 Santa Clara, CA 95054, USA 295 Email: venkat.mahalingams@gmail.com 297 Kannan KV Sampath 298 Redeem, 299 India 300 Email: kannankvs@gmail.com 302 Ping Pan 303 Infinera 304 Email: ppan@infinera.com 306 Sami Boutros 307 Cisco Systems, Inc. 308 3750 Cisco Way 309 San Jose, California 95134 310 USA 311 Email: sboutros@cisco.com 313 " 314 DESCRIPTION 315 "Copyright (c) 2014 IETF Trust and the persons identified 316 as the document authors. All rights reserved. 318 This MIB module contains generic object definitions for 319 MPLS OAM maintenance identifiers." 321 -- Revision history. 323 REVISION 324 "201406150000Z" -- June 15, 2014 325 DESCRIPTION 326 "MPLS OAM Identifiers MIB objects for LSPs and 327 Pseudowires" 329 ::= { mplsStdMIB xxx } -- xxx to be replaced with the correct 330 -- OID value assigned by 331 -- IANA (see section 9). 333 -- TEXTUAL-CONVENTIONs 335 MplsOamPhbTCValue ::= TEXTUAL-CONVENTION 336 STATUS current 337 DESCRIPTION 338 "This is the Per-hop Behavior (PHB) traffic class values 339 for the MPLS OAM operations." 340 SYNTAX INTEGER { 341 be (1), 342 af1 (2), 343 af2 (3), 344 af3 (4), 345 af4 (5), 346 ef (6), 347 cs6 (7), 348 cs7 (8) 349 } 351 -- Top level components of this MIB module. 353 -- notifications 354 mplsOamIdNotifications 355 OBJECT IDENTIFIER ::= { mplsOamIdStdMIB 0 } 356 -- tables, scalars 357 mplsOamIdObjects OBJECT IDENTIFIER ::= { mplsOamIdStdMIB 1 } 358 -- conformance 359 mplsOamIdConformance 360 OBJECT IDENTIFIER ::= { mplsOamIdStdMIB 2 } 362 -- Start of MPLS Transport Profile MEG table 364 mplsOamIdMegIndexNext OBJECT-TYPE 365 SYNTAX IndexIntegerNextFree (0..4294967295) 366 MAX-ACCESS read-only 367 STATUS current 368 DESCRIPTION 369 "This object contains an unused value for 370 mplsOamIdMegIndex, or a zero to indicate 371 that none exist. Negative values are not allowed, 372 as they do not correspond to valid values of 373 mplsOamIdMegIndex." 374 ::= { mplsOamIdObjects 1 } 375 mplsOamIdMegTable OBJECT-TYPE 376 SYNTAX SEQUENCE OF MplsOamIdMegEntry 377 MAX-ACCESS not-accessible 378 STATUS current 379 DESCRIPTION 380 "This table contains information about the Maintenance 381 Entity Groups (MEG). 383 MEG as mentioned in MPLS-TP OAM framework defines a set 384 of one or more maintenance entities (ME). 385 Maintenance Entities define a relationship between any 386 two points of a transport path in an OAM domain to which 387 maintenance and monitoring operations apply." 388 ::= { mplsOamIdObjects 2 } 390 mplsOamIdMegEntry OBJECT-TYPE 391 SYNTAX MplsOamIdMegEntry 392 MAX-ACCESS not-accessible 393 STATUS current 394 DESCRIPTION 395 "An entry in this table represents MPLS-TP MEG. 396 An entry can be created by a network administrator 397 or by an SNMP agent as instructed by an MPLS-TP OAM 398 Framework. 400 When a new entry is created with 401 mplsOamIdMegOperatorType set to ipCompatible (1), 402 then as per [RFC6370] (MEG_ID for LSP is LSP_ID and 403 MEG_ID for PW is PW_Path_ID), MEP_ID can be 404 automatically formed. 406 For co-routed bidirectional LSP, MEG_ID is 407 A1-{Global_ID::Node_ID::Tunnel_Num}::Z9-{Global_ID:: 408 Node_ID::Tunnel_Num}::LSP_Num. 410 For associated bidirectional LSP, MEG_ID is A1- 411 {Global_ID::Node_ID::Tunnel_Num::LSP_Num}:: Z9- 412 {Global_ID::Node_ID::Tunnel_Num::LSP_Num} 414 For LSP, MEP_ID is formed using, 415 Global_ID::Node_ID::Tunnel_Num::LSP_Num 416 For PW, MEG_ID is formed using AGI::A1- 417 {Global_ID::Node_ID::AC_ID}:: Z9- 418 {Global_ID::Node_ID::AC_ID}. 420 For PW, MEP_ID is formed using 421 AGI::Global_ID::Node_ID::AC_ID 423 MEP_ID is retrieved from the mplsOamIdMegServicePointer 424 object based on the mplsOamIdMegServicePointerType value. 425 ICC MEG_ID for LSP and PW is formed using the objects 426 mplsOamIdMegIdIcc and mplsOamIdMegIdUmc. 428 MEP_ID can be formed using MEG_ID::MEP_Index." 429 REFERENCE 430 "1. RFC5860, Requirements for OAM in MPLS Transport 431 Networks, May 2010. 432 2. RFC6371, Operations, Administration, and Maintenance 433 Framework for MPLS-Based Transport Networks, 434 September 2011 Section 3. 435 3. RFC6370, MPLS Transport Profile (MPLS-TP) Identifiers. 436 4. RFC6923, MPLS Transport Profile (MPLS-TP) Identifiers 437 Following ITU-T Conventions." 438 INDEX { mplsOamIdMegIndex } 439 ::= { mplsOamIdMegTable 1 } 441 MplsOamIdMegEntry ::= SEQUENCE { 442 mplsOamIdMegIndex Unsigned32, 443 mplsOamIdMegName SnmpAdminString, 444 mplsOamIdMegOperatorType INTEGER, 445 mplsOamIdMegIdCc SnmpAdminString, 446 mplsOamIdMegIdIcc SnmpAdminString, 447 mplsOamIdMegIdUmc SnmpAdminString, 448 mplsOamIdMegServicePointerType INTEGER, 449 mplsOamIdMegMpLocation INTEGER, 450 mplsOamIdMegPathFlow INTEGER, 451 mplsOamIdMegOperStatus INTEGER, 452 mplsOamIdMegSubOperStatus BITS, 453 mplsOamIdMegRowStatus RowStatus, 454 mplsOamIdMegStorageType StorageType 455 } 457 mplsOamIdMegIndex OBJECT-TYPE 458 SYNTAX Unsigned32 (1..4294967295) 459 MAX-ACCESS not-accessible 460 STATUS current 461 DESCRIPTION 462 "Index for the conceptual row identifying a MEG within 463 this MEG table. Managers should obtain new values for row 464 creation in this table by reading 465 mplsOamIdMegIndexNext." 466 ::= { mplsOamIdMegEntry 1 } 468 mplsOamIdMegName OBJECT-TYPE 469 SYNTAX SnmpAdminString (SIZE(0..48)) 470 MAX-ACCESS read-create 471 STATUS current 472 DESCRIPTION 473 "Each Maintenance Entity Group has unique name amongst 474 all those used or available to a service provider or 475 operator. It facilitates easy identification of 476 administrative responsibility for each MEG." 477 ::= { mplsOamIdMegEntry 2 } 479 mplsOamIdMegOperatorType OBJECT-TYPE 480 SYNTAX INTEGER { 481 ipCompatible (1), 483 iccBased (2) 484 } 485 MAX-ACCESS read-create 486 STATUS current 487 DESCRIPTION 488 "Indicates the operator type for MEG. Conceptual rows 489 having 'iccBased' as operator type, MUST have valid 490 values for the objects mplsOamIdMegIdIcc and 491 mplsOamIdMegIdUmc when the row status is active." 492 REFERENCE 493 "1. RFC6370, MPLS Transport Profile (MPLS-TP) 494 Identifiers. 495 2. RFC6923, MPLS Transport Profile (MPLS-TP) Identifiers 496 Following ITU-T Conventions. Section 3.1" 497 DEFVAL { ipCompatible } 498 ::= { mplsOamIdMegEntry 3 } 500 mplsOamIdMegIdCc OBJECT-TYPE 501 SYNTAX SnmpAdminString (SIZE(0..2)) 502 MAX-ACCESS read-create 503 STATUS current 504 DESCRIPTION 505 "Global uniqueness is assured by concatenating the ICC 506 with a Country Code (CC). The Country Code (alpha-2) 507 is a string of two alphabetic characters represented 508 with upper case letters (i.e., A-Z). 510 This object MUST contain a non-null ICC value if 511 the MplsOamIdMegOperatorType value is iccBased(2), 512 otherwise a null ICC value with octet size 0 513 should be assigned." 514 REFERENCE 515 "RFC6923, MPLS Transport Profile (MPLS-TP) Identifiers 516 Following ITU-T Conventions. Section 3." 517 DEFVAL {""} 518 ::= { mplsOamIdMegEntry 4 } 520 mplsOamIdMegIdIcc OBJECT-TYPE 521 SYNTAX SnmpAdminString (SIZE(0..6)) 522 MAX-ACCESS read-create 523 STATUS current 524 DESCRIPTION 525 "Unique code assigned to Network Operator or Service 526 Provider maintained by ITU-T. The ITU Carrier Code 527 used to form MEGID. 529 This object MUST contain a non-null ICC value if 530 the MplsOamIdMegOperatorType value is iccBased(2), 531 otherwise a null ICC value with octet size 0 532 should be assigned." 533 REFERENCE 534 "RFC6923, MPLS Transport Profile (MPLS-TP) Identifiers 535 Following ITU-T Conventions. Section 3.1." 536 DEFVAL {""} 537 ::= { mplsOamIdMegEntry 5 } 539 mplsOamIdMegIdUmc OBJECT-TYPE 540 SYNTAX SnmpAdminString (SIZE(0..7)) 541 MAX-ACCESS read-create 542 STATUS current 543 DESCRIPTION 544 "Unique code assigned by Network Operator or Service 545 Provider and is appended to mplsOamIdMegIdIcc to form 546 the MEGID. 547 This object MUST contain a non-null ICC value if 548 the MplsOamIdMegOperatorType value is iccBased(2), 549 otherwise a null ICC value with octet size 0 550 should be assigned." 551 REFERENCE 552 "RFC6923, MPLS Transport Profile (MPLS-TP) Identifiers 553 Following ITU-T Conventions. Section 7.1." 554 DEFVAL {""} 555 ::= { mplsOamIdMegEntry 6 } 557 mplsOamIdMegServicePointerType OBJECT-TYPE 558 SYNTAX INTEGER { 559 lsp (1), 560 pseudowire (2), 561 section (3) 562 } 563 MAX-ACCESS read-create 564 STATUS current 565 DESCRIPTION 566 "Indicates the service type for the MEG. 567 If the service type indicates lsp, the service pointer 568 in mplsOamIdMeTable points to an entry in 569 the mplsTunnelTable [RFC3812]. 571 If the value is pseudowire service type, the service 572 pointer in mplsOamIdMeTable points to an entry in 573 the pwTable [RFC5601]. 575 If the value is section service type, the service 576 pointer in mplsOamIdMeTable points to an entry in 577 the mplsTunnelTable [RFC3812]." 578 REFERENCE 579 "1. Multiprotocol Label Switching (MPLS) Traffic 580 Engineering (TE) Management Information 581 Base (MIB), Srinivasan, et al, RFC 3812, June 2004 582 2. Pseudowire (PW) Management Information Base (MIB), 583 Nadeau & Zelig, RFC 5601, July 2009." 584 DEFVAL { lsp } 585 ::= { mplsOamIdMegEntry 7 } 587 mplsOamIdMegMpLocation OBJECT-TYPE 588 SYNTAX INTEGER { 590 perNode (1), 591 perInterface (2) 592 } 593 MAX-ACCESS read-create 594 STATUS current 595 DESCRIPTION 596 "Indicates the MP location type for this MEG. 598 If the value is perNode, then the MEG in the LSR supports 599 only perNode MEP/MIP, i.e., only one MEP/MIP in an LSR. 601 If the value is perInterface, then the MEG in the LSR 602 supports perInterface MEPs/MIPs, i.e., two MEPs/MIPs in 603 an LSR." 604 REFERENCE 605 "RFC 6371, Operations, Administration, and Maintenance 606 Framework for MPLS-Based Transport Networks, 607 September 2011." 608 DEFVAL { perNode } 609 ::= { mplsOamIdMegEntry 8 } 611 mplsOamIdMegPathFlow OBJECT-TYPE 612 SYNTAX INTEGER { 613 unidirectionalPointToPoint (1), 614 coRoutedBidirectionalPointToPoint (2), 615 associatedBidirectionalPointToPoint (3), 616 unidirectionalPointToMultiPoint (4) 617 } 618 MAX-ACCESS read-create 619 STATUS current 620 DESCRIPTION 621 "Indicates the transport path flow for this MEG. 622 In case of a unidirectional point-to-point transport path, 623 a single unidirectional Maintenance Entity is defined to 624 monitor it. 625 In case of associated bidirectional point-to-point transport 626 paths, two independent unidirectional Maintenance Entities are 627 defined to independently monitor each direction. 628 In case of co-routed bidirectional point-to-point transport 629 paths, a single bidirectional Maintenance Entity is defined to 630 monitor both directions congruently. 631 In case of unidirectional point-to-multipoint transport paths, 632 a single unidirectional Maintenance Entity for each leaf is 633 defined to monitor the transport path from the root to 634 that leaf." 635 REFERENCE 636 "RFC 6371, Operations, Administration, and Maintenance 637 Framework for MPLS-Based Transport Networks, 638 September 2011." 639 DEFVAL { coRoutedBidirectionalPointToPoint } 640 ::= { mplsOamIdMegEntry 9 } 642 mplsOamIdMegOperStatus OBJECT-TYPE 643 SYNTAX INTEGER { 644 up (1), 645 down (2) 646 } 647 MAX-ACCESS read-only 648 STATUS current 649 DESCRIPTION 650 "This object specifies the operational status of the 651 Maintenance Entity Group (MEG). This object is used to 652 send the notification to the SNMP manager about the MEG. 654 The value up (1) indicates that the MEG and its monitored 655 path are operationally up. The value down (2) indicates 656 that the MEG is operationally down. 658 When the value of mplsOamIdMegOperStatus is up(1), all 659 the bits of mplsOamIdMegSubOperStatus must be cleared. 660 When the value of mplsOamIdMegOperStatus is down(2), 661 at least one bit of mplsOamIdMegSubOperStatus must be 662 set." 663 ::= { mplsOamIdMegEntry 10 } 665 mplsOamIdMegSubOperStatus OBJECT-TYPE 666 SYNTAX BITS { 667 megDown (0), 668 meDown (1), 669 oamAppDown (2), 670 pathDown (3) 671 } 672 MAX-ACCESS read-only 673 STATUS current 674 DESCRIPTION 675 "This object specifies the reason why the MEG operational 676 status as mentioned by the object mplsOamIdMegOperStatus 677 is down. This object is used to send the notification to 678 the SNMP manager about the MEG. 680 The bit 0 (megDown) indicates the MEG is down. 681 The bit 1 (meDown) indicates the ME table is 682 down. 683 The bit 2 (oamAppDown) indicates that the 684 OAM application has notified that the entity (LSP or PW) 685 monitored by this MEG is down. Currently, BFD is the 686 only supported OAM application. 687 The bit 3 (pathDown) indicates that the underlying 688 LSP or PW is down." 689 ::= { mplsOamIdMegEntry 11 } 691 mplsOamIdMegRowStatus OBJECT-TYPE 692 SYNTAX RowStatus 693 MAX-ACCESS read-create 694 STATUS current 695 DESCRIPTION 697 "This variable is used to create, modify, and/or delete 698 a row in this table. When a row in this table is in 699 active(1) state, no objects in that row can be modified 700 by the agent except mplsOamIdMegRowStatus." 701 ::= { mplsOamIdMegEntry 12 } 703 mplsOamIdMegStorageType OBJECT-TYPE 704 SYNTAX StorageType 705 MAX-ACCESS read-create 706 STATUS current 707 DESCRIPTION 708 "This variable indicates the storage type for this 709 object. 710 Conceptual rows having the value 'permanent' 711 need not allow write-access to any columnar 712 objects in the row." 713 DEFVAL { volatile } 714 ::= { mplsOamIdMegEntry 13 } 716 -- End of MPLS Transport Profile MEG table 718 -- Start of MPLS Transport Profile ME table 720 mplsOamIdMeIndexNext OBJECT-TYPE 721 SYNTAX IndexIntegerNextFree (0..4294967295) 722 MAX-ACCESS read-only 723 STATUS current 724 DESCRIPTION 725 "This object contains an unused value for 726 mplsOamIdMeIndex, or a zero to indicate 727 that none exist. Negative values are not allowed, 728 as they do not correspond to valid values of 729 mplsOamIdMeIndex." 730 ::= { mplsOamIdObjects 3 } 732 mplsOamIdMeMpIndexNext OBJECT-TYPE 733 SYNTAX IndexIntegerNextFree (0..4294967295) 734 MAX-ACCESS read-only 735 STATUS current 736 DESCRIPTION 737 "This object contains an unused value for 738 mplsOamIdMeMpIndex, or a zero to indicate 739 that none exist. Negative values are not allowed, 740 as they do not correspond to valid values of 741 mplsOamIdMeMpIndex." 742 ::= { mplsOamIdObjects 4 } 744 mplsOamIdMeTable OBJECT-TYPE 745 SYNTAX SEQUENCE OF MplsOamIdMeEntry 746 MAX-ACCESS not-accessible 747 STATUS current 748 DESCRIPTION 749 "This table contains MPLS-TP maintenance entity 750 information. 752 ME is some portion of a transport path that requires 753 management bounded by two points (called MEPs), and the 754 relationship between those points to which maintenance 755 and monitoring operations apply. 757 This table is generic enough to handle MEPs and MIPs 758 information within a MEG." 759 ::= { mplsOamIdObjects 5 } 761 mplsOamIdMeEntry OBJECT-TYPE 762 SYNTAX MplsOamIdMeEntry 763 MAX-ACCESS not-accessible STATUS current 764 DESCRIPTION 765 "An entry in this table represents MPLS-TP maintenance 766 entity. This entry represents the ME if the source and 767 sink MEPs are defined. 769 A ME is a p2p entity. One ME has two such MEPs. 770 A MEG is a group of one or more MEs. One MEG can have 771 two or more MEPs. 773 For P2P LSP, one MEG has one ME and this ME is associated 774 two MEPs (source and sink MEPs) within a MEG. 775 Each mplsOamIdMeIndex value denotes the ME within a MEG. 777 In case of unidirectional point-to-point transport paths, 778 a single unidirectional Maintenance Entity is defined to 779 monitor it and mplsOamIdMeServicePointer points to 780 unidirectional point-to-point path. 782 In case of associated bidirectional point-to-point 783 transport paths, two independent unidirectional 784 Maintenance Entities are defined to independently monitor 785 each direction and each mplsOamIdMeServicePointer MIB 786 object points to unique unidirectional transport path. 787 This has implications for transactions that terminate at 788 or query a MIP, as a return path from MIP to source MEP 789 does not necessarily exist within the MEG. 791 In case of co-routed bidirectional point-to-point 792 transport paths, a single bidirectional Maintenance Entity 793 is defined to monitor both directions congruently and 794 mplsOamIdMeServicePointer MIB object points to co-routed 795 bidirectional point-to-point transport path. 797 In case of unidirectional point-to-multipoint transport 798 paths, a single unidirectional Maintenance entity for each 799 leaf is defined to monitor the transport path from the 800 root to that leaf and each leaf has different transport 801 path information in mplsOamIdMeServicePointer MIB object. 802 Note that the MplsOamIdMeEntry should be created manually 803 once the MEG is configured for OAM operations." 804 INDEX { mplsOamIdMegIndex, 805 mplsOamIdMeIndex, 806 mplsOamIdMeMpIndex 807 } 808 ::= { mplsOamIdMeTable 1 } 810 MplsOamIdMeEntry ::= SEQUENCE { 811 mplsOamIdMeIndex Unsigned32, 812 mplsOamIdMeMpIndex Unsigned32, 813 mplsOamIdMeName SnmpAdminString, 814 mplsOamIdMeMpIfIndex InterfaceIndexOrZero, 815 mplsOamIdMeSourceMepIndex Unsigned32, 816 mplsOamIdMeSinkMepIndex Unsigned32, 817 mplsOamIdMeMpType INTEGER, 818 mplsOamIdMeMepDirection INTEGER, 819 mplsOamIdMeProactiveOamPhbTCValue MplsOamPhbTCValue, 820 mplsOamIdMeOnDemandOamPhbTCValue MplsOamPhbTCValue, 821 mplsOamIdMeServicePointer RowPointer, 822 mplsOamIdMeRowStatus RowStatus, 823 mplsOamIdMeStorageType StorageType 824 } 826 mplsOamIdMeIndex OBJECT-TYPE 827 SYNTAX Unsigned32 (1..4294967295) 828 MAX-ACCESS not-accessible 829 STATUS current 830 DESCRIPTION 831 "Uniquely identifies a maintenance entity index within 832 a MEG. Managers should obtain new values for row 833 creation in this table by reading 834 mplsOamIdMeIndexNext." 835 ::= { mplsOamIdMeEntry 1 } 837 mplsOamIdMeMpIndex OBJECT-TYPE 839 SYNTAX Unsigned32 (1..4294967295) 840 MAX-ACCESS not-accessible 841 STATUS current 842 DESCRIPTION 843 "Indicates the maintenance point index, used to create 844 multiple MEPs in a node of single ME. The value of this 845 object can be MEP index or MIP index. Managers should 846 obtain new values for row creation in this table by reading 847 mplsOamIdMeMpIndexNext." 848 ::= { mplsOamIdMeEntry 2 } 850 mplsOamIdMeName OBJECT-TYPE 851 SYNTAX SnmpAdminString (SIZE(1..48)) 852 MAX-ACCESS read-create 853 STATUS current 854 DESCRIPTION 855 "This object denotes the ME name, each 856 Maintenance Entity has unique name within MEG." 857 ::= { mplsOamIdMeEntry 3 } 859 mplsOamIdMeMpIfIndex OBJECT-TYPE 860 SYNTAX InterfaceIndexOrZero 861 MAX-ACCESS read-create 862 STATUS current 863 DESCRIPTION 864 "Indicates the maintenance point interface. 865 If the mplsOamIdMegMpLocation object value 866 is perNode (1), the MP interface index should point 867 to incoming interface or outgoing interface or 868 zero (indicates the MP OAM packets are initiated 869 from forwarding engine). 871 If the mplsOamIdMegMpLocation object value is 872 perInterface (2), the MP interface index should point to 873 incoming interface or outgoing interface." 874 REFERENCE 875 "RFC 6371, Operations, Administration, and Maintenance 876 Framework for MPLS-Based Transport Networks, 877 September 2011. 878 RFC 2863 - The Interfaces Group MIB, McCloghrie, K., 879 and F. Kastenholtz, June 2000." 880 DEFVAL { 0 } 881 ::= { mplsOamIdMeEntry 4 } 883 mplsOamIdMeSourceMepIndex OBJECT-TYPE 884 SYNTAX Unsigned32 885 MAX-ACCESS read-create 886 STATUS current 887 DESCRIPTION 888 "Indicates the source MEP Index of the ME. This object 889 should be configured if mplsOamIdMegOperatorType object 890 in the mplsOamIdMegEntry is configured as iccBased (2). 891 If the MEG is configured for IP based operator, 892 the value of this object should be set zero and the MEP 893 ID will be automatically derived from the service 894 Identifiers(MPLS-TP LSP/PW Identifier)." 895 DEFVAL { 0 } 896 ::= { mplsOamIdMeEntry 5 } 898 mplsOamIdMeSinkMepIndex OBJECT-TYPE 899 SYNTAX Unsigned32 900 MAX-ACCESS read-create 901 STATUS current 902 DESCRIPTION 903 "Indicates the sink MEP Index of the ME. This object 904 should be configured if mplsOamIdMegOperatorType object 905 in the mplsOamIdMegEntry is configured as iccBased (2). 906 If the MEG is configured for IP based operator, 907 the value of this object should be set zero and the MEP 908 ID will be automatically derived from the service 909 Identifiers(MPLS-TP LSP/PW Identifier)." 910 DEFVAL { 0 } 911 ::= { mplsOamIdMeEntry 6 } 913 mplsOamIdMeMpType OBJECT-TYPE 914 SYNTAX INTEGER { 915 mep (1), 916 mip (2) 917 } 918 MAX-ACCESS read-create 919 STATUS current 920 DESCRIPTION 921 "Indicates the maintenance point type within the MEG. 923 The object should have the value mep (1), only in the 924 Ingress or Egress nodes of the transport path. 926 The object can have the value mip (2), 927 in the intermediate nodes and possibly in the end nodes 928 of the transport path." 929 DEFVAL { mep } 930 ::= { mplsOamIdMeEntry 7 } 932 mplsOamIdMeMepDirection OBJECT-TYPE 933 SYNTAX INTEGER { 934 up (1), 935 down (2), 936 notApplicable (3) 937 } 938 MAX-ACCESS read-create 939 STATUS current 940 DESCRIPTION 941 "Indicates the direction of the MEP. This object 942 should be configured if mplsOamIdMeMpType is 944 configured as mep (1) else notApplicable (3) is set." 945 DEFVAL { down } 946 ::= { mplsOamIdMeEntry 8 } 948 mplsOamIdMeProactiveOamPhbTCValue OBJECT-TYPE 949 SYNTAX MplsOamPhbTCValue 950 MAX-ACCESS read-create 951 STATUS current 952 DESCRIPTION 953 "Indicates the Per-hop Behavior (PHB) value for this source 954 MEP generated proactive traffic." 955 DEFVAL { ef } 956 ::= { mplsOamIdMeEntry 9 } 958 mplsOamIdMeOnDemandOamPhbTCValue OBJECT-TYPE 959 SYNTAX MplsOamPhbTCValue 960 MAX-ACCESS read-create 961 STATUS current 962 DESCRIPTION 963 "Indicates the Per-hop Behavior (PHB) value for this 964 source MEP generated on-demand traffic." 965 DEFVAL { ef } 967 ::= { mplsOamIdMeEntry 10 } 969 mplsOamIdMeServicePointer OBJECT-TYPE 971 SYNTAX RowPointer 972 MAX-ACCESS read-create 973 STATUS current 974 DESCRIPTION 975 "This variable represents a pointer to the MPLS-TP 976 transport path. This value MUST point at an entry in the 977 mplsTunnelEntry if mplsOamIdMegServicePointerType 978 is configured as lsp (1) or at an entry in the pwEntry if 979 mplsOamIdMegServicePointerType is configured 980 as pseudowire (2). 982 Note: This service pointer object, is placed in ME table 983 instead of MEG table, since it will be useful in case of 984 point-to-multipoint, where each ME will point to different 985 branches of a P2MP tree." 986 ::= { mplsOamIdMeEntry 11 } 988 mplsOamIdMeRowStatus OBJECT-TYPE 989 SYNTAX RowStatus 990 MAX-ACCESS read-create 991 STATUS current 992 DESCRIPTION 993 "This variable is used to create, modify, and/or 994 delete a row in this table. When a row in this 995 table is in active(1) state, no objects in that row 996 can be modified by the agent except 997 mplsOamIdMeRowStatus." 998 ::= { mplsOamIdMeEntry 12 } 1000 mplsOamIdMeStorageType OBJECT-TYPE 1001 SYNTAX StorageType 1002 MAX-ACCESS read-create 1003 STATUS current 1004 DESCRIPTION 1005 "This variable indicates the storage type for this 1006 object. 1007 Conceptual rows having the value 'permanent' 1008 need not allow write-access to any columnar 1009 objects in the row." 1010 DEFVAL { volatile } 1011 ::= { mplsOamIdMeEntry 13 } 1013 -- End of MPLS Transport Profile ME table 1015 -- End of MPLS-TP OAM Tables 1017 -- Notification Definitions of MPLS-TP identifiers 1019 mplsOamIdDefectCondition NOTIFICATION-TYPE 1020 OBJECTS { 1021 mplsOamIdMegName, 1022 mplsOamIdMeName, 1023 mplsOamIdMegOperStatus, 1024 mplsOamIdMegSubOperStatus 1025 } 1026 STATUS current 1027 DESCRIPTION 1028 "This notification is sent whenever the operational 1029 status of MEG is changed." 1030 ::= { mplsOamIdNotifications 1 } 1032 -- End of Notifications. 1034 -- Module Compliance. 1036 mplsOamIdCompliances 1037 OBJECT IDENTIFIER ::= { mplsOamIdConformance 1 } 1039 mplsOamIdGroups 1040 OBJECT IDENTIFIER ::= { mplsOamIdConformance 2 } 1042 -- Compliance requirement for fully compliant implementations. 1044 mplsOamIdModuleFullCompliance MODULE-COMPLIANCE 1045 STATUS current 1046 DESCRIPTION "Compliance statement for agents that provide full 1047 support for MPLS-TP-OAM-STD-MIB. Such devices can 1048 then be monitored and also be configured using 1049 this MIB module." 1051 MODULE IF-MIB -- The Interfaces Group MIB, RFC 2863. 1052 MANDATORY-GROUPS { 1053 ifGeneralInformationGroup, 1054 ifCounterDiscontinuityGroup 1055 } 1057 MODULE -- This module. 1058 MANDATORY-GROUPS { 1059 mplsOamIdMegGroup, 1060 mplsOamIdMeGroup 1061 } 1063 GROUP mplsOamIdNotificationObjectsGroup 1064 DESCRIPTION "This group is only mandatory for those 1065 implementations which can efficiently implement 1066 the notifications contained in this group." 1068 GROUP mplsOamIdNotificationGroup 1069 DESCRIPTION "This group is only mandatory for those 1070 implementations which can efficiently implement 1071 the notifications contained in this group." 1073 ::= { mplsOamIdCompliances 1 } 1075 -- Units of conformance. 1077 mplsOamIdMegGroup OBJECT-GROUP 1078 OBJECTS { 1079 mplsOamIdMegIndexNext, 1080 mplsOamIdMegName, 1081 mplsOamIdMegOperatorType, 1082 mplsOamIdMegIdCc, 1083 mplsOamIdMegIdIcc, 1084 mplsOamIdMegIdUmc, 1085 mplsOamIdMegServicePointerType, 1086 mplsOamIdMegMpLocation, 1087 mplsOamIdMegOperStatus, 1088 mplsOamIdMegSubOperStatus, 1089 mplsOamIdMegPathFlow, 1090 mplsOamIdMegRowStatus, 1091 mplsOamIdMegStorageType 1092 } 1094 STATUS current 1095 DESCRIPTION 1096 "Collection of objects needed for MPLS MEG information." 1097 ::= { mplsOamIdGroups 1 } 1099 mplsOamIdMeGroup OBJECT-GROUP 1100 OBJECTS { 1101 mplsOamIdMeIndexNext, 1102 mplsOamIdMeMpIndexNext, 1103 mplsOamIdMeName, 1104 mplsOamIdMeMpIfIndex, 1105 mplsOamIdMeSourceMepIndex, 1106 mplsOamIdMeSinkMepIndex, 1107 mplsOamIdMeMpType, 1108 mplsOamIdMeMepDirection, 1109 mplsOamIdMeProactiveOamPhbTCValue, 1110 mplsOamIdMeOnDemandOamPhbTCValue, 1111 mplsOamIdMeServicePointer, 1112 mplsOamIdMeRowStatus, 1113 mplsOamIdMeStorageType 1114 } 1115 STATUS current 1116 DESCRIPTION 1117 "Collection of objects needed for MPLS ME information." 1118 ::= { mplsOamIdGroups 2 } 1120 mplsOamIdNotificationObjectsGroup OBJECT-GROUP 1121 OBJECTS { 1123 mplsOamIdMegOperStatus, 1125 mplsOamIdMegSubOperStatus 1126 } 1127 STATUS current 1128 DESCRIPTION 1129 "Collection of objects needed to implement notifications." 1130 ::= { mplsOamIdGroups 3 } 1132 mplsOamIdNotificationGroup NOTIFICATION-GROUP 1133 NOTIFICATIONS { 1134 mplsOamIdDefectCondition 1135 } 1136 STATUS current 1137 DESCRIPTION 1138 "Set of notifications implemented in this module." 1139 ::= { mplsOamIdGroups 4 } 1141 END 1143 8. Security Consideration 1145 There is a number of management objects defined in this MIB module 1146 that has a MAX-ACCESS clause of read-create. Such objects may be 1147 considered sensitive or vulnerable in some network environments. 1148 The support for SET operations in a non-secure environment 1149 without proper protection can have a negative effect on network 1150 operations. 1152 Some of the readable objects in this MIB module (i.e., objects 1153 with a MAX-ACCESS other than not-accessible) may be considered 1154 sensitive or vulnerable in some network environments. 1155 It is thus important to control even GET and/or NOTIFY access 1156 to these objects and possibly to even encrypt the values of these 1157 objects when sending them over the network via SNMP. These are 1158 the tables and objects and their sensitivity/vulnerability: 1160 SNMP versions prior to SNMPv3 did not include adequate security. 1161 Even if the network itself is secure (for example by using IPsec), 1162 even then, there is no control as to who on the secure network 1163 is allowed to access and GET/SET (read/change/create/delete) 1164 the objects in this MIB module. 1166 It is RECOMMENDED that implementers consider the security features 1167 as provided by the SNMPv3 framework (see [RFC3410], section 8), 1168 including full supports for the SNMPv3 cryptographic mechanisms 1169 (for authentication and privacy). 1171 Further, deployment of SNMP versions prior to SNMPv3 is NOT 1172 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 1173 enable cryptographic security. It is then a customer/operator 1174 responsibility to ensure that the SNMP entity giving access to an 1175 instance of this MIB module is properly configured to give access to 1176 the objects only to those principles (users) that have legitimate 1177 rights to indeed GET or SET (change/create/delete) them. 1179 9. IANA Considerations 1180 IANA is requested to assign an OID for the MIB module from the "MIB 1181 Transmission Group - MPLS STD" sub-registry of the "Internet-standard 1182 MIB - Transmission Group" registry for the MPLS-TP OAM ID MIB module 1183 specified in this document. 1185 10. References 1187 10.1 Normative References 1189 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1190 Requirement Levels", BCP 14, RFC 2119, March 1997. 1192 [RFC2578] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 1193 "Structure of Management Information Version 2 (SMIv2)", 1194 STD 58, RFC 2578, April 1999. 1196 [RFC2579] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 1197 "Textual Conventions for SMIv2", STD 58, RFC 2579, April 1198 1999. 1200 [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 1201 "Conformance Statements for SMIv2", STD 58, RFC 2580, 1202 April 1999. 1204 [RFC2863] McCloghrie, K. and F. Kastenholtz, "The Interfaces Group 1205 MIB ", RFC 2863, June 2000 1207 [RFC3031] Rosen, E., Viswanathan, A., and R. Callon, 1208 "Multiprotocol Label Switching Architecture", RFC 3031, 1209 January 2001. 1211 [RFC3289] Baker, F., Chan, K., and A. Smith, "Management 1212 Information Base for the Differentiated Services 1213 Architecture", RFC 3289, May 2002. 1215 [RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An 1216 Architecture for Describing Simple Network Management 1217 Protocol (SNMP) Management Frameworks", STD 62, RFC 1218 3411, December 2002. 1220 [RFC5601] Zelig, D., Ed., and T. Nadeau, Ed., "Pseudowire (PW) 1221 Management Information Base (MIB)", RFC 5601, July 2009. 1223 10.2 Informative References 1225 [RFC3410] J. Case, R. Mundy, D. pertain, B.Stewart, "Introduction 1226 and Applicability Statement for Internet Standard 1227 Management Framework", RFC 3410, December 2002. 1229 [RFC3811] Nadeau, T., Ed., and J. Cucchiara, Ed., "Definitions of 1230 Textual Conventions (TCs) for Multiprotocol Label 1231 Switching (MPLS) Management", RFC 3811, June 2004. 1233 [RFC3812] Srinivasan, C., Viswanathan, A., and T. Nadeau, 1234 "Multiprotocol Label Switching (MPLS) Traffic 1235 Engineering (TE) Management Information Base (MIB)", RFC 1236 3812, June 2004. 1238 [RFC3813] Srinivasan, C., Viswanathan, A., and T. Nadeau, 1239 "Multiprotocol Label Switching (MPLS) Label Switching 1240 (LSR) Router Management Information Base (MIB)", RFC 1241 3813, June 2004. 1243 [RFC5654] Niven-Jenkins, B., Ed., Brungard, D., Ed., Betts, M., 1244 Ed., Sprecher, N., and S. Ueno, "Requirements of an MPLS 1245 Transport Profile", RFC 5654, September 2009. 1247 [RFC6370] Bocci, M., Swallow, G., and E. Gray, "MPLS-TP 1248 Identifiers", RFC 6370, September 2011. 1250 [RFC6371] Busi, I., Niven-Jenkins, B., and D. Allan, "MPLS-TP OAM 1251 Framework and Overview", RFC 6371, September 2011. 1253 [RFC6923] R. Winter, Ed, E. Gray, Ed., H. van Helvoort, and M. 1254 Betts, "MPLS-TP Identifiers Following ITU-T 1255 Conventions", RFC 6923, May 2013. 1257 [RFC5860] M. Vigoureux, Ed, D. Ward, Ed, M. Betts, Ed, "OAM in MPLS 1258 Transport Networks", RFC 5860, May 2010. 1260 11. Acknowledgments 1262 We wish to thank Muly Ilan, Adrian Farrel, Joan Cucchiara and 1263 Weiying Cheng for their valuable comments on this document. 1265 12. Authors' Addresses 1267 Venkatesan Mahalingam 1268 Dell Inc. 1269 5450 Great America Parkway, 1270 Santa Clara, CA 95054, USA 1271 Email: venkat.mahalingams@gmail.com 1273 Sam Aldrin 1274 Huawei Technologies, co. 1275 2330 Central Express Way, 1276 Santa Clara, CA 95051, USA 1277 Email: aldrin.ietf@gmail.com 1279 Thomas D. Nadeau 1280 Brocade 1281 Email: tnadeau@lucidvision.com 1283 Kannan KV Sampath 1284 Redeem, 1285 India 1286 Email: kannankvs@gmail.com 1288 Ping Pan 1289 Infinera 1290 Email: ppan@infinera.com 1292 Sami Boutros 1293 Cisco Systems, Inc. 1294 3750 Cisco Way 1295 San Jose, California 95134 1296 USA 1297 Email: sboutros@cisco.com