idnits 2.17.1 draft-ietf-mpls-tp-oam-id-mib-10.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 8, 2015) is 3152 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 Google, Inc. 5 Expires: March 11, 2016 M.Venkatesan 6 Dell, Inc. 7 Kannan KV Sampath 8 Redeem 9 Thomas D. Nadeau 10 Brocade 12 September 8, 2015 14 MPLS-TP Operations, Administration, and Management (OAM) Identifiers 15 Management Information Base (MIB) 16 draft-ietf-mpls-tp-oam-id-mib-10 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 11, 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 10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 28 82 10.1 Normative References . . . . . . . . . . . . . . . . . . . 28 83 10.2 Informative References . . . . . . . . . . . . . . . . . . 29 84 11. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 30 85 12. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 30 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 Tunnel LSP 97 (Label 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 with the SMIv2, which is described in STD 123 58(RFC2578, RFC2579, 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 RFC 132 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 BFD: Bidirectional Forwarding Detection 145 ICC: ITU Carrier Code 146 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 belong 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 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 an 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 -- Sink 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 "201508290000Z" -- August 29, 2015 287 ORGANIZATION 288 "Multiprotocol Label Switching (MPLS) Working Group" 289 CONTACT-INFO 290 " 291 Sam Aldrin 292 Google, Inc. 293 1600 Amphitheatre Parkway 294 Mountain View, CA 94043 295 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 322 " 324 DESCRIPTION 325 "Copyright (c) 2015 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 "201508290000Z" -- August 29, 2015 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. RFC 5860, Requirements for OAM in MPLS Transport 424 Networks, May 2010. 425 2. RFC 6371, Operations, Administration, and Maintenance 426 Framework for MPLS-Based Transport Networks, 427 September 2011 Section 3. 428 3. RFC 6370, MPLS Transport Profile (MPLS-TP) Identifiers. 429 4. RFC 6923, 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 a 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), 475 iccBased (2) 476 } 477 MAX-ACCESS read-create 478 STATUS current 479 DESCRIPTION 480 "Indicates the operator type for MEG. Conceptual rows 481 having 'iccBased' as operator type, MUST have valid 482 values for the objects mplsOamIdMegIdIcc and 483 mplsOamIdMegIdUmc when the row status is active." 484 REFERENCE 485 "1. RFC 6370, MPLS Transport Profile (MPLS-TP) 486 Identifiers. 487 2. RFC 6923, MPLS Transport Profile (MPLS-TP) Identifiers 488 Following ITU-T Conventions. Section 3.1" 489 DEFVAL { ipCompatible } 490 ::= { mplsOamIdMegEntry 3 } 492 mplsOamIdMegIdCc OBJECT-TYPE 493 SYNTAX SnmpAdminString (SIZE(0..2)) 494 MAX-ACCESS read-create 495 STATUS current 496 DESCRIPTION 497 "Global uniqueness is assured by concatenating the ICC 498 with a Country Code (CC). The Country Code (alpha-2) 499 is a string of two alphabetic characters represented 500 with upper case letters (i.e., A-Z). 502 This object MUST contain a non-null value if 503 the MplsOamIdMegOperatorType value is iccBased(2), 504 otherwise a null value with octet size 0 505 should be assigned." 506 REFERENCE 507 "RFC 6923, MPLS Transport Profile (MPLS-TP) Identifiers 508 Following ITU-T Conventions. Section 3." 509 DEFVAL {""} 510 ::= { mplsOamIdMegEntry 4 } 511 mplsOamIdMegIdIcc OBJECT-TYPE 512 SYNTAX SnmpAdminString (SIZE(0..6)) 513 MAX-ACCESS read-create 514 STATUS current 515 DESCRIPTION 516 "Unique code assigned to Network Operator or Service 517 Provider maintained by ITU-T. The ITU Carrier Code 518 used to form MEGID. 520 This object MUST contain a non-null value if 521 the MplsOamIdMegOperatorType value is iccBased(2), 522 otherwise a null value with octet size 0 523 should be assigned." 524 REFERENCE 525 "RFC 6923, MPLS Transport Profile (MPLS-TP) Identifiers 526 Following ITU-T Conventions. Section 3.1." 527 DEFVAL {""} 528 ::= { mplsOamIdMegEntry 5 } 530 mplsOamIdMegIdUmc OBJECT-TYPE 531 SYNTAX SnmpAdminString (SIZE(0..7)) 532 MAX-ACCESS read-create 533 STATUS current 534 DESCRIPTION 535 "Unique code assigned by Network Operator or Service 536 Provider, which is appended to mplsOamIdMegIdIcc to form 537 the MEGID. 538 This object MUST contain a non-null value if 539 the MplsOamIdMegOperatorType value is iccBased(2), 540 otherwise a null value with octet size 0 541 should be assigned." 542 REFERENCE 543 "RFC 6923, MPLS Transport Profile (MPLS-TP) Identifiers 544 Following ITU-T Conventions. Section 7.1." 545 DEFVAL {""} 546 ::= { mplsOamIdMegEntry 6 } 548 mplsOamIdMegServicePointerType OBJECT-TYPE 550 SYNTAX INTEGER { 551 tunnel (1), 552 lsp (2), 553 pseudowire (3), 554 section (4) 555 } 556 MAX-ACCESS read-create 557 STATUS current 558 DESCRIPTION 559 "Indicates the service type for the MEG. 560 If the service type indicates tunnel, the service pointer 561 in mplsOamIdMeTable points to an entry in 562 the point-to-point mplsTunnelTable [RFC3812]. 564 If the service type indicates lsp, the service pointer 565 in mplsOamIdMeTable points to an entry in 566 the co-routed or associated bidirectional mplsTunnelTable. 568 If the value is pseudowire (3) service type, the service 569 pointer in mplsOamIdMeTable points to an entry in 570 the pwTable [RFC5601]. 572 If the value is section service type, the service 573 pointer in mplsOamIdMeTable points to an entry in 574 the mplsTunnelTable [RFC3812]." 575 REFERENCE 576 "1. RFC 3812, Multiprotocol Label Switching (MPLS) 577 Traffic Engineering (TE) Management Information 578 Base (MIB), June 2004. 579 2. RFC 5601, Pseudowire (PW) Management Information 580 Base (MIB), July 2009." 581 DEFVAL { lsp } 582 ::= { mplsOamIdMegEntry 7 } 584 mplsOamIdMegMpLocation OBJECT-TYPE 585 SYNTAX INTEGER { 587 perNode (1), 588 perInterface (2) 589 } 590 MAX-ACCESS read-create 591 STATUS current 592 DESCRIPTION 593 "Indicates the MP location type for this MEG. 595 If the value is perNode, then the MEG in the LSR supports 596 only perNode MEP/MIP, i.e., only one MEP/MIP in an LSR. 598 If the value is perInterface, then the MEG in the LSR 599 supports perInterface MEPs/MIPs, i.e., two MEPs/MIPs in 600 an LSR." 601 REFERENCE 602 "RFC 6371, Operations, Administration, and Maintenance 603 Framework for MPLS-Based Transport Networks, 604 September 2011." 605 DEFVAL { perNode } 606 ::= { mplsOamIdMegEntry 8 } 608 mplsOamIdMegPathFlow OBJECT-TYPE 609 SYNTAX INTEGER { 610 unidirectionalPointToPoint (1), 611 coRoutedBidirectionalPointToPoint (2), 612 associatedBidirectionalPointToPoint (3), 613 unidirectionalPointToMultiPoint (4) 614 } 615 MAX-ACCESS read-create 616 STATUS current 617 DESCRIPTION 618 "Indicates the transport path flow for this MEG. 619 In case of a unidirectional point-to-point transport path, 620 a single unidirectional Maintenance Entity is defined to 621 monitor it. 622 In case of associated bidirectional point-to-point transport 623 paths, two independent unidirectional Maintenance Entities are 624 defined to independently monitor each direction. 625 In case of co-routed bidirectional point-to-point transport 626 paths, a single bidirectional Maintenance Entity is defined to 627 monitor both directions congruently. 628 In case of unidirectional point-to-multipoint transport paths, 629 a single unidirectional Maintenance Entity for each leaf is 630 defined to monitor the transport path from the root to 631 that leaf." 632 REFERENCE 633 "RFC 6371, Operations, Administration, and Maintenance 634 Framework for MPLS-Based Transport Networks, 635 September 2011." 636 DEFVAL { coRoutedBidirectionalPointToPoint } 637 ::= { mplsOamIdMegEntry 9 } 639 mplsOamIdMegOperStatus OBJECT-TYPE 640 SYNTAX INTEGER { 641 up (1), 642 down (2) 643 } 644 MAX-ACCESS read-only 645 STATUS current 646 DESCRIPTION 647 "This object specifies the operational status of the 648 Maintenance Entity Group (MEG). This object is used to 649 send the notification to the SNMP manager about the MEG. 651 The value up (1) indicates that the MEG and its monitored 652 path are operationally up. The value down (2) indicates 653 that the MEG is operationally down. 655 When the value of mplsOamIdMegOperStatus is up (1), all 656 the bits of mplsOamIdMegSubOperStatus must be cleared. 657 When the value of mplsOamIdMegOperStatus is down (2), 658 at least one bit of mplsOamIdMegSubOperStatus must be 659 set." 660 ::= { mplsOamIdMegEntry 10 } 662 mplsOamIdMegSubOperStatus OBJECT-TYPE 663 SYNTAX BITS { 664 megDown (0), 665 meDown (1), 666 oamAppDown (2), 667 pathDown (3) 668 } 669 MAX-ACCESS read-only 670 STATUS current 671 DESCRIPTION 672 "This object specifies the reason why the MEG operational 673 status as mentioned by the object mplsOamIdMegOperStatus 674 is down. This object is used to send the notification to 675 the SNMP manager about the MEG. 677 The bit 0 (megDown) indicates the MEG is down. 678 The bit 1 (meDown) indicates the ME table is 679 down. 680 The bit 2 (oamAppDown) indicates that the 681 OAM application has notified that the entity (LSP or PW) 682 monitored by this MEG is down. Currently, BFD is the 683 only supported OAM application. 684 The bit 3 (pathDown) indicates that the underlying 685 LSP or PW is down." 686 ::= { mplsOamIdMegEntry 11 } 688 mplsOamIdMegRowStatus OBJECT-TYPE 689 SYNTAX RowStatus 690 MAX-ACCESS read-create 691 STATUS current 692 DESCRIPTION 694 "This variable is used to create, modify, and/or delete 695 a row in this table. When a row in this table is in 696 active (1) state, no objects in that row can be modified 697 by the agent except mplsOamIdMegRowStatus." 698 ::= { mplsOamIdMegEntry 12 } 700 mplsOamIdMegStorageType OBJECT-TYPE 701 SYNTAX StorageType 702 MAX-ACCESS read-create 703 STATUS current 704 DESCRIPTION 705 "This variable indicates the storage type for this 706 object. 707 Conceptual rows having the value 'permanent' 708 need not allow write-access to any columnar 709 objects in the row." 710 DEFVAL { volatile } 711 ::= { mplsOamIdMegEntry 13 } 713 -- End of MPLS Transport Profile MEG table 715 -- Start of MPLS Transport Profile ME table 717 mplsOamIdMeIndexNext OBJECT-TYPE 718 SYNTAX IndexIntegerNextFree (0..4294967295) 719 MAX-ACCESS read-only 720 STATUS current 721 DESCRIPTION 722 "This object contains an unused value for 723 mplsOamIdMeIndex, or a zero to indicate 724 that none exist. Negative values are not allowed, 725 as they do not correspond to valid values of 726 mplsOamIdMeIndex." 727 ::= { mplsOamIdObjects 3 } 729 mplsOamIdMeMpIndexNext OBJECT-TYPE 730 SYNTAX IndexIntegerNextFree (0..4294967295) 731 MAX-ACCESS read-only 732 STATUS current 733 DESCRIPTION 734 "This object contains an unused value for 735 mplsOamIdMeMpIndex, or a zero to indicate 736 that none exist. Negative values are not allowed, 737 as they do not correspond to valid values of 738 mplsOamIdMeMpIndex." 739 ::= { mplsOamIdObjects 4 } 741 mplsOamIdMeTable OBJECT-TYPE 742 SYNTAX SEQUENCE OF MplsOamIdMeEntry 743 MAX-ACCESS not-accessible 744 STATUS current 745 DESCRIPTION 746 "This table contains MPLS-TP maintenance entity 747 information. 749 ME is some portion of a transport path that requires 750 management bounded by two points (called MEPs), and the 751 relationship between those points to which maintenance 752 and monitoring operations apply. 754 This table is generic enough to handle MEPs and MIPs 755 information within a MEG." 756 ::= { mplsOamIdObjects 5 } 758 mplsOamIdMeEntry OBJECT-TYPE 759 SYNTAX MplsOamIdMeEntry 760 MAX-ACCESS not-accessible STATUS current 761 DESCRIPTION 762 "An entry in this table represents MPLS-TP maintenance 763 entity. This entry represents the ME if the source and 764 sink MEPs are defined. 766 A ME is a point-to-point entity. One ME has two such MEPs. 767 A MEG is a group of one or more MEs. One MEG can have 768 two or more MEPs. 770 For point-to-point LSP, one MEG has one ME and this ME 771 is associated two MEPs (source and sink MEPs) within 772 a MEG. Each mplsOamIdMeIndex value denotes the ME within 773 a MEG. 775 In case of unidirectional point-to-point transport paths, 776 a single unidirectional Maintenance Entity is defined to 777 monitor it and mplsOamIdMeServicePointer points to 778 unidirectional point-to-point path. 780 In case of associated bidirectional point-to-point 781 transport paths, two independent unidirectional 782 Maintenance Entities are defined to independently monitor 783 each direction and each mplsOamIdMeServicePointer MIB 784 object points to unique unidirectional transport path. 785 This has implications for transactions that terminate at 786 or query a MIP, as a return path from MIP to source MEP 787 does not necessarily exist within the MEG. 789 In case of co-routed bidirectional point-to-point 790 transport paths, a single bidirectional Maintenance Entity 791 is defined to monitor both directions congruently and 792 mplsOamIdMeServicePointer MIB object points to co-routed 793 bidirectional point-to-point transport path. 795 In case of unidirectional point-to-multipoint transport 796 paths, a single unidirectional Maintenance entity for each 797 leaf is defined to monitor the transport path from the 798 root to that leaf and each leaf has different transport 799 path information in mplsOamIdMeServicePointer MIB object. 800 Note that the MplsOamIdMeEntry should be created manually 801 once the MEG is configured for OAM operations." 802 INDEX { mplsOamIdMegIndex, 803 mplsOamIdMeIndex, 804 mplsOamIdMeMpIndex 805 } 806 ::= { mplsOamIdMeTable 1 } 808 MplsOamIdMeEntry ::= SEQUENCE { 809 mplsOamIdMeIndex Unsigned32, 810 mplsOamIdMeMpIndex Unsigned32, 811 mplsOamIdMeName SnmpAdminString, 812 mplsOamIdMeMpIfIndex InterfaceIndexOrZero, 813 mplsOamIdMeSourceMepIndex Unsigned32, 814 mplsOamIdMeSinkMepIndex Unsigned32, 815 mplsOamIdMeMpType INTEGER, 816 mplsOamIdMeMepDirection INTEGER, 817 mplsOamIdMeServicePointer RowPointer, 818 mplsOamIdMeRowStatus RowStatus, 819 mplsOamIdMeStorageType StorageType 820 } 822 mplsOamIdMeIndex OBJECT-TYPE 823 SYNTAX Unsigned32 (1..4294967295) 824 MAX-ACCESS not-accessible 825 STATUS current 826 DESCRIPTION 827 "Uniquely identifies a maintenance entity index within 828 a MEG. Managers should obtain new values for row 829 creation in this table by reading 830 mplsOamIdMeIndexNext." 831 ::= { mplsOamIdMeEntry 1 } 833 mplsOamIdMeMpIndex OBJECT-TYPE 835 SYNTAX Unsigned32 (1..4294967295) 836 MAX-ACCESS not-accessible 837 STATUS current 838 DESCRIPTION 839 "Indicates the maintenance point index, used to create 840 multiple MEPs in a node of single ME. The value of this 841 object can be MEP index or MIP index. Managers should 842 obtain new values for row creation in this table by reading 843 mplsOamIdMeMpIndexNext." 844 ::= { mplsOamIdMeEntry 2 } 846 mplsOamIdMeName OBJECT-TYPE 847 SYNTAX SnmpAdminString (SIZE(1..48)) 848 MAX-ACCESS read-create 849 STATUS current 850 DESCRIPTION 851 "This object denotes the ME name, each 852 Maintenance Entity has unique name within MEG." 853 ::= { mplsOamIdMeEntry 3 } 855 mplsOamIdMeMpIfIndex OBJECT-TYPE 856 SYNTAX InterfaceIndexOrZero 857 MAX-ACCESS read-create 858 STATUS current 859 DESCRIPTION 860 "Indicates the maintenance point interface. 861 If the mplsOamIdMegMpLocation object value 862 is perNode (1), the MP interface index should point 863 to incoming interface or outgoing interface or 864 zero (indicates the MP OAM packets are initiated 865 from forwarding engine). 867 If the mplsOamIdMegMpLocation object value is 868 perInterface (2), the MP interface index should point to 869 incoming interface or outgoing interface." 870 REFERENCE 871 "1. RFC 6371, Operations, Administration, and Maintenance 872 Framework for MPLS-Based Transport Networks, 873 September 2011. 874 2. RFC 2863 - The Interfaces Group MIB, McCloghrie, K., 875 and F. Kastenholtz, June 2000." 876 DEFVAL { 0 } 877 ::= { mplsOamIdMeEntry 4 } 879 mplsOamIdMeSourceMepIndex OBJECT-TYPE 880 SYNTAX Unsigned32 881 MAX-ACCESS read-create 882 STATUS current 883 DESCRIPTION 884 "Indicates the source MEP Index of the ME. This object 885 should be configured if mplsOamIdMegOperatorType object 886 in the mplsOamIdMegEntry is configured as iccBased (2). 887 If the MEG is configured for IP-based operator, 888 the value of this object should be set zero and the MEP 889 ID will be automatically derived from the service 890 Identifiers(MPLS-TP LSP/PW Identifier)." 891 DEFVAL { 0 } 892 ::= { mplsOamIdMeEntry 5 } 894 mplsOamIdMeSinkMepIndex OBJECT-TYPE 895 SYNTAX Unsigned32 896 MAX-ACCESS read-create 897 STATUS current 898 DESCRIPTION 899 "Indicates the sink MEP Index of the ME. This object 900 should be configured if mplsOamIdMegOperatorType object 901 in the mplsOamIdMegEntry is configured as iccBased (2). 902 If the MEG is configured for IP-based operator, 903 the value of this object should be set to zero and the MEP 904 ID will be automatically derived from the service 905 Identifiers (MPLS-TP LSP/PW Identifier)." 906 DEFVAL { 0 } 907 ::= { mplsOamIdMeEntry 6 } 909 mplsOamIdMeMpType OBJECT-TYPE 910 SYNTAX INTEGER { 911 mep (1), 912 mip (2) 913 } 914 MAX-ACCESS read-create 915 STATUS current 916 DESCRIPTION 917 "Indicates the maintenance point type within the MEG. 919 The object should have the value mep (1), only in the 920 Ingress or Egress nodes of the transport path. 922 The object can have the value mip (2), in 923 the Intermediate nodes and possibly in the Egress 924 nodes of the transport path." 925 DEFVAL { mep } 926 ::= { mplsOamIdMeEntry 7 } 928 mplsOamIdMeMepDirection OBJECT-TYPE 929 SYNTAX INTEGER { 930 up (1), 931 down (2), 932 notApplicable (3) 933 } 934 MAX-ACCESS read-create 935 STATUS current 936 DESCRIPTION 937 "Indicates the direction of the MEP. This object 938 should be configured if mplsOamIdMeMpType is 939 configured as mep (1) else notApplicable (3) is set." 940 DEFVAL { down } 941 ::= { mplsOamIdMeEntry 8 } 943 mplsOamIdMeServicePointer OBJECT-TYPE 945 SYNTAX RowPointer 946 MAX-ACCESS read-create 947 STATUS current 948 DESCRIPTION 949 "This variable represents a pointer to the MPLS-TP 950 transport path. This value MUST point at an entry in the 951 mplsTunnelEntry if mplsOamIdMegServicePointerType 952 is configured as tunnel (1) or lsp (2) or section (4) or 953 at an entry in the pwEntry if 954 mplsOamIdMegServicePointerType is configured 955 as pseudowire (3). 957 Note: This service pointer object is placed in the ME table 958 instead of the MEG table since it will be useful in case of 959 point-to-multipoint, where each ME will point to different 960 branches of a P2MP tree." 961 ::= { mplsOamIdMeEntry 9 } 963 mplsOamIdMeRowStatus OBJECT-TYPE 964 SYNTAX RowStatus 965 MAX-ACCESS read-create 966 STATUS current 967 DESCRIPTION 968 "This variable is used to create, modify, and/or 969 delete a row in this table. When a row in this 970 table is in active (1) state, no objects in that row 971 can be modified by the agent except 972 mplsOamIdMeRowStatus." 973 ::= { mplsOamIdMeEntry 10 } 975 mplsOamIdMeStorageType OBJECT-TYPE 976 SYNTAX StorageType 977 MAX-ACCESS read-create 978 STATUS current 979 DESCRIPTION 980 "This variable indicates the storage type for this 981 object. 982 Conceptual rows having the value 'permanent' 983 need not allow write-access to any columnar 984 objects in the row." 985 DEFVAL { volatile } 986 ::= { mplsOamIdMeEntry 11 } 988 -- End of MPLS Transport Profile ME table 990 -- End of MPLS-TP OAM Tables 992 -- Notification Definitions of MPLS-TP identifiers 994 mplsOamIdDefectCondition NOTIFICATION-TYPE 995 OBJECTS { 996 mplsOamIdMegName, 997 mplsOamIdMeName, 998 mplsOamIdMegOperStatus, 999 mplsOamIdMegSubOperStatus 1000 } 1001 STATUS current 1002 DESCRIPTION 1003 "This notification is sent whenever the operational 1004 status of MEG is changed." 1005 ::= { mplsOamIdNotifications 1 } 1007 -- End of Notifications. 1009 -- Module Compliance. 1011 mplsOamIdCompliances 1012 OBJECT IDENTIFIER ::= { mplsOamIdConformance 1 } 1014 mplsOamIdGroups 1015 OBJECT IDENTIFIER ::= { mplsOamIdConformance 2 } 1017 -- Compliance requirement for fully compliant implementations. 1019 mplsOamIdModuleFullCompliance MODULE-COMPLIANCE 1020 STATUS current 1021 DESCRIPTION "Compliance statement for agents that provide full 1022 support for MPLS-TP-OAM-STD-MIB. Such devices can 1023 then be monitored and also be configured using 1024 this MIB module." 1026 MODULE IF-MIB -- The Interfaces Group MIB, RFC 2863. 1027 MANDATORY-GROUPS { 1028 ifGeneralInformationGroup, 1029 ifCounterDiscontinuityGroup 1030 } 1032 MODULE -- This module. 1033 MANDATORY-GROUPS { 1034 mplsOamIdMegGroup, 1035 mplsOamIdMeGroup 1036 } 1038 GROUP mplsOamIdNotificationObjectsGroup 1039 DESCRIPTION "This group is only mandatory for those 1040 implementations which can efficiently implement 1041 the notifications contained in this group." 1043 GROUP mplsOamIdNotificationGroup 1044 DESCRIPTION "This group is only mandatory for those 1045 implementations which can efficiently implement 1046 the notifications contained in this group." 1048 ::= { mplsOamIdCompliances 1 } 1050 -- Compliance requirement for read-only implementations. 1052 mplsOamIdModuleReadOnlyCompliance MODULE-COMPLIANCE 1053 STATUS current 1054 DESCRIPTION 1055 "Compliance statement for agents that only provide 1056 read-only support for the MPLS-TP-OAM-STD-MIB module." 1058 MODULE -- this module 1060 MANDATORY-GROUPS { 1061 mplsOamIdMegGroup, 1062 mplsOamIdMeGroup 1063 } 1065 GROUP mplsOamIdNotificationObjectsGroup 1066 DESCRIPTION "This group is only mandatory for those 1067 implementations which can efficiently implement 1068 the notifications contained in this group." 1070 GROUP mplsOamIdNotificationGroup 1071 DESCRIPTION "This group is only mandatory for those 1072 implementations which can efficiently implement 1073 the notifications contained in this group." 1075 -- mplsOamIdMegTable 1077 OBJECT mplsOamIdMegName 1078 MIN-ACCESS read-only 1079 DESCRIPTION 1080 "Write access is not required." 1082 OBJECT mplsOamIdMegOperatorType 1083 MIN-ACCESS read-only 1084 DESCRIPTION 1085 "Write access is not required." 1087 OBJECT mplsOamIdMegIdCc 1088 MIN-ACCESS read-only 1089 DESCRIPTION 1090 "Write access is not required." 1092 OBJECT mplsOamIdMegIdIcc 1093 MIN-ACCESS read-only 1094 DESCRIPTION 1095 "Write access is not required." 1097 OBJECT mplsOamIdMegIdUmc 1098 MIN-ACCESS read-only 1099 DESCRIPTION 1100 "Write access is not required." 1102 OBJECT mplsOamIdMegServicePointerType 1103 MIN-ACCESS read-only 1104 DESCRIPTION 1105 "Write access is not required." 1107 OBJECT mplsOamIdMegMpLocation 1108 MIN-ACCESS read-only 1109 DESCRIPTION 1110 "Write access is not required." 1112 OBJECT mplsOamIdMegPathFlow 1113 MIN-ACCESS read-only 1114 DESCRIPTION 1115 "Write access is not required." 1117 OBJECT mplsOamIdMegRowStatus 1118 SYNTAX RowStatus { active(1) } 1119 MIN-ACCESS read-only 1120 DESCRIPTION 1121 "Write access is not required." 1123 OBJECT mplsOamIdMegStorageType 1124 MIN-ACCESS read-only 1125 DESCRIPTION 1126 "Write access is not required." 1128 -- mplsOamIdMeTable 1130 OBJECT mplsOamIdMeName 1131 MIN-ACCESS read-only 1132 DESCRIPTION 1133 "Write access is not required." 1135 OBJECT mplsOamIdMeMpIfIndex 1136 MIN-ACCESS read-only 1137 DESCRIPTION 1138 "Write access is not required." 1140 OBJECT mplsOamIdMeSourceMepIndex 1141 MIN-ACCESS read-only 1142 DESCRIPTION 1143 "Write access is not required." 1145 OBJECT mplsOamIdMeSinkMepIndex 1146 MIN-ACCESS read-only 1147 DESCRIPTION 1148 "Write access is not required." 1150 OBJECT mplsOamIdMeMpType 1151 MIN-ACCESS read-only 1152 DESCRIPTION 1153 "Write access is not required." 1155 OBJECT mplsOamIdMeMepDirection 1156 MIN-ACCESS read-only 1157 DESCRIPTION 1158 "Write access is not required." 1160 OBJECT mplsOamIdMeServicePointer 1161 MIN-ACCESS read-only 1162 DESCRIPTION 1163 "Write access is not required." 1165 OBJECT mplsOamIdMeRowStatus 1166 SYNTAX RowStatus { active(1) } 1167 MIN-ACCESS read-only 1168 DESCRIPTION 1169 "Write access is not required." 1171 OBJECT mplsOamIdMeStorageType 1172 MIN-ACCESS read-only 1173 DESCRIPTION 1174 "Write access is not required." 1176 ::= { mplsOamIdCompliances 2 } 1178 -- Units of conformance. 1180 mplsOamIdMegGroup OBJECT-GROUP 1181 OBJECTS { 1182 mplsOamIdMegIndexNext, 1183 mplsOamIdMegName, 1184 mplsOamIdMegOperatorType, 1185 mplsOamIdMegIdCc, 1186 mplsOamIdMegIdIcc, 1187 mplsOamIdMegIdUmc, 1188 mplsOamIdMegServicePointerType, 1189 mplsOamIdMegMpLocation, 1190 mplsOamIdMegOperStatus, 1191 mplsOamIdMegSubOperStatus, 1192 mplsOamIdMegPathFlow, 1193 mplsOamIdMegRowStatus, 1194 mplsOamIdMegStorageType 1195 } 1197 STATUS current 1198 DESCRIPTION 1199 "Collection of objects needed for MPLS MEG information." 1200 ::= { mplsOamIdGroups 1 } 1202 mplsOamIdMeGroup OBJECT-GROUP 1203 OBJECTS { 1204 mplsOamIdMeIndexNext, 1205 mplsOamIdMeMpIndexNext, 1206 mplsOamIdMeName, 1207 mplsOamIdMeMpIfIndex, 1208 mplsOamIdMeSourceMepIndex, 1209 mplsOamIdMeSinkMepIndex, 1210 mplsOamIdMeMpType, 1211 mplsOamIdMeMepDirection, 1212 mplsOamIdMeServicePointer, 1213 mplsOamIdMeRowStatus, 1214 mplsOamIdMeStorageType 1215 } 1216 STATUS current 1217 DESCRIPTION 1218 "Collection of objects needed for MPLS ME information." 1219 ::= { mplsOamIdGroups 2 } 1221 mplsOamIdNotificationObjectsGroup OBJECT-GROUP 1222 OBJECTS { 1224 mplsOamIdMegOperStatus, 1226 mplsOamIdMegSubOperStatus 1227 } 1228 STATUS current 1229 DESCRIPTION 1230 "Collection of objects needed to implement notifications." 1231 ::= { mplsOamIdGroups 3 } 1233 mplsOamIdNotificationGroup NOTIFICATION-GROUP 1234 NOTIFICATIONS { 1235 mplsOamIdDefectCondition 1236 } 1237 STATUS current 1238 DESCRIPTION 1239 "Set of notifications implemented in this module." 1240 ::= { mplsOamIdGroups 4 } 1242 END 1244 8. Security Consideration 1246 This MIB relates to a system that will provide network connectivity 1247 and packet forwarding services. As such, improper manipulation of the 1248 objects represented by this MIB may result in denial of service to a 1249 large number of end-users. 1251 There are number of management objects defined in this MIB module 1252 with a MAX-ACCESS clause of read-create. Such objects may be 1253 considered sensitive or vulnerable in some network environments. 1254 The support for SET operations in a non-secure environment 1255 without proper protection opens devices to attack. 1257 Some of the readable objects in this MIB module (i.e., objects 1258 with a MAX-ACCESS other than not-accessible) may be considered 1259 sensitive or vulnerable in some network environments. 1260 It is thus important to control even GET and/or NOTIFY access 1261 to these objects and possibly to even encrypt the values of these 1262 objects when sending them over the network via SNMP. These are 1263 the tables and objects and their sensitivity/vulnerability: 1265 - mplsOamIdMegTable and mplsOamIdMeTable collectively show 1266 the MPLS OAM characteristics. If an Administrator does not want to 1267 reveal this information, then these tables should be considered 1268 sensitive/vulnerable. 1270 SNMP versions prior to SNMPv3 did not include adequate security. Even 1271 if the network itself is secure (for example by using IPsec), there 1272 is no control as to who on the secure network is allowed to access 1273 and GET/SET (read/change/create/delete) the objects in this MIB 1274 module. 1276 Implementations SHOULD provide the security features described by the 1277 SNMPv3 framework (see [RFC3410]), and implementations claiming 1278 compliance to the SNMPv3 standard MUST include full support for 1279 authentication and privacy via the User-based Security Model (USM) 1280 [RFC3414] with the AES cipher algorithm [RFC3826]. Implementations 1281 MAY also provide support for the Transport Security Model (TSM) 1282 [RFC5591] in combination with a secure transport such as SSH 1283 [RFC5592] or TLS/DTLS [RFC6353]. 1285 Further, deployment of SNMP versions prior to SNMPv3 is NOT 1286 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 1287 enable cryptographic security. It is then a customer/operator 1288 responsibility to ensure that the SNMP entity giving access to an 1289 instance of this MIB module is properly configured to give access to 1290 the objects only to those principals (users) that have legitimate 1291 rights to indeed GET or SET (change/create/delete) them. 1293 9. IANA Considerations 1295 IANA is requested to assign an OID for the MIB module from the "MIB 1296 Transmission Group - MPLS STD" sub-registry of the "Internet-standard 1297 MIB - Transmission Group" registry for the MPLS-TP OAM ID MIB module 1298 specified in this document. 1300 10. References 1302 10.1 Normative References 1304 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1305 Requirement Levels", BCP 14, RFC 2119, March 1997. 1307 [RFC2578] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 1308 "Structure of Management Information Version 2 (SMIv2)", 1309 STD 58, RFC 2578, April 1999. 1311 [RFC2579] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 1312 "Textual Conventions for SMIv2", STD 58, RFC 2579, April 1313 1999. 1315 [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 1316 "Conformance Statements for SMIv2", STD 58, RFC 2580, 1317 April 1999. 1319 [RFC2863] McCloghrie, K. and F. Kastenholtz, "The Interfaces Group 1320 MIB ", RFC 2863, June 2000 1322 [RFC3031] Rosen, E., Viswanathan, A., and R. Callon, 1323 "Multiprotocol Label Switching Architecture", RFC 3031, 1324 January 2001. 1326 [RFC3289] Baker, F., Chan, K., and A. Smith, "Management 1327 Information Base for the Differentiated Services 1328 Architecture", RFC 3289, May 2002. 1330 [RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An 1331 Architecture for Describing Simple Network Management 1332 Protocol (SNMP) Management Frameworks", STD 62, RFC 1333 3411, December 2002. 1335 [RFC5601] Zelig, D., Ed., and T. Nadeau, Ed., "Pseudowire (PW) 1336 Management Information Base (MIB)", RFC 5601, July 2009. 1338 10.2 Informative References 1340 [RFC3410] J. Case, R. Mundy, D. pertain, B.Stewart, "Introduction 1341 and Applicability Statement for Internet Standard 1342 Management Framework", RFC 3410, December 2002. 1344 [RFC3414] Blumenthal, U. and B. Wijnen, "User-based Security 1345 Model(USM) for version 3 of the Simple Network 1346 Management Protocol (SNMPv3)", STD 62, RFC 3414, 1347 December 2002. 1349 [RFC3811] Nadeau, T., Ed., and J. Cucchiara, Ed., "Definitions of 1350 Textual Conventions (TCs) for Multiprotocol Label 1351 Switching (MPLS) Management", RFC 3811, June 2004. 1353 [RFC3812] Srinivasan, C., Viswanathan, A., and T. Nadeau, 1354 "Multiprotocol Label Switching (MPLS) Traffic 1355 Engineering (TE) Management Information Base (MIB)", RFC 1356 3812, June 2004. 1358 [RFC3813] Srinivasan, C., Viswanathan, A., and T. Nadeau, 1359 "Multiprotocol Label Switching (MPLS) Label Switching 1360 (LSR) Router Management Information Base (MIB)", RFC 1361 3813, June 2004. 1363 [RFC3826] Blumenthal, U., F. Maino and K. McCloghrie, "The 1364 Advanced Encryption Standard (AES) Cipher Algorithm in 1365 the SNMP User-based Security Model", RFC 3826, June 1366 2004. 1368 [RFC5591] Harrington, D. and W. Hardaker, "Transport Security 1369 Model for the Simple Network Management Protocol 1370 (SNMP)",RFC 5591, June 2009. 1372 [RFC5592] Harrington, D., Salowey, J., and W. Hardaker, "Secure 1373 Shell Transport Model for the Simple Network Management 1374 Protocol (SNMP)", RFC 5592, June 2009. 1376 [RFC5654] Niven-Jenkins, B., Ed., Brungard, D., Ed., Betts, M., 1377 Ed., Sprecher, N., and S. Ueno, "Requirements of an MPLS 1378 Transport Profile", RFC 5654, September 2009. 1380 [RFC6353] Hardaker, W., "Transport Layer Security (TLS) Transport 1381 Model for the Simple Network Management Protocol 1382 (SNMP)", STD 78, RFC 6353, July 2011. 1384 [RFC6370] Bocci, M., Swallow, G., and E. Gray, "MPLS-TP 1385 Identifiers", RFC 6370, September 2011. 1387 [RFC6371] Busi, I., Niven-Jenkins, B., and D. Allan, "MPLS-TP OAM 1388 Framework and Overview", RFC 6371, September 2011. 1390 [RFC6923] R. Winter, Ed, E. Gray, Ed., H. van Helvoort, and M. 1391 Betts, "MPLS-TP Identifiers Following ITU-T 1392 Conventions", RFC 6923, May 2013. 1394 [RFC5860] M. Vigoureux, Ed, D. Ward, Ed, M. Betts, Ed, "OAM in MPLS 1395 Transport Networks", RFC 5860, May 2010. 1397 11. Acknowledgments 1399 We wish to thank Muly Ilan, Adrian Farrel, Joan Cucchiara, 1400 Weiying Cheng, Mach Chen, Peter Yee, and Tina TSOU for their 1401 valuable comments on this document. 1403 12. Authors' Addresses 1405 Venkatesan Mahalingam 1406 Dell, Inc. 1407 5450 Great America Parkway, 1408 Santa Clara, CA 95054, USA 1409 Email: venkat.mahalingams@gmail.com 1411 Sam Aldrin 1412 Google, Inc. 1413 1600 Amphitheatre Parkway 1414 Mountain View, CA 94043 1415 USA 1416 Email: aldrin.ietf@gmail.com 1418 Thomas D. Nadeau 1419 Brocade 1420 Email: tnadeau@lucidvision.com 1421 Kannan KV Sampath 1422 Redeem, 1423 India 1424 Email: kannankvs@gmail.com 1426 Ping Pan 1427 Infinera 1428 Email: ppan@infinera.com 1430 Sami Boutros 1431 Cisco Systems, Inc. 1432 3750 Cisco Way 1433 San Jose, California 95134 1434 USA 1435 Email: sboutros@cisco.com