idnits 2.17.1 draft-ietf-mpls-tp-oam-id-mib-00.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 (June 25, 2012) is 4320 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: December 27, 2012 M.Venkatesan 6 Dell Inc. 7 Kannan KV Sampath 8 Aricent Group 9 Thomas D. Nadeau 10 Juniper Networks 11 Sami Boutros 12 Cisco Systems 13 Ping Pan 14 Infinera 16 June 25, 2012 18 MPLS-TP Operations, Administration, and Management (OAM) Identifiers 19 Management Information Base (MIB) 20 draft-ietf-mpls-tp-oam-id-mib-00 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 December 27, 2012. 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 . . . . . . . . . . . . . . . . . . . . 21 83 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 22 84 10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 22 85 10.1 Normative References . . . . . . . . . . . . . . . . . . . 22 86 10.2 Informative References . . . . . . . . . . . . . . . . . . 22 87 11. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 23 88 12. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 23 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 bi-directional, associated 156 bi-directional 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 } 218 This will create an entry in the mplsOamIdMegTable to manage and 219 monitor the MPLS tunnel. 221 The following ME table is used to associate the path information 222 to a MEG. 224 In mplsOamIdMeTable: 226 { 227 -- ME index (Index to the table) 228 mplsOamIdMeIndex = 1, 230 -- MP index (Index to the table) 231 mplsOamIdMeMpIndex = 1, 232 mplsOamIdMeName = "ME1", 233 mplsOamIdMeMpIfIndex = 0, 234 -- Source MEP id is derived from the IP compatible MPLS tunnel 235 mplsOamIdMeSourceMepIndex = 0, 236 -- Source MEP id is derived from the IP compatible MPLS tunnel 237 mplsOamIdMeSinkMepIndex = 0, 238 mplsOamIdMeMpType = mep (1), 239 mplsOamIdMeMepDirection = down (2), 240 mplsOamIdMeProactiveOamPhbTCValue = 0, 241 mplsOamIdMeOnDemandOamPhbTCValue = 0, 242 -- RowPointer MUST point to the first accessible column of an 243 -- MPLS tunnel 244 mplsOamIdMeServicePointer = mplsTunnelName.1.1.10.20, 245 -- Mandatory parameters needed to activate the row go here 246 mplsOamIdMeRowStatus = createAndGo (4) 247 } 249 7. MPLS OAM Identifiers MIB definitions 251 MPLS-OAM-ID-STD-MIB DEFINITIONS ::= BEGIN 253 IMPORTS 254 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, 255 Unsigned32, zeroDotZero 256 FROM SNMPv2-SMI -- [RFC2578] 257 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 258 FROM SNMPv2-CONF -- [RFC2580] 259 RowStatus, RowPointer, StorageType 260 FROM SNMPv2-TC -- [RFC2579] 261 SnmpAdminString 262 FROM SNMP-FRAMEWORK-MIB -- [RFC3411] 263 mplsStdMIB 264 FROM MPLS-TC-STD-MIB -- [RFC3811] 265 InterfaceIndexOrZero, ifGeneralInformationGroup, 266 ifCounterDiscontinuityGroup 267 FROM IF-MIB; -- [RFC2863] 269 mplsOamIdStdMIB MODULE-IDENTITY 270 LAST-UPDATED 271 "201206030000Z" -- June 03, 2012 272 ORGANIZATION 273 "Multiprotocol Label Switching (MPLS) Working Group" 274 CONTACT-INFO 275 " 276 Sam Aldrin 277 Huawei Technologies, co. 279 2330 Central Express Way, 281 Santa Clara, CA 95051, USA 282 Email: aldrin.ietf@gmail.com 284 Thomas D. Nadeau 285 Juniper Networks 286 10 Technology Park Drive, 287 Westford, MA 01886 288 Email: tnadeau@juniper.net 290 Venkatesan Mahalingam 291 Dell Inc. 292 350 Holger way, San Jose, CA, USA 293 Email: venkat.mahalingams@gmail.com 295 Kannan KV Sampath 296 Aricent 297 India 298 Email: Kannan.Sampath@aricent.com 300 Ping Pan 301 Infinera 302 Email: ppan@infinera.com 304 Sami Boutros 305 Cisco Systems, Inc. 306 3750 Cisco Way 307 San Jose, California 95134 308 USA 309 Email: sboutros@cisco.com 311 " 312 DESCRIPTION 313 "Copyright (c) 2012 IETF Trust and the persons identified 314 as the document authors. All rights reserved. 316 This MIB module contains generic object definitions for 317 MPLS OAM maintenance identifiers in MPLS based transport 318 networks." 320 -- Revision history. 322 REVISION 323 "201206030000Z" -- June 03, 2012 324 DESCRIPTION 325 "MPLS OAM Identifiers mib objects for LSPs and 326 Pseudowires" 328 ::= { mplsStdMIB xxx } -- xxx to be replaced with correct value 330 -- Top level components of this MIB module. 332 -- notifications 333 mplsOamIdNotifications 334 OBJECT IDENTIFIER ::= { mplsOamIdStdMIB 0 } 335 -- tables, scalars 336 mplsOamIdObjects OBJECT IDENTIFIER ::= { mplsOamIdStdMIB 1 } 337 -- conformance 338 mplsOamIdConformance 339 OBJECT IDENTIFIER ::= { mplsOamIdStdMIB 2 } 341 -- Start of MPLS Transport Profile MEG table 343 mplsOamIdMegTable OBJECT-TYPE 344 SYNTAX SEQUENCE OF MplsOamIdMegEntry 345 MAX-ACCESS not-accessible 346 STATUS current 347 DESCRIPTION 348 "This table contains information about the Maintenance 349 Entity Groups (MEG). 351 MEG as mentioned in MPLS-TP OAM framework defines a set 352 of one or more maintenance entities (ME). 353 Maintenance Entities define a relationship between any 354 two points of a transport path in an OAM domain to which 355 maintenance and monitoring operations apply." 356 ::= { mplsOamIdObjects 1 } 358 mplsOamIdMegEntry OBJECT-TYPE 359 SYNTAX MplsOamIdMegEntry 360 MAX-ACCESS not-accessible 361 STATUS current 362 DESCRIPTION 363 "An entry in this table represents MPLS-TP MEG. 364 An entry can be created by a network administrator 365 or by an SNMP agent as instructed by an MPLS-TP OAM 366 Framework. 368 When a new entry is created with 369 mplsOamIdMegOperatorType set to ipCompatible (1), 370 then as per [RFC6370] (MEG_ID for LSP is LSP_ID and 371 MEG_ID for PW is PW_Path_ID), MEP_ID can be 372 automatically formed. 374 For co-routed bidirectional LSP, MEG_ID is 375 A1-{Global_ID::Node_ID::Tunnel_Num}::Z9-{Global_ID:: 377 Node_ID::Tunnel_Num}::LSP_Num. 379 For associated bidirectional LSP, MEG_ID is A1- 380 {Global_ID::Node_ID::Tunnel_Num::LSP_Num}:: Z9- 381 {Global_ID::Node_ID::Tunnel_Num::LSP_Num} 383 For LSP, MEP_ID is formed using, 384 Global_ID::Node_ID::Tunnel_Num::LSP_Num 386 For PW, MEG_ID is formed using AGI::A1- 387 {Global_ID::Node_ID::AC_ID}:: Z9- 388 {Global_ID::Node_ID::AC_ID}. 390 For PW, MEP_ID is formed using 391 AGI::Global_ID::Node_ID::AC_ID 393 MEP_ID is retrieved from the mplsOamIdMegServicePointer 394 object based on the mplsOamIdMegServiceType value. 395 ICC MEG_ID for LSP and PW is formed using the objects 396 mplsOamIdMegIdIcc and mplsOamIdMegIdUmc. 398 MEP_ID can be formed using MEG_ID::MEP_Index." 399 REFERENCE 400 "1. RFC 5860, Requirements for OAM in MPLS Transport 401 Networks, May 2010. 402 2. RFC 6371, Operations, Administration, and Maintenance 403 Framework for MPLS-Based Transport Networks, 404 September 2011. 405 3. RFC 6370, MPLS Transport Profile (MPLS-TP) Identifiers. 406 4. MPLS-TP Identifiers Following ITU-T Conventions 407 [TP-ITUIDS]." 408 INDEX { mplsOamIdMegIndex } 409 ::= { mplsOamIdMegTable 1 } 411 MplsOamIdMegEntry ::= SEQUENCE { 412 mplsOamIdMegIndex Unsigned32, 413 mplsOamIdMegName SnmpAdminString, 414 mplsOamIdMegOperatorType INTEGER, 415 mplsOamIdMegIdIcc SnmpAdminString, 416 mplsOamIdMegIdUmc SnmpAdminString, 417 mplsOamIdMegServiceType INTEGER, 418 mplsOamIdMegMpLocation INTEGER, 419 mplsOamIdMegRowStatus RowStatus, 420 mplsOamIdMegStorageType StorageType 421 } 423 mplsOamIdMegIndex OBJECT-TYPE 424 SYNTAX Unsigned32 425 MAX-ACCESS not-accessible 426 STATUS current 427 DESCRIPTION 428 "Index for the conceptual row identifying a MEG within 430 this MEG table." 431 ::= { mplsOamIdMegEntry 1 } 433 mplsOamIdMegName OBJECT-TYPE 434 SYNTAX SnmpAdminString (SIZE(1..48)) 435 MAX-ACCESS read-create 436 STATUS current 437 DESCRIPTION 438 "Each Maintenance Entity Group has unique name amongst 439 all those used or available to a service provider or 440 operator. It facilitates easy identification of 441 administrative responsibility for each MEG." 442 ::= { mplsOamIdMegEntry 2 } 444 mplsOamIdMegOperatorType OBJECT-TYPE 445 SYNTAX INTEGER { 446 ipCompatible (1), 448 iccBased (2) 449 } 450 MAX-ACCESS read-create 451 STATUS current 452 DESCRIPTION 453 "Indicates the operator type for MEG. Conceptual rows 454 having 'iccBased' as operator type, should have valid 455 values for the objects mplsOamIdMegIdIcc and 456 mplsOamIdMegIdUmc while making the row status active." 457 REFERENCE 458 "1. RFC 6370, MPLS Transport Profile (MPLS-TP) 459 Identifiers. 460 2. MPLS-TP Identifiers Following ITU-T Conventions 461 [TP-ITUIDS]." 462 DEFVAL { ipCompatible } 463 ::= { mplsOamIdMegEntry 3 } 465 mplsOamIdMegIdIcc OBJECT-TYPE 466 SYNTAX SnmpAdminString (SIZE(1..6)) 467 MAX-ACCESS read-write 468 STATUS current 469 DESCRIPTION 470 "Unique code assigned to Network Operator or Service 471 Provider maintained by ITU-T. The ITU Carrier Code 472 used to form MEGID. 474 This object contains non-null ICC value if 475 the MplsOamIdMegOperatorType value is iccBased(2), 476 otherwise null ICC value should be assigned." 477 REFERENCE 479 "MPLS-TP Identifiers Following ITU-T Conventions 480 [TP-ITUIDS]." 481 DEFVAL {""} 482 ::= { mplsOamIdMegEntry 4 } 484 mplsOamIdMegIdUmc OBJECT-TYPE 485 SYNTAX SnmpAdminString (SIZE(1..7)) 486 MAX-ACCESS read-write 487 STATUS current 488 DESCRIPTION 489 "Unique code assigned by Network Operator or Service 490 Provider and is appended to mplsOamIdMegIdIcc to form 491 the MEGID. 492 This object contains non-null ICC value if 493 the MplsOamIdMegOperatorType value is iccBased(2), 494 otherwise null ICC value should be assigned." 495 REFERENCE 496 "MPLS-TP Identifiers Following ITU-T Conventions 497 [TP-ITUIDS]." 498 DEFVAL {""} 499 ::= { mplsOamIdMegEntry 5 } 501 mplsOamIdMegServiceType OBJECT-TYPE 503 SYNTAX INTEGER { 504 lsp (1), 505 pseudowire (2), 506 section (3) 507 } 508 MAX-ACCESS read-create 509 STATUS current 510 DESCRIPTION 511 "Indicates the service type for which the MEG is created. 513 If the service type indicates lsp, the service pointer 514 in mplsOamIdMeTable points to the TE tunnel table entry. 516 If the value is pseudowire service type, the service 517 pointer in mplsOamIdMeTable points to the pseudowire 518 table entry. 520 If the value is section service type, the service 521 pointer in mplsOamIdMeTable points to a section entry." 523 DEFVAL { lsp } 524 ::= { mplsOamIdMegEntry 6 } 526 mplsOamIdMegMpLocation OBJECT-TYPE 527 SYNTAX INTEGER { 529 perNode (1), 530 perInterface (2) 531 } 532 MAX-ACCESS read-create 533 STATUS current 534 DESCRIPTION 535 "Indicates the MP location type for this MEG. 537 If the value is perNode, then the MEG in the LSR supports 538 only perNode MEP/MIP, i.e., only one MEP/MIP in an LSR. 540 If the value is perInterface, then the MEG in the LSR 541 supports perInterface MEPs/MIPs, i.e., two MEPs/MIPs in 542 an LSR." 543 REFERENCE 544 "RFC 6371, Operations, Administration, and Maintenance 545 Framework for MPLS-Based Transport Networks, 546 September 2011." 547 DEFVAL { perNode } 548 ::= { mplsOamIdMegEntry 7 } 550 mplsOamIdMegRowStatus OBJECT-TYPE 551 SYNTAX RowStatus 552 MAX-ACCESS read-create 553 STATUS current 554 DESCRIPTION 556 "This variable is used to create, modify, and/or delete 557 a row in this table. When a row in this table is in 558 active(1) state, no objects in that row can be modified 559 by the agent except mplsOamIdMegRowStatus." 560 ::= { mplsOamIdMegEntry 8 } 562 mplsOamIdMegStorageType OBJECT-TYPE 563 SYNTAX StorageType 564 MAX-ACCESS read-create 565 STATUS current 566 DESCRIPTION 567 "This variable indicates the storage type for this 568 object. 569 Conceptual rows having the value 'permanent' 570 need not allow write-access to any columnar 571 objects in the row." 572 DEFVAL { volatile } 573 ::= { mplsOamIdMegEntry 9 } 575 -- End of MPLS Transport Profile MEG table 577 -- Start of MPLS Transport Profile ME table 578 mplsOamIdMeTable OBJECT-TYPE 579 SYNTAX SEQUENCE OF MplsOamIdMeEntry 580 MAX-ACCESS not-accessible 581 STATUS current 582 DESCRIPTION 583 "This table contains MPLS-TP maintenance entity 584 information. 586 ME is some portion of a transport path that requires 587 management bounded by two points (called MEPs), and the 588 relationship between those points to which maintenance 589 and monitoring operations apply. 591 This table is generic enough to handle MEPs and MIPs 592 information within a MEG." 593 ::= { mplsOamIdObjects 2 } 595 mplsOamIdMeEntry OBJECT-TYPE 596 SYNTAX MplsOamIdMeEntry 597 MAX-ACCESS not-accessible 598 STATUS current 599 DESCRIPTION 600 "An entry in this table represents MPLS-TP maintenance 601 entity. This entry represents the ME if the source and 602 sink MEPs are defined. 604 A ME is a p2p entity. One ME has two such MEPs. 605 A MEG is a group of one or more MEs. One MEG can have 606 two or more MEPs. 608 For P2P LSP, one MEG has one ME and this ME is associated 609 two MEPs (source and sink MEPs) within a MEG. 610 Each mplsOamIdMeIndex value denotes the ME within a MEG. 612 In case of unidirectional point-to-point transport paths, 613 a single unidirectional Maintenance Entity is defined to 614 monitor it. 616 In case of associated bi-directional point-to-point 617 transport paths, two independent unidirectional 618 Maintenance Entities are defined to independently monitor 619 each direction. This has implications for transactions 620 that terminate at or query a MIP, as a return path from 621 MIP to source MEP does not necessarily exist within 622 the MEG. 624 In case of co-routed bi-directional point-to-point 625 transport paths, a single bidirectional Maintenance Entity 626 is defined to monitor both directions congruently. 628 In case of unidirectional point-to-multipoint transport 629 paths, a single unidirectional Maintenance entity for 630 each leaf is defined to monitor the transport path from 631 the root to that leaf." 632 INDEX { mplsOamIdMegIndex, 633 mplsOamIdMeIndex, 634 mplsOamIdMeMpIndex 635 } 636 ::= { mplsOamIdMeTable 1 } 638 MplsOamIdMeEntry ::= SEQUENCE { 639 mplsOamIdMeIndex Unsigned32, 640 mplsOamIdMeMpIndex Unsigned32, 641 mplsOamIdMeName SnmpAdminString, 642 mplsOamIdMeMpIfIndex InterfaceIndexOrZero, 643 mplsOamIdMeSourceMepIndex Unsigned32, 644 mplsOamIdMeSinkMepIndex Unsigned32, 645 mplsOamIdMeMpType INTEGER, 646 mplsOamIdMeMepDirection INTEGER, 647 mplsOamIdMeProactiveOamSessIndex Unsigned32, 648 mplsOamIdMeProactiveOamPhbTCValue INTEGER, 649 mplsOamIdMeOnDemandOamPhbTCValue INTEGER, 650 mplsOamIdMeServicePointer RowPointer, 651 mplsOamIdMeRowStatus RowStatus, 652 mplsOamIdMeStorageType StorageType 653 } 655 mplsOamIdMeIndex OBJECT-TYPE 656 SYNTAX Unsigned32 657 MAX-ACCESS not-accessible 658 STATUS current 659 DESCRIPTION 660 "Uniquely identifies a maintenance entity index within 661 a MEG." 662 ::= { mplsOamIdMeEntry 1 } 664 mplsOamIdMeMpIndex OBJECT-TYPE 665 SYNTAX Unsigned32 666 MAX-ACCESS not-accessible 667 STATUS current 668 DESCRIPTION 669 "Indicates the maintenance point index, used to create 670 multiple MEPs in a node of single ME. The value of this 671 object can be MEP index or MIP index." 673 ::= { mplsOamIdMeEntry 2 } 675 mplsOamIdMeName OBJECT-TYPE 676 SYNTAX SnmpAdminString (SIZE(1..48)) 677 MAX-ACCESS read-create 678 STATUS current 679 DESCRIPTION 680 "This object denotes the ME name, each 681 Maintenance Entity has unique name within MEG." 682 ::= { mplsOamIdMeEntry 3 } 684 mplsOamIdMeMpIfIndex OBJECT-TYPE 685 SYNTAX InterfaceIndexOrZero 686 MAX-ACCESS read-create 687 STATUS current 688 DESCRIPTION 689 "Indicates the maintenance point interface. 690 If the mplsOamIdMegMpLocation object value 691 is perNode (1), the MP interface index should point 692 to incoming interface or outgoing interface or 693 zero (indicates the MP OAM packets are initiated 694 from forwarding engine). 696 If the mplsOamIdMegMpLocation object value is 697 perInterface (2), the MP interface index should point to 698 incoming interface or outgoing interface." 699 REFERENCE 700 "RFC 6371, Operations, Administration, and Maintenance 701 Framework for MPLS-Based Transport Networks, 702 September 2011." 703 DEFVAL { 0 } 704 ::= { mplsOamIdMeEntry 4 } 706 mplsOamIdMeSourceMepIndex OBJECT-TYPE 707 SYNTAX Unsigned32 708 MAX-ACCESS read-create 709 STATUS current 710 DESCRIPTION 711 "Indicates the source MEP Index of the ME. This object 712 should be configured if mplsOamIdMegOperatorType object 713 in the mplsOamIdMegEntry is configured as iccBased (2). 714 If the MEG is configured for IP based operator, 715 the value of this object should be set zero and the MEP 716 ID will be automatically derived from the service 717 Identifiers(MPLS-TP LSP/PW Identifier)." 718 DEFVAL { 0 } 719 ::= { mplsOamIdMeEntry 5 } 721 mplsOamIdMeSinkMepIndex OBJECT-TYPE 722 SYNTAX Unsigned32 723 MAX-ACCESS read-create 724 STATUS current 725 DESCRIPTION 726 "Indicates the sink MEP Index of the ME. This object 727 should be configured if mplsOamIdMegOperatorType object 728 in the mplsOamIdMegEntry is configured as iccBased (2). 729 If the MEG is configured for IP based operator, 730 the value of this object should be set zero and the MEP 731 ID will be automatically derived from the service 732 Identifiers(MPLS-TP LSP/PW Identifier)." 733 DEFVAL { 0 } 734 ::= { mplsOamIdMeEntry 6 } 736 mplsOamIdMeMpType OBJECT-TYPE 737 SYNTAX INTEGER { 738 mep (1), 739 mip (2) 740 } 741 MAX-ACCESS read-create 742 STATUS current 743 DESCRIPTION 744 "Indicates the maintenance point type within the MEG. 746 The object should have the value mep (1), only in the 747 Ingress or Egress nodes of the transport path. 749 The object can have the value mip (2), 750 in the intermediate nodes and possibly in the end nodes 751 of the transport path." 752 DEFVAL { mep } 753 ::= { mplsOamIdMeEntry 7 } 755 mplsOamIdMeMepDirection OBJECT-TYPE 756 SYNTAX INTEGER { 757 up (1), 758 down (2) 759 } 761 MAX-ACCESS read-create 762 STATUS current 763 DESCRIPTION 764 "Indicates the direction of the MEP. This object 765 should be configured if mplsOamIdMeMpType is 767 configured as mep (1)." 768 DEFVAL { down } 769 ::= { mplsOamIdMeEntry 8 } 771 mplsOamIdMeProactiveOamSessIndex OBJECT-TYPE 772 SYNTAX Unsigned32 773 MAX-ACCESS read-only 774 STATUS current 775 DESCRIPTION 776 "Indicates the proactive OAM session index for this MP. 777 When a proactive OAM session for this MP is established, 778 the underlying proactive initiator has to update this 779 object with the proactive OAM session index." 780 DEFVAL { 0 } 781 ::= { mplsOamIdMeEntry 9 } 783 mplsOamIdMeProactiveOamPhbTCValue OBJECT-TYPE 784 SYNTAX INTEGER { 785 ef1 (1), 786 ef2 (2), 787 af1 (3), 788 af2 (4), 789 af3 (5), 790 be (6) 791 } 792 MAX-ACCESS read-create 793 STATUS current 794 DESCRIPTION 795 "Indicates the Per-hop Behavior (PHB) value for this source 796 MEP generated proactive traffic." 797 DEFVAL { ef1 } 798 ::= { mplsOamIdMeEntry 10 } 800 mplsOamIdMeOnDemandOamPhbTCValue OBJECT-TYPE 801 SYNTAX INTEGER { 802 ef1 (1), 803 ef2 (2), 804 af1 (3), 805 af2 (4), 806 af3 (5), 807 be (6) 808 } 810 MAX-ACCESS read-create 811 STATUS current 812 DESCRIPTION 813 "Indicates the Per-hop Behavior (PHB) value for this 814 source MEP generated on-demand traffic." 815 DEFVAL { ef1 } 817 ::= { mplsOamIdMeEntry 11 } 819 mplsOamIdMeServicePointer OBJECT-TYPE 821 SYNTAX RowPointer 822 MAX-ACCESS read-create 823 STATUS current 824 DESCRIPTION 825 "This variable represents a pointer to the MPLS-TP 826 transport path. This value may point at an entry in the 827 mplsTunnelEntry if mplsOamIdMegServiceType is configured 828 as lsp (1) or at an entry in the pwEntry if 829 mplsOamIdMegServiceType is configured as pseudowire (2). 831 Note: This service pointer object, is placed in ME table 832 instead of MEG table, since it will be useful in case of 833 poinit-to-multipoint, where each ME will point to different 834 branches of a P2MP tree." 835 DEFVAL { zeroDotZero } 836 ::= { mplsOamIdMeEntry 12 } 838 mplsOamIdMeRowStatus OBJECT-TYPE 839 SYNTAX RowStatus 840 MAX-ACCESS read-create 841 STATUS current 842 DESCRIPTION 843 "This variable is used to create, modify, and/or 844 delete a row in this table. When a row in this 845 table is in active(1) state, no objects in that row 846 can be modified by the agent except 847 mplsOamIdMeRowStatus." 848 ::= { mplsOamIdMeEntry 13 } 850 mplsOamIdMeStorageType OBJECT-TYPE 851 SYNTAX StorageType 852 MAX-ACCESS read-create 853 STATUS current 854 DESCRIPTION 855 "This variable indicates the storage type for this 856 object. 857 Conceptual rows having the value 'permanent' 858 need not allow write-access to any columnar 859 objects in the row." 860 DEFVAL { volatile } 861 ::= { mplsOamIdMeEntry 14 } 863 -- End of MPLS Transport Profile ME table 865 -- End of MPLS-TP OAM Tables 867 -- Notification Definitions of MPLS-TP identifiers 869 mplsOamIdMegOperStatus OBJECT-TYPE 870 SYNTAX INTEGER { 871 up (1), 872 down (2) 873 } 874 MAX-ACCESS accessible-for-notify 875 STATUS current 876 DESCRIPTION 877 "This object specifies the operational status of the 878 Maintenance Entity Group (MEG). This object is used to 879 send the notification to the SNMP manager about the MEG. 881 The value up (1) indicates that the MEG and its monitored 882 path are operationally up. The value down (2) indicates 883 that the MEG is operationally down." 884 ::= { mplsOamIdObjects 3 } 886 mplsOamIdMegSubOperStatus OBJECT-TYPE 887 SYNTAX BITS { 888 megDown (0), 889 meDown (1), 890 oamAppDown (2), 891 pathDown (3) 892 } 893 MAX-ACCESS accessible-for-notify 894 STATUS current 895 DESCRIPTION 896 "This object specifies the reason why the MEG operational 897 status as mentioned by the object mplsOamIdMegOperStatus 898 is down. This object is used to send the notification to 899 the SNMP manager about the MEG. 901 The bit 0 (megDown) when set indicates the MEG is down. 902 MEG table can be made down administratively. 903 The bit 1 (meDown) when set indicates the ME table is 904 down. ME can be made down administratively. 906 The bit 2 (oamAppDown) when set indicates that the 907 OAM application has notified that the entity (LSP or PW) 908 monitored by this MEG is down. Currently, BFD is the 909 only supported OAM application. 910 The bit 3 (pathDown) when set indicates that the 911 underlying LSP or PW is down." 912 ::= { mplsOamIdObjects 4 } 914 mplsOamIdDefectCondition NOTIFICATION-TYPE 915 OBJECTS { 916 mplsOamIdMegName, 917 mplsOamIdMeName, 919 mplsOamIdMegOperStatus, 920 mplsOamIdMegSubOperStatus 921 } 922 STATUS current 923 DESCRIPTION 924 "This notification signifies the operational status of MEG. 926 The information that are carried in this notification are 927 Meg Name, Me Name, MegOperStatus and 928 MegSubOperStatus. 929 " 930 ::= { mplsOamIdNotifications 1 } 932 -- End of Notifications. 934 -- Module Compliance. 936 mplsOamIdGroups 937 OBJECT IDENTIFIER ::= { mplsOamIdConformance 1 } 939 mplsOamIdCompliances 940 OBJECT IDENTIFIER ::= { mplsOamIdConformance 2 } 942 -- Compliance requirement for fully compliant implementations. 944 mplsOamIdModuleFullCompliance MODULE-COMPLIANCE 945 STATUS current 946 DESCRIPTION "Compliance statement for agents that provide full 947 support for MPLS-TP-OAM-STD-MIB. Such devices can 948 then be monitored and also be configured using 949 this MIB module." 951 MODULE IF-MIB -- The Interfaces Group MIB, RFC 2863. 952 MANDATORY-GROUPS { 953 ifGeneralInformationGroup, 954 ifCounterDiscontinuityGroup 955 } 957 MODULE -- This module. 958 MANDATORY-GROUPS { 959 mplsOamIdMegGroup, 960 mplsOamIdMeGroup 961 } 963 GROUP mplsOamIdNotificationObjectsGroup 964 DESCRIPTION "This group is only mandatory for those 965 implementations which can efficiently implement 966 the notifications contained in this group." 968 GROUP mplsOamIdNotificationGroup 969 DESCRIPTION "This group is only mandatory for those 970 implementations which can efficiently implement 971 the notifications contained in this group." 973 ::= { mplsOamIdCompliances 1 } 975 -- Units of conformance. 977 mplsOamIdMegGroup OBJECT-GROUP 978 OBJECTS { 979 mplsOamIdMegName, 980 mplsOamIdMegOperatorType, 981 mplsOamIdMegIdIcc, 982 mplsOamIdMegIdUmc, 983 mplsOamIdMegServiceType, 984 mplsOamIdMegMpLocation, 985 mplsOamIdMegRowStatus, 986 mplsOamIdMegStorageType 987 } 989 STATUS current 990 DESCRIPTION 991 "Collection of objects needed for MPLS MEG information." 992 ::= { mplsOamIdGroups 1 } 994 mplsOamIdMeGroup OBJECT-GROUP 995 OBJECTS { 996 mplsOamIdMeName, 997 mplsOamIdMeMpIfIndex, 998 mplsOamIdMeSourceMepIndex, 999 mplsOamIdMeSinkMepIndex, 1000 mplsOamIdMeMpType, 1001 mplsOamIdMeMepDirection, 1002 mplsOamIdMeProactiveOamSessIndex, 1003 mplsOamIdMeProactiveOamPhbTCValue, 1004 mplsOamIdMeOnDemandOamPhbTCValue, 1005 mplsOamIdMeServicePointer, 1006 mplsOamIdMeRowStatus, 1007 mplsOamIdMeStorageType 1008 } 1009 STATUS current 1010 DESCRIPTION 1011 "Collection of objects needed for MPLS ME information." 1012 ::= { mplsOamIdGroups 2 } 1014 mplsOamIdNotificationObjectsGroup OBJECT-GROUP 1015 OBJECTS { 1017 mplsOamIdMegOperStatus, 1019 mplsOamIdMegSubOperStatus 1020 } 1021 STATUS current 1022 DESCRIPTION 1023 "Collection of objects needed to implement notifications." 1024 ::= { mplsOamIdGroups 3 } 1026 mplsOamIdNotificationGroup NOTIFICATION-GROUP 1027 NOTIFICATIONS { 1028 mplsOamIdDefectCondition 1029 } 1030 STATUS current 1031 DESCRIPTION 1032 "Set of notifications implemented in this module." 1033 ::= { mplsOamIdGroups 4 } 1035 END 1037 8. Security Consideration 1039 There is a number of management objects defined in this MIB module 1040 that has a MAX-ACCESS clause of read-write.. Such objects may be 1041 considered sensitive or vulnerable in some network environments. 1042 The support for SET operations in a non-secure environment 1043 without proper protection can have a negative effect on network 1044 operations. 1046 Some of the readable objects in this MIB module (i.e., objects 1047 with a MAX-ACCESS other than not-accessible) may be considered 1048 sensitive or vulnerable in some network environments. 1049 It is thus important to control even GET and/or NOTIFY access 1050 to these objects and possibly to even encrypt the values of these 1051 objects when sending them over the network via SNMP. These are 1052 the tables and objects and their sensitivity/vulnerability: 1054 SNMP versions prior to SNMPv3 did not include adequate security. 1055 Even if the network itself is secure (for example by using IPsec), 1056 even then, there is no control as to who on the secure network 1057 is allowed to access and GET/SET (read/change/create/delete) 1058 the objects in this MIB module. 1060 It is RECOMMENDED that implementers consider the security features 1061 as provided by the SNMPv3 framework (see [RFC3410], section 8), 1062 including full supports for the SNMPv3 cryptographic mechanisms 1063 (for authentication and privacy). 1065 Further, deployment of SNMP versions prior to SNMPv3 is NOT 1066 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 1067 enable cryptographic security. It is then a customer/operator 1068 responsibility to ensure that the SNMP entity giving access to an 1069 instance of this MIB module is properly configured to give access to 1070 the objects only to those principles (users) that have legitimate 1071 rights to indeed GET or SET (change/create/delete) them. 1073 9. IANA Considerations 1075 To be added in a later version of this document. 1077 10. References 1079 10.1 Normative References 1081 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1082 Requirement Levels", BCP 14, RFC 2119, March 1997. 1084 [RFC2578] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 1085 "Structure of Management Information Version 2 (SMIv2)", 1086 STD 58, RFC 2578, April 1999. 1088 [RFC2579] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 1089 "Textual Conventions for SMIv2", STD 58, RFC 2579, April 1090 1999. 1092 [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 1093 "Conformance Statements for SMIv2", STD 58, RFC 2580, 1094 April 1999. 1096 [RFC2863] McCloghrie, K. and F. Kastenholtz, "The Interfaces Group 1097 MIB ", RFC 2863, June 2000 1099 [RFC3031] Rosen, E., Viswanathan, A., and R. Callon, 1100 "Multiprotocol Label Switching Architecture", RFC 3031, 1101 January 2001. 1103 [RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An 1104 Architecture for Describing Simple Network Management 1105 Protocol (SNMP) Management Frameworks", STD 62, RFC 1106 3411, December 2002. 1108 10.2 Informative References 1110 [RFC3812] Srinivasan, C., Viswanathan, A., and T. Nadeau, 1111 "Multiprotocol Label Switching (MPLS) Traffic 1112 Engineering (TE) Management Information Base (MIB)", RFC 1113 3812, June 2004. 1115 [RFC3813] Srinivasan, C., Viswanathan, A., and T. Nadeau, 1116 "Multiprotocol Label Switching (MPLS) Label Switching 1117 (LSR) Router Management Information Base (MIB)", RFC 1118 3813, June 2004. 1120 [RFC3410] J. Case, R. Mundy, D. pertain, B.Stewart, "Introduction 1121 and Applicability Statement for Internet Standard 1122 Management Framework", RFC 3410, December 2002. 1124 [RFC3811] Nadeau, T., Ed., and J. Cucchiara, Ed., "Definitions of 1125 Textual Conventions (TCs) for Multiprotocol Label 1126 Switching (MPLS) Management", RFC 3811, June 2004. 1128 [RFC5654] Niven-Jenkins, B., Ed., Brungard, D., Ed., Betts, M., 1129 Ed., Sprecher, N., and S. Ueno, "Requirements of an MPLS 1130 Transport Profile", RFC 5654, September 2009. 1132 [TP-ITUIDS] R. Winter, Ed, E. Gray, Ed., H. van Helvoort, and M. 1133 Betts, "MPLS-TP Identifiers Following ITU-T 1134 Conventions", ID draft-ietf-mpls-tp-itu-t-identifiers- 1135 03, March 2012. 1137 [RFC6370] Bocci, M., Swallow, G., and E. Gray, "MPLS-TP 1138 Identifiers", RFC 6370, September 2011. 1140 [RFC6371] Busi, I., Niven-Jenkins, B., and D. Allan, "MPLS-TP OAM 1141 Framework and Overview", RFC 6371, September 2011. 1143 11. Acknowledgments 1144 We wish to thank Muly Ilan, Adrian Farrel and Joan Cucchiara for 1145 their valuable comments on this document. 1147 12. Authors' Addresses 1149 Sam Aldrin 1150 Huawei Technologies, co. 1151 2330 Central Express Way, 1152 Santa Clara, CA 95051, USA 1153 Email: aldrin.ietf@gmail.com 1155 Thomas D. Nadeau 1156 Juniper Networks 1157 10 Technology Park Drive, Westford, MA 01886 1158 Email: tnadeau@juniper.net 1160 Venkatesan Mahalingam 1161 Dell Inc. 1162 350 Holger way, San Jose, CA, USA 1163 Email: venkat.mahalingams@gmail.com 1165 Kannan KV Sampath 1166 Aricent 1167 India 1168 Email: Kannan.Sampath@aricent.com 1170 Ping Pan 1171 Infinera 1172 Email: ppan@infinera.com 1174 Sami Boutros 1175 Cisco Systems, Inc. 1176 3750 Cisco Way 1177 San Jose, California 95134 1178 USA 1179 Email: sboutros@cisco.com