idnits 2.17.1 draft-ietf-mpls-tp-oam-id-mib-07.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 (February 02, 2015) is 3342 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: August 06, 2015 M.Venkatesan 6 Dell Inc. 7 Kannan KV Sampath 8 Redeem 9 Thomas D. Nadeau 10 Brocade 12 February 02, 2015 14 MPLS-TP Operations, Administration, and Management (OAM) Identifiers 15 Management Information Base (MIB) 16 draft-ietf-mpls-tp-oam-id-mib-07 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 August 06, 2015. 50 Copyright and License Notice 52 Copyright (c) 2015 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 . . . . . . . . . . . . . . . . . . . . . . . . . . 4 73 4. Feature List . . . . . . . . . . . . . . . . . . . . . . . . . 4 74 5. Brief description of MIB Objects . . . . . . . . . . . . . . . 4 75 5.1. mplsOamIdMegTable . . . . . . . . . . . . . . . . . . . . 4 76 5.2. mplsOamIdMeTable . . . . . . . . . . . . . . . . . . . . . 5 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 . . . . . . . . . . . . . . . . . . . . . . . 27 85 12. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 27 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 Switched Path), Pseudowires and Sections. 99 At the time of writing, SNMP SET is no longer recommended as a way to 100 configure MPLS networks as was described in [RFC3812]. However, 101 since the MIB modules specified in this document are intended to work 102 in parallel with the MIB modules for MPLS specified in [RFC3812], 103 certain objects defined here are specified with MAX-ACCESS of read- 104 write or read-create so that specifications of the base tables in 105 [RFC3812] and the new MIB modules in this document are consistent. 106 Although the examples described in Section 6 specify means to 107 configure OAM identifiers for MPLS-TP tunnels, this should be seen as 108 indicating how the MIB values would be returned in the specified 109 circumstances having been configured by alternative means. 111 2. The Internet-Standard Management Framework 113 For a detailed overview of the documents that describe the current 114 Internet-Standard Management Framework, please refer to section 7 of 115 RFC3410 [RFC3410]. 117 Managed objects are accessed via a virtual information store, termed 118 the Management Information Base or MIB. MIB objects are generally 119 accessed through the Simple Network Management Protocol (SNMP). 120 Objects in the MIB are defined using the mechanisms defined in the 121 Structure of Management Information (SMI). This memo specifies a MIB 122 module that is compliant to the SMIv2, which is described in STD 58, 123 RFC2578, STD 58, RFC2579 and STD58, RFC2580. 125 3. Overview 127 3.1 Conventions used in this document 129 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 130 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 131 "OPTIONAL" in this document are to be interpreted as described in 132 RFC-2119 [RFC2119]. 134 3.2 Terminology 135 This document uses terminology from the Multiprotocol Label Switching 136 Architecture [RFC3031], MPLS Traffic Engineering (TE) MIB [RFC3812], 137 MPLS Label Switching Router (LSR) MIB [RFC3813], OAM Framework for 138 MPLS-Based Transport Networks [RFC6371], MPLS Transport Profile 139 (MPLS-TP) Identifiers [RFC6370], MPLS-TP Identifiers Following ITU-T 140 Conventions [RFC6923], and OAM in MPLS Transport Networks [RFC5860]. 142 3.3 Acronyms 144 ICC: ITU Carrier Code 145 IP: Internet Protocol 147 LSP: Label Switched Path 148 LSR: Label Switching Router 149 MIB: Management Information Base 150 ME: Maintenance Entity 151 MEG: Maintenance Entity Group 152 MEP: Maintenance Entity Group End Point 153 MIP: Maintenance Entity Group Intermediate Point 154 MPLS: Multi-Protocol Label Switching 155 MPLS-TP: MPLS Transport Profile 156 PW: Pseudowire 157 TE: Traffic Engineering 158 TP: Transport Profile 160 4. Feature List 162 The MPLS transport profile OAM identifiers MIB module is designed 163 to satisfy the following requirements and constraints: 165 - The MIB module supports configuration of OAM identifiers for 166 MPLS point-to-point Tunnels, point-to-multipoint LSPs, co- 167 routed bidirectional LSPs, associated bidirectional LSPs and 168 Pseudowires. 170 5. Brief description of MIB Objects 172 The objects described in this section support the functionality 173 described in documents [RFC5654] and [RFC6370]. The tables support 174 both IP compatible and ICC based OAM identifiers configurations 175 for MPLS Tunnels, LSPs and Pseudowires. 177 5.1. mplsOamIdMegTable 179 The mplsOamIdMegTable is used to manage one or more 180 Maintenance Entities (MEs) that belongs to the same transport path. 182 When a new entry is created with mplsOamIdMegOperatorType set to 183 ipCompatible (1), then as per [RFC6370] (MEG_ID for LSP 184 is LSP_ID and MEG_ID for PW is PW_Path_ID), MEP_ID can be 185 automatically formed. 187 For ICC based transport path, the user is expected to configure 188 the ICC identifier explicitly in this table for MPLS Tunnels, LSPs 189 and pseudowires. 191 5.2. mplsOamIdMeTable 193 The mplsOamIdMeTable defines a relationship between two points 194 (source and sink) of a transport path to which maintenance and 195 monitoring operations apply. The two points that define 196 a maintenance entity are called Maintenance Entity Group 197 End Points (MEPs). 199 In between MEPs, there are zero or more intermediate points, 200 called Maintenance Entity Group Intermediate Points (MIPs). 201 MEPs and MIPs are associated with the MEG and can be shared by 202 more than one ME in a MEG. 204 6. MPLS OAM identifier configuration for MPLS LSP example 206 In this section, we provide an example of the OAM identifier 207 configuration for an MPLS co-routed bidirectional LSP. 209 This example provides usage of a MEG and ME tables for management and 210 monitoring operations of an MPLS LSP. 212 This example considers the OAM identifiers configuration on a 213 head-end LSR to manage and monitor a MPLS LSP. 214 Only relevant objects which are applicable for IP based OAM 215 identifiers of MPLS co-routed bidirectional LSP are illustrated here. 217 In mplsOamIdMegTable: 219 { 220 -- MEG index (Index to the table) 221 mplsOamIdMegIndex = 1, 222 mplsOamIdMegName = "MEG1", 223 mplsOamIdMegOperatorType = ipCompatible (1), 224 mplsOamIdMegServicePointerType = lsp (1), 225 mplsOamIdMegMpLocation = perNode(1), 226 -- Mandatory parameters needed to activate the row go here 227 mplsOamIdMegRowStatus = createAndGo (4), 228 mplsOamIdMegPathFlow 229 = coRoutedBidirectionalPointToPoint (2) 230 } 232 This will create an entry in the mplsOamIdMegTable to manage and 233 monitor the MPLS tunnel. 235 The following ME table is used to associate the path information 236 to a MEG. 238 In mplsOamIdMeTable: 240 { 241 -- ME index (Index to the table) 242 mplsOamIdMeIndex = 1, 244 -- MP index (Index to the table) 245 mplsOamIdMeMpIndex = 1, 246 mplsOamIdMeName = "ME1", 247 mplsOamIdMeMpIfIndex = 0, 248 -- Source MEP id is derived from the IP compatible MPLS LSP 249 mplsOamIdMeSourceMepIndex = 0, 250 -- Source MEP id is derived from the IP compatible MPLS LSP 251 mplsOamIdMeSinkMepIndex = 0, 252 mplsOamIdMeMpType = mep (1), 253 mplsOamIdMeMepDirection = down (2), 254 -- RowPointer MUST point to the first accessible column of an 255 -- MPLS LSP 256 mplsOamIdMeServicePointer = mplsTunnelName.1.1.10.20, 257 -- Mandatory parameters needed to activate the row go here 258 mplsOamIdMeRowStatus = createAndGo (4) 259 } 261 7. MPLS OAM Identifiers MIB definitions 263 MPLS-OAM-ID-STD-MIB DEFINITIONS ::= BEGIN 265 IMPORTS 266 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, 267 Unsigned32 268 FROM SNMPv2-SMI -- [RFC2578] 269 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 270 FROM SNMPv2-CONF -- [RFC2580] 271 RowStatus, RowPointer, StorageType 272 FROM SNMPv2-TC -- [RFC2579] 273 SnmpAdminString 274 FROM SNMP-FRAMEWORK-MIB -- [RFC3411] 276 IndexIntegerNextFree 277 FROM DIFFSERV-MIB -- [RFC3289] 278 mplsStdMIB 279 FROM MPLS-TC-STD-MIB -- [RFC3811] 280 InterfaceIndexOrZero, ifGeneralInformationGroup, 281 ifCounterDiscontinuityGroup 282 FROM IF-MIB; -- [RFC2863] 284 mplsOamIdStdMIB MODULE-IDENTITY 285 LAST-UPDATED 286 "201412250000Z" -- December 25, 2014 287 ORGANIZATION 288 "Multiprotocol Label Switching (MPLS) Working Group" 289 CONTACT-INFO 290 " 291 Sam Aldrin 292 Huawei Technologies, co. 293 2330 Central Express Way, 295 Santa Clara, CA 95051, USA 296 Email: aldrin.ietf@gmail.com 298 Thomas D. Nadeau 299 Email: tnadeau@lucidvision.com 301 Venkatesan Mahalingam 302 Dell Inc. 303 5450 Great America Parkway, 304 Santa Clara, CA 95054, USA 305 Email: venkat.mahalingams@gmail.com 307 Kannan KV Sampath 308 Redeem, 309 India 310 Email: kannankvs@gmail.com 312 Ping Pan 313 Infinera 314 Email: ppan@infinera.com 316 Sami Boutros 317 Cisco Systems, Inc. 318 3750 Cisco Way 319 San Jose, California 95134 320 USA 321 Email: sboutros@cisco.com 323 " 324 DESCRIPTION 325 "Copyright (c) 2014 IETF Trust and the persons identified 326 as the document authors. All rights reserved. 328 This MIB module contains generic object definitions for 329 MPLS OAM maintenance identifiers." 331 -- Revision history. 333 REVISION 334 "201412250000Z" -- December 25, 2014 335 DESCRIPTION 336 "MPLS OAM Identifiers MIB objects for Tunnels, LSPs, 337 Pseudowires and Sections" 339 ::= { mplsStdMIB xxx } -- xxx to be replaced with the correct 340 -- OID value assigned by 341 -- IANA (see section 9). 343 -- Top level components of this MIB module. 345 -- notifications 346 mplsOamIdNotifications 347 OBJECT IDENTIFIER ::= { mplsOamIdStdMIB 0 } 348 -- tables, scalars 349 mplsOamIdObjects OBJECT IDENTIFIER ::= { mplsOamIdStdMIB 1 } 350 -- conformance 351 mplsOamIdConformance 352 OBJECT IDENTIFIER ::= { mplsOamIdStdMIB 2 } 354 -- Start of MPLS Transport Profile MEG table 356 mplsOamIdMegIndexNext OBJECT-TYPE 357 SYNTAX IndexIntegerNextFree (0..4294967295) 358 MAX-ACCESS read-only 359 STATUS current 360 DESCRIPTION 361 "This object contains an unused value for 362 mplsOamIdMegIndex, or a zero to indicate 363 that none exist. Negative values are not allowed, 364 as they do not correspond to valid values of 365 mplsOamIdMegIndex." 366 ::= { mplsOamIdObjects 1 } 367 mplsOamIdMegTable OBJECT-TYPE 368 SYNTAX SEQUENCE OF MplsOamIdMegEntry 369 MAX-ACCESS not-accessible 370 STATUS current 371 DESCRIPTION 372 "This table contains information about the Maintenance 373 Entity Groups (MEG). 375 MEG as mentioned in MPLS-TP OAM framework defines a set 376 of one or more maintenance entities (ME). 377 Maintenance Entities define a relationship between any 378 two points of a transport path in an OAM domain to which 379 maintenance and monitoring operations apply." 380 ::= { mplsOamIdObjects 2 } 382 mplsOamIdMegEntry OBJECT-TYPE 383 SYNTAX MplsOamIdMegEntry 384 MAX-ACCESS not-accessible 385 STATUS current 386 DESCRIPTION 387 "An entry in this table represents MPLS-TP MEG. 388 An entry can be created by a network administrator 389 or by an SNMP agent as instructed by an MPLS-TP OAM 390 Framework. 392 When a new entry is created with 393 mplsOamIdMegOperatorType set to ipCompatible (1), 394 then as per [RFC6370] (MEG_ID for LSP is LSP_ID and 395 MEG_ID for PW is PW_Path_ID), MEP_ID can be 396 automatically formed. 398 For co-routed bidirectional LSP, MEG_ID is 399 A1-{Global_ID::Node_ID::Tunnel_Num}::Z9-{Global_ID:: 400 Node_ID::Tunnel_Num}::LSP_Num. 402 For associated bidirectional LSP, MEG_ID is A1- 403 {Global_ID::Node_ID::Tunnel_Num::LSP_Num}:: Z9- 404 {Global_ID::Node_ID::Tunnel_Num::LSP_Num} 406 For LSP, MEP_ID is formed using, 407 Global_ID::Node_ID::Tunnel_Num::LSP_Num 409 For PW, MEG_ID is formed using AGI::A1- 410 {Global_ID::Node_ID::AC_ID}:: Z9- 411 {Global_ID::Node_ID::AC_ID}. 413 For PW, MEP_ID is formed using 414 AGI::Global_ID::Node_ID::AC_ID 416 MEP_ID is retrieved from the mplsOamIdMegServicePointer 417 object based on the mplsOamIdMegServicePointerType value. 418 ICC MEG_ID for LSP and PW is formed using the objects 419 mplsOamIdMegIdIcc and mplsOamIdMegIdUmc. 421 MEP_ID can be formed using MEG_ID::MEP_Index." 422 REFERENCE 423 "1. RFC5860, Requirements for OAM in MPLS Transport 424 Networks, May 2010. 425 2. RFC6371, Operations, Administration, and Maintenance 426 Framework for MPLS-Based Transport Networks, 427 September 2011 Section 3. 428 3. RFC6370, MPLS Transport Profile (MPLS-TP) Identifiers. 429 4. RFC6923, MPLS Transport Profile (MPLS-TP) Identifiers 430 Following ITU-T Conventions." 431 INDEX { mplsOamIdMegIndex } 432 ::= { mplsOamIdMegTable 1 } 434 MplsOamIdMegEntry ::= SEQUENCE { 435 mplsOamIdMegIndex Unsigned32, 436 mplsOamIdMegName SnmpAdminString, 437 mplsOamIdMegOperatorType INTEGER, 438 mplsOamIdMegIdCc SnmpAdminString, 439 mplsOamIdMegIdIcc SnmpAdminString, 440 mplsOamIdMegIdUmc SnmpAdminString, 441 mplsOamIdMegServicePointerType INTEGER, 442 mplsOamIdMegMpLocation INTEGER, 443 mplsOamIdMegPathFlow INTEGER, 444 mplsOamIdMegOperStatus INTEGER, 445 mplsOamIdMegSubOperStatus BITS, 446 mplsOamIdMegRowStatus RowStatus, 447 mplsOamIdMegStorageType StorageType 448 } 450 mplsOamIdMegIndex OBJECT-TYPE 451 SYNTAX Unsigned32 (1..4294967295) 452 MAX-ACCESS not-accessible 453 STATUS current 454 DESCRIPTION 455 "Index for the conceptual row identifying a MEG within 456 this MEG table. Managers should obtain new values for row 457 creation in this table by reading 458 mplsOamIdMegIndexNext." 459 ::= { mplsOamIdMegEntry 1 } 461 mplsOamIdMegName OBJECT-TYPE 462 SYNTAX SnmpAdminString (SIZE(0..48)) 463 MAX-ACCESS read-create 464 STATUS current 465 DESCRIPTION 466 "Each Maintenance Entity Group has unique name amongst 467 all those used or available to a service provider or 468 operator. It facilitates easy identification of 469 administrative responsibility for each MEG." 470 ::= { mplsOamIdMegEntry 2 } 472 mplsOamIdMegOperatorType OBJECT-TYPE 473 SYNTAX INTEGER { 474 ipCompatible (1), 476 iccBased (2) 477 } 478 MAX-ACCESS read-create 479 STATUS current 480 DESCRIPTION 481 "Indicates the operator type for MEG. Conceptual rows 482 having 'iccBased' as operator type, MUST have valid 483 values for the objects mplsOamIdMegIdIcc and 484 mplsOamIdMegIdUmc when the row status is active." 485 REFERENCE 486 "1. RFC6370, MPLS Transport Profile (MPLS-TP) 487 Identifiers. 488 2. RFC6923, MPLS Transport Profile (MPLS-TP) Identifiers 489 Following ITU-T Conventions. Section 3.1" 490 DEFVAL { ipCompatible } 491 ::= { mplsOamIdMegEntry 3 } 493 mplsOamIdMegIdCc OBJECT-TYPE 494 SYNTAX SnmpAdminString (SIZE(0..2)) 495 MAX-ACCESS read-create 496 STATUS current 497 DESCRIPTION 498 "Global uniqueness is assured by concatenating the ICC 499 with a Country Code (CC). The Country Code (alpha-2) 500 is a string of two alphabetic characters represented 501 with upper case letters (i.e., A-Z). 503 This object MUST contain a non-null ICC value if 504 the MplsOamIdMegOperatorType value is iccBased(2), 505 otherwise a null ICC value with octet size 0 506 should be assigned." 507 REFERENCE 508 "RFC6923, MPLS Transport Profile (MPLS-TP) Identifiers 509 Following ITU-T Conventions. Section 3." 510 DEFVAL {""} 511 ::= { mplsOamIdMegEntry 4 } 513 mplsOamIdMegIdIcc OBJECT-TYPE 514 SYNTAX SnmpAdminString (SIZE(0..6)) 515 MAX-ACCESS read-create 516 STATUS current 517 DESCRIPTION 518 "Unique code assigned to Network Operator or Service 519 Provider maintained by ITU-T. The ITU Carrier Code 520 used to form MEGID. 522 This object MUST contain a non-null ICC value if 523 the MplsOamIdMegOperatorType value is iccBased(2), 524 otherwise a null ICC value with octet size 0 525 should be assigned." 526 REFERENCE 527 "RFC6923, MPLS Transport Profile (MPLS-TP) Identifiers 528 Following ITU-T Conventions. Section 3.1." 529 DEFVAL {""} 530 ::= { mplsOamIdMegEntry 5 } 532 mplsOamIdMegIdUmc OBJECT-TYPE 533 SYNTAX SnmpAdminString (SIZE(0..7)) 534 MAX-ACCESS read-create 535 STATUS current 536 DESCRIPTION 537 "Unique code assigned by Network Operator or Service 538 Provider and is appended to mplsOamIdMegIdIcc to form 539 the MEGID. 540 This object MUST contain a non-null ICC value if 541 the MplsOamIdMegOperatorType value is iccBased(2), 542 otherwise a null ICC value with octet size 0 543 should be assigned." 544 REFERENCE 545 "RFC6923, MPLS Transport Profile (MPLS-TP) Identifiers 546 Following ITU-T Conventions. Section 7.1." 547 DEFVAL {""} 548 ::= { mplsOamIdMegEntry 6 } 550 mplsOamIdMegServicePointerType OBJECT-TYPE 552 SYNTAX INTEGER { 553 tunnel (1), 554 lsp (2), 555 pseudowire (3), 556 section (4) 557 } 558 MAX-ACCESS read-create 559 STATUS current 560 DESCRIPTION 561 "Indicates the service type for the MEG. 563 If the service type indicates tunnel, the service pointer 564 in mplsOamIdMeTable points to an entry in 565 the point-to-point mplsTunnelTable [RFC3812]. 567 If the service type indicates lsp, the service pointer 568 in mplsOamIdMeTable points to an entry in 569 the co-routed or associated bidirectional mplsTunnelTable. 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. 803 Note that the MplsOamIdMeEntry should be created manually 804 once the MEG is configured for OAM operations." 805 INDEX { mplsOamIdMegIndex, 806 mplsOamIdMeIndex, 807 mplsOamIdMeMpIndex 808 } 809 ::= { mplsOamIdMeTable 1 } 811 MplsOamIdMeEntry ::= SEQUENCE { 812 mplsOamIdMeIndex Unsigned32, 813 mplsOamIdMeMpIndex Unsigned32, 814 mplsOamIdMeName SnmpAdminString, 815 mplsOamIdMeMpIfIndex InterfaceIndexOrZero, 816 mplsOamIdMeSourceMepIndex Unsigned32, 817 mplsOamIdMeSinkMepIndex Unsigned32, 818 mplsOamIdMeMpType INTEGER, 819 mplsOamIdMeMepDirection INTEGER, 820 mplsOamIdMeServicePointer RowPointer, 821 mplsOamIdMeRowStatus RowStatus, 822 mplsOamIdMeStorageType StorageType 823 } 825 mplsOamIdMeIndex OBJECT-TYPE 826 SYNTAX Unsigned32 (1..4294967295) 827 MAX-ACCESS not-accessible 828 STATUS current 829 DESCRIPTION 830 "Uniquely identifies a maintenance entity index within 831 a MEG. Managers should obtain new values for row 832 creation in this table by reading 833 mplsOamIdMeIndexNext." 834 ::= { mplsOamIdMeEntry 1 } 836 mplsOamIdMeMpIndex OBJECT-TYPE 838 SYNTAX Unsigned32 (1..4294967295) 839 MAX-ACCESS not-accessible 840 STATUS current 841 DESCRIPTION 842 "Indicates the maintenance point index, used to create 843 multiple MEPs in a node of single ME. The value of this 844 object can be MEP index or MIP index. Managers should 845 obtain new values for row creation in this table by reading 846 mplsOamIdMeMpIndexNext." 847 ::= { mplsOamIdMeEntry 2 } 849 mplsOamIdMeName OBJECT-TYPE 850 SYNTAX SnmpAdminString (SIZE(1..48)) 851 MAX-ACCESS read-create 852 STATUS current 853 DESCRIPTION 854 "This object denotes the ME name, each 855 Maintenance Entity has unique name within MEG." 856 ::= { mplsOamIdMeEntry 3 } 858 mplsOamIdMeMpIfIndex OBJECT-TYPE 859 SYNTAX InterfaceIndexOrZero 860 MAX-ACCESS read-create 861 STATUS current 862 DESCRIPTION 863 "Indicates the maintenance point interface. 864 If the mplsOamIdMegMpLocation object value 865 is perNode (1), the MP interface index should point 866 to incoming interface or outgoing interface or 867 zero (indicates the MP OAM packets are initiated 868 from forwarding engine). 870 If the mplsOamIdMegMpLocation object value is 871 perInterface (2), the MP interface index should point to 872 incoming interface or outgoing interface." 873 REFERENCE 874 "RFC 6371, Operations, Administration, and Maintenance 875 Framework for MPLS-Based Transport Networks, 876 September 2011. 877 RFC 2863 - The Interfaces Group MIB, McCloghrie, K., 878 and F. Kastenholtz, June 2000." 879 DEFVAL { 0 } 880 ::= { mplsOamIdMeEntry 4 } 882 mplsOamIdMeSourceMepIndex OBJECT-TYPE 883 SYNTAX Unsigned32 884 MAX-ACCESS read-create 885 STATUS current 886 DESCRIPTION 887 "Indicates the source MEP Index of the ME. This object 888 should be configured if mplsOamIdMegOperatorType object 889 in the mplsOamIdMegEntry is configured as iccBased (2). 890 If the MEG is configured for IP based operator, 891 the value of this object should be set zero and the MEP 892 ID will be automatically derived from the service 893 Identifiers(MPLS-TP LSP/PW Identifier)." 894 DEFVAL { 0 } 895 ::= { mplsOamIdMeEntry 5 } 897 mplsOamIdMeSinkMepIndex OBJECT-TYPE 898 SYNTAX Unsigned32 899 MAX-ACCESS read-create 900 STATUS current 901 DESCRIPTION 902 "Indicates the sink MEP Index of the ME. This object 903 should be configured if mplsOamIdMegOperatorType object 904 in the mplsOamIdMegEntry is configured as iccBased (2). 905 If the MEG is configured for IP based operator, 906 the value of this object should be set zero and the MEP 907 ID will be automatically derived from the service 908 Identifiers(MPLS-TP LSP/PW Identifier)." 909 DEFVAL { 0 } 910 ::= { mplsOamIdMeEntry 6 } 912 mplsOamIdMeMpType OBJECT-TYPE 913 SYNTAX INTEGER { 914 mep (1), 915 mip (2) 916 } 917 MAX-ACCESS read-create 918 STATUS current 919 DESCRIPTION 920 "Indicates the maintenance point type within the MEG. 922 The object should have the value mep (1), only in the 923 Ingress or Egress nodes of the transport path. 925 The object can have the value mip (2), 926 in the intermediate nodes and possibly in the end nodes 927 of the transport path." 928 DEFVAL { mep } 929 ::= { mplsOamIdMeEntry 7 } 931 mplsOamIdMeMepDirection OBJECT-TYPE 932 SYNTAX INTEGER { 933 up (1), 934 down (2), 935 notApplicable (3) 936 } 937 MAX-ACCESS read-create 938 STATUS current 939 DESCRIPTION 940 "Indicates the direction of the MEP. This object 941 should be configured if mplsOamIdMeMpType is 943 configured as mep (1) else notApplicable (3) is set." 944 DEFVAL { down } 945 ::= { mplsOamIdMeEntry 8 } 947 mplsOamIdMeServicePointer OBJECT-TYPE 949 SYNTAX RowPointer 950 MAX-ACCESS read-create 951 STATUS current 952 DESCRIPTION 953 "This variable represents a pointer to the MPLS-TP 954 transport path. This value MUST point at an entry in the 955 mplsTunnelEntry if mplsOamIdMegServicePointerType 956 is configured as tunnel (1) or lsp (2) or section (4) or 957 at an entry in the pwEntry if 958 mplsOamIdMegServicePointerType is configured 959 as pseudowire (3). 961 Note: This service pointer object, is placed in ME table 962 instead of MEG table, since it will be useful in case of 963 point-to-multipoint, where each ME will point to different 964 branches of a P2MP tree." 965 ::= { mplsOamIdMeEntry 9 } 967 mplsOamIdMeRowStatus OBJECT-TYPE 968 SYNTAX RowStatus 969 MAX-ACCESS read-create 970 STATUS current 971 DESCRIPTION 972 "This variable is used to create, modify, and/or 973 delete a row in this table. When a row in this 974 table is in active(1) state, no objects in that row 975 can be modified by the agent except 976 mplsOamIdMeRowStatus." 977 ::= { mplsOamIdMeEntry 10 } 979 mplsOamIdMeStorageType OBJECT-TYPE 980 SYNTAX StorageType 981 MAX-ACCESS read-create 982 STATUS current 983 DESCRIPTION 984 "This variable indicates the storage type for this 985 object. 986 Conceptual rows having the value 'permanent' 987 need not allow write-access to any columnar 988 objects in the row." 989 DEFVAL { volatile } 990 ::= { mplsOamIdMeEntry 11 } 992 -- End of MPLS Transport Profile ME table 994 -- End of MPLS-TP OAM Tables 996 -- Notification Definitions of MPLS-TP identifiers 998 mplsOamIdDefectCondition NOTIFICATION-TYPE 999 OBJECTS { 1000 mplsOamIdMegName, 1001 mplsOamIdMeName, 1002 mplsOamIdMegOperStatus, 1003 mplsOamIdMegSubOperStatus 1004 } 1005 STATUS current 1006 DESCRIPTION 1007 "This notification is sent whenever the operational 1008 status of MEG is changed." 1009 ::= { mplsOamIdNotifications 1 } 1011 -- End of Notifications. 1013 -- Module Compliance. 1015 mplsOamIdCompliances 1016 OBJECT IDENTIFIER ::= { mplsOamIdConformance 1 } 1018 mplsOamIdGroups 1019 OBJECT IDENTIFIER ::= { mplsOamIdConformance 2 } 1021 -- Compliance requirement for fully compliant implementations. 1023 mplsOamIdModuleFullCompliance MODULE-COMPLIANCE 1024 STATUS current 1025 DESCRIPTION "Compliance statement for agents that provide full 1026 support for MPLS-TP-OAM-STD-MIB. Such devices can 1027 then be monitored and also be configured using 1028 this MIB module." 1030 MODULE IF-MIB -- The Interfaces Group MIB, RFC 2863. 1031 MANDATORY-GROUPS { 1032 ifGeneralInformationGroup, 1033 ifCounterDiscontinuityGroup 1034 } 1036 MODULE -- This module. 1037 MANDATORY-GROUPS { 1038 mplsOamIdMegGroup, 1039 mplsOamIdMeGroup 1040 } 1042 GROUP mplsOamIdNotificationObjectsGroup 1043 DESCRIPTION "This group is only mandatory for those 1044 implementations which can efficiently implement 1045 the notifications contained in this group." 1047 GROUP mplsOamIdNotificationGroup 1048 DESCRIPTION "This group is only mandatory for those 1049 implementations which can efficiently implement 1050 the notifications contained in this group." 1052 ::= { mplsOamIdCompliances 1 } 1054 -- Units of conformance. 1056 mplsOamIdMegGroup OBJECT-GROUP 1057 OBJECTS { 1058 mplsOamIdMegIndexNext, 1059 mplsOamIdMegName, 1060 mplsOamIdMegOperatorType, 1061 mplsOamIdMegIdCc, 1062 mplsOamIdMegIdIcc, 1063 mplsOamIdMegIdUmc, 1064 mplsOamIdMegServicePointerType, 1065 mplsOamIdMegMpLocation, 1066 mplsOamIdMegOperStatus, 1067 mplsOamIdMegSubOperStatus, 1068 mplsOamIdMegPathFlow, 1069 mplsOamIdMegRowStatus, 1070 mplsOamIdMegStorageType 1071 } 1073 STATUS current 1074 DESCRIPTION 1075 "Collection of objects needed for MPLS MEG information." 1076 ::= { mplsOamIdGroups 1 } 1078 mplsOamIdMeGroup OBJECT-GROUP 1079 OBJECTS { 1080 mplsOamIdMeIndexNext, 1081 mplsOamIdMeMpIndexNext, 1082 mplsOamIdMeName, 1083 mplsOamIdMeMpIfIndex, 1084 mplsOamIdMeSourceMepIndex, 1085 mplsOamIdMeSinkMepIndex, 1086 mplsOamIdMeMpType, 1087 mplsOamIdMeMepDirection, 1088 mplsOamIdMeServicePointer, 1089 mplsOamIdMeRowStatus, 1090 mplsOamIdMeStorageType 1092 } 1093 STATUS current 1094 DESCRIPTION 1095 "Collection of objects needed for MPLS ME information." 1096 ::= { mplsOamIdGroups 2 } 1098 mplsOamIdNotificationObjectsGroup OBJECT-GROUP 1099 OBJECTS { 1101 mplsOamIdMegOperStatus, 1103 mplsOamIdMegSubOperStatus 1104 } 1105 STATUS current 1106 DESCRIPTION 1107 "Collection of objects needed to implement notifications." 1108 ::= { mplsOamIdGroups 3 } 1110 mplsOamIdNotificationGroup NOTIFICATION-GROUP 1111 NOTIFICATIONS { 1112 mplsOamIdDefectCondition 1113 } 1114 STATUS current 1115 DESCRIPTION 1116 "Set of notifications implemented in this module." 1117 ::= { mplsOamIdGroups 4 } 1119 END 1121 8. Security Consideration 1123 There is a number of management objects defined in this MIB module 1124 that has a MAX-ACCESS clause of read-create. Such objects may be 1125 considered sensitive or vulnerable in some network environments. 1126 The support for SET operations in a non-secure environment 1127 without proper protection can have a negative effect on network 1128 operations. 1130 Some of the readable objects in this MIB module (i.e., objects 1131 with a MAX-ACCESS other than not-accessible) may be considered 1132 sensitive or vulnerable in some network environments. 1133 It is thus important to control even GET and/or NOTIFY access 1134 to these objects and possibly to even encrypt the values of these 1135 objects when sending them over the network via SNMP. These are 1136 the tables and objects and their sensitivity/vulnerability: 1138 - mplsOamIdMegTable and mplsOamIdMeTable collectively show 1139 the MPLS OAM characteristics. If an Administrator does not want to 1140 reveal this information, then these tables should be considered 1141 sensitive/vulnerable. 1143 SNMP versions prior to SNMPv3 did not include adequate security. Even 1144 if the network itself is secure (for example by using IPsec), there 1145 is no control as to who on the secure network is allowed to access 1146 and GET/SET (read/change/create/delete) the objects in this MIB 1147 module. 1149 Implementations SHOULD provide the security features described by the 1150 SNMPv3 framework (see [RFC3410]), and implementations claiming 1151 compliance to the SNMPv3 standard MUST include full support for 1152 authentication and privacy via the User-based Security Model (USM) 1153 [RFC3414] with the AES cipher algorithm [RFC3826]. Implementations 1154 MAY also provide support for the Transport Security Model (TSM) 1155 [RFC5591] in combination with a secure transport such as SSH 1156 [RFC5592] or TLS/DTLS [RFC6353]. 1158 Further, deployment of SNMP versions prior to SNMPv3 is NOT 1159 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 1160 enable cryptographic security. It is then a customer/operator 1161 responsibility to ensure that the SNMP entity giving access to an 1162 instance of this MIB module is properly configured to give access to 1163 the objects only to those principals (users) that have legitimate 1164 rights to indeed GET or SET (change/create/delete) them. 1166 9. IANA Considerations 1168 IANA is requested to assign an OID for the MIB module from the "MIB 1169 Transmission Group - MPLS STD" sub-registry of the "Internet-standard 1170 MIB - Transmission Group" registry for the MPLS-TP OAM ID MIB module 1171 specified in this document. 1173 10. References 1175 10.1 Normative References 1177 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1178 Requirement Levels", BCP 14, RFC 2119, March 1997. 1180 [RFC2578] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 1181 "Structure of Management Information Version 2 (SMIv2)", 1182 STD 58, RFC 2578, April 1999. 1184 [RFC2579] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 1185 "Textual Conventions for SMIv2", STD 58, RFC 2579, April 1186 1999. 1188 [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 1189 "Conformance Statements for SMIv2", STD 58, RFC 2580, 1190 April 1999. 1192 [RFC2863] McCloghrie, K. and F. Kastenholtz, "The Interfaces Group 1193 MIB ", RFC 2863, June 2000 1195 [RFC3031] Rosen, E., Viswanathan, A., and R. Callon, 1196 "Multiprotocol Label Switching Architecture", RFC 3031, 1197 January 2001. 1199 [RFC3289] Baker, F., Chan, K., and A. Smith, "Management 1200 Information Base for the Differentiated Services 1201 Architecture", RFC 3289, May 2002. 1203 [RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An 1204 Architecture for Describing Simple Network Management 1205 Protocol (SNMP) Management Frameworks", STD 62, RFC 1206 3411, December 2002. 1208 [RFC5601] Zelig, D., Ed., and T. Nadeau, Ed., "Pseudowire (PW) 1209 Management Information Base (MIB)", RFC 5601, July 2009. 1211 10.2 Informative References 1213 [RFC3410] J. Case, R. Mundy, D. pertain, B.Stewart, "Introduction 1214 and Applicability Statement for Internet Standard 1215 Management Framework", RFC 3410, December 2002. 1217 [RFC3414] Blumenthal, U. and B. Wijnen, "User-based Security 1218 Model(USM) for version 3 of the Simple Network 1219 Management Protocol (SNMPv3)", STD 62, RFC 3414, 1220 December 2002. 1222 [RFC3811] Nadeau, T., Ed., and J. Cucchiara, Ed., "Definitions of 1223 Textual Conventions (TCs) for Multiprotocol Label 1224 Switching (MPLS) Management", RFC 3811, June 2004. 1226 [RFC3812] Srinivasan, C., Viswanathan, A., and T. Nadeau, 1227 "Multiprotocol Label Switching (MPLS) Traffic 1228 Engineering (TE) Management Information Base (MIB)", RFC 1229 3812, June 2004. 1231 [RFC3813] Srinivasan, C., Viswanathan, A., and T. Nadeau, 1232 "Multiprotocol Label Switching (MPLS) Label Switching 1233 (LSR) Router Management Information Base (MIB)", RFC 1234 3813, June 2004. 1236 [RFC3826] Blumenthal, U., F. Maino and K. McCloghrie, "The 1237 Advanced Encryption Standard (AES) Cipher Algorithm in 1238 the SNMP User-based Security Model", RFC 3826, June 1239 2004. 1241 [RFC5591] Harrington, D. and W. Hardaker, "Transport Security 1242 Model for the Simple Network Management Protocol 1243 (SNMP)",RFC 5591, June 2009. 1245 [RFC5592] Harrington, D., Salowey, J., and W. Hardaker, "Secure 1246 Shell Transport Model for the Simple Network Management 1247 Protocol (SNMP)", RFC 5592, June 2009. 1249 [RFC5654] Niven-Jenkins, B., Ed., Brungard, D., Ed., Betts, M., 1250 Ed., Sprecher, N., and S. Ueno, "Requirements of an MPLS 1251 Transport Profile", RFC 5654, September 2009. 1253 [RFC6353] Hardaker, W., "Transport Layer Security (TLS) Transport 1254 Model for the Simple Network Management Protocol 1255 (SNMP)", STD 78, RFC 6353, July 2011. 1257 [RFC6370] Bocci, M., Swallow, G., and E. Gray, "MPLS-TP 1258 Identifiers", RFC 6370, September 2011. 1260 [RFC6371] Busi, I., Niven-Jenkins, B., and D. Allan, "MPLS-TP OAM 1261 Framework and Overview", RFC 6371, September 2011. 1263 [RFC6923] R. Winter, Ed, E. Gray, Ed., H. van Helvoort, and M. 1264 Betts, "MPLS-TP Identifiers Following ITU-T 1265 Conventions", RFC 6923, May 2013. 1267 [RFC5860] M. Vigoureux, Ed, D. Ward, Ed, M. Betts, Ed, "OAM in MPLS 1268 Transport Networks", RFC 5860, May 2010. 1270 11. Acknowledgments 1272 We wish to thank Muly Ilan, Adrian Farrel, Joan Cucchiara, 1273 Weiying Cheng and Mach Chen for their valuable comments on this 1274 document. 1276 12. Authors' Addresses 1278 Venkatesan Mahalingam 1279 Dell Inc. 1280 5450 Great America Parkway, 1281 Santa Clara, CA 95054, USA 1282 Email: venkat.mahalingams@gmail.com 1283 Sam Aldrin 1284 Huawei Technologies, co. 1285 2330 Central Express Way, 1286 Santa Clara, CA 95051, USA 1287 Email: aldrin.ietf@gmail.com 1289 Thomas D. Nadeau 1290 Brocade 1291 Email: tnadeau@lucidvision.com 1293 Kannan KV Sampath 1294 Redeem, 1295 India 1296 Email: kannankvs@gmail.com 1298 Ping Pan 1299 Infinera 1300 Email: ppan@infinera.com 1302 Sami Boutros 1303 Cisco Systems, Inc. 1304 3750 Cisco Way 1305 San Jose, California 95134 1306 USA 1307 Email: sboutros@cisco.com