idnits 2.17.1 draft-ietf-mpls-tp-oam-id-mib-01.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 (October 08, 2012) is 4212 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) == Outdated reference: A later version (-08) exists of draft-ietf-mpls-tp-itu-t-identifiers-03 Summary: 0 errors (**), 0 flaws (~~), 2 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group 3 INTERNET-DRAFT Sam Aldrin 4 Intended Status: Standards Track Huawei Technologies 5 Expires: April 11, 2013 M.Venkatesan 6 Dell Inc. 7 Kannan KV Sampath 8 Redeem 9 Thomas D. Nadeau 10 Juniper Networks 11 Sami Boutros 12 Cisco Systems 13 Ping Pan 14 Infinera 16 October 08, 2012 18 MPLS-TP Operations, Administration, and Management (OAM) Identifiers 19 Management Information Base (MIB) 20 draft-ietf-mpls-tp-oam-id-mib-01 22 Abstract 24 This memo defines a portion of the Management Information Base (MIB) 25 for use with network management protocols in the Internet community. 26 In particular, it describes Operations, Administration, and 27 Management (OAM) identifiers related managed objects for 28 Multiprotocol Label Switching (MPLS) based Transport Profile (TP). 30 Status of this Memo 32 This Internet-Draft is submitted to IETF in full conformance with the 33 provisions of BCP 78 and BCP 79. 35 Internet-Drafts are working documents of the Internet Engineering 36 Task Force (IETF), its areas, and its working groups. Note that 37 other groups may also distribute working documents as Internet- 38 Drafts. 40 Internet-Drafts are draft documents valid for a maximum of six months 41 and may be updated, replaced, or obsoleted by other documents at any 42 time. It is inappropriate to use Internet-Drafts as reference 43 material or to cite them other than as "work in progress." 45 The list of current Internet-Drafts can be accessed at 46 http://www.ietf.org/ietf/1id-abstracts.txt. 48 The list of Internet-Draft Shadow Directories can be accessed at 49 http://www.ietf.org/shadow.html. 51 This Internet-Draft will expire on April 11, 2013. 53 Copyright and License Notice 55 Copyright (c) 2012 IETF Trust and the persons identified as the 56 document authors. All rights reserved. 58 This document is subject to BCP 78 and the IETF Trust's Legal 59 Provisions Relating to IETF Documents 60 (http://trustee.ietf.org/license-info) in effect on the date of 61 publication of this document. Please review these documents 62 carefully, as they describe your rights and restrictions with respect 63 to this document. Code Components extracted from this document must 64 include Simplified BSD License text as described in Section 4.e of 65 the Trust Legal Provisions and are provided without warranty as 66 described in the Simplified BSD License. 68 Table of Contents 70 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 71 2. The Internet-Standard Management Framework . . . . . . . . . . 3 72 3. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 73 3.1 Conventions used in this document . . . . . . . . . . . . . 3 74 3.2 Terminology . . . . . . . . . . . . . . . . . . . . . . . . 3 75 3.3 Acronyms . . . . . . . . . . . . . . . . . . . . . . . . . . 3 76 4. Feature List . . . . . . . . . . . . . . . . . . . . . . . . . 4 77 5. Brief description of MIB Objects . . . . . . . . . . . . . . . 4 78 5.1. mplsOamIdMegTable . . . . . . . . . . . . . . . . . . . . 4 79 5.2. mplsOamIdMeTable . . . . . . . . . . . . . . . . . . . . . 4 80 6. Example of MPLS OAM identifier configuration for MPLS tunnel . 5 81 7. MPLS OAM Identifiers MIB definitions . . . . . . . . . . . . . 6 82 8. Security Consideration . . . . . . . . . . . . . . . . . . . . 23 83 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 24 84 10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 24 85 10.1 Normative References . . . . . . . . . . . . . . . . . . . 24 86 10.2 Informative References . . . . . . . . . . . . . . . . . . 25 87 11. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 25 88 12. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 26 90 1 Introduction 92 This memo defines a portion of the Management Information Base (MIB) 93 for use with network management protocols in the Internet community. 94 In particular, it describes managed objects for modeling a 95 Multiprotocol Label Switching (MPLS) [RFC3031] based transport 96 profile. 98 This MIB module should be used for performing the OAM operations for 99 MPLS LSPs, Pseudowires and Sections. 101 2. The Internet-Standard Management Framework 103 For a detailed overview of the documents that describe the current 104 Internet-Standard Management Framework, please refer to section 7 of 105 RFC3410 [RFC3410]. 107 Managed objects are accessed via a virtual information store, termed 108 the Management Information Base or MIB. MIB objects are generally 109 accessed through the Simple Network Management Protocol (SNMP). 110 Objects in the MIB are defined using the mechanisms defined in the 111 Structure of Management Information (SMI). This memo specifies a MIB 112 module that is compliant to the SMIv2, which is described in STD 58, 113 RFC2578, STD 58, RFC2579 and STD58, RFC2580. 115 3. Overview 117 3.1 Conventions used in this document 119 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 120 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 121 "OPTIONAL" in this document are to be interpreted as described in 122 RFC-2119 [RFC2119]. 124 3.2 Terminology 126 This document uses terminology from the MPLS architecture document 127 [RFC3031], MPLS Traffic Engineering Management information [RFC3812], 128 MPLS Label Switch Router MIB [RFC3813], MPLS-TP OAM Framework 129 document [RFC6371] and MPLS-TP Identifiers document [RFC6370]. 131 3.3 Acronyms 133 ICC: ITU Carrier Code 134 IP: Internet Protocol 136 LSP: Label Switching Path 137 LSR: Label Switching Router 138 MIB: Management Information Base 139 ME: Maintenance Entity 140 MEG: Maintenance Entity Group 141 MEP: Maintenance Entity Group End Point 142 MIP: Maintenance Intermediate Point 143 MPLS: Multi-Protocol Label Switching 144 MPLS-TP: MPLS Transport Profile 145 PW: Pseudowire 146 TE: Traffic Engineering 147 TP: Transport Profile 149 4. Feature List 151 The MPLS transport profile OAM identifiers MIB module is designed 152 to satisfy the following requirements and constraints: 154 - The MIB module supports configuration of OAM identifiers for 155 point-to-point, co-routed bidirectional, associated 156 bidirectional MPLS tunnels and MPLS Pseudowires. 158 5. Brief description of MIB Objects 160 The objects described in this section support the functionality 161 described in documents [RFC5654] and [RFC6370]. The tables support 162 both IP compatible and ICC based OAM identifiers configurations 163 for MPLS Tunnels and Pseudowires. 165 5.1. mplsOamIdMegTable 167 The mplsOamIdMegTable is used to manage one or more 168 Maintenance Entities (MEs) that belongs to the same transport path. 170 When a new entry is created with mplsOamIdMegOperatorType set to 171 ipCompatible (1), then as per [RFC6370] (MEG_ID for LSP 172 is LSP_ID and MEG_ID for PW is PW_Path_ID), MEP_ID can be 173 automatically formed. 175 For ICC based transport path, the user is expected to configure 176 the ICC identifier explicitly in this table for MPLS tunnel 177 and pseudowires. 179 5.2. mplsOamIdMeTable 181 The mplsOamIdMeTable defines a relationship between two points 182 (source and sink) of a transport path to which maintenance and 183 monitoring operations apply. The two points that define 184 a maintenance entity are called Maintenance Entity Group 185 End Points (MEPs). 187 In between MEPs, there are zero or more intermediate points, 188 called Maintenance Entity Group Intermediate Points (MIPs). 189 MEPs and MIPs are associated with the MEG and can be shared by 190 more than one ME in a MEG. 192 6. Example of MPLS OAM identifier configuration for MPLS tunnel 194 In this section, we provide an example of the OAM identifier 195 configuration for MPLS co-routed bidirectional tunnel. 197 This example provides usage of a MEG and ME tables for management and 198 monitoring operations of MPLS tunnel. 200 This example considers the OAM identifiers configuration on a 201 head-end LSR to manage and monitor a MPLS tunnel. 202 Only relevant objects which are applicable for IP based OAM 203 identifiers of co-routed MPLS tunnel are illustrated here. 205 In mplsOamIdMegTable: 207 { 208 -- MEG index (Index to the table) 209 mplsOamIdMegIndex = 1, 210 mplsOamIdMegName = "MEG1", 211 mplsOamIdMegOperatorType = ipCompatible (1), 212 mplsOamIdMegServiceType = lsp (1), 213 mplsOamIdMegMpLocation = perNode(1), 214 -- Mandatory parameters needed to activate the row go here 215 mplsOamIdMegRowStatus = createAndGo (4), 216 mplsOamIdMegPathFlow 217 = coRoutedBidirectionalPointToPoint (2) 218 } 220 This will create an entry in the mplsOamIdMegTable to manage and 221 monitor the MPLS tunnel. 223 The following ME table is used to associate the path information 224 to a MEG. 226 In mplsOamIdMeTable: 228 { 229 -- ME index (Index to the table) 230 mplsOamIdMeIndex = 1, 232 -- MP index (Index to the table) 233 mplsOamIdMeMpIndex = 1, 234 mplsOamIdMeName = "ME1", 235 mplsOamIdMeMpIfIndex = 0, 236 -- Source MEP id is derived from the IP compatible MPLS tunnel 237 mplsOamIdMeSourceMepIndex = 0, 238 -- Source MEP id is derived from the IP compatible MPLS tunnel 239 mplsOamIdMeSinkMepIndex = 0, 240 mplsOamIdMeMpType = mep (1), 241 mplsOamIdMeMepDirection = down (2), 242 mplsOamIdMeProactiveOamPhbTCValue = 0, 243 mplsOamIdMeOnDemandOamPhbTCValue = 0, 244 -- RowPointer MUST point to the first accessible column of an 245 -- MPLS tunnel 246 mplsOamIdMeServicePointer = mplsTunnelName.1.1.10.20, 247 -- Mandatory parameters needed to activate the row go here 248 mplsOamIdMeRowStatus = createAndGo (4) 249 } 251 7. MPLS OAM Identifiers MIB definitions 253 MPLS-OAM-ID-STD-MIB DEFINITIONS ::= BEGIN 255 IMPORTS 256 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, 257 Unsigned32, zeroDotZero 258 FROM SNMPv2-SMI -- [RFC2578] 259 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 260 FROM SNMPv2-CONF -- [RFC2580] 261 RowStatus, RowPointer, StorageType 262 FROM SNMPv2-TC -- [RFC2579] 263 SnmpAdminString 264 FROM SNMP-FRAMEWORK-MIB -- [RFC3411] 265 mplsStdMIB 266 FROM MPLS-TC-STD-MIB -- [RFC3811] 267 InterfaceIndexOrZero, ifGeneralInformationGroup, 268 ifCounterDiscontinuityGroup 269 FROM IF-MIB; -- [RFC2863] 271 mplsOamIdStdMIB MODULE-IDENTITY 272 LAST-UPDATED 273 "201210080000Z" -- October 08, 2012 274 ORGANIZATION 275 "Multiprotocol Label Switching (MPLS) Working Group" 276 CONTACT-INFO 277 " 278 Sam Aldrin 279 Huawei Technologies, co. 280 2330 Central Express Way, 282 Santa Clara, CA 95051, USA 283 Email: aldrin.ietf@gmail.com 285 Thomas D. Nadeau 286 Juniper Networks 287 10 Technology Park Drive, 288 Westford, MA 01886 289 Email: tnadeau@juniper.net 291 Venkatesan Mahalingam 292 Dell Inc. 293 350 Holger way, San Jose, CA, USA 294 Email: venkat.mahalingams@gmail.com 296 Kannan KV Sampath 297 Redeem, 298 India 299 Email: kannankvs@gmail.com 301 Ping Pan 302 Infinera 303 Email: ppan@infinera.com 305 Sami Boutros 306 Cisco Systems, Inc. 307 3750 Cisco Way 308 San Jose, California 95134 309 USA 310 Email: sboutros@cisco.com 312 " 313 DESCRIPTION 314 "Copyright (c) 2012 IETF Trust and the persons identified 315 as the document authors. All rights reserved. 317 This MIB module contains generic object definitions for 318 MPLS OAM maintenance identifiers in MPLS based transport 319 networks." 321 -- Revision history. 323 REVISION 324 "201210080000Z" -- October 08, 2012 326 DESCRIPTION 327 "MPLS OAM Identifiers mib objects for LSPs and 328 Pseudowires" 330 ::= { mplsStdMIB xxx } -- xxx to be replaced with correct value 332 -- Top level components of this MIB module. 334 -- notifications 335 mplsOamIdNotifications 336 OBJECT IDENTIFIER ::= { mplsOamIdStdMIB 0 } 337 -- tables, scalars 338 mplsOamIdObjects OBJECT IDENTIFIER ::= { mplsOamIdStdMIB 1 } 339 -- conformance 340 mplsOamIdConformance 341 OBJECT IDENTIFIER ::= { mplsOamIdStdMIB 2 } 343 -- Start of MPLS Transport Profile MEG table 345 mplsOamIdMegTable OBJECT-TYPE 346 SYNTAX SEQUENCE OF MplsOamIdMegEntry 347 MAX-ACCESS not-accessible 348 STATUS current 349 DESCRIPTION 350 "This table contains information about the Maintenance 351 Entity Groups (MEG). 353 MEG as mentioned in MPLS-TP OAM framework defines a set 354 of one or more maintenance entities (ME). 355 Maintenance Entities define a relationship between any 356 two points of a transport path in an OAM domain to which 357 maintenance and monitoring operations apply." 358 ::= { mplsOamIdObjects 1 } 360 mplsOamIdMegEntry OBJECT-TYPE 361 SYNTAX MplsOamIdMegEntry 362 MAX-ACCESS not-accessible 363 STATUS current 364 DESCRIPTION 365 "An entry in this table represents MPLS-TP MEG. 366 An entry can be created by a network administrator 367 or by an SNMP agent as instructed by an MPLS-TP OAM 368 Framework. 370 When a new entry is created with 371 mplsOamIdMegOperatorType set to ipCompatible (1), 372 then as per [RFC6370] (MEG_ID for LSP is LSP_ID and 373 MEG_ID for PW is PW_Path_ID), MEP_ID can be 374 automatically formed. 376 For co-routed bidirectional LSP, MEG_ID is 377 A1-{Global_ID::Node_ID::Tunnel_Num}::Z9-{Global_ID:: 378 Node_ID::Tunnel_Num}::LSP_Num. 380 For associated bidirectional LSP, MEG_ID is A1- 381 {Global_ID::Node_ID::Tunnel_Num::LSP_Num}:: Z9- 382 {Global_ID::Node_ID::Tunnel_Num::LSP_Num} 384 For LSP, MEP_ID is formed using, 385 Global_ID::Node_ID::Tunnel_Num::LSP_Num 387 For PW, MEG_ID is formed using AGI::A1- 388 {Global_ID::Node_ID::AC_ID}:: Z9- 389 {Global_ID::Node_ID::AC_ID}. 391 For PW, MEP_ID is formed using 392 AGI::Global_ID::Node_ID::AC_ID 394 MEP_ID is retrieved from the mplsOamIdMegServicePointer 395 object based on the mplsOamIdMegServiceType value. 396 ICC MEG_ID for LSP and PW is formed using the objects 397 mplsOamIdMegIdIcc and mplsOamIdMegIdUmc. 399 MEP_ID can be formed using MEG_ID::MEP_Index." 400 REFERENCE 401 "1. RFC 5860, Requirements for OAM in MPLS Transport 402 Networks, May 2010. 403 2. RFC 6371, Operations, Administration, and Maintenance 404 Framework for MPLS-Based Transport Networks, 405 September 2011. 406 3. RFC 6370, MPLS Transport Profile (MPLS-TP) Identifiers. 407 4. MPLS-TP Identifiers Following ITU-T Conventions 408 [TP-ITUIDS]." 409 INDEX { mplsOamIdMegIndex } 410 ::= { mplsOamIdMegTable 1 } 412 MplsOamIdMegEntry ::= SEQUENCE { 413 mplsOamIdMegIndex Unsigned32, 414 mplsOamIdMegName SnmpAdminString, 415 mplsOamIdMegOperatorType INTEGER, 416 mplsOamIdMegIdIcc SnmpAdminString, 417 mplsOamIdMegIdUmc SnmpAdminString, 418 mplsOamIdMegServiceType INTEGER, 419 mplsOamIdMegMpLocation INTEGER, 420 mplsOamIdMegRowStatus RowStatus, 421 mplsOamIdMegStorageType StorageType, 422 mplsOamIdMegPathFlow INTEGER 423 } 425 mplsOamIdMegIndex OBJECT-TYPE 426 SYNTAX Unsigned32 427 MAX-ACCESS not-accessible 428 STATUS current 429 DESCRIPTION 430 "Index for the conceptual row identifying a MEG within 432 this MEG table." 433 ::= { mplsOamIdMegEntry 1 } 435 mplsOamIdMegName OBJECT-TYPE 436 SYNTAX SnmpAdminString (SIZE(1..48)) 437 MAX-ACCESS read-create 438 STATUS current 439 DESCRIPTION 440 "Each Maintenance Entity Group has unique name amongst 441 all those used or available to a service provider or 442 operator. It facilitates easy identification of 443 administrative responsibility for each MEG." 444 ::= { mplsOamIdMegEntry 2 } 446 mplsOamIdMegOperatorType OBJECT-TYPE 447 SYNTAX INTEGER { 448 ipCompatible (1), 450 iccBased (2) 451 } 452 MAX-ACCESS read-create 453 STATUS current 454 DESCRIPTION 455 "Indicates the operator type for MEG. Conceptual rows 456 having 'iccBased' as operator type, should have valid 457 values for the objects mplsOamIdMegIdIcc and 458 mplsOamIdMegIdUmc while making the row status active." 459 REFERENCE 460 "1. RFC 6370, MPLS Transport Profile (MPLS-TP) 461 Identifiers. 462 2. MPLS-TP Identifiers Following ITU-T Conventions 463 [TP-ITUIDS]." 464 DEFVAL { ipCompatible } 465 ::= { mplsOamIdMegEntry 3 } 467 mplsOamIdMegIdIcc OBJECT-TYPE 468 SYNTAX SnmpAdminString (SIZE(1..6)) 469 MAX-ACCESS read-write 470 STATUS current 471 DESCRIPTION 472 "Unique code assigned to Network Operator or Service 473 Provider maintained by ITU-T. The ITU Carrier Code 474 used to form MEGID. 476 This object contains non-null ICC value if 477 the MplsOamIdMegOperatorType value is iccBased(2), 478 otherwise null ICC value should be assigned." 479 REFERENCE 481 "MPLS-TP Identifiers Following ITU-T Conventions 482 [TP-ITUIDS]." 483 DEFVAL {""} 484 ::= { mplsOamIdMegEntry 4 } 486 mplsOamIdMegIdUmc OBJECT-TYPE 487 SYNTAX SnmpAdminString (SIZE(1..7)) 488 MAX-ACCESS read-write 489 STATUS current 490 DESCRIPTION 491 "Unique code assigned by Network Operator or Service 492 Provider and is appended to mplsOamIdMegIdIcc to form 493 the MEGID. 494 This object contains non-null ICC value if 495 the MplsOamIdMegOperatorType value is iccBased(2), 496 otherwise null ICC value should be assigned." 497 REFERENCE 498 "MPLS-TP Identifiers Following ITU-T Conventions 499 [TP-ITUIDS]." 500 DEFVAL {""} 501 ::= { mplsOamIdMegEntry 5 } 503 mplsOamIdMegServiceType OBJECT-TYPE 505 SYNTAX INTEGER { 506 lsp (1), 507 pseudowire (2), 508 section (3) 509 } 510 MAX-ACCESS read-create 511 STATUS current 512 DESCRIPTION 513 "Indicates the service type for which the MEG is created. 515 If the service type indicates lsp, the service pointer 516 in mplsOamIdMeTable points to the TE tunnel table entry. 518 If the value is pseudowire service type, the service 519 pointer in mplsOamIdMeTable points to the pseudowire 520 table entry. 522 If the value is section service type, the service 523 pointer in mplsOamIdMeTable points to a section entry." 524 DEFVAL { lsp } 525 ::= { mplsOamIdMegEntry 6 } 527 mplsOamIdMegMpLocation OBJECT-TYPE 528 SYNTAX INTEGER { 530 perNode (1), 531 perInterface (2) 532 } 533 MAX-ACCESS read-create 534 STATUS current 535 DESCRIPTION 536 "Indicates the MP location type for this MEG. 538 If the value is perNode, then the MEG in the LSR supports 539 only perNode MEP/MIP, i.e., only one MEP/MIP in an LSR. 541 If the value is perInterface, then the MEG in the LSR 542 supports perInterface MEPs/MIPs, i.e., two MEPs/MIPs in 543 an LSR." 544 REFERENCE 545 "RFC 6371, Operations, Administration, and Maintenance 546 Framework for MPLS-Based Transport Networks, 547 September 2011." 548 DEFVAL { perNode } 549 ::= { mplsOamIdMegEntry 7 } 551 mplsOamIdMegRowStatus OBJECT-TYPE 552 SYNTAX RowStatus 553 MAX-ACCESS read-create 554 STATUS current 555 DESCRIPTION 557 "This variable is used to create, modify, and/or delete 558 a row in this table. When a row in this table is in 559 active(1) state, no objects in that row can be modified 560 by the agent except mplsOamIdMegRowStatus." 561 ::= { mplsOamIdMegEntry 8 } 563 mplsOamIdMegStorageType OBJECT-TYPE 564 SYNTAX StorageType 565 MAX-ACCESS read-create 566 STATUS current 567 DESCRIPTION 568 "This variable indicates the storage type for this 569 object. 570 Conceptual rows having the value 'permanent' 571 need not allow write-access to any columnar 572 objects in the row." 573 DEFVAL { volatile } 574 ::= { mplsOamIdMegEntry 9 } 576 mplsOamIdMegPathFlow OBJECT-TYPE 577 SYNTAX INTEGER { 578 unidirectionalPointToPoint (1), 579 coRoutedBidirectionalPointToPoint (2), 580 associatedBidirectionalPointToPoint (3), 581 unidirectionalPointToMultiPoint (4) 582 } 583 MAX-ACCESS read-create 584 STATUS current 585 DESCRIPTION 586 "Indicates the transport path flow for this MEG. 587 In case of a unidirectional point-to-point transport path, 588 a single unidirectional Maintenance Entity is defined to 589 monitor it. 590 In case of associated bidirectional point-to-point transport 591 paths, two independent unidirectional Maintenance Entities are 592 defined to independently monitor each direction. 593 In case of co-routed bidirectional point-to-point transport 594 paths, a single bidirectional Maintenance Entity is defined to 595 monitor both directions congruently. 596 In case of unidirectional point-to-multipoint transport paths, 597 a single unidirectional Maintenance Entity for each leaf is 598 defined to monitor the transport path from the root to 599 that leaf." 600 REFERENCE 601 "RFC 6371, Operations, Administration, and Maintenance 602 Framework for MPLS-Based Transport Networks, 603 September 2011." 604 DEFVAL { coRoutedBidirectionalPointToPoint } 605 ::= { mplsOamIdMegEntry 10 } 607 -- End of MPLS Transport Profile MEG table 609 -- Start of MPLS Transport Profile ME table 610 mplsOamIdMeTable OBJECT-TYPE 611 SYNTAX SEQUENCE OF MplsOamIdMeEntry 612 MAX-ACCESS not-accessible 613 STATUS current 614 DESCRIPTION 615 "This table contains MPLS-TP maintenance entity 616 information. 618 ME is some portion of a transport path that requires 619 management bounded by two points (called MEPs), and the 620 relationship between those points to which maintenance 621 and monitoring operations apply. 623 This table is generic enough to handle MEPs and MIPs 624 information within a MEG." 625 ::= { mplsOamIdObjects 2 } 627 mplsOamIdMeEntry OBJECT-TYPE 628 SYNTAX MplsOamIdMeEntry 629 MAX-ACCESS not-accessible 630 STATUS current 631 DESCRIPTION 632 "An entry in this table represents MPLS-TP maintenance 633 entity. This entry represents the ME if the source and 634 sink MEPs are defined. 636 A ME is a p2p entity. One ME has two such MEPs. 637 A MEG is a group of one or more MEs. One MEG can have 638 two or more MEPs. 640 For P2P LSP, one MEG has one ME and this ME is associated 641 two MEPs (source and sink MEPs) within a MEG. 642 Each mplsOamIdMeIndex value denotes the ME within a MEG. 644 In case of unidirectional point-to-point transport paths, 645 a single unidirectional Maintenance Entity is defined to 646 monitor it and mplsOamIdMeServicePointer points to 647 unidirectional point-to-point path. 649 In case of associated bidirectional point-to-point 650 transport paths, two independent unidirectional 651 Maintenance Entities are defined to independently monitor 652 each direction and each mplsOamIdMeServicePointer MIB 653 object points to unique unidirectional transport path. 654 This has implications for transactions that terminate at 655 or query a MIP, as a return path from MIP to source MEP 656 does not necessarily exist within the MEG. 658 In case of co-routed bidirectional point-to-point 659 transport paths, a single bidirectional Maintenance Entity 660 is defined to monitor both directions congruently and 661 mplsOamIdMeServicePointer MIB object points to co-routed 662 bidirectional point-to-point transport path. 664 In case of unidirectional point-to-multipoint transport 665 paths, a single unidirectional Maintenance entity for each 666 leaf is defined to monitor the transport path from the 667 root to that leaf and each leaf has different transport 668 path information in mplsOamIdMeServicePointer MIB object." 669 INDEX { mplsOamIdMegIndex, 670 mplsOamIdMeIndex, 671 mplsOamIdMeMpIndex 672 } 673 ::= { mplsOamIdMeTable 1 } 675 MplsOamIdMeEntry ::= SEQUENCE { 676 mplsOamIdMeIndex Unsigned32, 677 mplsOamIdMeMpIndex Unsigned32, 678 mplsOamIdMeName SnmpAdminString, 679 mplsOamIdMeMpIfIndex InterfaceIndexOrZero, 680 mplsOamIdMeSourceMepIndex Unsigned32, 681 mplsOamIdMeSinkMepIndex Unsigned32, 682 mplsOamIdMeMpType INTEGER, 683 mplsOamIdMeMepDirection INTEGER, 684 mplsOamIdMeProactiveOamSessIndex Unsigned32, 685 mplsOamIdMeProactiveOamPhbTCValue INTEGER, 686 mplsOamIdMeOnDemandOamPhbTCValue INTEGER, 687 mplsOamIdMeServicePointer RowPointer, 688 mplsOamIdMeRowStatus RowStatus, 689 mplsOamIdMeStorageType StorageType 690 } 692 mplsOamIdMeIndex OBJECT-TYPE 693 SYNTAX Unsigned32 694 MAX-ACCESS not-accessible 695 STATUS current 696 DESCRIPTION 697 "Uniquely identifies a maintenance entity index within 698 a MEG." 699 ::= { mplsOamIdMeEntry 1 } 701 mplsOamIdMeMpIndex OBJECT-TYPE 703 SYNTAX Unsigned32 704 MAX-ACCESS not-accessible 705 STATUS current 706 DESCRIPTION 707 "Indicates the maintenance point index, used to create 708 multiple MEPs in a node of single ME. The value of this 709 object can be MEP index or MIP index." 711 ::= { mplsOamIdMeEntry 2 } 713 mplsOamIdMeName OBJECT-TYPE 714 SYNTAX SnmpAdminString (SIZE(1..48)) 715 MAX-ACCESS read-create 716 STATUS current 717 DESCRIPTION 718 "This object denotes the ME name, each 719 Maintenance Entity has unique name within MEG." 720 ::= { mplsOamIdMeEntry 3 } 722 mplsOamIdMeMpIfIndex OBJECT-TYPE 723 SYNTAX InterfaceIndexOrZero 724 MAX-ACCESS read-create 725 STATUS current 726 DESCRIPTION 727 "Indicates the maintenance point interface. 728 If the mplsOamIdMegMpLocation object value 729 is perNode (1), the MP interface index should point 730 to incoming interface or outgoing interface or 731 zero (indicates the MP OAM packets are initiated 732 from forwarding engine). 734 If the mplsOamIdMegMpLocation object value is 735 perInterface (2), the MP interface index should point to 736 incoming interface or outgoing interface." 737 REFERENCE 738 "RFC 6371, Operations, Administration, and Maintenance 739 Framework for MPLS-Based Transport Networks, 740 September 2011." 741 DEFVAL { 0 } 742 ::= { mplsOamIdMeEntry 4 } 744 mplsOamIdMeSourceMepIndex OBJECT-TYPE 745 SYNTAX Unsigned32 746 MAX-ACCESS read-create 747 STATUS current 748 DESCRIPTION 749 "Indicates the source MEP Index of the ME. This object 750 should be configured if mplsOamIdMegOperatorType object 751 in the mplsOamIdMegEntry is configured as iccBased (2). 752 If the MEG is configured for IP based operator, 753 the value of this object should be set zero and the MEP 754 ID will be automatically derived from the service 755 Identifiers(MPLS-TP LSP/PW Identifier)." 757 DEFVAL { 0 } 758 ::= { mplsOamIdMeEntry 5 } 760 mplsOamIdMeSinkMepIndex OBJECT-TYPE 761 SYNTAX Unsigned32 762 MAX-ACCESS read-create 763 STATUS current 764 DESCRIPTION 765 "Indicates the sink MEP Index of the ME. This object 766 should be configured if mplsOamIdMegOperatorType object 767 in the mplsOamIdMegEntry is configured as iccBased (2). 768 If the MEG is configured for IP based operator, 769 the value of this object should be set zero and the MEP 770 ID will be automatically derived from the service 771 Identifiers(MPLS-TP LSP/PW Identifier)." 772 DEFVAL { 0 } 773 ::= { mplsOamIdMeEntry 6 } 775 mplsOamIdMeMpType OBJECT-TYPE 776 SYNTAX INTEGER { 777 mep (1), 778 mip (2) 779 } 780 MAX-ACCESS read-create 781 STATUS current 782 DESCRIPTION 783 "Indicates the maintenance point type within the MEG. 785 The object should have the value mep (1), only in the 786 Ingress or Egress nodes of the transport path. 788 The object can have the value mip (2), 789 in the intermediate nodes and possibly in the end nodes 790 of the transport path." 791 DEFVAL { mep } 792 ::= { mplsOamIdMeEntry 7 } 794 mplsOamIdMeMepDirection OBJECT-TYPE 795 SYNTAX INTEGER { 796 up (1), 797 down (2) 798 } 799 MAX-ACCESS read-create 800 STATUS current 801 DESCRIPTION 802 "Indicates the direction of the MEP. This object 803 should be configured if mplsOamIdMeMpType is 804 configured as mep (1)." 805 DEFVAL { down } 806 ::= { mplsOamIdMeEntry 8 } 808 mplsOamIdMeProactiveOamSessIndex OBJECT-TYPE 809 SYNTAX Unsigned32 810 MAX-ACCESS read-only 811 STATUS current 812 DESCRIPTION 813 "Indicates the proactive OAM session index for this MP. 814 When a proactive OAM session for this MP is established, 815 the underlying proactive initiator has to update this 816 object with the proactive OAM session index. 817 Incase of bidirectional transport path, either one 818 direction of proactive OAM transmission/reception failure 819 results into complete path down." 820 DEFVAL { 0 } 821 ::= { mplsOamIdMeEntry 9 } 823 mplsOamIdMeProactiveOamPhbTCValue OBJECT-TYPE 824 SYNTAX INTEGER { 825 be (1), 826 af1 (2), 827 af2 (3), 828 af3 (4), 829 af4 (5), 830 ef (6), 831 cs6 (7), 832 cs7 (8) 833 } 834 MAX-ACCESS read-create 835 STATUS current 836 DESCRIPTION 837 "Indicates the Per-hop Behavior (PHB) value for this source 838 MEP generated proactive traffic." 839 DEFVAL { ef } 840 ::= { mplsOamIdMeEntry 10 } 842 mplsOamIdMeOnDemandOamPhbTCValue OBJECT-TYPE 843 SYNTAX INTEGER { 844 be (1), 845 af1 (2), 846 af2 (3), 847 af3 (4), 848 af4 (5), 849 ef (6), 850 cs6 (7), 851 cs7 (8) 853 } 854 MAX-ACCESS read-create 855 STATUS current 856 DESCRIPTION 857 "Indicates the Per-hop Behavior (PHB) value for this 858 source MEP generated on-demand traffic." 859 DEFVAL { ef } 861 ::= { mplsOamIdMeEntry 11 } 863 mplsOamIdMeServicePointer OBJECT-TYPE 865 SYNTAX RowPointer 866 MAX-ACCESS read-create 867 STATUS current 868 DESCRIPTION 869 "This variable represents a pointer to the MPLS-TP 870 transport path. This value may point at an entry in the 871 mplsTunnelEntry if mplsOamIdMegServiceType is configured 872 as lsp (1) or at an entry in the pwEntry if 873 mplsOamIdMegServiceType is configured as pseudowire (2). 875 Note: This service pointer object, is placed in ME table 876 instead of MEG table, since it will be useful in case of 877 point-to-multipoint, where each ME will point to different 878 branches of a P2MP tree." 879 DEFVAL { zeroDotZero } 880 ::= { mplsOamIdMeEntry 12 } 882 mplsOamIdMeRowStatus OBJECT-TYPE 883 SYNTAX RowStatus 884 MAX-ACCESS read-create 885 STATUS current 886 DESCRIPTION 887 "This variable is used to create, modify, and/or 888 delete a row in this table. When a row in this 889 table is in active(1) state, no objects in that row 890 can be modified by the agent except 891 mplsOamIdMeRowStatus." 892 ::= { mplsOamIdMeEntry 13 } 894 mplsOamIdMeStorageType OBJECT-TYPE 895 SYNTAX StorageType 896 MAX-ACCESS read-create 897 STATUS current 898 DESCRIPTION 899 "This variable indicates the storage type for this 900 object. 902 Conceptual rows having the value 'permanent' 903 need not allow write-access to any columnar 904 objects in the row." 905 DEFVAL { volatile } 906 ::= { mplsOamIdMeEntry 14 } 908 -- End of MPLS Transport Profile ME table 910 -- End of MPLS-TP OAM Tables 912 -- Notification Definitions of MPLS-TP identifiers 914 mplsOamIdMegOperStatus OBJECT-TYPE 915 SYNTAX INTEGER { 916 up (1), 917 down (2) 918 } 919 MAX-ACCESS accessible-for-notify 920 STATUS current 921 DESCRIPTION 922 "This object specifies the operational status of the 923 Maintenance Entity Group (MEG). This object is used to 924 send the notification to the SNMP manager about the MEG. 926 The value up (1) indicates that the MEG and its monitored 927 path are operationally up. The value down (2) indicates 928 that the MEG is operationally down." 929 ::= { mplsOamIdObjects 3 } 931 mplsOamIdMegSubOperStatus OBJECT-TYPE 932 SYNTAX BITS { 933 megDown (0), 934 meDown (1), 935 oamAppDown (2), 936 pathDown (3) 937 } 938 MAX-ACCESS accessible-for-notify 939 STATUS current 940 DESCRIPTION 941 "This object specifies the reason why the MEG operational 942 status as mentioned by the object mplsOamIdMegOperStatus 943 is down. This object is used to send the notification to 944 the SNMP manager about the MEG. 946 The bit 0 (megDown) when set indicates the MEG is down. 947 MEG table can be made down administratively. 948 The bit 1 (meDown) when set indicates the ME table is 949 down. ME can be made down administratively. 950 The bit 2 (oamAppDown) when set indicates that the 951 OAM application has notified that the entity (LSP or PW) 952 monitored by this MEG is down. Currently, BFD is the 953 only supported OAM application. 954 The bit 3 (pathDown) when set indicates that the 955 underlying LSP or PW is down." 956 ::= { mplsOamIdObjects 4 } 958 mplsOamIdDefectCondition NOTIFICATION-TYPE 959 OBJECTS { 960 mplsOamIdMegName, 961 mplsOamIdMeName, 963 mplsOamIdMegOperStatus, 964 mplsOamIdMegSubOperStatus 965 } 966 STATUS current 967 DESCRIPTION 968 "This notification signifies the operational status of MEG. 970 The information that are carried in this notification are 971 Meg Name, Me Name, MegOperStatus and 972 MegSubOperStatus. 973 " 974 ::= { mplsOamIdNotifications 1 } 976 -- End of Notifications. 978 -- Module Compliance. 980 mplsOamIdGroups 981 OBJECT IDENTIFIER ::= { mplsOamIdConformance 1 } 983 mplsOamIdCompliances 984 OBJECT IDENTIFIER ::= { mplsOamIdConformance 2 } 986 -- Compliance requirement for fully compliant implementations. 988 mplsOamIdModuleFullCompliance MODULE-COMPLIANCE 989 STATUS current 990 DESCRIPTION "Compliance statement for agents that provide full 991 support for MPLS-TP-OAM-STD-MIB. Such devices can 992 then be monitored and also be configured using 993 this MIB module." 995 MODULE IF-MIB -- The Interfaces Group MIB, RFC 2863. 996 MANDATORY-GROUPS { 997 ifGeneralInformationGroup, 998 ifCounterDiscontinuityGroup 999 } 1001 MODULE -- This module. 1002 MANDATORY-GROUPS { 1003 mplsOamIdMegGroup, 1004 mplsOamIdMeGroup 1005 } 1007 GROUP mplsOamIdNotificationObjectsGroup 1008 DESCRIPTION "This group is only mandatory for those 1009 implementations which can efficiently implement 1010 the notifications contained in this group." 1012 GROUP mplsOamIdNotificationGroup 1013 DESCRIPTION "This group is only mandatory for those 1014 implementations which can efficiently implement 1015 the notifications contained in this group." 1017 ::= { mplsOamIdCompliances 1 } 1019 -- Units of conformance. 1021 mplsOamIdMegGroup OBJECT-GROUP 1022 OBJECTS { 1023 mplsOamIdMegName, 1024 mplsOamIdMegOperatorType, 1025 mplsOamIdMegIdIcc, 1026 mplsOamIdMegIdUmc, 1027 mplsOamIdMegServiceType, 1028 mplsOamIdMegMpLocation, 1029 mplsOamIdMegRowStatus, 1030 mplsOamIdMegStorageType, 1031 mplsOamIdMegPathFlow 1032 } 1034 STATUS current 1035 DESCRIPTION 1036 "Collection of objects needed for MPLS MEG information." 1037 ::= { mplsOamIdGroups 1 } 1039 mplsOamIdMeGroup OBJECT-GROUP 1040 OBJECTS { 1041 mplsOamIdMeName, 1042 mplsOamIdMeMpIfIndex, 1043 mplsOamIdMeSourceMepIndex, 1044 mplsOamIdMeSinkMepIndex, 1045 mplsOamIdMeMpType, 1046 mplsOamIdMeMepDirection, 1047 mplsOamIdMeProactiveOamSessIndex, 1048 mplsOamIdMeProactiveOamPhbTCValue, 1049 mplsOamIdMeOnDemandOamPhbTCValue, 1050 mplsOamIdMeServicePointer, 1051 mplsOamIdMeRowStatus, 1052 mplsOamIdMeStorageType 1053 } 1054 STATUS current 1055 DESCRIPTION 1056 "Collection of objects needed for MPLS ME information." 1057 ::= { mplsOamIdGroups 2 } 1059 mplsOamIdNotificationObjectsGroup OBJECT-GROUP 1060 OBJECTS { 1062 mplsOamIdMegOperStatus, 1064 mplsOamIdMegSubOperStatus 1065 } 1066 STATUS current 1067 DESCRIPTION 1068 "Collection of objects needed to implement notifications." 1069 ::= { mplsOamIdGroups 3 } 1071 mplsOamIdNotificationGroup NOTIFICATION-GROUP 1072 NOTIFICATIONS { 1073 mplsOamIdDefectCondition 1074 } 1075 STATUS current 1076 DESCRIPTION 1077 "Set of notifications implemented in this module." 1078 ::= { mplsOamIdGroups 4 } 1080 END 1082 8. Security Consideration 1084 There is a number of management objects defined in this MIB module 1085 that has a MAX-ACCESS clause of read-write.. Such objects may be 1086 considered sensitive or vulnerable in some network environments. 1087 The support for SET operations in a non-secure environment 1088 without proper protection can have a negative effect on network 1089 operations. 1091 Some of the readable objects in this MIB module (i.e., objects 1092 with a MAX-ACCESS other than not-accessible) may be considered 1093 sensitive or vulnerable in some network environments. 1094 It is thus important to control even GET and/or NOTIFY access 1095 to these objects and possibly to even encrypt the values of these 1096 objects when sending them over the network via SNMP. These are 1097 the tables and objects and their sensitivity/vulnerability: 1099 SNMP versions prior to SNMPv3 did not include adequate security. 1100 Even if the network itself is secure (for example by using IPsec), 1101 even then, there is no control as to who on the secure network 1102 is allowed to access and GET/SET (read/change/create/delete) 1103 the objects in this MIB module. 1105 It is RECOMMENDED that implementers consider the security features 1106 as provided by the SNMPv3 framework (see [RFC3410], section 8), 1107 including full supports for the SNMPv3 cryptographic mechanisms 1108 (for authentication and privacy). 1110 Further, deployment of SNMP versions prior to SNMPv3 is NOT 1111 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 1112 enable cryptographic security. It is then a customer/operator 1113 responsibility to ensure that the SNMP entity giving access to an 1114 instance of this MIB module is properly configured to give access to 1115 the objects only to those principles (users) that have legitimate 1116 rights to indeed GET or SET (change/create/delete) them. 1118 9. IANA Considerations 1120 To be added in a later version of this document. 1122 10. References 1124 10.1 Normative References 1126 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1127 Requirement Levels", BCP 14, RFC 2119, March 1997. 1129 [RFC2578] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 1130 "Structure of Management Information Version 2 (SMIv2)", 1131 STD 58, RFC 2578, April 1999. 1133 [RFC2579] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 1134 "Textual Conventions for SMIv2", STD 58, RFC 2579, April 1135 1999. 1137 [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 1138 "Conformance Statements for SMIv2", STD 58, RFC 2580, 1139 April 1999. 1141 [RFC2863] McCloghrie, K. and F. Kastenholtz, "The Interfaces Group 1142 MIB ", RFC 2863, June 2000 1144 [RFC3031] Rosen, E., Viswanathan, A., and R. Callon, 1145 "Multiprotocol Label Switching Architecture", RFC 3031, 1146 January 2001. 1148 [RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An 1149 Architecture for Describing Simple Network Management 1150 Protocol (SNMP) Management Frameworks", STD 62, RFC 1151 3411, December 2002. 1153 10.2 Informative References 1155 [RFC3812] Srinivasan, C., Viswanathan, A., and T. Nadeau, 1156 "Multiprotocol Label Switching (MPLS) Traffic 1157 Engineering (TE) Management Information Base (MIB)", RFC 1158 3812, June 2004. 1160 [RFC3813] Srinivasan, C., Viswanathan, A., and T. Nadeau, 1161 "Multiprotocol Label Switching (MPLS) Label Switching 1162 (LSR) Router Management Information Base (MIB)", RFC 1163 3813, June 2004. 1165 [RFC3410] J. Case, R. Mundy, D. pertain, B.Stewart, "Introduction 1166 and Applicability Statement for Internet Standard 1167 Management Framework", RFC 3410, December 2002. 1169 [RFC3811] Nadeau, T., Ed., and J. Cucchiara, Ed., "Definitions of 1170 Textual Conventions (TCs) for Multiprotocol Label 1171 Switching (MPLS) Management", RFC 3811, June 2004. 1173 [RFC5654] Niven-Jenkins, B., Ed., Brungard, D., Ed., Betts, M., 1174 Ed., Sprecher, N., and S. Ueno, "Requirements of an MPLS 1175 Transport Profile", RFC 5654, September 2009. 1177 [TP-ITUIDS] R. Winter, Ed, E. Gray, Ed., H. van Helvoort, and M. 1178 Betts, "MPLS-TP Identifiers Following ITU-T 1179 Conventions", ID draft-ietf-mpls-tp-itu-t-identifiers- 1180 03, March 2012. 1182 [RFC6370] Bocci, M., Swallow, G., and E. Gray, "MPLS-TP 1183 Identifiers", RFC 6370, September 2011. 1185 [RFC6371] Busi, I., Niven-Jenkins, B., and D. Allan, "MPLS-TP OAM 1186 Framework and Overview", RFC 6371, September 2011. 1188 11. Acknowledgments 1189 We wish to thank Muly Ilan, Adrian Farrel, Joan Cucchiara and 1190 Weiying Cheng for their valuable comments on this document. 1192 12. Authors' Addresses 1194 Sam Aldrin 1195 Huawei Technologies, co. 1196 2330 Central Express Way, 1197 Santa Clara, CA 95051, USA 1198 Email: aldrin.ietf@gmail.com 1200 Thomas D. Nadeau 1201 Juniper Networks 1202 10 Technology Park Drive, Westford, MA 01886 1203 Email: tnadeau@juniper.net 1205 Venkatesan Mahalingam 1206 Dell Inc. 1207 350 Holger way, San Jose, CA, USA 1208 Email: venkat.mahalingams@gmail.com 1210 Kannan KV Sampath 1211 Redeem, 1212 India 1213 Email: kannankvs@gmail.com 1215 Ping Pan 1216 Infinera 1217 Email: ppan@infinera.com 1219 Sami Boutros 1220 Cisco Systems, Inc. 1221 3750 Cisco Way 1222 San Jose, California 95134 1223 USA 1224 Email: sboutros@cisco.com