idnits 2.17.1 draft-ietf-mpls-tp-oam-id-mib-03.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 18, 2013) is 3963 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 20, 2013 M.Venkatesan 6 Dell Inc. 7 Kannan KV Sampath 8 Redeem 9 Thomas D. Nadeau 10 Juniper Networks 12 June 18, 2013 14 MPLS-TP Operations, Administration, and Management (OAM) Identifiers 15 Management Information Base (MIB) 16 draft-ietf-mpls-tp-oam-id-mib-03 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 20, 2013. 49 Copyright and License Notice 51 Copyright (c) 2013 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 . . . . . . . . . . . . . . . . . . . . . . 26 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 "201306180000Z" -- June 18, 2013 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 Juniper Networks 290 10 Technology Park Drive, 291 Westford, MA 01886 292 Email: tnadeau@juniper.net 294 Venkatesan Mahalingam 295 Dell Inc. 296 350 Holger way, San Jose, CA, USA 297 Email: venkat.mahalingams@gmail.com 299 Kannan KV Sampath 300 Redeem, 301 India 302 Email: kannankvs@gmail.com 304 Ping Pan 305 Infinera 306 Email: ppan@infinera.com 308 Sami Boutros 309 Cisco Systems, Inc. 310 3750 Cisco Way 311 San Jose, California 95134 312 USA 313 Email: sboutros@cisco.com 315 " 316 DESCRIPTION 317 "Copyright (c) 2013 IETF Trust and the persons identified 318 as the document authors. All rights reserved. 320 This MIB module contains generic object definitions for 321 MPLS OAM maintenance identifiers." 323 -- Revision history. 325 REVISION 326 "201306180000Z" -- June 18, 2013 327 DESCRIPTION 328 "MPLS OAM Identifiers MIB objects for LSPs and 329 Pseudowires" 331 ::= { mplsStdMIB xxx } -- xxx to be replaced with the correct 332 -- OID value assigned by 333 -- IANA (see section 9). 335 -- TEXTUAL-CONVENTIONs 337 MplsOamPhbTCValue ::= TEXTUAL-CONVENTION 338 STATUS current 339 DESCRIPTION 340 "This is the Per-hop Behavior (PHB) traffic class values 341 for the MPLS OAM operations." 342 SYNTAX INTEGER { 343 be (1), 344 af1 (2), 345 af2 (3), 346 af3 (4), 347 af4 (5), 348 ef (6), 349 cs6 (7), 350 cs7 (8) 351 } 353 -- Top level components of this MIB module. 355 -- notifications 356 mplsOamIdNotifications 357 OBJECT IDENTIFIER ::= { mplsOamIdStdMIB 0 } 358 -- tables, scalars 359 mplsOamIdObjects OBJECT IDENTIFIER ::= { mplsOamIdStdMIB 1 } 360 -- conformance 361 mplsOamIdConformance 362 OBJECT IDENTIFIER ::= { mplsOamIdStdMIB 2 } 364 -- Start of MPLS Transport Profile MEG table 366 mplsOamIdMegIndexNext OBJECT-TYPE 367 SYNTAX IndexIntegerNextFree (0..4294967295) 368 MAX-ACCESS read-only 369 STATUS current 370 DESCRIPTION 371 "This object contains an unused value for 372 mplsOamIdMegIndex, or a zero to indicate 373 that none exist. Negative values are not allowed, 374 as they do not correspond to valid values of 375 mplsOamIdMegIndex." 376 ::= { mplsOamIdObjects 1 } 377 mplsOamIdMegTable OBJECT-TYPE 378 SYNTAX SEQUENCE OF MplsOamIdMegEntry 379 MAX-ACCESS not-accessible 380 STATUS current 381 DESCRIPTION 382 "This table contains information about the Maintenance 383 Entity Groups (MEG). 385 MEG as mentioned in MPLS-TP OAM framework defines a set 386 of one or more maintenance entities (ME). 387 Maintenance Entities define a relationship between any 388 two points of a transport path in an OAM domain to which 389 maintenance and monitoring operations apply." 390 ::= { mplsOamIdObjects 2 } 392 mplsOamIdMegEntry OBJECT-TYPE 393 SYNTAX MplsOamIdMegEntry 394 MAX-ACCESS not-accessible 395 STATUS current 396 DESCRIPTION 397 "An entry in this table represents MPLS-TP MEG. 398 An entry can be created by a network administrator 399 or by an SNMP agent as instructed by an MPLS-TP OAM 400 Framework. 402 When a new entry is created with 403 mplsOamIdMegOperatorType set to ipCompatible (1), 404 then as per [RFC6370] (MEG_ID for LSP is LSP_ID and 405 MEG_ID for PW is PW_Path_ID), MEP_ID can be 406 automatically formed. 408 For co-routed bidirectional LSP, MEG_ID is 409 A1-{Global_ID::Node_ID::Tunnel_Num}::Z9-{Global_ID:: 410 Node_ID::Tunnel_Num}::LSP_Num. 412 For associated bidirectional LSP, MEG_ID is A1- 413 {Global_ID::Node_ID::Tunnel_Num::LSP_Num}:: Z9- 414 {Global_ID::Node_ID::Tunnel_Num::LSP_Num} 416 For LSP, MEP_ID is formed using, 417 Global_ID::Node_ID::Tunnel_Num::LSP_Num 419 For PW, MEG_ID is formed using AGI::A1- 420 {Global_ID::Node_ID::AC_ID}:: Z9- 421 {Global_ID::Node_ID::AC_ID}. 423 For PW, MEP_ID is formed using 424 AGI::Global_ID::Node_ID::AC_ID 426 MEP_ID is retrieved from the mplsOamIdMegServicePointer 427 object based on the mplsOamIdMegServicePointerType value. 428 ICC MEG_ID for LSP and PW is formed using the objects 429 mplsOamIdMegIdIcc and mplsOamIdMegIdUmc. 431 MEP_ID can be formed using MEG_ID::MEP_Index." 432 REFERENCE 433 "1. RFC5860, Requirements for OAM in MPLS Transport 434 Networks, May 2010. 435 2. RFC6371, Operations, Administration, and Maintenance 436 Framework for MPLS-Based Transport Networks, 437 September 2011 Section 3. 438 3. RFC6370, MPLS Transport Profile (MPLS-TP) Identifiers. 439 4. RFC6923, MPLS Transport Profile (MPLS-TP) Identifiers 440 Following ITU-T Conventions." 441 INDEX { mplsOamIdMegIndex } 442 ::= { mplsOamIdMegTable 1 } 444 MplsOamIdMegEntry ::= SEQUENCE { 445 mplsOamIdMegIndex Unsigned32, 446 mplsOamIdMegName SnmpAdminString, 447 mplsOamIdMegOperatorType INTEGER, 448 mplsOamIdMegIdCc SnmpAdminString, 449 mplsOamIdMegIdIcc SnmpAdminString, 450 mplsOamIdMegIdUmc SnmpAdminString, 451 mplsOamIdMegServicePointerType INTEGER, 452 mplsOamIdMegMpLocation INTEGER, 453 mplsOamIdMegPathFlow INTEGER, 454 mplsOamIdMegOperStatus INTEGER, 455 mplsOamIdMegSubOperStatus BITS, 456 mplsOamIdMegRowStatus RowStatus, 457 mplsOamIdMegStorageType StorageType 458 } 460 mplsOamIdMegIndex OBJECT-TYPE 461 SYNTAX Unsigned32 (1..4294967295) 462 MAX-ACCESS not-accessible 463 STATUS current 464 DESCRIPTION 465 "Index for the conceptual row identifying a MEG within 466 this MEG table. Managers should obtain new values for row 467 creation in this table by reading 468 mplsOamIdMegIndexNext." 469 ::= { mplsOamIdMegEntry 1 } 471 mplsOamIdMegName OBJECT-TYPE 472 SYNTAX SnmpAdminString (SIZE(0..48)) 473 MAX-ACCESS read-create 474 STATUS current 475 DESCRIPTION 476 "Each Maintenance Entity Group has unique name amongst 477 all those used or available to a service provider or 478 operator. It facilitates easy identification of 479 administrative responsibility for each MEG." 480 ::= { mplsOamIdMegEntry 2 } 482 mplsOamIdMegOperatorType OBJECT-TYPE 483 SYNTAX INTEGER { 484 ipCompatible (1), 486 iccBased (2) 487 } 488 MAX-ACCESS read-create 489 STATUS current 490 DESCRIPTION 491 "Indicates the operator type for MEG. Conceptual rows 492 having 'iccBased' as operator type, MUST have valid 493 values for the objects mplsOamIdMegIdIcc and 494 mplsOamIdMegIdUmc when the row status is active." 495 REFERENCE 496 "1. RFC6370, MPLS Transport Profile (MPLS-TP) 497 Identifiers. 498 2. RFC6923, MPLS Transport Profile (MPLS-TP) Identifiers 499 Following ITU-T Conventions. Section 3.1" 500 DEFVAL { ipCompatible } 501 ::= { mplsOamIdMegEntry 3 } 503 mplsOamIdMegIdCc OBJECT-TYPE 504 SYNTAX SnmpAdminString (SIZE(0..2)) 505 MAX-ACCESS read-create 506 STATUS current 507 DESCRIPTION 508 "Global uniqueness is assured by concatenating the ICC 509 with a Country Code (CC). The Country Code (alpha-2) 510 is a string of two alphabetic characters represented 511 with upper case letters (i.e., A-Z). 513 This object MUST contain a non-null ICC value if 514 the MplsOamIdMegOperatorType value is iccBased(2), 515 otherwise a null ICC value with octet size 0 516 should be assigned." 517 REFERENCE 518 "RFC6923, MPLS Transport Profile (MPLS-TP) Identifiers 519 Following ITU-T Conventions. Section 3." 520 DEFVAL {""} 521 ::= { mplsOamIdMegEntry 4 } 523 mplsOamIdMegIdIcc OBJECT-TYPE 524 SYNTAX SnmpAdminString (SIZE(0..6)) 525 MAX-ACCESS read-create 526 STATUS current 527 DESCRIPTION 528 "Unique code assigned to Network Operator or Service 529 Provider maintained by ITU-T. The ITU Carrier Code 530 used to form MEGID. 532 This object MUST contain a non-null ICC value if 533 the MplsOamIdMegOperatorType value is iccBased(2), 534 otherwise a null ICC value with octet size 0 535 should be assigned." 536 REFERENCE 537 "RFC6923, MPLS Transport Profile (MPLS-TP) Identifiers 538 Following ITU-T Conventions. Section 3.1." 539 DEFVAL {""} 540 ::= { mplsOamIdMegEntry 5 } 542 mplsOamIdMegIdUmc OBJECT-TYPE 543 SYNTAX SnmpAdminString (SIZE(0..7)) 544 MAX-ACCESS read-create 545 STATUS current 546 DESCRIPTION 547 "Unique code assigned by Network Operator or Service 548 Provider and is appended to mplsOamIdMegIdIcc to form 549 the MEGID. 550 This object MUST contain a non-null ICC value if 551 the MplsOamIdMegOperatorType value is iccBased(2), 552 otherwise a null ICC value with octet size 0 553 should be assigned." 554 REFERENCE 555 "RFC6923, MPLS Transport Profile (MPLS-TP) Identifiers 556 Following ITU-T Conventions. Section 7.1." 557 DEFVAL {""} 558 ::= { mplsOamIdMegEntry 6 } 560 mplsOamIdMegServicePointerType OBJECT-TYPE 562 SYNTAX INTEGER { 563 lsp (1), 564 pseudowire (2), 565 section (3) 566 } 567 MAX-ACCESS read-create 568 STATUS current 569 DESCRIPTION 570 "Indicates the service type for the MEG. 571 If the service type indicates lsp, the service pointer 572 in mplsOamIdMeTable points to an entry in 573 the mplsTunnelTable [RFC3812]. 575 If the value is pseudowire service type, the service 576 pointer in mplsOamIdMeTable points to an entry in 577 the pwTable [RFC5601]. 579 If the value is section service type, the service 580 pointer in mplsOamIdMeTable points to an entry in 581 the mplsTunnelTable [RFC3812]." 582 REFERENCE 583 "1. Multiprotocol Label Switching (MPLS) Traffic 584 Engineering (TE) Management Information 585 Base (MIB), Srinivasan, et al, RFC 3812, June 2004 586 2. Pseudowire (PW) Management Information Base (MIB), 587 Nadeau & Zelig, RFC 5601, July 2009." 588 DEFVAL { lsp } 589 ::= { mplsOamIdMegEntry 7 } 591 mplsOamIdMegMpLocation OBJECT-TYPE 592 SYNTAX INTEGER { 594 perNode (1), 595 perInterface (2) 596 } 597 MAX-ACCESS read-create 598 STATUS current 599 DESCRIPTION 600 "Indicates the MP location type for this MEG. 602 If the value is perNode, then the MEG in the LSR supports 603 only perNode MEP/MIP, i.e., only one MEP/MIP in an LSR. 605 If the value is perInterface, then the MEG in the LSR 606 supports perInterface MEPs/MIPs, i.e., two MEPs/MIPs in 607 an LSR." 609 REFERENCE 610 "RFC 6371, Operations, Administration, and Maintenance 611 Framework for MPLS-Based Transport Networks, 612 September 2011." 613 DEFVAL { perNode } 614 ::= { mplsOamIdMegEntry 8 } 616 mplsOamIdMegPathFlow OBJECT-TYPE 617 SYNTAX INTEGER { 618 unidirectionalPointToPoint (1), 619 coRoutedBidirectionalPointToPoint (2), 620 associatedBidirectionalPointToPoint (3), 621 unidirectionalPointToMultiPoint (4) 622 } 623 MAX-ACCESS read-create 624 STATUS current 625 DESCRIPTION 626 "Indicates the transport path flow for this MEG. 627 In case of a unidirectional point-to-point transport path, 628 a single unidirectional Maintenance Entity is defined to 629 monitor it. 630 In case of associated bidirectional point-to-point transport 631 paths, two independent unidirectional Maintenance Entities are 632 defined to independently monitor each direction. 633 In case of co-routed bidirectional point-to-point transport 634 paths, a single bidirectional Maintenance Entity is defined to 635 monitor both directions congruently. 636 In case of unidirectional point-to-multipoint transport paths, 637 a single unidirectional Maintenance Entity for each leaf is 638 defined to monitor the transport path from the root to 639 that leaf." 640 REFERENCE 641 "RFC 6371, Operations, Administration, and Maintenance 642 Framework for MPLS-Based Transport Networks, 643 September 2011." 644 DEFVAL { coRoutedBidirectionalPointToPoint } 645 ::= { mplsOamIdMegEntry 9 } 647 mplsOamIdMegOperStatus OBJECT-TYPE 648 SYNTAX INTEGER { 649 up (1), 650 down (2) 651 } 652 MAX-ACCESS read-only 653 STATUS current 654 DESCRIPTION 655 "This object specifies the operational status of the 656 Maintenance Entity Group (MEG). This object is used to 657 send the notification to the SNMP manager about the MEG. 659 The value up (1) indicates that the MEG and its monitored 660 path are operationally up. The value down (2) indicates 661 that the MEG is operationally down. 663 When the value of mplsOamIdMegOperStatus is up(1), all 664 the bits of mplsOamIdMegSubOperStatus must be cleared. 665 When the value of mplsOamIdMegOperStatus is down(2), 666 at least one bit of mplsOamIdMegSubOperStatus must be 667 set." 668 ::= { mplsOamIdMegEntry 10 } 670 mplsOamIdMegSubOperStatus OBJECT-TYPE 671 SYNTAX BITS { 672 megDown (0), 673 meDown (1), 674 oamAppDown (2), 675 pathDown (3) 676 } 677 MAX-ACCESS read-only 678 STATUS current 679 DESCRIPTION 680 "This object specifies the reason why the MEG operational 681 status as mentioned by the object mplsOamIdMegOperStatus 682 is down. This object is used to send the notification to 683 the SNMP manager about the MEG. 685 The bit 0 (megDown) indicates the MEG is down. 686 The bit 1 (meDown) indicates the ME table is 687 down. 688 The bit 2 (oamAppDown) indicates that the 689 OAM application has notified that the entity (LSP or PW) 690 monitored by this MEG is down. Currently, BFD is the 691 only supported OAM application. 692 The bit 3 (pathDown) indicates that the underlying 693 LSP or PW is down." 694 ::= { mplsOamIdMegEntry 11 } 696 mplsOamIdMegRowStatus OBJECT-TYPE 697 SYNTAX RowStatus 698 MAX-ACCESS read-create 699 STATUS current 700 DESCRIPTION 702 "This variable is used to create, modify, and/or delete 703 a row in this table. When a row in this table is in 704 active(1) state, no objects in that row can be modified 705 by the agent except mplsOamIdMegRowStatus." 706 ::= { mplsOamIdMegEntry 12 } 708 mplsOamIdMegStorageType OBJECT-TYPE 709 SYNTAX StorageType 710 MAX-ACCESS read-create 711 STATUS current 712 DESCRIPTION 713 "This variable indicates the storage type for this 714 object. 715 Conceptual rows having the value 'permanent' 716 need not allow write-access to any columnar 717 objects in the row." 718 DEFVAL { volatile } 719 ::= { mplsOamIdMegEntry 13 } 721 -- End of MPLS Transport Profile MEG table 723 -- Start of MPLS Transport Profile ME table 725 mplsOamIdMeIndexNext OBJECT-TYPE 726 SYNTAX IndexIntegerNextFree (0..4294967295) 727 MAX-ACCESS read-only 728 STATUS current 729 DESCRIPTION 730 "This object contains an unused value for 731 mplsOamIdMeIndex, or a zero to indicate 732 that none exist. Negative values are not allowed, 733 as they do not correspond to valid values of 734 mplsOamIdMeIndex." 735 ::= { mplsOamIdObjects 3 } 737 mplsOamIdMeMpIndexNext OBJECT-TYPE 738 SYNTAX IndexIntegerNextFree (0..4294967295) 739 MAX-ACCESS read-only 740 STATUS current 741 DESCRIPTION 742 "This object contains an unused value for 743 mplsOamIdMeMpIndex, or a zero to indicate 744 that none exist. Negative values are not allowed, 745 as they do not correspond to valid values of 746 mplsOamIdMeMpIndex." 747 ::= { mplsOamIdObjects 4 } 749 mplsOamIdMeTable OBJECT-TYPE 750 SYNTAX SEQUENCE OF MplsOamIdMeEntry 751 MAX-ACCESS not-accessible 752 STATUS current 753 DESCRIPTION 754 "This table contains MPLS-TP maintenance entity 755 information. 757 ME is some portion of a transport path that requires 758 management bounded by two points (called MEPs), and the 759 relationship between those points to which maintenance 760 and monitoring operations apply. 762 This table is generic enough to handle MEPs and MIPs 763 information within a MEG." 764 ::= { mplsOamIdObjects 5 } 766 mplsOamIdMeEntry OBJECT-TYPE 767 SYNTAX MplsOamIdMeEntry 768 MAX-ACCESS not-accessible STATUS current 769 DESCRIPTION 770 "An entry in this table represents MPLS-TP maintenance 771 entity. This entry represents the ME if the source and 772 sink MEPs are defined. 774 A ME is a p2p entity. One ME has two such MEPs. 775 A MEG is a group of one or more MEs. One MEG can have 776 two or more MEPs. 778 For P2P LSP, one MEG has one ME and this ME is associated 779 two MEPs (source and sink MEPs) within a MEG. 780 Each mplsOamIdMeIndex value denotes the ME within a MEG. 782 In case of unidirectional point-to-point transport paths, 783 a single unidirectional Maintenance Entity is defined to 784 monitor it and mplsOamIdMeServicePointer points to 785 unidirectional point-to-point path. 787 In case of associated bidirectional point-to-point 788 transport paths, two independent unidirectional 789 Maintenance Entities are defined to independently monitor 790 each direction and each mplsOamIdMeServicePointer MIB 791 object points to unique unidirectional transport path. 792 This has implications for transactions that terminate at 793 or query a MIP, as a return path from MIP to source MEP 794 does not necessarily exist within the MEG. 796 In case of co-routed bidirectional point-to-point 797 transport paths, a single bidirectional Maintenance Entity 798 is defined to monitor both directions congruently and 799 mplsOamIdMeServicePointer MIB object points to co-routed 800 bidirectional point-to-point transport path. 802 In case of unidirectional point-to-multipoint transport 803 paths, a single unidirectional Maintenance entity for each 804 leaf is defined to monitor the transport path from the 805 root to that leaf and each leaf has different transport 806 path information in mplsOamIdMeServicePointer MIB object. 807 Note that the MplsOamIdMeEntry should be created manually 808 once the MEG is configured for OAM operations." 809 INDEX { mplsOamIdMegIndex, 810 mplsOamIdMeIndex, 811 mplsOamIdMeMpIndex 812 } 813 ::= { mplsOamIdMeTable 1 } 815 MplsOamIdMeEntry ::= SEQUENCE { 816 mplsOamIdMeIndex Unsigned32, 817 mplsOamIdMeMpIndex Unsigned32, 818 mplsOamIdMeName SnmpAdminString, 819 mplsOamIdMeMpIfIndex InterfaceIndexOrZero, 820 mplsOamIdMeSourceMepIndex Unsigned32, 821 mplsOamIdMeSinkMepIndex Unsigned32, 822 mplsOamIdMeMpType INTEGER, 823 mplsOamIdMeMepDirection INTEGER, 824 mplsOamIdMeProactiveOamPhbTCValue MplsOamPhbTCValue, 825 mplsOamIdMeOnDemandOamPhbTCValue MplsOamPhbTCValue, 826 mplsOamIdMeServicePointer RowPointer, 827 mplsOamIdMeRowStatus RowStatus, 828 mplsOamIdMeStorageType StorageType 829 } 831 mplsOamIdMeIndex OBJECT-TYPE 832 SYNTAX Unsigned32 (1..4294967295) 833 MAX-ACCESS not-accessible 834 STATUS current 835 DESCRIPTION 836 "Uniquely identifies a maintenance entity index within 837 a MEG. Managers should obtain new values for row 838 creation in this table by reading 839 mplsOamIdMeIndexNext." 840 ::= { mplsOamIdMeEntry 1 } 842 mplsOamIdMeMpIndex OBJECT-TYPE 844 SYNTAX Unsigned32 (1..4294967295) 845 MAX-ACCESS not-accessible 846 STATUS current 847 DESCRIPTION 848 "Indicates the maintenance point index, used to create 849 multiple MEPs in a node of single ME. The value of this 850 object can be MEP index or MIP index. Managers should 851 obtain new values for row creation in this table by reading 852 mplsOamIdMeMpIndexNext." 853 ::= { mplsOamIdMeEntry 2 } 855 mplsOamIdMeName OBJECT-TYPE 856 SYNTAX SnmpAdminString (SIZE(1..48)) 857 MAX-ACCESS read-create 858 STATUS current 859 DESCRIPTION 860 "This object denotes the ME name, each 861 Maintenance Entity has unique name within MEG." 862 ::= { mplsOamIdMeEntry 3 } 864 mplsOamIdMeMpIfIndex OBJECT-TYPE 865 SYNTAX InterfaceIndexOrZero 866 MAX-ACCESS read-create 867 STATUS current 868 DESCRIPTION 869 "Indicates the maintenance point interface. 870 If the mplsOamIdMegMpLocation object value 871 is perNode (1), the MP interface index should point 872 to incoming interface or outgoing interface or 873 zero (indicates the MP OAM packets are initiated 874 from forwarding engine). 876 If the mplsOamIdMegMpLocation object value is 877 perInterface (2), the MP interface index should point to 878 incoming interface or outgoing interface." 879 REFERENCE 880 "RFC 6371, Operations, Administration, and Maintenance 881 Framework for MPLS-Based Transport Networks, 882 September 2011. 883 RFC 2863 - The Interfaces Group MIB, McCloghrie, K., 884 and F. Kastenholtz, June 2000." 885 DEFVAL { 0 } 886 ::= { mplsOamIdMeEntry 4 } 888 mplsOamIdMeSourceMepIndex OBJECT-TYPE 889 SYNTAX Unsigned32 890 MAX-ACCESS read-create 891 STATUS current 892 DESCRIPTION 893 "Indicates the source MEP Index of the ME. This object 894 should be configured if mplsOamIdMegOperatorType object 895 in the mplsOamIdMegEntry is configured as iccBased (2). 897 If the MEG is configured for IP based operator, 898 the value of this object should be set zero and the MEP 899 ID will be automatically derived from the service 900 Identifiers(MPLS-TP LSP/PW Identifier)." 901 DEFVAL { 0 } 902 ::= { mplsOamIdMeEntry 5 } 904 mplsOamIdMeSinkMepIndex OBJECT-TYPE 905 SYNTAX Unsigned32 906 MAX-ACCESS read-create 907 STATUS current 908 DESCRIPTION 909 "Indicates the sink MEP Index of the ME. This object 910 should be configured if mplsOamIdMegOperatorType object 911 in the mplsOamIdMegEntry is configured as iccBased (2). 912 If the MEG is configured for IP based operator, 913 the value of this object should be set zero and the MEP 914 ID will be automatically derived from the service 915 Identifiers(MPLS-TP LSP/PW Identifier)." 916 DEFVAL { 0 } 917 ::= { mplsOamIdMeEntry 6 } 919 mplsOamIdMeMpType OBJECT-TYPE 920 SYNTAX INTEGER { 921 mep (1), 922 mip (2) 923 } 924 MAX-ACCESS read-create 925 STATUS current 926 DESCRIPTION 927 "Indicates the maintenance point type within the MEG. 929 The object should have the value mep (1), only in the 930 Ingress or Egress nodes of the transport path. 932 The object can have the value mip (2), 933 in the intermediate nodes and possibly in the end nodes 934 of the transport path." 935 DEFVAL { mep } 936 ::= { mplsOamIdMeEntry 7 } 938 mplsOamIdMeMepDirection OBJECT-TYPE 939 SYNTAX INTEGER { 940 up (1), 941 down (2), 942 notApplicable (3) 943 } 945 MAX-ACCESS read-create 946 STATUS current 947 DESCRIPTION 948 "Indicates the direction of the MEP. This object 949 should be configured if mplsOamIdMeMpType is 951 configured as mep (1) else notApplicable (3) is set." 952 DEFVAL { down } 953 ::= { mplsOamIdMeEntry 8 } 955 mplsOamIdMeProactiveOamPhbTCValue OBJECT-TYPE 956 SYNTAX MplsOamPhbTCValue 957 MAX-ACCESS read-create 958 STATUS current 959 DESCRIPTION 960 "Indicates the Per-hop Behavior (PHB) value for this source 961 MEP generated proactive traffic." 962 DEFVAL { ef } 963 ::= { mplsOamIdMeEntry 9 } 965 mplsOamIdMeOnDemandOamPhbTCValue OBJECT-TYPE 966 SYNTAX MplsOamPhbTCValue 967 MAX-ACCESS read-create 968 STATUS current 969 DESCRIPTION 970 "Indicates the Per-hop Behavior (PHB) value for this 971 source MEP generated on-demand traffic." 972 DEFVAL { ef } 974 ::= { mplsOamIdMeEntry 10 } 976 mplsOamIdMeServicePointer OBJECT-TYPE 978 SYNTAX RowPointer 979 MAX-ACCESS read-create 980 STATUS current 981 DESCRIPTION 982 "This variable represents a pointer to the MPLS-TP 983 transport path. This value MUST point at an entry in the 984 mplsTunnelEntry if mplsOamIdMegServicePointerType 985 is configured as lsp (1) or at an entry in the pwEntry if 986 mplsOamIdMegServicePointerType is configured 987 as pseudowire (2). 989 Note: This service pointer object, is placed in ME table 990 instead of MEG table, since it will be useful in case of 991 point-to-multipoint, where each ME will point to different 992 branches of a P2MP tree." 994 ::= { mplsOamIdMeEntry 11 } 996 mplsOamIdMeRowStatus OBJECT-TYPE 997 SYNTAX RowStatus 998 MAX-ACCESS read-create 999 STATUS current 1000 DESCRIPTION 1001 "This variable is used to create, modify, and/or 1002 delete a row in this table. When a row in this 1003 table is in active(1) state, no objects in that row 1004 can be modified by the agent except 1005 mplsOamIdMeRowStatus." 1006 ::= { mplsOamIdMeEntry 12 } 1008 mplsOamIdMeStorageType OBJECT-TYPE 1009 SYNTAX StorageType 1010 MAX-ACCESS read-create 1011 STATUS current 1012 DESCRIPTION 1013 "This variable indicates the storage type for this 1014 object. 1015 Conceptual rows having the value 'permanent' 1016 need not allow write-access to any columnar 1017 objects in the row." 1018 DEFVAL { volatile } 1019 ::= { mplsOamIdMeEntry 13 } 1021 -- End of MPLS Transport Profile ME table 1023 -- End of MPLS-TP OAM Tables 1025 -- Notification Definitions of MPLS-TP identifiers 1027 mplsOamIdDefectCondition NOTIFICATION-TYPE 1028 OBJECTS { 1029 mplsOamIdMegName, 1030 mplsOamIdMeName, 1031 mplsOamIdMegOperStatus, 1032 mplsOamIdMegSubOperStatus 1033 } 1034 STATUS current 1035 DESCRIPTION 1036 "This notification is sent whenever the operational 1037 status of MEG is changed." 1038 ::= { mplsOamIdNotifications 1 } 1040 -- End of Notifications. 1042 -- Module Compliance. 1044 mplsOamIdCompliances 1045 OBJECT IDENTIFIER ::= { mplsOamIdConformance 1 } 1047 mplsOamIdGroups 1048 OBJECT IDENTIFIER ::= { mplsOamIdConformance 2 } 1050 -- Compliance requirement for fully compliant implementations. 1052 mplsOamIdModuleFullCompliance MODULE-COMPLIANCE 1053 STATUS current 1054 DESCRIPTION "Compliance statement for agents that provide full 1055 support for MPLS-TP-OAM-STD-MIB. Such devices can 1056 then be monitored and also be configured using 1057 this MIB module." 1059 MODULE IF-MIB -- The Interfaces Group MIB, RFC 2863. 1060 MANDATORY-GROUPS { 1061 ifGeneralInformationGroup, 1062 ifCounterDiscontinuityGroup 1063 } 1065 MODULE -- This module. 1066 MANDATORY-GROUPS { 1067 mplsOamIdMegGroup, 1068 mplsOamIdMeGroup 1069 } 1071 GROUP mplsOamIdNotificationObjectsGroup 1072 DESCRIPTION "This group is only mandatory for those 1073 implementations which can efficiently implement 1074 the notifications contained in this group." 1076 GROUP mplsOamIdNotificationGroup 1077 DESCRIPTION "This group is only mandatory for those 1078 implementations which can efficiently implement 1079 the notifications contained in this group." 1081 ::= { mplsOamIdCompliances 1 } 1083 -- Units of conformance. 1085 mplsOamIdMegGroup OBJECT-GROUP 1086 OBJECTS { 1087 mplsOamIdMegIndexNext, 1088 mplsOamIdMegName, 1089 mplsOamIdMegOperatorType, 1090 mplsOamIdMegIdCc, 1091 mplsOamIdMegIdIcc, 1092 mplsOamIdMegIdUmc, 1093 mplsOamIdMegServicePointerType, 1094 mplsOamIdMegMpLocation, 1095 mplsOamIdMegOperStatus, 1096 mplsOamIdMegSubOperStatus, 1097 mplsOamIdMegPathFlow, 1098 mplsOamIdMegRowStatus, 1099 mplsOamIdMegStorageType 1100 } 1102 STATUS current 1103 DESCRIPTION 1104 "Collection of objects needed for MPLS MEG information." 1105 ::= { mplsOamIdGroups 1 } 1107 mplsOamIdMeGroup OBJECT-GROUP 1108 OBJECTS { 1109 mplsOamIdMeIndexNext, 1110 mplsOamIdMeMpIndexNext, 1111 mplsOamIdMeName, 1112 mplsOamIdMeMpIfIndex, 1113 mplsOamIdMeSourceMepIndex, 1114 mplsOamIdMeSinkMepIndex, 1115 mplsOamIdMeMpType, 1116 mplsOamIdMeMepDirection, 1117 mplsOamIdMeProactiveOamPhbTCValue, 1118 mplsOamIdMeOnDemandOamPhbTCValue, 1119 mplsOamIdMeServicePointer, 1120 mplsOamIdMeRowStatus, 1121 mplsOamIdMeStorageType 1122 } 1123 STATUS current 1124 DESCRIPTION 1125 "Collection of objects needed for MPLS ME information." 1126 ::= { mplsOamIdGroups 2 } 1128 mplsOamIdNotificationObjectsGroup OBJECT-GROUP 1129 OBJECTS { 1131 mplsOamIdMegOperStatus, 1133 mplsOamIdMegSubOperStatus 1134 } 1135 STATUS current 1136 DESCRIPTION 1137 "Collection of objects needed to implement notifications." 1138 ::= { mplsOamIdGroups 3 } 1140 mplsOamIdNotificationGroup NOTIFICATION-GROUP 1141 NOTIFICATIONS { 1142 mplsOamIdDefectCondition 1143 } 1144 STATUS current 1145 DESCRIPTION 1146 "Set of notifications implemented in this module." 1147 ::= { mplsOamIdGroups 4 } 1149 END 1151 8. Security Consideration 1153 There is a number of management objects defined in this MIB module 1154 that has a MAX-ACCESS clause of read-create. Such objects may be 1155 considered sensitive or vulnerable in some network environments. 1156 The support for SET operations in a non-secure environment 1157 without proper protection can have a negative effect on network 1158 operations. 1160 Some of the readable objects in this MIB module (i.e., objects 1161 with a MAX-ACCESS other than not-accessible) may be considered 1162 sensitive or vulnerable in some network environments. 1163 It is thus important to control even GET and/or NOTIFY access 1164 to these objects and possibly to even encrypt the values of these 1165 objects when sending them over the network via SNMP. These are 1166 the tables and objects and their sensitivity/vulnerability: 1168 SNMP versions prior to SNMPv3 did not include adequate security. 1169 Even if the network itself is secure (for example by using IPsec), 1170 even then, there is no control as to who on the secure network 1171 is allowed to access and GET/SET (read/change/create/delete) 1172 the objects in this MIB module. 1174 It is RECOMMENDED that implementers consider the security features 1175 as provided by the SNMPv3 framework (see [RFC3410], section 8), 1176 including full supports for the SNMPv3 cryptographic mechanisms 1177 (for authentication and privacy). 1179 Further, deployment of SNMP versions prior to SNMPv3 is NOT 1180 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 1181 enable cryptographic security. It is then a customer/operator 1182 responsibility to ensure that the SNMP entity giving access to an 1183 instance of this MIB module is properly configured to give access to 1184 the objects only to those principles (users) that have legitimate 1185 rights to indeed GET or SET (change/create/delete) them. 1187 9. IANA Considerations 1189 IANA is requested to assign an OID for the MIB module from the "MIB 1190 Transmission Group - MPLS STD" sub-registry of the "Internet-standard 1191 MIB - Transmission Group" registry for the MPLS-TP OAM ID MIB module 1192 specified in this document. 1194 10. References 1196 10.1 Normative References 1198 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1199 Requirement Levels", BCP 14, RFC 2119, March 1997. 1201 [RFC2578] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 1202 "Structure of Management Information Version 2 (SMIv2)", 1203 STD 58, RFC 2578, April 1999. 1205 [RFC2579] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 1206 "Textual Conventions for SMIv2", STD 58, RFC 2579, April 1207 1999. 1209 [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 1210 "Conformance Statements for SMIv2", STD 58, RFC 2580, 1211 April 1999. 1213 [RFC2863] McCloghrie, K. and F. Kastenholtz, "The Interfaces Group 1214 MIB ", RFC 2863, June 2000 1216 [RFC3031] Rosen, E., Viswanathan, A., and R. Callon, 1217 "Multiprotocol Label Switching Architecture", RFC 3031, 1218 January 2001. 1220 [RFC3289] Baker, F., Chan, K., and A. Smith, "Management 1221 Information Base for the Differentiated Services 1222 Architecture", RFC 3289, May 2002. 1224 [RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An 1225 Architecture for Describing Simple Network Management 1226 Protocol (SNMP) Management Frameworks", STD 62, RFC 1227 3411, December 2002. 1229 [RFC5601] Zelig, D., Ed., and T. Nadeau, Ed., "Pseudowire (PW) 1230 Management Information Base (MIB)", RFC 5601, July 2009. 1232 10.2 Informative References 1234 [RFC3410] J. Case, R. Mundy, D. pertain, B.Stewart, "Introduction 1235 and Applicability Statement for Internet Standard 1236 Management Framework", RFC 3410, December 2002. 1238 [RFC3811] Nadeau, T., Ed., and J. Cucchiara, Ed., "Definitions of 1239 Textual Conventions (TCs) for Multiprotocol Label 1240 Switching (MPLS) Management", RFC 3811, June 2004. 1242 [RFC3812] Srinivasan, C., Viswanathan, A., and T. Nadeau, 1243 "Multiprotocol Label Switching (MPLS) Traffic 1244 Engineering (TE) Management Information Base (MIB)", RFC 1245 3812, June 2004. 1247 [RFC3813] Srinivasan, C., Viswanathan, A., and T. Nadeau, 1248 "Multiprotocol Label Switching (MPLS) Label Switching 1249 (LSR) Router Management Information Base (MIB)", RFC 1250 3813, June 2004. 1252 [RFC5654] Niven-Jenkins, B., Ed., Brungard, D., Ed., Betts, M., 1253 Ed., Sprecher, N., and S. Ueno, "Requirements of an MPLS 1254 Transport Profile", RFC 5654, September 2009. 1256 [RFC6370] Bocci, M., Swallow, G., and E. Gray, "MPLS-TP 1257 Identifiers", RFC 6370, September 2011. 1259 [RFC6371] Busi, I., Niven-Jenkins, B., and D. Allan, "MPLS-TP OAM 1260 Framework and Overview", RFC 6371, September 2011. 1262 [RFC6923] R. Winter, Ed, E. Gray, Ed., H. van Helvoort, and M. 1263 Betts, "MPLS-TP Identifiers Following ITU-T 1264 Conventions", RFC 6923, May 2013. 1266 [RFC5860] M. Vigoureux, Ed, D. Ward, Ed, M. Betts, Ed, "OAM in MPLS 1267 Transport Networks", RFC 5860, May 2010. 1269 11. Acknowledgments 1271 We wish to thank Muly Ilan, Adrian Farrel, Joan Cucchiara and 1272 Weiying Cheng for their valuable comments on this document. 1274 12. Authors' Addresses 1276 Venkatesan Mahalingam 1277 Dell Inc. 1278 350 Holger way, San Jose, CA, USA 1279 Email: venkat.mahalingams@gmail.com 1281 Sam Aldrin 1282 Huawei Technologies, co. 1283 2330 Central Express Way, 1284 Santa Clara, CA 95051, USA 1285 Email: aldrin.ietf@gmail.com 1287 Thomas D. Nadeau 1288 Juniper Networks 1289 10 Technology Park Drive, Westford, MA 01886 1290 Email: tnadeau@juniper.net 1292 Kannan KV Sampath 1293 Redeem, 1294 India 1295 Email: kannankvs@gmail.com 1297 Ping Pan 1298 Infinera 1299 Email: ppan@infinera.com 1301 Sami Boutros 1302 Cisco Systems, Inc. 1303 3750 Cisco Way 1304 San Jose, California 95134 1305 USA 1306 Email: sboutros@cisco.com