idnits 2.17.00 (12 Aug 2021) /tmp/idnits17477/draft-ietf-mpls-tp-oam-id-mib-11.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 (September 10, 2015) is 2438 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) -- Obsolete informational reference (is this intentional?): RFC 5226 (Obsoleted by RFC 8126) Summary: 0 errors (**), 0 flaws (~~), 1 warning (==), 2 comments (--). 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 Google, Inc. 5 Expires: March 13, 2016 M.Venkatesan 6 Dell, Inc. 7 Kannan KV Sampath 8 Redeem 9 Thomas D. Nadeau 10 Brocade 12 September 10, 2015 14 MPLS-TP Operations, Administration, and Management (OAM) Identifiers 15 Management Information Base (MIB) 16 draft-ietf-mpls-tp-oam-id-mib-11 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 managed objects to configure the 23 Operations, Administration, and Management (OAM) identifiers 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 March 13, 2016. 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 . . . . . . . . . . . . . . . . . . . . 27 80 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 28 81 9.1 IANA Considerations for MPLS-OAM-ID-STD-MIB . . . . . . . . 28 82 10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 28 83 10.1 Normative References . . . . . . . . . . . . . . . . . . . 28 84 10.2 Informative References . . . . . . . . . . . . . . . . . . 29 85 11. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 31 86 12. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 31 88 1 Introduction 90 This memo defines a portion of the Management Information Base (MIB) 91 for use with network management protocols in the Internet community. 92 In particular, it describes managed objects for modeling a 93 Multiprotocol Label Switching- (MPLS) [RFC3031] based transport 94 profile. 96 This MIB module should be used for performing the OAM (Operations, 97 Administration, and Maintenance) operations for MPLS Tunnel LSP 98 (Label Switched Path), Pseudowires, and Sections. 100 At the time of writing, SNMP SET is no longer recommended as a way to 101 configure MPLS networks as was described in [RFC3812]. However, 102 since the MIB modules specified in this document are intended to work 103 in parallel with the MIB modules for MPLS specified in [RFC3812], 104 certain objects defined here are specified with MAX-ACCESS of read- 105 write or read-create so that specifications of the base tables in 106 [RFC3812] and the new MIB modules in this document are consistent. 107 Although the examples described in Section 6 specify means to 108 configure OAM identifiers for MPLS-TP tunnels, this should be seen as 109 indicating how the MIB values would be returned in the specified 110 circumstances having been configured by alternative means. 112 2. The Internet-Standard Management Framework 114 For a detailed overview of the documents that describe the current 115 Internet-Standard Management Framework, please refer to section 7 of 116 RFC3410 [RFC3410]. 118 Managed objects are accessed via a virtual information store, termed 119 the Management Information Base or MIB. MIB objects are generally 120 accessed through the Simple Network Management Protocol (SNMP). 121 Objects in the MIB are defined using the mechanisms defined in the 122 Structure of Management Information (SMI). This memo specifies a MIB 123 module that is compliant with the SMIv2, which is described in STD 124 58(RFC2578, RFC2579, RFC2580). 126 3. Overview 128 3.1 Conventions used in this document 130 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 131 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 132 "OPTIONAL" in this document are to be interpreted as described in RFC 133 2119 [RFC2119]. 135 3.2 Terminology 136 This document uses terminology from the Multiprotocol Label Switching 137 Architecture [RFC3031], MPLS Traffic Engineering (TE) MIB [RFC3812], 138 MPLS Label Switching Router (LSR) MIB [RFC3813], OAM Framework for 139 MPLS-Based Transport Networks [RFC6371], MPLS Transport Profile 140 (MPLS-TP) Identifiers [RFC6370], MPLS-TP Identifiers Following ITU-T 141 Conventions [RFC6923], and OAM in MPLS Transport Networks [RFC5860]. 143 3.3 Acronyms 145 BFD: Bidirectional Forwarding Detection 146 ICC: ITU Carrier Code 147 IP: Internet Protocol 148 LSP: Label Switched Path 149 LSR: Label Switching Router 150 MIB: Management Information Base 151 ME: Maintenance Entity 152 MEG: Maintenance Entity Group 153 MEP: Maintenance Entity Group End Point 154 MIP: Maintenance Entity Group Intermediate Point 155 MPLS: Multi-Protocol Label Switching 156 MPLS-TP: MPLS Transport Profile 157 PW: Pseudowire 158 TE: Traffic Engineering 159 TP: Transport Profile 161 4. Feature List 163 The MPLS transport profile OAM identifiers MIB module is designed 164 to satisfy the following requirements and constraints: 166 - The MIB module supports configuration of OAM identifiers for 167 MPLS point-to-point Tunnels, point-to-multipoint LSPs, co- 168 routed bidirectional LSPs, associated bidirectional LSPs, and 169 Pseudowires. 171 5. Brief description of MIB Objects 173 The objects described in this section support the functionality 174 described in documents [RFC5654] and [RFC6370]. The tables support 175 both IP-compatible and ICC-based OAM identifiers configurations 176 for MPLS Tunnels, LSPs, and Pseudowires. 178 5.1. mplsOamIdMegTable 180 The mplsOamIdMegTable is used to manage one or more 181 Maintenance Entities (MEs) that belong to the same transport path. 183 When a new entry is created with mplsOamIdMegOperatorType set to 184 ipCompatible (1), then as per [RFC6370] (MEG_ID for LSP 185 is LSP_ID and MEG_ID for PW is PW_Path_ID), MEP_ID can be 186 automatically formed. 188 For ICC-based transport path, the user is expected to configure 189 the ICC identifier explicitly in this table for MPLS Tunnels, LSPs, 190 and Pseudowires. 192 5.2. mplsOamIdMeTable 194 The mplsOamIdMeTable defines a relationship between two points 195 (source and sink) of a transport path to which maintenance and 196 monitoring operations apply. The two points that define 197 a maintenance entity are called Maintenance Entity Group 198 End Points (MEPs). 200 In between MEPs, there are zero or more intermediate points, 201 called Maintenance Entity Group Intermediate Points (MIPs). 202 MEPs and MIPs are associated with the MEG and can be shared by 203 more than one ME in a MEG. 205 6. MPLS OAM identifier configuration for MPLS LSP example 207 In this section, we provide an example of the OAM identifier 208 configuration for an MPLS co-routed bidirectional LSP. 210 This example provides usage of MEG and ME tables for management and 211 monitoring operations of an MPLS LSP. 213 This example considers the OAM identifiers configuration on a 214 head-end LSR to manage and monitor an MPLS LSP. 215 Only relevant objects which are applicable for IP-based OAM 216 identifiers of MPLS co-routed bidirectional LSP are illustrated here. 218 In mplsOamIdMegTable: 220 { 221 -- MEG index (Index to the table) 222 mplsOamIdMegIndex = 1, 223 mplsOamIdMegName = "MEG1", 224 mplsOamIdMegOperatorType = ipCompatible (1), 225 mplsOamIdMegServicePointerType = lsp (1), 226 mplsOamIdMegMpLocation = perNode(1), 227 -- Mandatory parameters needed to activate the row go here 228 mplsOamIdMegRowStatus = createAndGo (4), 229 mplsOamIdMegPathFlow 230 = coRoutedBidirectionalPointToPoint (2) 231 } 233 This will create an entry in the mplsOamIdMegTable to manage and 234 monitor the MPLS tunnel. 236 The following ME table is used to associate the path information 237 to a MEG. 239 In mplsOamIdMeTable: 241 { 242 -- ME index (Index to the table) 243 mplsOamIdMeIndex = 1, 245 -- MP index (Index to the table) 246 mplsOamIdMeMpIndex = 1, 247 mplsOamIdMeName = "ME1", 248 mplsOamIdMeMpIfIndex = 0, 249 -- Source MEP id is derived from the IP-compatible MPLS LSP 250 mplsOamIdMeSourceMepIndex = 0, 251 -- Sink MEP id is derived from the IP-compatible MPLS LSP 252 mplsOamIdMeSinkMepIndex = 0, 253 mplsOamIdMeMpType = mep (1), 254 mplsOamIdMeMepDirection = down (2), 255 -- RowPointer MUST point to the first accessible column of an 256 -- MPLS LSP 257 mplsOamIdMeServicePointer = mplsTunnelName.1.1.10.20, 258 -- Mandatory parameters needed to activate the row go here 259 mplsOamIdMeRowStatus = createAndGo (4) 260 } 262 7. MPLS OAM Identifiers MIB definitions 264 MPLS-OAM-ID-STD-MIB DEFINITIONS ::= BEGIN 266 IMPORTS 267 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, 268 Unsigned32 269 FROM SNMPv2-SMI -- [RFC2578] 270 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 271 FROM SNMPv2-CONF -- [RFC2580] 272 RowStatus, RowPointer, StorageType 273 FROM SNMPv2-TC -- [RFC2579] 274 SnmpAdminString 275 FROM SNMP-FRAMEWORK-MIB -- [RFC3411] 277 IndexIntegerNextFree 278 FROM DIFFSERV-MIB -- [RFC3289] 279 mplsStdMIB 280 FROM MPLS-TC-STD-MIB -- [RFC3811] 281 InterfaceIndexOrZero, ifGeneralInformationGroup, 282 ifCounterDiscontinuityGroup 283 FROM IF-MIB; -- [RFC2863] 285 mplsOamIdStdMIB MODULE-IDENTITY 286 LAST-UPDATED 287 "201508290000Z" -- August 29, 2015 288 ORGANIZATION 289 "Multiprotocol Label Switching (MPLS) Working Group" 290 CONTACT-INFO 291 " 292 Sam Aldrin 293 Google, Inc. 294 1600 Amphitheatre Parkway 295 Mountain View, CA 94043 296 USA 297 Email: aldrin.ietf@gmail.com 299 Thomas D. Nadeau 300 Email: tnadeau@lucidvision.com 302 Venkatesan Mahalingam 303 Dell, Inc. 304 5450 Great America Parkway, 305 Santa Clara, CA 95054, USA 306 Email: venkat.mahalingams@gmail.com 308 Kannan KV Sampath 309 Redeem, 310 India 311 Email: kannankvs@gmail.com 313 Ping Pan 314 Infinera 315 Email: ppan@infinera.com 317 Sami Boutros 318 Cisco Systems, Inc. 319 3750 Cisco Way 320 San Jose, California 95134 321 USA 322 Email: sboutros@cisco.com 323 " 325 DESCRIPTION 326 "Copyright (c) 2015 IETF Trust and the persons identified 327 as the document authors. All rights reserved. 329 This MIB module contains generic object definitions for 330 MPLS OAM maintenance identifiers." 332 -- Revision history. 334 REVISION 335 "201508290000Z" -- August 29, 2015 336 DESCRIPTION 337 "MPLS OAM Identifiers MIB objects for Tunnels, LSPs, 338 Pseudowires, and Sections" 340 ::= { mplsStdMIB xxx } -- xxx to be replaced with the correct 341 -- OID value assigned by 342 -- IANA (see section 9). 344 -- Top level components of this MIB module. 346 -- notifications 347 mplsOamIdNotifications 348 OBJECT IDENTIFIER ::= { mplsOamIdStdMIB 0 } 349 -- tables, scalars 350 mplsOamIdObjects OBJECT IDENTIFIER ::= { mplsOamIdStdMIB 1 } 351 -- conformance 352 mplsOamIdConformance 353 OBJECT IDENTIFIER ::= { mplsOamIdStdMIB 2 } 355 -- Start of MPLS Transport Profile MEG table 357 mplsOamIdMegIndexNext OBJECT-TYPE 358 SYNTAX IndexIntegerNextFree (0..4294967295) 359 MAX-ACCESS read-only 360 STATUS current 361 DESCRIPTION 362 "This object contains an unused value for 363 mplsOamIdMegIndex, or a zero to indicate 364 that none exist. Negative values are not allowed, 365 as they do not correspond to valid values of 366 mplsOamIdMegIndex." 367 ::= { mplsOamIdObjects 1 } 368 mplsOamIdMegTable OBJECT-TYPE 369 SYNTAX SEQUENCE OF MplsOamIdMegEntry 370 MAX-ACCESS not-accessible 371 STATUS current 372 DESCRIPTION 373 "This table contains information about the Maintenance 374 Entity Groups (MEG). 376 MEG as mentioned in MPLS-TP OAM framework defines a set 377 of one or more maintenance entities (ME). 378 Maintenance Entities define a relationship between any 379 two points of a transport path in an OAM domain to which 380 maintenance and monitoring operations apply." 381 ::= { mplsOamIdObjects 2 } 383 mplsOamIdMegEntry OBJECT-TYPE 384 SYNTAX MplsOamIdMegEntry 385 MAX-ACCESS not-accessible 386 STATUS current 387 DESCRIPTION 388 "An entry in this table represents MPLS-TP MEG. 389 An entry can be created by a network administrator 390 or by an SNMP agent as instructed by an MPLS-TP OAM 391 Framework. 393 When a new entry is created with 394 mplsOamIdMegOperatorType set to ipCompatible (1), 395 then as per [RFC6370] (MEG_ID for LSP is LSP_ID and 396 MEG_ID for PW is PW_Path_ID), MEP_ID can be 397 automatically formed. 399 For co-routed bidirectional LSP, MEG_ID is 400 A1-{Global_ID::Node_ID::Tunnel_Num}::Z9-{Global_ID:: 401 Node_ID::Tunnel_Num}::LSP_Num. 403 For associated bidirectional LSP, MEG_ID is A1- 404 {Global_ID::Node_ID::Tunnel_Num::LSP_Num}::Z9- 405 {Global_ID::Node_ID::Tunnel_Num::LSP_Num} 407 For LSP, MEP_ID is formed using, 408 Global_ID::Node_ID::Tunnel_Num::LSP_Num 410 For PW, MEG_ID is formed using AGI::A1- 411 {Global_ID::Node_ID::AC_ID}::Z9- 412 {Global_ID::Node_ID::AC_ID}. 414 For PW, MEP_ID is formed using 415 AGI::Global_ID::Node_ID::AC_ID 417 MEP_ID is retrieved from the mplsOamIdMegServicePointer 418 object based on the mplsOamIdMegServicePointerType value. 419 ICC MEG_ID for LSP and PW is formed using the objects 420 mplsOamIdMegIdIcc and mplsOamIdMegIdUmc. 422 MEP_ID can be formed using MEG_ID::MEP_Index." 423 REFERENCE 424 "1. RFC 5860, Requirements for OAM in MPLS Transport 425 Networks, May 2010. 426 2. RFC 6371, Operations, Administration, and Maintenance 427 Framework for MPLS-Based Transport Networks, 428 September 2011 Section 3. 429 3. RFC 6370, MPLS Transport Profile (MPLS-TP) Identifiers. 430 4. RFC 6923, MPLS Transport Profile (MPLS-TP) Identifiers 431 Following ITU-T Conventions." 432 INDEX { mplsOamIdMegIndex } 433 ::= { mplsOamIdMegTable 1 } 435 MplsOamIdMegEntry ::= SEQUENCE { 436 mplsOamIdMegIndex Unsigned32, 437 mplsOamIdMegName SnmpAdminString, 438 mplsOamIdMegOperatorType INTEGER, 439 mplsOamIdMegIdCc SnmpAdminString, 440 mplsOamIdMegIdIcc SnmpAdminString, 441 mplsOamIdMegIdUmc SnmpAdminString, 442 mplsOamIdMegServicePointerType INTEGER, 443 mplsOamIdMegMpLocation INTEGER, 444 mplsOamIdMegPathFlow INTEGER, 445 mplsOamIdMegOperStatus INTEGER, 446 mplsOamIdMegSubOperStatus BITS, 447 mplsOamIdMegRowStatus RowStatus, 448 mplsOamIdMegStorageType StorageType 449 } 451 mplsOamIdMegIndex OBJECT-TYPE 452 SYNTAX Unsigned32 (1..4294967295) 453 MAX-ACCESS not-accessible 454 STATUS current 455 DESCRIPTION 456 "Index for the conceptual row identifying a MEG within 457 this MEG table. Managers should obtain new values for row 458 creation in this table by reading 459 mplsOamIdMegIndexNext." 460 ::= { mplsOamIdMegEntry 1 } 462 mplsOamIdMegName OBJECT-TYPE 463 SYNTAX SnmpAdminString (SIZE(0..48)) 464 MAX-ACCESS read-create 465 STATUS current 466 DESCRIPTION 467 "Each Maintenance Entity Group has a unique name amongst 468 all those used or available to a service provider or 469 operator. It facilitates easy identification of 470 administrative responsibility for each MEG." 471 ::= { mplsOamIdMegEntry 2 } 473 mplsOamIdMegOperatorType OBJECT-TYPE 474 SYNTAX INTEGER { 475 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. RFC 6370, MPLS Transport Profile (MPLS-TP) 487 Identifiers. 488 2. RFC 6923, 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 value if 504 the MplsOamIdMegOperatorType value is iccBased(2), 505 otherwise a null value with octet size 0 506 should be assigned." 507 REFERENCE 508 "RFC 6923, MPLS Transport Profile (MPLS-TP) Identifiers 509 Following ITU-T Conventions. Section 3." 510 DEFVAL {""} 511 ::= { mplsOamIdMegEntry 4 } 512 mplsOamIdMegIdIcc OBJECT-TYPE 513 SYNTAX SnmpAdminString (SIZE(0..6)) 514 MAX-ACCESS read-create 515 STATUS current 516 DESCRIPTION 517 "Unique code assigned to Network Operator or Service 518 Provider maintained by ITU-T. The ITU Carrier Code 519 used to form MEGID. 521 This object MUST contain a non-null value if 522 the MplsOamIdMegOperatorType value is iccBased(2), 523 otherwise a null value with octet size 0 524 should be assigned." 525 REFERENCE 526 "RFC 6923, MPLS Transport Profile (MPLS-TP) Identifiers 527 Following ITU-T Conventions. Section 3.1." 528 DEFVAL {""} 529 ::= { mplsOamIdMegEntry 5 } 531 mplsOamIdMegIdUmc OBJECT-TYPE 532 SYNTAX SnmpAdminString (SIZE(0..7)) 533 MAX-ACCESS read-create 534 STATUS current 535 DESCRIPTION 536 "Unique code assigned by Network Operator or Service 537 Provider, which is appended to mplsOamIdMegIdIcc to form 538 the MEGID. 539 This object MUST contain a non-null value if 540 the MplsOamIdMegOperatorType value is iccBased(2), 541 otherwise a null value with octet size 0 542 should be assigned." 543 REFERENCE 544 "RFC 6923, MPLS Transport Profile (MPLS-TP) Identifiers 545 Following ITU-T Conventions. Section 7.1." 546 DEFVAL {""} 547 ::= { mplsOamIdMegEntry 6 } 549 mplsOamIdMegServicePointerType OBJECT-TYPE 551 SYNTAX INTEGER { 552 tunnel (1), 553 lsp (2), 554 pseudowire (3), 555 section (4) 556 } 557 MAX-ACCESS read-create 558 STATUS current 559 DESCRIPTION 560 "Indicates the service type for the MEG. 561 If the service type indicates tunnel, the service pointer 562 in mplsOamIdMeTable points to an entry in 563 the point-to-point mplsTunnelTable [RFC3812]. 565 If the service type indicates lsp, the service pointer 566 in mplsOamIdMeTable points to an entry in 567 the co-routed or associated bidirectional mplsTunnelTable. 569 If the value is pseudowire (3) service type, the service 570 pointer in mplsOamIdMeTable points to an entry in 571 the pwTable [RFC5601]. 573 If the value is section service type, the service 574 pointer in mplsOamIdMeTable points to an entry in 575 the mplsTunnelTable [RFC3812]." 576 REFERENCE 577 "1. RFC 3812, Multiprotocol Label Switching (MPLS) 578 Traffic Engineering (TE) Management Information 579 Base (MIB), June 2004. 580 2. RFC 5601, Pseudowire (PW) Management Information 581 Base (MIB), July 2009." 582 DEFVAL { lsp } 583 ::= { mplsOamIdMegEntry 7 } 585 mplsOamIdMegMpLocation OBJECT-TYPE 586 SYNTAX INTEGER { 588 perNode (1), 589 perInterface (2) 590 } 591 MAX-ACCESS read-create 592 STATUS current 593 DESCRIPTION 594 "Indicates the MP location type for this MEG. 596 If the value is perNode, then the MEG in the LSR supports 597 only perNode MEP/MIP, i.e., only one MEP/MIP in an LSR. 599 If the value is perInterface, then the MEG in the LSR 600 supports perInterface MEPs/MIPs, i.e., two MEPs/MIPs in 601 an LSR." 602 REFERENCE 603 "RFC 6371, Operations, Administration, and Maintenance 604 Framework for MPLS-Based Transport Networks, 605 September 2011." 606 DEFVAL { perNode } 607 ::= { mplsOamIdMegEntry 8 } 609 mplsOamIdMegPathFlow OBJECT-TYPE 610 SYNTAX INTEGER { 611 unidirectionalPointToPoint (1), 612 coRoutedBidirectionalPointToPoint (2), 613 associatedBidirectionalPointToPoint (3), 614 unidirectionalPointToMultiPoint (4) 615 } 616 MAX-ACCESS read-create 617 STATUS current 618 DESCRIPTION 619 "Indicates the transport path flow for this MEG. 620 In case of a unidirectional point-to-point transport path, 621 a single unidirectional Maintenance Entity is defined to 622 monitor it. 623 In case of associated bidirectional point-to-point transport 624 paths, two independent unidirectional Maintenance Entities are 625 defined to independently monitor each direction. 626 In case of co-routed bidirectional point-to-point transport 627 paths, a single bidirectional Maintenance Entity is defined to 628 monitor both directions congruently. 629 In case of unidirectional point-to-multipoint transport paths, 630 a single unidirectional Maintenance Entity for each leaf is 631 defined to monitor the transport path from the root to 632 that leaf." 633 REFERENCE 634 "RFC 6371, Operations, Administration, and Maintenance 635 Framework for MPLS-Based Transport Networks, 636 September 2011." 637 DEFVAL { coRoutedBidirectionalPointToPoint } 638 ::= { mplsOamIdMegEntry 9 } 640 mplsOamIdMegOperStatus OBJECT-TYPE 641 SYNTAX INTEGER { 642 up (1), 643 down (2) 644 } 645 MAX-ACCESS read-only 646 STATUS current 647 DESCRIPTION 648 "This object specifies the operational status of the 649 Maintenance Entity Group (MEG). This object is used to 650 send the notification to the SNMP manager about the MEG. 652 The value up (1) indicates that the MEG and its monitored 653 path are operationally up. The value down (2) indicates 654 that the MEG is operationally down. 656 When the value of mplsOamIdMegOperStatus is up (1), all 657 the bits of mplsOamIdMegSubOperStatus must be cleared. 658 When the value of mplsOamIdMegOperStatus is down (2), 659 at least one bit of mplsOamIdMegSubOperStatus must be 660 set." 661 ::= { mplsOamIdMegEntry 10 } 663 mplsOamIdMegSubOperStatus OBJECT-TYPE 664 SYNTAX BITS { 665 megDown (0), 666 meDown (1), 667 oamAppDown (2), 668 pathDown (3) 669 } 670 MAX-ACCESS read-only 671 STATUS current 672 DESCRIPTION 673 "This object specifies the reason why the MEG operational 674 status as mentioned by the object mplsOamIdMegOperStatus 675 is down. This object is used to send the notification to 676 the SNMP manager about the MEG. 678 The bit 0 (megDown) indicates the MEG is down. 679 The bit 1 (meDown) indicates the ME table is 680 down. 681 The bit 2 (oamAppDown) indicates that the 682 OAM application has notified that the entity (LSP or PW) 683 monitored by this MEG is down. Currently, BFD is the 684 only supported OAM application. 685 The bit 3 (pathDown) indicates that the underlying 686 LSP or PW is down." 687 ::= { mplsOamIdMegEntry 11 } 689 mplsOamIdMegRowStatus OBJECT-TYPE 690 SYNTAX RowStatus 691 MAX-ACCESS read-create 692 STATUS current 693 DESCRIPTION 695 "This variable is used to create, modify, and/or delete 696 a row in this table. When a row in this table is in 697 active (1) state, no objects in that row can be modified 698 by the agent except mplsOamIdMegRowStatus." 699 ::= { mplsOamIdMegEntry 12 } 701 mplsOamIdMegStorageType OBJECT-TYPE 702 SYNTAX StorageType 703 MAX-ACCESS read-create 704 STATUS current 705 DESCRIPTION 706 "This variable indicates the storage type for this 707 object. 708 Conceptual rows having the value 'permanent' 709 need not allow write-access to any columnar 710 objects in the row." 711 DEFVAL { volatile } 712 ::= { mplsOamIdMegEntry 13 } 714 -- End of MPLS Transport Profile MEG table 716 -- Start of MPLS Transport Profile ME table 718 mplsOamIdMeIndexNext OBJECT-TYPE 719 SYNTAX IndexIntegerNextFree (0..4294967295) 720 MAX-ACCESS read-only 721 STATUS current 722 DESCRIPTION 723 "This object contains an unused value for 724 mplsOamIdMeIndex, or a zero to indicate 725 that none exist. Negative values are not allowed, 726 as they do not correspond to valid values of 727 mplsOamIdMeIndex." 728 ::= { mplsOamIdObjects 3 } 730 mplsOamIdMeMpIndexNext OBJECT-TYPE 731 SYNTAX IndexIntegerNextFree (0..4294967295) 732 MAX-ACCESS read-only 733 STATUS current 734 DESCRIPTION 735 "This object contains an unused value for 736 mplsOamIdMeMpIndex, or a zero to indicate 737 that none exist. Negative values are not allowed, 738 as they do not correspond to valid values of 739 mplsOamIdMeMpIndex." 740 ::= { mplsOamIdObjects 4 } 742 mplsOamIdMeTable OBJECT-TYPE 743 SYNTAX SEQUENCE OF MplsOamIdMeEntry 744 MAX-ACCESS not-accessible 745 STATUS current 746 DESCRIPTION 747 "This table contains MPLS-TP maintenance entity 748 information. 750 ME is some portion of a transport path that requires 751 management bounded by two points (called MEPs), and the 752 relationship between those points to which maintenance 753 and monitoring operations apply. 755 This table is generic enough to handle MEPs and MIPs 756 information within a MEG." 757 ::= { mplsOamIdObjects 5 } 759 mplsOamIdMeEntry OBJECT-TYPE 760 SYNTAX MplsOamIdMeEntry 761 MAX-ACCESS not-accessible STATUS current 762 DESCRIPTION 763 "An entry in this table represents MPLS-TP maintenance 764 entity. This entry represents the ME if the source and 765 sink MEPs are defined. 767 A ME is a point-to-point entity. One ME has two such MEPs. 768 A MEG is a group of one or more MEs. One MEG can have 769 two or more MEPs. 771 For point-to-point LSP, one MEG has one ME and this ME 772 is associated two MEPs (source and sink MEPs) within 773 a MEG. Each mplsOamIdMeIndex value denotes the ME within 774 a MEG. 776 In case of unidirectional point-to-point transport paths, 777 a single unidirectional Maintenance Entity is defined to 778 monitor it and mplsOamIdMeServicePointer points to 779 unidirectional point-to-point path. 781 In case of associated bidirectional point-to-point 782 transport paths, two independent unidirectional 783 Maintenance Entities are defined to independently monitor 784 each direction and each mplsOamIdMeServicePointer MIB 785 object points to unique unidirectional transport path. 786 This has implications for transactions that terminate at 787 or query a MIP, as a return path from MIP to source MEP 788 does not necessarily exist within the MEG. 790 In case of co-routed bidirectional point-to-point 791 transport paths, a single bidirectional Maintenance Entity 792 is defined to monitor both directions congruently and 793 mplsOamIdMeServicePointer MIB object points to co-routed 794 bidirectional point-to-point transport path. 796 In case of unidirectional point-to-multipoint transport 797 paths, a single unidirectional Maintenance entity for each 798 leaf is defined to monitor the transport path from the 799 root to that leaf and each leaf has different transport 800 path information in mplsOamIdMeServicePointer MIB object. 801 Note that the MplsOamIdMeEntry should be created manually 802 once the MEG is configured for OAM operations." 803 INDEX { mplsOamIdMegIndex, 804 mplsOamIdMeIndex, 805 mplsOamIdMeMpIndex 806 } 807 ::= { mplsOamIdMeTable 1 } 809 MplsOamIdMeEntry ::= SEQUENCE { 810 mplsOamIdMeIndex Unsigned32, 811 mplsOamIdMeMpIndex Unsigned32, 812 mplsOamIdMeName SnmpAdminString, 813 mplsOamIdMeMpIfIndex InterfaceIndexOrZero, 814 mplsOamIdMeSourceMepIndex Unsigned32, 815 mplsOamIdMeSinkMepIndex Unsigned32, 816 mplsOamIdMeMpType INTEGER, 817 mplsOamIdMeMepDirection INTEGER, 818 mplsOamIdMeServicePointer RowPointer, 819 mplsOamIdMeRowStatus RowStatus, 820 mplsOamIdMeStorageType StorageType 821 } 823 mplsOamIdMeIndex OBJECT-TYPE 824 SYNTAX Unsigned32 (1..4294967295) 825 MAX-ACCESS not-accessible 826 STATUS current 827 DESCRIPTION 828 "Uniquely identifies a maintenance entity index within 829 a MEG. Managers should obtain new values for row 830 creation in this table by reading 831 mplsOamIdMeIndexNext." 832 ::= { mplsOamIdMeEntry 1 } 834 mplsOamIdMeMpIndex OBJECT-TYPE 836 SYNTAX Unsigned32 (1..4294967295) 837 MAX-ACCESS not-accessible 838 STATUS current 839 DESCRIPTION 840 "Indicates the maintenance point index, used to create 841 multiple MEPs in a node of single ME. The value of this 842 object can be MEP index or MIP index. Managers should 843 obtain new values for row creation in this table by reading 844 mplsOamIdMeMpIndexNext." 845 ::= { mplsOamIdMeEntry 2 } 847 mplsOamIdMeName OBJECT-TYPE 848 SYNTAX SnmpAdminString (SIZE(1..48)) 849 MAX-ACCESS read-create 850 STATUS current 851 DESCRIPTION 852 "This object denotes the ME name, each 853 Maintenance Entity has unique name within MEG." 854 ::= { mplsOamIdMeEntry 3 } 856 mplsOamIdMeMpIfIndex OBJECT-TYPE 857 SYNTAX InterfaceIndexOrZero 858 MAX-ACCESS read-create 859 STATUS current 860 DESCRIPTION 861 "Indicates the maintenance point interface. 862 If the mplsOamIdMegMpLocation object value 863 is perNode (1), the MP interface index should point 864 to incoming interface or outgoing interface or 865 zero (indicates the MP OAM packets are initiated 866 from forwarding engine). 868 If the mplsOamIdMegMpLocation object value is 869 perInterface (2), the MP interface index should point to 870 incoming interface or outgoing interface." 871 REFERENCE 872 "1. RFC 6371, Operations, Administration, and Maintenance 873 Framework for MPLS-Based Transport Networks, 874 September 2011. 875 2. RFC 2863 - The Interfaces Group MIB, McCloghrie, K., 876 and F. Kastenholtz, June 2000." 877 DEFVAL { 0 } 878 ::= { mplsOamIdMeEntry 4 } 880 mplsOamIdMeSourceMepIndex OBJECT-TYPE 881 SYNTAX Unsigned32 882 MAX-ACCESS read-create 883 STATUS current 884 DESCRIPTION 885 "Indicates the source MEP Index of the ME. This object 886 should be configured if mplsOamIdMegOperatorType object 887 in the mplsOamIdMegEntry is configured as iccBased (2). 888 If the MEG is configured for IP-based operator, 889 the value of this object should be set zero and the MEP 890 ID will be automatically derived from the service 891 Identifiers(MPLS-TP LSP/PW Identifier)." 892 DEFVAL { 0 } 893 ::= { mplsOamIdMeEntry 5 } 895 mplsOamIdMeSinkMepIndex OBJECT-TYPE 896 SYNTAX Unsigned32 897 MAX-ACCESS read-create 898 STATUS current 899 DESCRIPTION 900 "Indicates the sink MEP Index of the ME. This object 901 should be configured if mplsOamIdMegOperatorType object 902 in the mplsOamIdMegEntry is configured as iccBased (2). 903 If the MEG is configured for IP-based operator, 904 the value of this object should be set to zero and the MEP 905 ID will be automatically derived from the service 906 Identifiers (MPLS-TP LSP/PW Identifier)." 907 DEFVAL { 0 } 908 ::= { mplsOamIdMeEntry 6 } 910 mplsOamIdMeMpType OBJECT-TYPE 911 SYNTAX INTEGER { 912 mep (1), 913 mip (2) 914 } 915 MAX-ACCESS read-create 916 STATUS current 917 DESCRIPTION 918 "Indicates the maintenance point type within the MEG. 920 The object should have the value mep (1), only in the 921 Ingress or Egress nodes of the transport path. 923 The object can have the value mip (2), in 924 the Intermediate nodes and possibly in the Egress 925 nodes of the transport path." 926 DEFVAL { mep } 927 ::= { mplsOamIdMeEntry 7 } 929 mplsOamIdMeMepDirection OBJECT-TYPE 930 SYNTAX INTEGER { 931 up (1), 932 down (2), 933 notApplicable (3) 934 } 935 MAX-ACCESS read-create 936 STATUS current 937 DESCRIPTION 938 "Indicates the direction of the MEP. This object 939 should be configured if mplsOamIdMeMpType is 940 configured as mep (1) else notApplicable (3) is set." 941 DEFVAL { down } 942 ::= { mplsOamIdMeEntry 8 } 944 mplsOamIdMeServicePointer OBJECT-TYPE 946 SYNTAX RowPointer 947 MAX-ACCESS read-create 948 STATUS current 949 DESCRIPTION 950 "This variable represents a pointer to the MPLS-TP 951 transport path. This value MUST point at an entry in the 952 mplsTunnelEntry if mplsOamIdMegServicePointerType 953 is configured as tunnel (1) or lsp (2) or section (4) or 954 at an entry in the pwEntry if 955 mplsOamIdMegServicePointerType is configured 956 as pseudowire (3). 958 Note: This service pointer object is placed in the ME table 959 instead of the MEG table since it will be useful in case of 960 point-to-multipoint, where each ME will point to different 961 branches of a P2MP tree." 962 ::= { mplsOamIdMeEntry 9 } 964 mplsOamIdMeRowStatus OBJECT-TYPE 965 SYNTAX RowStatus 966 MAX-ACCESS read-create 967 STATUS current 968 DESCRIPTION 969 "This variable is used to create, modify, and/or 970 delete a row in this table. When a row in this 971 table is in active (1) state, no objects in that row 972 can be modified by the agent except 973 mplsOamIdMeRowStatus." 974 ::= { mplsOamIdMeEntry 10 } 976 mplsOamIdMeStorageType OBJECT-TYPE 977 SYNTAX StorageType 978 MAX-ACCESS read-create 979 STATUS current 980 DESCRIPTION 981 "This variable indicates the storage type for this 982 object. 983 Conceptual rows having the value 'permanent' 984 need not allow write-access to any columnar 985 objects in the row." 986 DEFVAL { volatile } 987 ::= { mplsOamIdMeEntry 11 } 989 -- End of MPLS Transport Profile ME table 991 -- End of MPLS-TP OAM Tables 993 -- Notification Definitions of MPLS-TP identifiers 995 mplsOamIdDefectCondition NOTIFICATION-TYPE 996 OBJECTS { 997 mplsOamIdMegName, 998 mplsOamIdMeName, 999 mplsOamIdMegOperStatus, 1000 mplsOamIdMegSubOperStatus 1001 } 1002 STATUS current 1003 DESCRIPTION 1004 "This notification is sent whenever the operational 1005 status of MEG is changed." 1006 ::= { mplsOamIdNotifications 1 } 1008 -- End of Notifications. 1010 -- Module Compliance. 1012 mplsOamIdCompliances 1013 OBJECT IDENTIFIER ::= { mplsOamIdConformance 1 } 1015 mplsOamIdGroups 1016 OBJECT IDENTIFIER ::= { mplsOamIdConformance 2 } 1018 -- Compliance requirement for fully compliant implementations. 1020 mplsOamIdModuleFullCompliance MODULE-COMPLIANCE 1021 STATUS current 1022 DESCRIPTION "Compliance statement for agents that provide full 1023 support for MPLS-TP-OAM-STD-MIB. Such devices can 1024 then be monitored and also be configured using 1025 this MIB module." 1027 MODULE IF-MIB -- The Interfaces Group MIB, RFC 2863. 1028 MANDATORY-GROUPS { 1029 ifGeneralInformationGroup, 1030 ifCounterDiscontinuityGroup 1031 } 1033 MODULE -- This module. 1034 MANDATORY-GROUPS { 1035 mplsOamIdMegGroup, 1036 mplsOamIdMeGroup 1037 } 1039 GROUP mplsOamIdNotificationObjectsGroup 1040 DESCRIPTION "This group is only mandatory for those 1041 implementations which can efficiently implement 1042 the notifications contained in this group." 1044 GROUP mplsOamIdNotificationGroup 1045 DESCRIPTION "This group is only mandatory for those 1046 implementations which can efficiently implement 1047 the notifications contained in this group." 1049 ::= { mplsOamIdCompliances 1 } 1051 -- Compliance requirement for read-only implementations. 1053 mplsOamIdModuleReadOnlyCompliance MODULE-COMPLIANCE 1054 STATUS current 1055 DESCRIPTION 1056 "Compliance statement for agents that only provide 1057 read-only support for the MPLS-TP-OAM-STD-MIB module." 1059 MODULE -- this module 1061 MANDATORY-GROUPS { 1062 mplsOamIdMegGroup, 1063 mplsOamIdMeGroup 1064 } 1066 GROUP mplsOamIdNotificationObjectsGroup 1067 DESCRIPTION "This group is only mandatory for those 1068 implementations which can efficiently implement 1069 the notifications contained in this group." 1071 GROUP mplsOamIdNotificationGroup 1072 DESCRIPTION "This group is only mandatory for those 1073 implementations which can efficiently implement 1074 the notifications contained in this group." 1076 -- mplsOamIdMegTable 1078 OBJECT mplsOamIdMegName 1079 MIN-ACCESS read-only 1080 DESCRIPTION 1081 "Write access is not required." 1083 OBJECT mplsOamIdMegOperatorType 1084 MIN-ACCESS read-only 1085 DESCRIPTION 1086 "Write access is not required." 1088 OBJECT mplsOamIdMegIdCc 1089 MIN-ACCESS read-only 1090 DESCRIPTION 1091 "Write access is not required." 1093 OBJECT mplsOamIdMegIdIcc 1094 MIN-ACCESS read-only 1095 DESCRIPTION 1096 "Write access is not required." 1098 OBJECT mplsOamIdMegIdUmc 1099 MIN-ACCESS read-only 1100 DESCRIPTION 1101 "Write access is not required." 1103 OBJECT mplsOamIdMegServicePointerType 1104 MIN-ACCESS read-only 1105 DESCRIPTION 1106 "Write access is not required." 1108 OBJECT mplsOamIdMegMpLocation 1109 MIN-ACCESS read-only 1110 DESCRIPTION 1111 "Write access is not required." 1113 OBJECT mplsOamIdMegPathFlow 1114 MIN-ACCESS read-only 1115 DESCRIPTION 1116 "Write access is not required." 1118 OBJECT mplsOamIdMegRowStatus 1119 SYNTAX RowStatus { active(1) } 1120 MIN-ACCESS read-only 1121 DESCRIPTION 1122 "Write access is not required." 1124 OBJECT mplsOamIdMegStorageType 1125 MIN-ACCESS read-only 1126 DESCRIPTION 1127 "Write access is not required." 1129 -- mplsOamIdMeTable 1131 OBJECT mplsOamIdMeName 1132 MIN-ACCESS read-only 1133 DESCRIPTION 1134 "Write access is not required." 1136 OBJECT mplsOamIdMeMpIfIndex 1137 MIN-ACCESS read-only 1138 DESCRIPTION 1139 "Write access is not required." 1141 OBJECT mplsOamIdMeSourceMepIndex 1142 MIN-ACCESS read-only 1143 DESCRIPTION 1144 "Write access is not required." 1146 OBJECT mplsOamIdMeSinkMepIndex 1147 MIN-ACCESS read-only 1148 DESCRIPTION 1149 "Write access is not required." 1151 OBJECT mplsOamIdMeMpType 1152 MIN-ACCESS read-only 1153 DESCRIPTION 1154 "Write access is not required." 1156 OBJECT mplsOamIdMeMepDirection 1157 MIN-ACCESS read-only 1158 DESCRIPTION 1159 "Write access is not required." 1161 OBJECT mplsOamIdMeServicePointer 1162 MIN-ACCESS read-only 1163 DESCRIPTION 1164 "Write access is not required." 1166 OBJECT mplsOamIdMeRowStatus 1167 SYNTAX RowStatus { active(1) } 1168 MIN-ACCESS read-only 1169 DESCRIPTION 1170 "Write access is not required." 1172 OBJECT mplsOamIdMeStorageType 1173 MIN-ACCESS read-only 1174 DESCRIPTION 1175 "Write access is not required." 1177 ::= { mplsOamIdCompliances 2 } 1179 -- Units of conformance. 1181 mplsOamIdMegGroup OBJECT-GROUP 1182 OBJECTS { 1183 mplsOamIdMegIndexNext, 1184 mplsOamIdMegName, 1185 mplsOamIdMegOperatorType, 1186 mplsOamIdMegIdCc, 1187 mplsOamIdMegIdIcc, 1188 mplsOamIdMegIdUmc, 1189 mplsOamIdMegServicePointerType, 1190 mplsOamIdMegMpLocation, 1191 mplsOamIdMegOperStatus, 1192 mplsOamIdMegSubOperStatus, 1193 mplsOamIdMegPathFlow, 1194 mplsOamIdMegRowStatus, 1195 mplsOamIdMegStorageType 1196 } 1198 STATUS current 1199 DESCRIPTION 1200 "Collection of objects needed for MPLS MEG information." 1201 ::= { mplsOamIdGroups 1 } 1203 mplsOamIdMeGroup OBJECT-GROUP 1204 OBJECTS { 1205 mplsOamIdMeIndexNext, 1206 mplsOamIdMeMpIndexNext, 1207 mplsOamIdMeName, 1208 mplsOamIdMeMpIfIndex, 1209 mplsOamIdMeSourceMepIndex, 1210 mplsOamIdMeSinkMepIndex, 1211 mplsOamIdMeMpType, 1212 mplsOamIdMeMepDirection, 1213 mplsOamIdMeServicePointer, 1214 mplsOamIdMeRowStatus, 1215 mplsOamIdMeStorageType 1216 } 1217 STATUS current 1218 DESCRIPTION 1219 "Collection of objects needed for MPLS ME information." 1220 ::= { mplsOamIdGroups 2 } 1222 mplsOamIdNotificationObjectsGroup OBJECT-GROUP 1223 OBJECTS { 1225 mplsOamIdMegOperStatus, 1227 mplsOamIdMegSubOperStatus 1228 } 1229 STATUS current 1230 DESCRIPTION 1231 "Collection of objects needed to implement notifications." 1232 ::= { mplsOamIdGroups 3 } 1234 mplsOamIdNotificationGroup NOTIFICATION-GROUP 1235 NOTIFICATIONS { 1236 mplsOamIdDefectCondition 1237 } 1238 STATUS current 1239 DESCRIPTION 1240 "Set of notifications implemented in this module." 1241 ::= { mplsOamIdGroups 4 } 1243 END 1245 8. Security Consideration 1247 This MIB relates to a system that will provide network connectivity 1248 and packet forwarding services. As such, improper manipulation of the 1249 objects represented by this MIB may result in denial of service to a 1250 large number of end-users. 1252 There are number of management objects defined in this MIB module 1253 with a MAX-ACCESS clause of read-create. Such objects may be 1254 considered sensitive or vulnerable in some network environments. 1255 The support for SET operations in a non-secure environment 1256 without proper protection opens devices to attack. 1258 Some of the readable objects in this MIB module (i.e., objects 1259 with a MAX-ACCESS other than not-accessible) may be considered 1260 sensitive or vulnerable in some network environments. 1261 It is thus important to control even GET and/or NOTIFY access 1262 to these objects and possibly to even encrypt the values of these 1263 objects when sending them over the network via SNMP. These are 1264 the tables and objects and their sensitivity/vulnerability: 1266 - mplsOamIdMegTable and mplsOamIdMeTable collectively show 1267 the MPLS OAM characteristics. If an Administrator does not want to 1268 reveal this information, then these tables should be considered 1269 sensitive/vulnerable. 1271 SNMP versions prior to SNMPv3 did not include adequate security. Even 1272 if the network itself is secure (for example by using IPsec), there 1273 is no control as to who on the secure network is allowed to access 1274 and GET/SET (read/change/create/delete) the objects in this MIB 1275 module. 1277 Implementations SHOULD provide the security features described by the 1278 SNMPv3 framework (see [RFC3410]), and implementations claiming 1279 compliance to the SNMPv3 standard MUST include full support for 1280 authentication and privacy via the User-based Security Model (USM) 1281 [RFC3414] with the AES cipher algorithm [RFC3826]. Implementations 1282 MAY also provide support for the Transport Security Model (TSM) 1283 [RFC5591] in combination with a secure transport such as SSH 1284 [RFC5592] or TLS/DTLS [RFC6353]. 1286 Further, deployment of SNMP versions prior to SNMPv3 is NOT 1287 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 1288 enable cryptographic security. It is then a customer/operator 1289 responsibility to ensure that the SNMP entity giving access to an 1290 instance of this MIB module is properly configured to give access to 1291 the objects only to those principals (users) that have legitimate 1292 rights to indeed GET or SET (change/create/delete) them. 1294 9. IANA Considerations 1296 As described in [RFC4221] and [RFC6639], and as requested in the 1297 MPLS-TC-STD-MIB [RFC3811], MPLS-related Standards Track MIB modules 1298 should be rooted under the mplsStdMIB subtree. The following 1299 subsection lists a new assignment to be made by IANA under the 1300 mplsStdMIB subtree for the MPLS-OAM-ID-STD-MIB MIB module defined in 1301 this document. New assignments can only be made via a Standards 1302 Action as specified in [RFC5226]. 1304 9.1 IANA Considerations for MPLS-OAM-ID-STD-MIB 1306 IANA has to assign the OID { mplsStdMIB xxx } to the MPLS-OAM-ID-STD- 1307 MIB module specified in this document. 1309 10. References 1311 10.1 Normative References 1313 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1314 Requirement Levels", BCP 14, RFC 2119, March 1997. 1316 [RFC2578] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 1317 "Structure of Management Information Version 2 (SMIv2)", 1318 STD 58, RFC 2578, April 1999. 1320 [RFC2579] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 1321 "Textual Conventions for SMIv2", STD 58, RFC 2579, April 1322 1999. 1324 [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 1325 "Conformance Statements for SMIv2", STD 58, RFC 2580, 1326 April 1999. 1328 [RFC2863] McCloghrie, K. and F. Kastenholtz, "The Interfaces Group 1329 MIB ", RFC 2863, June 2000 1331 [RFC3031] Rosen, E., Viswanathan, A., and R. Callon, 1332 "Multiprotocol Label Switching Architecture", RFC 3031, 1333 January 2001. 1335 [RFC3289] Baker, F., Chan, K., and A. Smith, "Management 1336 Information Base for the Differentiated Services 1337 Architecture", RFC 3289, May 2002. 1339 [RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An 1340 Architecture for Describing Simple Network Management 1341 Protocol (SNMP) Management Frameworks", STD 62, RFC 1342 3411, December 2002. 1344 [RFC5601] Zelig, D., Ed., and T. Nadeau, Ed., "Pseudowire (PW) 1345 Management Information Base (MIB)", RFC 5601, July 2009. 1347 10.2 Informative References 1349 [RFC3410] J. Case, R. Mundy, D. pertain, B.Stewart, "Introduction 1350 and Applicability Statement for Internet Standard 1351 Management Framework", RFC 3410, December 2002. 1353 [RFC3414] Blumenthal, U. and B. Wijnen, "User-based Security 1354 Model(USM) for version 3 of the Simple Network 1355 Management Protocol (SNMPv3)", STD 62, RFC 3414, 1356 December 2002. 1358 [RFC3811] Nadeau, T., Ed., and J. Cucchiara, Ed., "Definitions of 1359 Textual Conventions (TCs) for Multiprotocol Label 1360 Switching (MPLS) Management", RFC 3811, June 2004. 1362 [RFC3812] Srinivasan, C., Viswanathan, A., and T. Nadeau, 1363 "Multiprotocol Label Switching (MPLS) Traffic 1364 Engineering (TE) Management Information Base (MIB)", RFC 1365 3812, June 2004. 1367 [RFC3813] Srinivasan, C., Viswanathan, A., and T. Nadeau, 1368 "Multiprotocol Label Switching (MPLS) Label Switching 1369 (LSR) Router Management Information Base (MIB)", RFC 1370 3813, June 2004. 1372 [RFC3826] Blumenthal, U., F. Maino and K. McCloghrie, "The 1373 Advanced Encryption Standard (AES) Cipher Algorithm in 1374 the SNMP User-based Security Model", RFC 3826, June 1375 2004. 1377 [RFC4221] Nadeau, T., Srinivasan, C., and A. Farrel, 1378 "Multiprotocol Label Switching (MPLS) Management 1379 Overview", RFC 4221, November 2005, . 1382 [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an 1383 IANA Considerations Section in RFCs", BCP 26, RFC 5226, 1384 May 2008, . 1386 [RFC5591] Harrington, D. and W. Hardaker, "Transport Security 1387 Model for the Simple Network Management Protocol 1388 (SNMP)",RFC 5591, June 2009. 1390 [RFC5592] Harrington, D., Salowey, J., and W. Hardaker, "Secure 1391 Shell Transport Model for the Simple Network Management 1392 Protocol (SNMP)", RFC 5592, June 2009. 1394 [RFC5654] Niven-Jenkins, B., Ed., Brungard, D., Ed., Betts, M., 1395 Ed., Sprecher, N., and S. Ueno, "Requirements of an MPLS 1396 Transport Profile", RFC 5654, September 2009. 1398 [RFC5860] M. Vigoureux, Ed, D. Ward, Ed, M. Betts, Ed, "OAM in MPLS 1399 Transport Networks", RFC 5860, May 2010. 1401 [RFC6353] Hardaker, W., "Transport Layer Security (TLS) Transport 1402 Model for the Simple Network Management Protocol 1403 (SNMP)", STD 78, RFC 6353, July 2011. 1405 [RFC6370] Bocci, M., Swallow, G., and E. Gray, "MPLS-TP 1406 Identifiers", RFC 6370, September 2011. 1408 [RFC6371] Busi, I., Niven-Jenkins, B., and D. Allan, "MPLS-TP OAM 1409 Framework and Overview", RFC 6371, September 2011. 1411 [RFC6639] King, D., Ed., and M. Venkatesan, Ed., "Multiprotocol 1412 Label Switching Transport Profile (MPLS-TP) MIB-Based 1413 Management Overview", RFC 6639, June 2012, 1414 . 1416 [RFC6923] R. Winter, Ed, E. Gray, Ed., H. van Helvoort, and M. 1417 Betts, "MPLS-TP Identifiers Following ITU-T 1418 Conventions", RFC 6923, May 2013. 1420 11. Acknowledgments 1422 We wish to thank Muly Ilan, Adrian Farrel, Joan Cucchiara, 1423 Weiying Cheng, Mach Chen, Peter Yee, and Tina TSOU for their 1424 valuable comments on this document. 1426 12. Authors' Addresses 1428 Venkatesan Mahalingam 1429 Dell, Inc. 1430 5450 Great America Parkway, 1431 Santa Clara, CA 95054, USA 1432 Email: venkat.mahalingams@gmail.com 1434 Sam Aldrin 1435 Google, Inc. 1436 1600 Amphitheatre Parkway 1437 Mountain View, CA 94043 1438 USA 1439 Email: aldrin.ietf@gmail.com 1441 Thomas D. Nadeau 1442 Brocade 1443 Email: tnadeau@lucidvision.com 1445 Kannan KV Sampath 1446 Redeem, 1447 India 1448 Email: kannankvs@gmail.com 1450 Ping Pan 1451 Infinera 1452 Email: ppan@infinera.com 1454 Sami Boutros 1455 Cisco Systems, Inc. 1456 3750 Cisco Way 1457 San Jose, California 95134 1458 USA 1459 Email: sboutros@cisco.com