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