idnits 2.17.1 draft-ietf-mpls-tp-linear-protection-mib-12.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (February 17, 2017) is 2587 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 MPLS Working Group Kingston Smiler Selvaraj 3 Internet-Draft IpInfusion 4 Intended status: Standards Track Venkatesan Mahalingam 5 Expires: August 21, 2017 Dell Inc. 6 Daniel King 7 Old Dog Consulting 8 Sam Aldrin 9 Google, Inc. 10 Jeong-dong Ryoo 11 ETRI 12 February 17, 2017 14 MPLS Transport Profile Linear Protection MIB 15 draft-ietf-mpls-tp-linear-protection-mib-12 17 Abstract 19 This memo defines a portion of the Management Information Base (MIB) 20 for use with network management protocols. In particular it defines 21 objects for managing Multiprotocol Label Switching-Transport Profile 22 (MPLS-TP) Linear Protection. 24 Status of This Memo 26 This Internet-Draft is submitted in full conformance with the 27 provisions of BCP 78 and BCP 79. 29 Internet-Drafts are working documents of the Internet Engineering 30 Task Force (IETF). Note that other groups may also distribute 31 working documents as Internet-Drafts. The list of current Internet- 32 Drafts is at http://datatracker.ietf.org/drafts/current/. 34 Internet-Drafts are draft documents valid for a maximum of six months 35 and may be updated, replaced, or obsoleted by other documents at any 36 time. It is inappropriate to use Internet-Drafts as reference 37 material or to cite them other than as "work in progress." 39 This Internet-Draft will expire on August 21, 2017. 41 Copyright Notice 43 Copyright (c) 2017 IETF Trust and the persons identified as the 44 document authors. All rights reserved. 46 This document is subject to BCP 78 and the IETF Trust's Legal 47 Provisions Relating to IETF Documents 48 (http://trustee.ietf.org/license-info) in effect on the date of 49 publication of this document. Please review these documents 50 carefully, as they describe your rights and restrictions with respect 51 to this document. Code Components extracted from this document must 52 include Simplified BSD License text as described in Section 4.e of 53 the Trust Legal Provisions and are provided without warranty as 54 described in the Simplified BSD License. 56 Table of Contents 58 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 59 2. The Internet-Standard Management Framework . . . . . . . . . 3 60 3. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 3 61 4. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 3 62 5. Structure of the MIB Module . . . . . . . . . . . . . . . . . 4 63 5.1. Textual Conventions . . . . . . . . . . . . . . . . . . . 4 64 5.2. The MPLS-TP Linear Protection Subtree . . . . . . . . . . 4 65 5.3. The Notifications Subtree . . . . . . . . . . . . . . . . 4 66 5.4. The Table Structures . . . . . . . . . . . . . . . . . . 5 67 6. Relationship to Other MIB Modules . . . . . . . . . . . . . . 6 68 6.1. Relationship to the MPLS OAM Identifiers MIB Module . . . 6 69 7. Example of Protection Switching Configuration . . . . . . . . 6 70 8. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 8 71 9. Security Considerations . . . . . . . . . . . . . . . . . . . 38 72 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 40 73 11. Contributing Authors . . . . . . . . . . . . . . . . . . . . 40 74 12. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 40 75 13. References . . . . . . . . . . . . . . . . . . . . . . . . . 40 76 13.1. Normative References . . . . . . . . . . . . . . . . . . 40 77 13.2. Informative References . . . . . . . . . . . . . . . . . 42 78 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 43 80 1. Introduction 82 This memo defines a portion of the Management Information Base (MIB) 83 for use with network management protocols. In particular it defines 84 objects for managing Multiprotocol Label Switching-Transport Profile 85 (MPLS-TP) Linear Protection. 87 This MIB module should be used for configuring and managing the MPLS- 88 TP linear protection for MPLS-TP Label Switched Paths (LSPs). 90 At the time of writing, Simple Network Management Protocol (SNMP) SET 91 is no longer recommended as a way to configure Multiprotocol Label 92 Switching (MPLS) networks as was described in RFC 3812 [RFC3812]. 93 However, since the MIB module specified in this document is intended 94 to work in parallel with the MIB module for MPLS specified in 95 [RFC3812] and the MIB module for MPLS-TP Operations, Administration, 96 and Maintenance (OAM) identifiers in RFC 7697 [RFC7697], certain 97 objects defined here are specified with MAX-ACCESS of read-write or 98 read-create so that specifications of the base tables in [RFC3812] 99 and [RFC7697] and the new MIB module in this document are consistent. 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 RFC 3410 [RFC3410]. 107 Managed objects are accessed via a virtual information store, termed 108 the MIB. MIB objects are generally accessed through the SNMP. 109 Objects in the MIB are defined using the mechanisms defined in the 110 Structure of Management Information (SMI). This memo specifies a MIB 111 module that is compliant to the SMIv2, which is described in STD 58, 112 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 113 [RFC2580]. 115 3. Conventions 117 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 118 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 119 document are to be interpreted as described in BCP 14, RFC 2119 120 [RFC2119]. 122 4. Overview 124 RFC 6378 [RFC6378] defines the protocol to provide a linear 125 protection switching mechanism for MPLS-TP for a point-to-point LSP 126 within the protection domain bounded by the end points of the LSP. 127 RFC 7271 [RFC7271] describes alternative mechanisms to perform some 128 of the functions defined in [RFC6378], and also defines additional 129 mechanisms, in order to provide operator control and experience that 130 more closely models the behavior of linear protection seen in other 131 transport networks. Two modes are defined for MPLS-TP linear 132 protection switching: Protection State Coordination (PSC) mode and 133 Automatic Protection Switching (APS) mode as specified in [RFC6378] 134 and [RFC7271], respectively. The detailed protocol specification of 135 MPLS transport profile linear protection is described in [RFC6378] 136 and [RFC7271]. 138 This document specifies a MIB module for the Label Edge Router (LER) 139 that supports MPLS-TP linear protection as described in [RFC6378] and 140 [RFC7271]. Objects defined in the document are generally applied to 141 both PSC and APS modes. If an object is valid for a particular mode 142 only, it is noted in the description for the object. 144 5. Structure of the MIB Module 146 5.1. Textual Conventions 148 The following new textual conventions are defined in this document: 150 o MplsLpsReq: This textual convention describes an object that 151 stores the PSC Request field of the PSC control packet. 153 o MplsLpsFpathPath: This textual convention describes an object that 154 stores the Fault Path (FPath) field and Data Path (Path) field of 155 the PSC control packet. 157 o MplsLpsCommand: This textual convention describes an object that 158 allows a user to perform any action over a protection domain. 160 o MplsLpsState: This textual convention describes an object that 161 stores the current state of the PSC state machine. 163 5.2. The MPLS-TP Linear Protection Subtree 165 MPLS-LPS-MIB is the MIB module defined in this document, and it is 166 put under mplsStdMIB [RFC3811]. 168 5.3. The Notifications Subtree 170 Notifications are defined to inform the management station about 171 switchover, provisioning mismatches, and protocol failures of the 172 linear protection domain. The following notifications are defined 173 for this purpose: 175 o The notification, mplsLpsEventSwitchover is to inform the 176 management station about the switchover of the active path. 178 o The notification, mplsLpsEventRevertiveMismatch is to inform the 179 management station about the provisioning mismatch in the 180 revertive mode across the end point of the protection domain. 182 o The notification, mplsLpsEventProtecTypeMismatch is to inform the 183 management station about the provisioning mismatch in protection 184 type, representing both bridge and switching types, across the end 185 point of the protection domain. 187 o The notification, mplsLpsEventCapabilitiesMismatch is to inform 188 the management station about the provisioning mismatch in 189 Capabilities TLVs across the end point of the protection domain. 191 o The notification, mplsLpsEventPathConfigMismatch is to inform the 192 management station about the provisioning mismatch in the 193 protection path configuration for PSC communication. 195 o The notification, mplsLpsEventFopNoResponse is to inform the 196 management station about the failure of protocol due to a lack of 197 response to a traffic switchover request in 50 ms. 199 o The notification, mplsLpsEventFopTimeout is to inform the 200 management station about the failure of protocol due to no 201 protocol message received during at least 3.5 times the long PSC 202 message interval. 204 5.4. The Table Structures 206 The MPLS-TP linear protection MIB module has four tables. The tables 207 are as follows 209 o mplsLpsConfigTable 211 This table is used to configure MPLS-TP linear protection domains. 212 An MPLS-TP linear protection domain (or a protection domain) is 213 identified by mplsLpsConfigDomainIndex. A protection domain 214 consists of two LERs and the working and protection paths that 215 connect the two LERs. The objects in this table are used to 216 configure properties that are specific to the protection domain. 217 Two Maintenance Entities (MEs) MUST be defined for each protection 218 domain: one for the working path and the other for the protection 219 path. Therefore, two entries of the mplsLpsMeConfigTable, which 220 is for configuring the MEs used in protection switching, are 221 associated to one entry in this table. 223 o mplsLpsStatusTable 225 This table provides the current status information of MPLS-TP 226 linear protection domains that have been configured on the system. 227 The entries of mplsLpsStatusTable have an AUGMENTS relationship 228 with the entries of mplsLpsConfigTable. When a protection domain 229 is configured or deleted in the mplsLpsConfigTable, then the 230 corresponding row of that session in the mplsLpsStatusTable is, 231 respectively, automatically created or deleted. 233 o mplsLpsMeConfigTable 235 This table is used to associate MEs to the protection domain. 236 Each protection domain requires two MEs. One entry in the 237 mplsLpsConfigTable is associated with two entries in this table: 238 one for the working path and the other for the protection path of 239 the protection domain. The mplsLpsMeConfigPath object in this 240 table indicates that the path is either working or protection. 241 The ME is identified by mplsOamIdMegIndex, mplsOamIdMeIndex and 242 mplsOamIdMeMpIndex, which are the same index values as the entry 243 in the mplsOamIdMeTable defined in [RFC7697]. The relationship 244 with the mplsOamIdMeTable is described in Section 6.1. 246 o mplsLpsMeStatusTable 248 This table provides the current information about protection 249 status of MEs that have been configured on the system. When an ME 250 configured or deleted in the mplsLpsMeConfigTable, then the 251 corresponding row of that session in the mplsLpsMeStatusTable is, 252 respectively, automatically created or deleted. 254 6. Relationship to Other MIB Modules 256 6.1. Relationship to the MPLS OAM Identifiers MIB Module 258 Entries in the mplsOamIdMeTable [RFC7697] are extended by entries in 259 the mplsLpsMeConfigTable. Note that the nature of the 'extends' 260 relationship is a sparse augmentation so that the entry in the 261 mplsLpsMeConfigTable has the same index values as the entry in the 262 mplsOamIdMeTable. Each time that an entry is created in the 263 mplsOamIdMeTable for which the LER supports MPLS-TP linear 264 protection, a row is created automatically in the 265 mplsLpsMeConfigTable. 267 When a point-to-point transport path needs to be monitored, one ME is 268 needed for the path and one entry in the mplsOamIdMeTable will be 269 created. But, the ME entry in the mplsOamIdMeTable may or may not 270 participate in protection switching. If an ME participates in 271 protection switching, an entry in mplsLpsMeConfigTable MUST be 272 created, and the objects in the entry indicates which protection 273 domain this ME belongs to and whether this ME is for either working 274 path or protection path. If the ME does not participate in 275 protection switching, an entry in mplsLpsMeConfigTable does not need 276 to be created. 278 7. Example of Protection Switching Configuration 280 This example considers the protection domain configuration on an LER 281 to provide protection for a co-routed bidirectional MPLS tunnel. For 282 the working and protection paths of the protection domain, two 283 Maintenance Entity Groups (MEGs) need to be configured and each MEG 284 contains one ME for a point-to-point transport path. For more 285 information on mplsOamIdMegTable and mplsOamIdMeTable, see [RFC7697]. 287 Although the example described in this section shows a way to 288 configure linear protection for MPLS-TP tunnels, this also indicates 289 how the MIB values would be returned if they had been configured by 290 alternative means. 292 The following table configures a protection domain. 294 In mplsLpsConfigTable: 295 mplsLpsConfigEntry ::= SEQUENCE 296 { 297 -- Protection Domain index (Index to the table) 298 mplsLpsConfigDomainIndex = 3, 299 -- Protection Domain name 300 mplsLpsConfigDomainName = "LPDomain3", 301 mplsLpsConfigMode = psc (1), 302 mplsLpsConfigProtectionType = oneColonOneBidirectional (2), 303 -- Mandatory parameters needed to activate the row go here 304 mplsLpsConfigRowStatus = createAndGo (4) 305 } 307 The following table associates the MEs with the protection domain. 309 In mplsLpsMeConfigTable: 310 MplsLpsMeConfigEntry ::= SEQUENCE 311 { 312 -- MEG index (Index to the table) 313 mplsOamIdMegIndex = 1, 314 -- ME index (Index to the table) 315 mplsOamIdMeIndex = 1, 316 -- MP index (Index to the table) 317 mplsOamIdMeMpIndex = 1, 318 -- Protection Domain this ME belongs to 319 mplsLpsMeConfigDomain = 3, 320 -- Configuration state 321 mplsLpsMeConfigPath = working(1) 322 } 323 { 324 -- MEG index (Index to the table) 325 mplsOamIdMegIndex = 2, 326 -- ME index (Index to the table) 327 mplsOamIdMeIndex = 2, 328 -- MP index (Index to the table) 329 mplsOamIdMeMpIndex = 2, 330 -- Protection Domain this ME belongs to 331 mplsLpsMeConfigDomain = 3, 332 -- Configuration state 333 mplsLpsMeConfigPath = protection(2) 334 } 336 8. Definitions 338 This MIB module makes reference to the following documents: 339 [RFC2578], [RFC2579], [RFC2580], [RFC3289], [RFC3411], [RFC3811], 340 [RFC6378], [RFC7271], [RFC7697], [G8121], and [G8151]. 342 MPLS-LPS-MIB DEFINITIONS ::= BEGIN 344 IMPORTS 345 MODULE-IDENTITY, NOTIFICATION-TYPE, OBJECT-TYPE, 346 Counter32, Unsigned32 347 FROM SNMPv2-SMI -- RFC 2578 349 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 350 FROM SNMPv2-CONF -- RFC 2580 352 TEXTUAL-CONVENTION, RowStatus, TimeStamp, StorageType, TruthValue 353 FROM SNMPv2-TC -- RFC 2579 355 SnmpAdminString 356 FROM SNMP-FRAMEWORK-MIB -- RFC 3411 358 IndexIntegerNextFree 359 FROM DIFFSERV-MIB -- RFC 3289 361 mplsStdMIB 362 FROM MPLS-TC-STD-MIB -- RFC 3811 364 mplsOamIdMegIndex, mplsOamIdMeIndex, mplsOamIdMeMpIndex 365 FROM MPLS-OAM-ID-STD-MIB; -- RFC 7697 367 mplsLpsMIB MODULE-IDENTITY 368 LAST-UPDATED "201702170000Z" -- February 17, 2017 369 ORGANIZATION "Multiprotocol Label Switching (MPLS) Working Group" 370 CONTACT-INFO 371 " 372 Kingston Smiler Selvaraj 373 IP Infusion 374 RMZ Centennial 375 Mahadevapura Post 376 Bangalore - 560048 India 377 EMail: kingstonsmiler@gmail.com 379 Venkatesan Mahalingam 380 Dell Inc. 381 5450 Great America Parkway, 382 Santa Clara, CA 95054, USA 383 Email: venkat.mahalingams@gmail.com 384 Daniel King 385 Old Dog Consulting 386 UK 387 Email:daniel@olddog.co.uk 389 Sam Aldrin 390 Google, Inc. 391 1600 Amphitheatre Parkway 392 Mountain View, CA 393 USA 394 Email: aldrin.ietf@gmail.com 396 Jeong-dong Ryoo 397 ETRI 398 218 Gajeong-ro 399 Yuseong-gu, Daejeon 34129 400 South Korea 401 Email:ryoo@etri.re.kr 402 " 403 DESCRIPTION 404 "This management information module supports the 405 configuration and management of MPLS-TP linear 406 protection domains. " 407 REVISION 408 "201702170000Z" -- February 17, 2017 409 DESCRIPTION 410 "MPLS-TP Protection Switching Domain objects for LSP 411 MEPs" 413 ::= { mplsStdMIB xxx } -- xxx to be replaced with 414 -- correct value 416 -- Top level components of this MIB module. 417 -- Notifications 418 mplsLpsNotifications 419 OBJECT IDENTIFIER ::= { mplsLpsMIB 0 } 421 -- tables, scalars 422 mplsLpsObjects 423 OBJECT IDENTIFIER ::= { mplsLpsMIB 1 } 425 -- conformance 426 mplsLpsConformance 427 OBJECT IDENTIFIER ::= { mplsLpsMIB 2 } 429 MplsLpsReq ::= TEXTUAL-CONVENTION 430 STATUS current 431 DESCRIPTION 432 "This Textual Convention describes an object that stores 433 the PSC Request field of the PSC control packet. The values 434 are as follows: 436 noRequest 437 No Request 439 doNotRevert 440 Do Not Revert 442 reverseRequest 443 Reverse Request 445 exercise 446 Exercise 448 waitToRestore 449 Wait-to-Restore 451 manualSwitch 452 Manual Switch 454 signalDegrade 455 Signal Degrade (SD) 457 signalFail 458 Signal Fail (SF) 460 forcedSwitch 461 Forced Switch 463 lockoutOfProtection 464 Lockout of Protection" 465 REFERENCE 466 "Section 4.2.2 of RFC6378 and Section 8 of RFC7271" 467 SYNTAX INTEGER { 468 noRequest (0), 469 doNotRevert (1), 470 reverseRequest (2), 471 exercise (3), 472 waitToRestore (4), 473 manualSwitch (5), 474 signalDegrade (7), 475 signalFail (10), 476 forcedSwitch (12), 477 lockoutOfProtection (14) 478 } 480 MplsLpsFpathPath ::= TEXTUAL-CONVENTION 481 DISPLAY-HINT "1x:" 482 STATUS current 483 DESCRIPTION 484 "This Textual Convention describes an object that stores 485 the Fault Path (FPath) field and Data Path (Path) field of 486 the PSC control packet. 488 FPath is located in the first octet and Path is 489 located in the second octet. 491 The value and the interpretation of FPath field is as follows: 493 2-255 494 for future extensions 496 1 497 the anomaly condition is on the working path 499 0 500 the anomaly condition is on the protection path 502 The value and the interpretation of Path field is as follows: 504 2-255 505 for future extensions 507 1 508 protection path is transporting user data traffic 510 0 511 protection path is not transporting user data traffic " 512 REFERENCE 513 "Section 4.2.5 and 4.2.6 of RFC6378" 514 SYNTAX OCTET STRING (SIZE (2)) 516 MplsLpsCommand ::= TEXTUAL-CONVENTION 517 STATUS current 518 DESCRIPTION 519 "This command allows a user to perform any action over a 520 protection domain. If the protection command cannot be 521 executed because an equal or higher priority request is 522 in effect, an inconsistentValue error is returned. 524 The command values are: 526 noCmd 527 This value should be returned by a read request when no 528 command has been written to the object in question since 529 initialization. This value may not be used in a write 530 operation. If noCmd is used in a write operation a 531 wrongValue error is returned. 533 clear 534 Clears all of the commands listed below for the protection 535 domain. 537 lockoutOfProtection 538 Prevents switching traffic to the protection path. 540 forcedSwitch 541 Switches traffic from the working path to the protection path. 543 manualSwitchToWork 544 Switches traffic from the protection path to the working path. 546 manualSwitchToProtect 547 Switches traffic from the working path to the protection path. 549 exercise 550 Used to verify the correct operation of the PSC communication 551 and the integrity of the protection path. This command is not 552 applicable to the PSC mode. 554 freeze 555 This command freezes the protection state and is a local 556 command that is not signaled to the remote node. 557 This command is not applicable to the PSC mode. 559 clearfreeze 560 Clears the local freeze. This command is not applicable to 561 the PSC mode. " 562 REFERENCE 563 "Sections 3.1 and 3.2 of RFC6378 and Sections 4.3 and 6 of 564 RFC7271" 565 SYNTAX INTEGER { 566 noCmd(1), 567 clear(2), 568 lockoutOfProtection(3), 569 forcedSwitch(4), 570 manualSwitchToWork(5), 571 manualSwitchToProtect(6), 572 exercise(7), 573 freeze(8), 574 clearfreeze(9) 575 } 577 MplsLpsState ::= TEXTUAL-CONVENTION 578 STATUS current 579 DESCRIPTION 580 "This Textual Convention describes an object that stores 581 the current state of the PSC state machine. The values 582 are as follows: 584 normal 585 normal state 587 unavLOlocal 588 Unavailable state due to local LO command. 590 unavSFPlocal 591 Unavailable state due to local SF-P. 593 unavSDPlocal 594 Unavailable state due to local SD-P. 596 unavLOremote 597 Unavailable state due to remote LO message. 599 unavSFPremote 600 Unavailable state due to remote SF-P message. 602 unavSDPremote 603 Unavailable state due to remote SD-P message. 605 protfailSFWlocal 606 Protecting Failure state due to local SF-W. 608 protfailSDWlocal 609 Protecting Failure state due to local SD-W. 611 protfailSFWremote 612 Protecting Failure state due to remote SF-W message. 614 protfailSDWremote 615 Protecting Failure state due to remote SD-W message. 617 switadmFSlocal 618 Switching Administrative state due to local FS command. 619 Same as Protecting administrative state due to local FS 620 command in the PSC mode. 622 switadmMSWlocal 623 Switching Administrative state due to local MS-W command 624 switadmMSPlocal 625 Switching Administrative state due to local MS-P command. 626 Same as Protecting administrative state due to local MS 627 command in the PSC mode 629 switadmFSremote 630 Switching Administrative state due to remote FS message. 631 Same as Protecting administrative state due to remote FS 632 message in the PSC mode. 634 switadmMSWremote 635 Switching Administrative state due to remote MS-W message 637 switadmMSPremote 638 Switching Administrative state due to remote MS-P message. 639 Same as Protecting administrative state due to remote MS 640 message in the PSC mode. 642 wtr 643 Wait-to-Restore state 645 dnr 646 Do-not-Revert state 648 exerLocal 649 Exercise state due to local EXER command. 651 exerRemote 652 Exercise state due to remote EXER message." 653 REFERENCE 654 "Section 11 of RFC7271" 656 SYNTAX INTEGER { 657 normal (1), 658 unavLOlocal (2), 659 unavSFPlocal (3), 660 unavSDPlocal (4), 661 unavLOremote (5), 662 unavSFPremote (6), 663 unavSDPremote (7), 664 protfailSFWlocal (8), 665 protfailSDWlocal (9), 666 protfailSFWremote (10), 667 protfailSDWremote (11), 668 switadmFSlocal (12), 669 switadmMSWlocal (13), 670 switadmMSPlocal (14), 671 switadmFSremote (15), 672 switadmMSWremote (16), 673 switadmMSPremote (17), 674 wtr (18), 675 dnr (19), 676 exerLocal (20), 677 exerRemote (21) 678 } 680 -- Start of 681 -- MPLS-TP Linear Protection Switching Configuration Table. 682 -- This table supports the addition, configuration and deletion 683 -- of MPLS-TP linear protection domains. 685 mplsLpsConfigDomainIndexNext OBJECT-TYPE 686 SYNTAX IndexIntegerNextFree (0..4294967295) 687 MAX-ACCESS read-only 688 STATUS current 689 DESCRIPTION 690 "This object contains an unused value for 691 mplsLpsConfigDomainIndex, or a zero to indicate 692 that none exist. Negative values are not allowed, 693 as they do not correspond to valid values of 694 mplsLpsConfigDomainIndex." 695 ::= { mplsLpsObjects 1 } 697 mplsLpsConfigTable OBJECT-TYPE 698 SYNTAX SEQUENCE OF MplsLpsConfigEntry 699 MAX-ACCESS not-accessible 700 STATUS current 701 DESCRIPTION 702 "This table lists the MPLS-TP linear protection domains that 703 have been configured on the system. 704 An entry is created by a network operator who wants to run 705 the MPLS-TP linear protection protocol for the protection 706 domain." 707 ::= { mplsLpsObjects 2 } 709 mplsLpsConfigEntry OBJECT-TYPE 710 SYNTAX MplsLpsConfigEntry 711 MAX-ACCESS not-accessible 712 STATUS current 713 DESCRIPTION 714 "A conceptual row in the mplsLpsConfigTable." 715 INDEX { mplsLpsConfigDomainIndex } 716 ::= { mplsLpsConfigTable 1 } 718 MplsLpsConfigEntry ::= SEQUENCE { 719 mplsLpsConfigDomainIndex Unsigned32, 720 mplsLpsConfigDomainName SnmpAdminString, 721 mplsLpsConfigMode INTEGER, 722 mplsLpsConfigProtectionType INTEGER, 723 mplsLpsConfigRevertive INTEGER, 724 mplsLpsConfigSdThreshold Unsigned32, 725 mplsLpsConfigSdBadSeconds Unsigned32, 726 mplsLpsConfigSdGoodSeconds Unsigned32, 727 mplsLpsConfigWaitToRestore Unsigned32, 728 mplsLpsConfigHoldOff Unsigned32, 729 mplsLpsConfigContinualTxInterval Unsigned32, 730 mplsLpsConfigRapidTxInterval Unsigned32, 731 mplsLpsConfigCommand MplsLpsCommand, 732 mplsLpsConfigCreationTime TimeStamp, 733 mplsLpsConfigRowStatus RowStatus, 734 mplsLpsConfigStorageType StorageType 735 } 737 mplsLpsConfigDomainIndex OBJECT-TYPE 738 SYNTAX Unsigned32 (1..4294967295) 739 MAX-ACCESS not-accessible 740 STATUS current 741 DESCRIPTION 742 "Index for the conceptual row identifying a protection domain. 743 Operators should obtain new values for row creation in this 744 table by reading mplsLpsConfigDomainIndexNext. 746 When the value of this object is the same as the value of 747 mplsLpsMeConfigDomain, that means that the 748 mplsLpsMeConfigDomain is defined as either the working path 749 or the protection path for this protection domain." 750 ::= { mplsLpsConfigEntry 1 } 752 mplsLpsConfigDomainName OBJECT-TYPE 753 SYNTAX SnmpAdminString (SIZE (0..32)) 754 MAX-ACCESS read-create 755 STATUS current 756 DESCRIPTION 757 "Textual name represents the MPLS-TP linear protection domain. 758 It facilitates easy administrative identification of 759 each protection domain." 760 DEFVAL {""} 761 ::= { mplsLpsConfigEntry 2 } 763 mplsLpsConfigMode OBJECT-TYPE 764 SYNTAX INTEGER { 765 psc(1), 766 aps(2) 767 } 769 MAX-ACCESS read-create 770 STATUS current 771 DESCRIPTION 772 "The mode of MPLS-TP linear protection mechanism. This can 773 either be PSC or APS as follows: 775 PSC 776 The Protection State Coordination mode as described in 777 RFC 6378. 779 APS 780 The Automatic Protection Switching mode as described in 781 RFC 7271. 783 This object may not be modified if the associated 784 mplsLpsConfigRowStatus object is equal to active(1). 786 The value of this object is not supposed to be changed 787 during operation. When the value should be changed, 788 the protection processes in both LERs MUST be 789 restarted with the same new value. 791 In case that this value is changed at one LER during 792 operation, the LER will generate PSC packets with a new 793 Capabilities TLV value. As a consequence, this will 794 result in mplsLpsEventCapabilitiesMismatch notification 795 at both LERs. " 796 REFERENCE 797 "Sections 9.2 and 10 of RFC7271" 798 DEFVAL {psc} 799 ::= { mplsLpsConfigEntry 3 } 801 mplsLpsConfigProtectionType OBJECT-TYPE 802 SYNTAX INTEGER { 803 onePlusOneUnidirectional (1), 804 oneColonOneBidirectional (2), 805 onePlusOneBidirectional (3) 806 } 807 MAX-ACCESS read-create 808 STATUS current 809 DESCRIPTION 810 "The protection architecture type of the Protection domain. 811 This represents both bridge type, which can be 812 either permanent bridge (1+1) or selector bridge (1:1), 813 and switching scheme, which can be 814 either unidirectional or bidirectional. 816 1+1 817 In the 1+1 protection scheme, a fully dedicated protection 818 path is allocated. Data traffic is copied and fed 819 at the source to both the working and the protection path. 820 The traffic on the working and the protection paths is 821 transmitted simultaneously to the sink of the protection 822 domain, where selection between the working and protection 823 paths is performed 825 1:1 826 In the 1:1 scheme, a protection path is allocated to 827 protect against a defect, failure, or a degradation in the 828 working path. In normal conditions, data traffic is 829 transmitted over the working path, while the protection path 830 functions in the idle state. If there is a defect on the 831 working path or a specific administrative request, 832 traffic is switched to the protection path. 834 bidirectional 835 In bidirectional protection scheme, both the directions 836 will be switched simultaneously even if the fault applies 837 to only one direction of the path. 839 unidirectional 840 In unidirectional protection scheme protection switching 841 will be performed independently for each direction of a 842 bidirectional transport path. 844 This object may not be modified if the associated 845 mplsLpsConfigRowStatus object is equal to active(1). " 846 REFERENCE 847 "Section 4.2.3 of RFC6378" 848 DEFVAL {oneColonOneBidirectional} 849 ::= { mplsLpsConfigEntry 4 } 851 mplsLpsConfigRevertive OBJECT-TYPE 852 SYNTAX INTEGER { nonrevertive(1), revertive(2) } 853 MAX-ACCESS read-create 854 STATUS current 855 DESCRIPTION 856 "This object represents the reversion mode of the linear 857 protection domain. The reversion mode of protection 858 mechanism may be either revertive or non-revertive. 860 nonrevertive 861 In non-revertive mode, after a service has been recovered, 862 traffic will be forwarded on the protection path. 864 revertive 865 In revertive mode, after a service has been recovered, 866 traffic will be redirected back onto the original working 867 path. 869 This object may not be modified if the associated 870 mplsLpsConfigRowStatus object is equal to active(1). " 871 REFERENCE 872 "Section 4.2.4 of RFC6378" 873 DEFVAL { revertive } 874 ::= { mplsLpsConfigEntry 5 } 876 mplsLpsConfigSdThreshold OBJECT-TYPE 877 SYNTAX Unsigned32 (0..100) 878 MAX-ACCESS read-create 879 STATUS current 880 DESCRIPTION 881 "This object holds the threshold value of the Signal Degrade 882 (SD) defect in percent. In order to detect the SD defect, 883 the MPLS-TP packet loss measurement (LM) is performed 884 every second. 886 If either the packet loss is negative (i.e., there are more 887 packets received than transmitted) or the packet loss ratio 888 (lost packets/transmitted packets) in percent is greater than 889 this threshold value, a Bad Second is declared. 890 Otherwise, a Good Second is declared. 892 The SD defect is detected if there are 893 mplsLpsConfigSdBadSeconds consecutive Bad Seconds 894 and cleared if there are 895 mplsLpsConfigSdGoodSeconds consecutive Good Seconds. 897 This object may be modified if the associated 898 mplsLpsConfigRowStatus object is equal to active(1)." 899 REFERENCE 900 "Clause 6.1.3.3 of [G8121] and Table 8-1 of [G8151]" 901 DEFVAL { 30 } 902 ::= { mplsLpsConfigEntry 6 } 904 mplsLpsConfigSdBadSeconds OBJECT-TYPE 905 SYNTAX Unsigned32 (2..10) 906 UNITS "seconds" 907 MAX-ACCESS read-create 908 STATUS current 909 DESCRIPTION 910 "This object holds the number of Bad Seconds to detect the SD. 912 If the number of consecutive Bad Seconds reaches this value, 913 the SD defect is detected and used as an input to 914 the protection switching process. 916 This object may be modified if the associated 917 mplsLpsConfigRowStatus object is equal to active(1). " 918 REFERENCE 919 "Clause 6.1.3.3 of [G8121] and Table 8-1 of [G8151]" 920 DEFVAL { 10 } 921 ::= { mplsLpsConfigEntry 7 } 923 mplsLpsConfigSdGoodSeconds OBJECT-TYPE 924 SYNTAX Unsigned32 (2..10) 925 UNITS "seconds" 926 MAX-ACCESS read-create 927 STATUS current 928 DESCRIPTION 929 "This object holds the number of Good Seconds to declare 930 the clearance of SD defect. 932 After an SD defect occurs at a path, if the number of 933 consecutive Good Seconds reaches this value for the 934 degraded path, the clearance of SD defect is declared and 935 used as an input to the protection switching process. 937 This object may be modified if the associated 938 mplsLpsConfigRowStatus object is equal to active(1)." 939 REFERENCE 940 "Clause 6.1.3.3 of [G8121] and Table 8-1 of [G8151]" 941 DEFVAL { 10 } 942 ::= { mplsLpsConfigEntry 8 } 944 mplsLpsConfigWaitToRestore OBJECT-TYPE 945 SYNTAX Unsigned32 (5..12) 946 UNITS "minutes" 947 MAX-ACCESS read-create 948 STATUS current 949 DESCRIPTION 950 "This object holds the Wait To Restore timer value in minutes, 951 and can be configured in 1 minute steps between 5 and 952 12 minutes. 954 The WTR timer is used to delay reversion of PSC state 955 to Normal state when recovering from a failure 956 condition on the working path when the protection 957 domain is configured for revertive behavior 959 This object may not be modified if the associated 960 mplsLpsConfigRowStatus object is equal to active(1)." 962 REFERENCE 963 "Section 3.5 of RFC6378" 964 DEFVAL { 5 } 965 ::= { mplsLpsConfigEntry 9 } 967 mplsLpsConfigHoldOff OBJECT-TYPE 968 SYNTAX Unsigned32 (0..100) 969 UNITS "deciseconds" 970 MAX-ACCESS read-create 971 STATUS current 972 DESCRIPTION 973 "The hold-off time in deciseconds. Represents the time 974 between SF/SD condition detection and declaration of 975 an SF/SD request to the protection switching logic. 976 It is intended to avoid unnecessary switching when a lower- 977 layer protection mechanism is in place. 978 Can be configured in steps of 100 milli-seconds. 980 When a new defect or more severe defect occurs at 981 the active path (the path from which the selector selects 982 the user data traffic) and this value is non-zero, 983 the hold-off timer will be started. A defect on the standby 984 path (the path from which the selector does not select the 985 user data traffic) does not trigger the start of the hold-off 986 timer as there is no need for a traffic switchover. 988 This object may not be modified if the associated 989 mplsLpsConfigRowStatus object is equal to active(1). " 990 REFERENCE 991 "Section 3.1 of RFC6378" 992 DEFVAL { 0 } 993 ::= { mplsLpsConfigEntry 10 } 995 mplsLpsConfigContinualTxInterval OBJECT-TYPE 996 SYNTAX Unsigned32 (1..20) 997 UNITS "seconds" 998 MAX-ACCESS read-create 999 STATUS current 1000 DESCRIPTION 1001 "The Continual Tx Time in Seconds. Represents the time 1002 interval to send the continual LPS packet to the other 1003 end based on the current state. 1005 This object may not be modified if the associated 1006 mplsLpsConfigRowStatus object is equal to active(1). " 1007 REFERENCE 1008 "Section 4.1 of RFC6378" 1009 DEFVAL { 5 } 1010 ::= { mplsLpsConfigEntry 11 } 1012 mplsLpsConfigRapidTxInterval OBJECT-TYPE 1013 SYNTAX Unsigned32 (1000..20000) 1014 UNITS "micro-seconds" 1015 MAX-ACCESS read-create 1016 STATUS current 1017 DESCRIPTION 1018 "The Rapid Tx interval in micro-Seconds. Represents the time 1019 interval to send the LPS packet to the other end, when 1020 there is a change in state of linear protection domain due 1021 to local input. The default value is 3.3 milli-seconds 1022 which is 3300 micro-seconds 1024 This object may not be modified if the associated 1025 mplsLpsConfigRowStatus object is equal to active(1). " 1026 REFERENCE 1027 "Section 4.1 of RFC6378" 1028 DEFVAL { 3300 } 1029 ::= { mplsLpsConfigEntry 12 } 1031 mplsLpsConfigCommand OBJECT-TYPE 1032 SYNTAX MplsLpsCommand 1033 MAX-ACCESS read-create 1034 STATUS current 1035 DESCRIPTION 1036 "Allows the initiation of an operator command on 1037 the protection domain. 1039 When read this object returns the last command written 1040 or noCmd if no command has been written 1041 since initialization. The return of the last command 1042 written does not imply that this command is currently in 1043 effect. This request may have been preempted by a higher 1044 priority local or remote request. 1046 This object may be modified if the associated 1047 mplsLpsConfigRowStatus object is equal to active(1). " 1048 REFERENCE 1049 "Sections 3.1 and 3.2 of RFC6378 and Sections 4.3 and 6 of 1050 RFC7271" 1051 DEFVAL { noCmd } 1052 ::= { mplsLpsConfigEntry 13 } 1054 mplsLpsConfigCreationTime OBJECT-TYPE 1055 SYNTAX TimeStamp 1056 MAX-ACCESS read-only 1057 STATUS current 1058 DESCRIPTION 1059 "The value of sysUpTime at the time the row was created." 1060 ::= { mplsLpsConfigEntry 14 } 1062 mplsLpsConfigRowStatus OBJECT-TYPE 1063 SYNTAX RowStatus 1064 MAX-ACCESS read-create 1065 STATUS current 1066 DESCRIPTION 1067 "This represents the status of the MPLS-TP linear 1068 protection domain entry. This variable is used to 1069 create, modify, and/or delete a row in this table." 1070 ::= { mplsLpsConfigEntry 15 } 1072 mplsLpsConfigStorageType OBJECT-TYPE 1073 SYNTAX StorageType 1074 MAX-ACCESS read-create 1075 STATUS current 1076 DESCRIPTION 1077 "The storage type for this conceptual row. 1078 Conceptual rows having the value 'permanent' need not 1079 allow write-access to any columnar objects in the row." 1080 DEFVAL { nonVolatile } 1081 ::= { mplsLpsConfigEntry 16 } 1083 -- 1084 -- MPLS-TP Linear Protection Switching Status Table 1085 -- This table provides Protection Switching domain statistics. 1086 -- 1088 mplsLpsStatusTable OBJECT-TYPE 1089 SYNTAX SEQUENCE OF MplsLpsStatusEntry 1090 MAX-ACCESS not-accessible 1091 STATUS current 1092 DESCRIPTION 1093 "This table provides status information about MPLS-TP 1094 linear protection domains that have been configured 1095 on the system." 1096 ::= { mplsLpsObjects 3 } 1098 mplsLpsStatusEntry OBJECT-TYPE 1099 SYNTAX MplsLpsStatusEntry 1100 MAX-ACCESS not-accessible 1101 STATUS current 1102 DESCRIPTION 1103 "A conceptual row in the mplsLpsStatusTable." 1104 AUGMENTS { mplsLpsConfigEntry } 1105 ::= { mplsLpsStatusTable 1 } 1107 MplsLpsStatusEntry ::= SEQUENCE { 1108 mplsLpsStatusState MplsLpsState, 1109 mplsLpsStatusReqRcv MplsLpsReq, 1110 mplsLpsStatusReqSent MplsLpsReq, 1111 mplsLpsStatusFpathPathRcv MplsLpsFpathPath, 1112 mplsLpsStatusFpathPathSent MplsLpsFpathPath, 1113 mplsLpsStatusRevertiveMismatch TruthValue, 1114 mplsLpsStatusProtecTypeMismatch TruthValue, 1115 mplsLpsStatusCapabilitiesMismatch TruthValue, 1116 mplsLpsStatusPathConfigMismatch TruthValue, 1117 mplsLpsStatusFopNoResponses Counter32, 1118 mplsLpsStatusFopTimeouts Counter32 1119 } 1121 mplsLpsStatusState OBJECT-TYPE 1122 SYNTAX MplsLpsState 1123 MAX-ACCESS read-only 1124 STATUS current 1125 DESCRIPTION 1126 "The current state of the PSC state machine." 1127 REFERENCE 1128 "Section 11 of RFC7271" 1129 ::= { mplsLpsStatusEntry 1 } 1131 mplsLpsStatusReqRcv OBJECT-TYPE 1132 SYNTAX MplsLpsReq 1133 MAX-ACCESS read-only 1134 STATUS current 1135 DESCRIPTION 1136 "The current value of the PSC Request field received on 1137 the most recent PSC packet." 1138 REFERENCE 1139 "Section 4.2 of RFC6378" 1140 ::= { mplsLpsStatusEntry 2 } 1142 mplsLpsStatusReqSent OBJECT-TYPE 1143 SYNTAX MplsLpsReq 1144 MAX-ACCESS read-only 1145 STATUS current 1146 DESCRIPTION 1147 "The current value of the PSC Request field sent on the 1148 most recent PSC packet." 1149 REFERENCE 1150 "Section 4.2 of RFC6378" 1151 ::= { mplsLpsStatusEntry 3 } 1153 mplsLpsStatusFpathPathRcv OBJECT-TYPE 1154 SYNTAX MplsLpsFpathPath 1155 MAX-ACCESS read-only 1156 STATUS current 1157 DESCRIPTION 1158 "The current value of the FPath and Path fields received 1159 on the most recent PSC packet." 1160 REFERENCE 1161 "Section 4.2 of RFC6378" 1162 ::= { mplsLpsStatusEntry 4 } 1164 mplsLpsStatusFpathPathSent OBJECT-TYPE 1165 SYNTAX MplsLpsFpathPath 1166 MAX-ACCESS read-only 1167 STATUS current 1168 DESCRIPTION 1169 "The current value of the FPath and Path fields sent 1170 on the most recent PSC packet." 1171 REFERENCE 1172 "Section 4.2 of RFC6378" 1173 ::= { mplsLpsStatusEntry 5 } 1175 mplsLpsStatusRevertiveMismatch OBJECT-TYPE 1176 SYNTAX TruthValue 1177 MAX-ACCESS read-only 1178 STATUS current 1179 DESCRIPTION 1180 "This object indicates the provisioning mismatch in 1181 revertive mode across the protection domain end points. 1182 The value of this object becomes true when a PSC message with 1183 incompatible Revertive field is received, or false 1184 when a PSC message with compatible Revertive field is 1185 received. " 1186 REFERENCE 1187 "Section 12 of RFC7271" 1188 ::= { mplsLpsStatusEntry 6 } 1190 mplsLpsStatusProtecTypeMismatch OBJECT-TYPE 1191 SYNTAX TruthValue 1192 MAX-ACCESS read-only 1193 STATUS current 1194 DESCRIPTION 1195 "This object indicates the provisioning mismatch in 1196 protection type, representing both bridge and switching types, 1197 across the protection domain end points. 1198 The value of this object becomes true when a PSC message with 1199 incompatible PT field is received, or false 1200 when a PSC message with compatible PT field is received. " 1201 REFERENCE 1202 "Section 12 of RFC7271" 1204 ::= { mplsLpsStatusEntry 7 } 1206 mplsLpsStatusCapabilitiesMismatch OBJECT-TYPE 1207 SYNTAX TruthValue 1208 MAX-ACCESS read-only 1209 STATUS current 1210 DESCRIPTION 1211 "This object indicates the provisioning mismatch in 1212 Capabilities TLVs across the protection domain end points. 1213 The value of this object becomes true when a PSC message with 1214 incompatible Capabilities TLV field is received, or false 1215 when a PSC message with compatible Capabilities TLV field is 1216 received. 1218 The Capabilities TLV with 0xF8000000 indicates that the APS 1219 mode is used for MPLS-TP linear protection mechanism, 1220 whereas PSC mode uses either the Capabilities TLV with Ox0 1221 or no existence of the Capabilities TLV." 1222 REFERENCE 1223 "Section 12 of RFC7271" 1224 ::= { mplsLpsStatusEntry 8 } 1226 mplsLpsStatusPathConfigMismatch OBJECT-TYPE 1227 SYNTAX TruthValue 1228 MAX-ACCESS read-only 1229 STATUS current 1230 DESCRIPTION 1231 "This object indicates the provisioning mismatch in the 1232 protection path configuration for PSC communication across 1233 the protection domain end points. 1235 The value of this object becomes true when a PSC message is 1236 received from the working path, or false when a PSC message 1237 is received from the protection path." 1238 REFERENCE 1239 "Section 12 of RFC7271" 1240 ::= { mplsLpsStatusEntry 9 } 1242 mplsLpsStatusFopNoResponses OBJECT-TYPE 1243 SYNTAX Counter32 1244 MAX-ACCESS read-only 1245 STATUS current 1246 DESCRIPTION 1247 "This object holds the number of occurrences of the failure 1248 of protocol due to a lack of response to a traffic switchover 1249 request within in 50 ms. 1251 When there is a traffic switchover due to a local request, 1252 a 50 ms timer is started to detect the failure of protocol 1253 due to no response. If there is no PSC message is received 1254 with the same Path value as in the transmitted PSC message 1255 until the 50 ms timer expires, the failure of protocol due to 1256 no response occurs." 1257 REFERENCE 1258 "Section 12 of RFC7271" 1259 ::= { mplsLpsStatusEntry 10 } 1261 mplsLpsStatusFopTimeouts OBJECT-TYPE 1262 SYNTAX Counter32 1263 MAX-ACCESS read-only 1264 STATUS current 1265 DESCRIPTION 1266 "This object holds the number of occurrences of the failure 1267 of protocol due to no PSC message received during at least 1268 3.5 times the long PSC message interval. 1270 When no PSC message is received on the protection path during 1271 at least 3.5 times the long PSC message interval and there 1272 is no defect on the protection path, the failure of protocol 1273 due to no PSC message occurs." 1274 REFERENCE 1275 "Section 12 of RFC7271" 1276 ::= { mplsLpsStatusEntry 11 } 1278 -- MPLS-TP Linear Protection ME Association Configuration Table 1279 -- This table supports the addition, configuration and deletion 1280 -- of MPLS-TP Linear Protection Maintenance Entities in protection 1281 -- domains. 1283 mplsLpsMeConfigTable OBJECT-TYPE 1284 SYNTAX SEQUENCE OF MplsLpsMeConfigEntry 1285 MAX-ACCESS not-accessible 1286 STATUS current 1287 DESCRIPTION 1288 "This table lists Maintenance Association that have been 1289 configured in Protection domains." 1290 ::= { mplsLpsObjects 4 } 1292 mplsLpsMeConfigEntry OBJECT-TYPE 1293 SYNTAX MplsLpsMeConfigEntry 1294 MAX-ACCESS not-accessible 1295 STATUS current 1296 DESCRIPTION 1297 "A conceptual row in the mplsLpsMeConfigTable. There is 1298 a sparse relationship between the conceptual rows of 1299 this table and mplsOamIdMeTable. 1301 Each time that an entry is created in the mplsOamIdMeTable 1302 for which the LER supports MPLS-TP linear protection, 1303 a row is created automatically in the mplsLpsMeConfigTable. 1305 An entry of this table is related to a single entry in 1306 mplsOamIdMeTable. When a point-to-point transport path 1307 needs to be monitored, one ME is needed for the path 1308 and one entry in the mplsOamIdMeTable will be created. 1309 But, the ME entry in the mplsOamIdMeTable may or may not 1310 participate in protection switching. 1312 If an ME participates in protection switching, 1313 an entry in mplsLpsMeConfigTable MUST be created, 1314 and the objects in the entry indicates 1315 which protection domain this ME belongs to and 1316 whether this ME is for either working path or protection path. 1318 If the ME does not participate in protection switching, 1319 an entry in mplsLpsMeConfigTable does not need to be created. " 1320 INDEX {mplsOamIdMegIndex, mplsOamIdMeIndex, mplsOamIdMeMpIndex} 1321 ::= { mplsLpsMeConfigTable 1 } 1323 MplsLpsMeConfigEntry ::= SEQUENCE { 1324 mplsLpsMeConfigDomain Unsigned32, 1325 mplsLpsMeConfigPath INTEGER 1326 } 1328 mplsLpsMeConfigDomain OBJECT-TYPE 1329 SYNTAX Unsigned32 (0..4294967295) 1330 MAX-ACCESS read-create 1331 STATUS current 1332 DESCRIPTION 1333 "This object holds the value of protection domain index wherein 1334 this ME is included. If this ME is not part of any 1335 protection domain then this object contains value 0. 1337 When the value of this object is the same as the value of 1338 mplsLpsConfigDomainIndex, that means that the object is 1339 defined as either the working path or the protection path 1340 of the protection domain corresponding to 1341 mplsLpsConfigDomainIndex." 1342 DEFVAL { 0 } 1343 ::= { mplsLpsMeConfigEntry 1 } 1345 mplsLpsMeConfigPath OBJECT-TYPE 1346 SYNTAX INTEGER { working(1), protection(2) } 1347 MAX-ACCESS read-create 1348 STATUS current 1349 DESCRIPTION 1350 "This object represents whether the ME is configured 1351 as either the working path or the protection path" 1352 REFERENCE 1353 "Section 4.3 of RFC6378" 1354 ::= { mplsLpsMeConfigEntry 2 } 1356 -- 1357 -- MPLS Linear Protection ME Status Table 1358 -- This table provides Protection Switching ME statistics. 1359 -- 1361 mplsLpsMeStatusTable OBJECT-TYPE 1362 SYNTAX SEQUENCE OF MplsLpsMeStatusEntry 1363 MAX-ACCESS not-accessible 1364 STATUS current 1365 DESCRIPTION 1366 "This table contains status information of all the MEs 1367 that are included in MPLS-TP linear protection domains." 1368 ::= { mplsLpsObjects 5 } 1370 mplsLpsMeStatusEntry OBJECT-TYPE 1371 SYNTAX MplsLpsMeStatusEntry 1372 MAX-ACCESS not-accessible 1373 STATUS current 1374 DESCRIPTION 1375 "A conceptual row in the mplsLpsMeStatusTable." 1376 AUGMENTS { mplsLpsMeConfigEntry } 1377 ::= { mplsLpsMeStatusTable 1 } 1379 MplsLpsMeStatusEntry ::= SEQUENCE { 1380 mplsLpsMeStatusCurrent BITS, 1381 mplsLpsMeStatusSignalDegrades Counter32, 1382 mplsLpsMeStatusSignalFailures Counter32, 1383 mplsLpsMeStatusSwitchovers Counter32, 1384 mplsLpsMeStatusLastSwitchover TimeStamp, 1385 mplsLpsMeStatusSwitchoverSeconds Counter32 1386 } 1388 mplsLpsMeStatusCurrent OBJECT-TYPE 1389 SYNTAX BITS { 1390 localSelectTraffic(0), 1391 localSD(1), 1392 localSF(2) 1393 } 1394 MAX-ACCESS read-only 1395 STATUS current 1396 DESCRIPTION 1397 "Indicates the current state of the ME. 1399 localSelectTraffic 1400 This bit indicates that traffic is being selected from 1401 this ME. 1403 localSD 1404 This bit implies that local signal degrade condition is 1405 in effect on this ME / path. 1407 localSF 1408 This bit implies that local signal failure condition is 1409 in effect on this ME / path." 1410 REFERENCE 1411 "Section 4.3 of RFC6378 and Section 7 of RFC7271" 1412 ::= { mplsLpsMeStatusEntry 1 } 1414 mplsLpsMeStatusSignalDegrades OBJECT-TYPE 1415 SYNTAX Counter32 1416 MAX-ACCESS read-only 1417 STATUS current 1418 DESCRIPTION 1419 "Represents the count of Signal Degrade conditions. 1420 For the detection and clearance of Signal Degrade, 1421 see the description of mplsLpsConfigSdThreshold." 1422 REFERENCE 1423 "Section 7 of RFC7271" 1424 ::= { mplsLpsMeStatusEntry 2 } 1426 mplsLpsMeStatusSignalFailures OBJECT-TYPE 1427 SYNTAX Counter32 1428 MAX-ACCESS read-only 1429 STATUS current 1430 DESCRIPTION 1431 "Represents the count of Signal failure conditions. 1432 This condition occurs when the OAM running on this ME 1433 detects the Signal Fail event." 1434 REFERENCE 1435 "Section 4.3 of RFC6378" 1436 ::= { mplsLpsMeStatusEntry 3 } 1438 mplsLpsMeStatusSwitchovers OBJECT-TYPE 1439 SYNTAX Counter32 1440 MAX-ACCESS read-only 1441 STATUS current 1442 DESCRIPTION 1443 "Represents the count of SwitchOvers happened in this ME. 1445 When the mplsLpsMeConfigPath is working, this object will 1446 return the number of times that traffic has been switched 1447 from this working path to the protection path. 1449 When the mplsLpsMeConfigPath is protection, this object 1450 will return the number of times that traffic has been 1451 switched back to the working path from this protection path." 1452 REFERENCE 1453 "Section 4.3 of RFC6378" 1454 ::= { mplsLpsMeStatusEntry 4 } 1456 mplsLpsMeStatusLastSwitchover OBJECT-TYPE 1457 SYNTAX TimeStamp 1458 MAX-ACCESS read-only 1459 STATUS current 1460 DESCRIPTION 1461 "This object holds the value of sysUpTime wherein the 1462 last switchover happened. 1464 When the mplsLpsMeConfigPath is working, this object 1465 will return the value of sysUpTime when traffic was switched 1466 from this path to the protection path. 1468 If traffic has never switched to the protection path, the 1469 value 0 will be returned. 1471 When the mplsLpsMeConfigPath is protection, this object 1472 will return the value of sysUpTime the last time that 1473 traffic was switched back to the working path from this path. 1474 If no traffic has ever switched back to the working path from 1475 this protection path, the value 0 will be returned." 1476 REFERENCE 1477 "Section 4.3 of RFC6378" 1478 ::= { mplsLpsMeStatusEntry 5 } 1480 mplsLpsMeStatusSwitchoverSeconds OBJECT-TYPE 1481 SYNTAX Counter32 1482 UNITS "seconds" 1483 MAX-ACCESS read-only 1484 STATUS current 1485 DESCRIPTION 1486 "The cumulative Protection Switching Duration (PSD) time 1487 in seconds. 1489 For the working path, this is the cumulative number of 1490 seconds that traffic was selected from the protection path. 1492 For the protection path, this is the cumulative number 1493 of seconds that the working path has been used to 1494 select traffic." 1495 REFERENCE 1496 "Section 4.3 of RFC6378" 1497 ::= { mplsLpsMeStatusEntry 6 } 1499 mplsLpsNotificationEnable OBJECT-TYPE 1500 SYNTAX BITS { 1501 switchover(0), 1502 revertiveMismatch(1), 1503 protecTypeMismatch(2), 1504 capabilitiesMismatch(3), 1505 pathConfigMismatch(4), 1506 fopNoResponse(5), 1507 fopTimeout(6) 1508 } 1509 MAX-ACCESS read-write 1510 STATUS current 1511 DESCRIPTION 1512 "Provides the ability to enable and disable notifications 1513 defined in this MIB module. 1515 switchover 1516 Indicates mplsLpsEventSwitchover notifications should be 1517 generated. 1519 revertiveMismatch 1520 Indicates mplsLpsEventRevertiveMismatch notifications 1521 should be generated. 1523 protecTypeMismatch 1524 Indicates mplsLpsEventProtecTypeMismatch notifications 1525 should be generated. 1527 capabilitiesMismatch 1528 Indicates mplsLpsEventCapabilitiesMismatch notifications 1529 should be generated. 1531 pathConfigMismatch 1532 Indicates mplsLpsEventPathConfigMismatch notifications 1533 should be generated. 1535 fopNoResponse 1536 Indicates mplsLpsEventFopNoResponse notifications 1537 should be generated. 1539 fopTimeout 1540 Indicates mplsLpsEventFopTimeout notifications 1541 should be generated." 1542 REFERENCE 1543 "Section 12 of RFC7271" 1544 DEFVAL { { } } 1545 ::= { mplsLpsObjects 6 } 1547 -- MPLS Linear Protection EVENTS 1549 mplsLpsEventSwitchover NOTIFICATION-TYPE 1550 OBJECTS { mplsLpsMeStatusSwitchovers, mplsLpsMeStatusCurrent } 1551 STATUS current 1552 DESCRIPTION 1553 "An mplsLpsEventSwitchover notification is sent when the 1554 value of an instance of mplsLpsMeStatusSwitchovers 1555 increments." 1556 ::= { mplsLpsNotifications 1 } 1558 mplsLpsEventRevertiveMismatch NOTIFICATION-TYPE 1559 OBJECTS { mplsLpsStatusRevertiveMismatch } 1560 STATUS current 1561 DESCRIPTION 1562 "An mplsLpsEventRevertiveMismatch notification is sent when 1563 the value of mplsLpsStatusRevertiveMismatch changes." 1564 ::= { mplsLpsNotifications 2 } 1566 mplsLpsEventProtecTypeMismatch NOTIFICATION-TYPE 1567 OBJECTS { mplsLpsStatusProtecTypeMismatch } 1568 STATUS current 1569 DESCRIPTION 1570 "An mplsLpsEventProtecTypeMismatch notification is sent 1571 when the value of mplsLpsStatusProtecTypeMismatch changes." 1572 ::= { mplsLpsNotifications 3 } 1574 mplsLpsEventCapabilitiesMismatch NOTIFICATION-TYPE 1575 OBJECTS { mplsLpsStatusCapabilitiesMismatch } 1576 STATUS current 1577 DESCRIPTION 1578 "An mplsLpsEventCapabilitiesMismatch notification is sent 1579 when the value of mplsLpsStatusCapabilitiesMismatch changes." 1580 ::= { mplsLpsNotifications 4 } 1582 mplsLpsEventPathConfigMismatch NOTIFICATION-TYPE 1583 OBJECTS { mplsLpsStatusPathConfigMismatch } 1584 STATUS current 1585 DESCRIPTION 1586 "An mplsLpsEventPathConfigMismatch notification is sent 1587 when the value of mplsLpsStatusPathConfigMismatch changes." 1589 ::= { mplsLpsNotifications 5 } 1591 mplsLpsEventFopNoResponse NOTIFICATION-TYPE 1592 OBJECTS { mplsLpsStatusFopNoResponses } 1593 STATUS current 1594 DESCRIPTION 1595 "An mplsLpsEventFopNoResponse notification is sent when the 1596 value of mplsLpsStatusFopNoResponses increments." 1597 ::= { mplsLpsNotifications 6 } 1599 mplsLpsEventFopTimeout NOTIFICATION-TYPE 1600 OBJECTS { mplsLpsStatusFopTimeouts } 1601 STATUS current 1602 DESCRIPTION 1603 "An mplsLpsEventFopTimeout notification is sent when the 1604 value of mplsLpsStatusFopTimeouts increments." 1605 ::= { mplsLpsNotifications 7 } 1607 -- End of Notifications. 1609 -- Module Compliance. 1611 mplsLpsCompliances 1612 OBJECT IDENTIFIER ::= { mplsLpsConformance 1 } 1614 mplsLpsGroups 1615 OBJECT IDENTIFIER ::= { mplsLpsConformance 2 } 1617 -- Compliance requirement for fully compliant implementations. 1619 mplsLpsModuleFullCompliance MODULE-COMPLIANCE 1620 STATUS current 1621 DESCRIPTION 1622 "Compliance statement for agents that provide full 1623 support for MPLS-LPS-MIB. Such devices can 1624 provide linear protection and also be configured using 1625 this MIB module." 1626 MODULE -- This module. 1627 MANDATORY-GROUPS { 1628 mplsLpsScalarGroup, 1629 mplsLpsTableGroup, 1630 mplsLpsMeTableGroup 1631 } 1632 GROUP mplsLpsNotificationGroup 1633 DESCRIPTION 1634 "This group is only mandatory for those 1635 implementations which can efficiently implement 1636 the notifications contained in this group." 1638 ::= { mplsLpsCompliances 1 } 1640 -- Compliance requirement for read-only implementations 1642 mplsLpsModuleReadOnlyCompliance MODULE-COMPLIANCE 1643 STATUS current 1644 DESCRIPTION 1645 "Compliance statement for agents that only provide 1646 read-only support for the MPLS-LPS-MIB module." 1648 MODULE -- this module 1650 MANDATORY-GROUPS { 1651 mplsLpsScalarGroup, 1652 mplsLpsTableGroup, 1653 mplsLpsMeTableGroup 1654 } 1655 GROUP mplsLpsNotificationGroup 1656 DESCRIPTION 1657 "This group is only mandatory for those 1658 implementations which can efficiently implement 1659 the notifications contained in this group." 1661 -- mplsLpsConfigTable 1663 OBJECT mplsLpsConfigMode 1664 MIN-ACCESS read-only 1665 DESCRIPTION 1666 "Write access is not required." 1668 OBJECT mplsLpsConfigProtectionType 1669 MIN-ACCESS read-only 1670 DESCRIPTION 1671 "Write access is not required." 1673 OBJECT mplsLpsConfigRevertive 1674 MIN-ACCESS read-only 1675 DESCRIPTION 1676 "Write access is not required." 1678 OBJECT mplsLpsConfigSdThreshold 1679 MIN-ACCESS read-only 1680 DESCRIPTION 1681 "Write access is not required." 1683 OBJECT mplsLpsConfigSdBadSeconds 1684 MIN-ACCESS read-only 1685 DESCRIPTION 1686 "Write access is not required." 1688 OBJECT mplsLpsConfigSdGoodSeconds 1689 MIN-ACCESS read-only 1690 DESCRIPTION 1691 "Write access is not required." 1693 OBJECT mplsLpsConfigWaitToRestore 1694 MIN-ACCESS read-only 1695 DESCRIPTION 1696 "Write access is not required." 1698 OBJECT mplsLpsConfigContinualTxInterval 1699 MIN-ACCESS read-only 1700 DESCRIPTION 1701 "Write access is not required." 1703 OBJECT mplsLpsConfigRapidTxInterval 1704 MIN-ACCESS read-only 1705 DESCRIPTION 1706 "Write access is not required." 1708 OBJECT mplsLpsConfigCommand 1709 MIN-ACCESS read-only 1710 DESCRIPTION 1711 "Write access is not required." 1713 OBJECT mplsLpsConfigRowStatus 1714 SYNTAX RowStatus { active(1) } 1715 MIN-ACCESS read-only 1716 DESCRIPTION 1717 "Write access is not required." 1719 OBJECT mplsLpsConfigStorageType 1720 MIN-ACCESS read-only 1721 DESCRIPTION 1722 "Write access is not required." 1724 -- mplsLpsMeConfigTable 1726 OBJECT mplsLpsMeConfigDomain 1727 MIN-ACCESS read-only 1728 DESCRIPTION 1729 "Write access is not required." 1731 OBJECT mplsLpsMeConfigPath 1732 MIN-ACCESS read-only 1733 DESCRIPTION 1734 "Write access is not required." 1736 ::= { mplsLpsCompliances 2 } 1738 -- Units of conformance. 1740 mplsLpsScalarGroup OBJECT-GROUP 1741 OBJECTS { 1742 mplsLpsConfigDomainIndexNext, 1743 mplsLpsNotificationEnable 1744 } 1745 STATUS current 1746 DESCRIPTION 1747 "Collection of objects needed for MPLS Linear Protection." 1748 ::= { mplsLpsGroups 1 } 1750 mplsLpsTableGroup OBJECT-GROUP 1751 OBJECTS { 1752 mplsLpsConfigDomainName, 1753 mplsLpsConfigRowStatus, 1754 mplsLpsConfigMode, 1755 mplsLpsConfigProtectionType, 1756 mplsLpsConfigRevertive, 1757 mplsLpsConfigSdThreshold, 1758 mplsLpsConfigSdBadSeconds, 1759 mplsLpsConfigSdGoodSeconds, 1760 mplsLpsConfigWaitToRestore, 1761 mplsLpsConfigHoldOff, 1762 mplsLpsConfigContinualTxInterval, 1763 mplsLpsConfigRapidTxInterval, 1764 mplsLpsConfigCommand, 1765 mplsLpsConfigCreationTime, 1766 mplsLpsConfigStorageType, 1767 mplsLpsStatusState, 1768 mplsLpsStatusReqRcv, 1769 mplsLpsStatusReqSent, 1770 mplsLpsStatusFpathPathRcv, 1771 mplsLpsStatusFpathPathSent, 1772 mplsLpsStatusRevertiveMismatch, 1773 mplsLpsStatusProtecTypeMismatch, 1774 mplsLpsStatusCapabilitiesMismatch, 1775 mplsLpsStatusPathConfigMismatch, 1776 mplsLpsStatusFopNoResponses, 1777 mplsLpsStatusFopTimeouts 1778 } 1779 STATUS current 1780 DESCRIPTION 1781 "Collection of objects needed for MPLS Linear Protection 1782 configuration and statistics." 1783 ::= { mplsLpsGroups 2 } 1785 mplsLpsMeTableGroup OBJECT-GROUP 1786 OBJECTS { 1787 mplsLpsMeConfigDomain, 1788 mplsLpsMeConfigPath, 1789 mplsLpsMeStatusCurrent, 1790 mplsLpsMeStatusSignalDegrades, 1791 mplsLpsMeStatusSignalFailures, 1792 mplsLpsMeStatusSwitchovers, 1793 mplsLpsMeStatusLastSwitchover, 1794 mplsLpsMeStatusSwitchoverSeconds 1795 } 1796 STATUS current 1797 DESCRIPTION 1798 "Collection of objects needed for MPLS Linear Protection 1799 ME configuration and statistics." 1800 ::= { mplsLpsGroups 3 } 1802 mplsLpsNotificationGroup NOTIFICATION-GROUP 1803 NOTIFICATIONS { 1804 mplsLpsEventSwitchover, 1805 mplsLpsEventRevertiveMismatch, 1806 mplsLpsEventProtecTypeMismatch, 1807 mplsLpsEventCapabilitiesMismatch, 1808 mplsLpsEventPathConfigMismatch, 1809 mplsLpsEventFopNoResponse, 1810 mplsLpsEventFopTimeout 1811 } 1812 STATUS current 1813 DESCRIPTION 1814 "Collection of objects needed to implement notifications." 1815 ::= { mplsLpsGroups 4 } 1817 -- MPLS-LPS-MIB module ends 1818 END 1820 9. Security Considerations 1822 There are a number of management objects defined in this MIB module 1823 with a MAX-ACCESS clause of read-write and/or read-create. Such 1824 objects may be considered sensitive or vulnerable in some networks in 1825 a non-secure environment without proper protection can have a 1826 negative effect on network operations. These are the tables and 1827 objects and their sensitivity/vulnerability: 1829 o mplsLpsConfigTable is used to configure MPLS-TP linear protection 1830 domains. Improper manipulation of the objects in this table may 1831 result in different behaviors than network operators have 1832 originally intended, such as delaying traffic switching or causing 1833 a race condition with server layer protection after network 1834 failure (mplsLpsConfigHoldOff), delaying or speeding up reversion 1835 after recovering network failure (mplsLpsConfigWaitToRestore), 1836 unexpected traffic switching (mplsLpsConfigCommand), or 1837 discontinuance of operation of a protection switching control 1838 process (mplsLpsConfigMode, mplsLpsConfigProtectionType). 1840 o mplsLpsMeConfigTable is used to assign each ME either working or 1841 protection path. Improper manipulation of this object may result 1842 in discontinuance of operation of a protection switching control 1843 process. 1845 o The notification is controlled by mplsLpsNotificationEnable 1846 object. In the case of the discontinuance of a protection 1847 switching control process, network operators may not be notified 1848 if the mplsLpsNotificationEnable object is compromised. 1850 Some of the readable objects in this MIB module (i.e., objects with a 1851 MAX-ACCESS other than not-accessible) may be considered sensitive or 1852 vulnerable in some network environments. It is thus important to 1853 control even GET and/or NOTIFY access to these objects and possibly 1854 to even encrypt the values of these objects when sending them over 1855 the network via SNMP. These are the tables and objects and their 1856 sensitivity/vulnerability: 1858 o mplsLpsStatusTable and mplsLpsMeStatusTable collectively show the 1859 history and current status of the MPLS-TP linear protection 1860 domains. They can be used to estimate the performances and 1861 qualities of the network being operated with the MPLS-TP linear 1862 protection. If an administrator does not want to reveal this 1863 information, then these tables should be considered sensitive/ 1864 vulnerable. 1866 SNMP versions prior to SNMPv3 did not include adequate security. 1867 Even if the network itself is secure (for example by using IPsec), 1868 there is no control as to who on the secure network is allowed to 1869 access and GET/SET (read/change/create/delete) the objects in this 1870 MIB module. 1872 Implementations SHOULD provide the security features described by the 1873 SNMPv3 framework (see [RFC3410]), and implementations claiming 1874 compliance to the SNMPv3 standard MUST include full support for 1875 authentication and privacy via the User-based Security Model (USM) 1876 RFC 3414 [RFC3414] with the AES cipher algorithm RFC 3826 [RFC3826]. 1878 Implementations MAY also provide support for the Transport Security 1879 Model (TSM) RFC 5591 [RFC5591] in combination with a secure transport 1880 such as SSH RFC 5592 [RFC5592] or TLS/DTLS RFC 6353 [RFC6353]. 1882 Further, deployment of SNMP versions prior to SNMPv3 is not 1883 recommended. Instead, it is RECOMMENDED to deploy SNMPv3 and to 1884 enable cryptographic security. It is then a customer/operator 1885 responsibility to ensure that the SNMP entity giving access to an 1886 instance of this MIB module is properly configured to give access to 1887 the objects only to those principals (users) that have legitimate 1888 rights to indeed GET or SET (change/create/delete) them. 1890 10. IANA Considerations 1892 IANA is requested to assign an OID for the MIB module from the "MIB 1893 Transmission Group - MPLS STD" sub-registry of the "Internet-standard 1894 MIB - Transmission Group" registry for the MPLS Linear Protection MIB 1895 module specified in this document. 1897 11. Contributing Authors 1899 Vishwas Manral 1900 Nano Sec 1901 599 Fairchild Drive 1902 Mountain View, CA 1903 USA 1905 EMail: vishwas@nanosec.io 1907 12. Acknowledgments 1909 The authors wish to thank Joan Cucchiara for her review as MIB 1910 Doctor. Joan's detailed comments were of great help for improving 1911 the quality of this document. 1913 The authors would also like to thank Loa Andersson and Adrian Farrel 1914 for their valuable comments and suggestion on this document. 1916 13. References 1918 13.1. Normative References 1920 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1921 Requirement Levels", BCP 14, RFC 2119, 1922 DOI 10.17487/RFC2119, March 1997, 1923 . 1925 [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. 1926 Schoenwaelder, Ed., "Structure of Management Information 1927 Version 2 (SMIv2)", STD 58, RFC 2578, 1928 DOI 10.17487/RFC2578, April 1999, 1929 . 1931 [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. 1932 Schoenwaelder, Ed., "Textual Conventions for SMIv2", 1933 STD 58, RFC 2579, DOI 10.17487/RFC2579, April 1999, 1934 . 1936 [RFC2580] McCloghrie, K., Ed., Perkins, D., Ed., and J. 1937 Schoenwaelder, Ed., "Conformance Statements for SMIv2", 1938 STD 58, RFC 2580, DOI 10.17487/RFC2580, April 1999, 1939 . 1941 [RFC3289] Baker, F., Chan, K., and A. Smith, "Management Information 1942 Base for the Differentiated Services Architecture", 1943 RFC 3289, DOI 10.17487/RFC3289, May 2002, 1944 . 1946 [RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An 1947 Architecture for Describing Simple Network Management 1948 Protocol (SNMP) Management Frameworks", STD 62, RFC 3411, 1949 DOI 10.17487/RFC3411, December 2002, 1950 . 1952 [RFC3414] Blumenthal, U. and B. Wijnen, "User-based Security Model 1953 (USM) for version 3 of the Simple Network Management 1954 Protocol (SNMPv3)", STD 62, RFC 3414, 1955 DOI 10.17487/RFC3414, December 2002, 1956 . 1958 [RFC3811] Nadeau, T., Ed. and J. Cucchiara, Ed., "Definitions of 1959 Textual Conventions (TCs) for Multiprotocol Label 1960 Switching (MPLS) Management", RFC 3811, 1961 DOI 10.17487/RFC3811, June 2004, 1962 . 1964 [RFC3826] Blumenthal, U., Maino, F., and K. McCloghrie, "The 1965 Advanced Encryption Standard (AES) Cipher Algorithm in the 1966 SNMP User-based Security Model", RFC 3826, 1967 DOI 10.17487/RFC3826, June 2004, 1968 . 1970 [RFC5591] Harrington, D. and W. Hardaker, "Transport Security Model 1971 for the Simple Network Management Protocol (SNMP)", 1972 STD 78, RFC 5591, DOI 10.17487/RFC5591, June 2009, 1973 . 1975 [RFC5592] Harrington, D., Salowey, J., and W. Hardaker, "Secure 1976 Shell Transport Model for the Simple Network Management 1977 Protocol (SNMP)", RFC 5592, DOI 10.17487/RFC5592, June 1978 2009, . 1980 [RFC6353] Hardaker, W., "Transport Layer Security (TLS) Transport 1981 Model for the Simple Network Management Protocol (SNMP)", 1982 STD 78, RFC 6353, DOI 10.17487/RFC6353, July 2011, 1983 . 1985 [RFC6378] Weingarten, Y., Ed., Bryant, S., Osborne, E., Sprecher, 1986 N., and A. Fulignoli, Ed., "MPLS Transport Profile (MPLS- 1987 TP) Linear Protection", RFC 6378, DOI 10.17487/RFC6378, 1988 October 2011, . 1990 [RFC7271] Ryoo, J., Ed., Gray, E., Ed., van Helvoort, H., 1991 D'Alessandro, A., Cheung, T., and E. Osborne, "MPLS 1992 Transport Profile (MPLS-TP) Linear Protection to Match the 1993 Operational Expectations of Synchronous Digital Hierarchy, 1994 Optical Transport Network, and Ethernet Transport Network 1995 Operators", RFC 7271, DOI 10.17487/RFC7271, June 2014, 1996 . 1998 [RFC7697] Pan, P., Aldrin, S., Venkatesan, M., Sampath, K., Nadeau, 1999 T., and S. Boutros, "MPLS Transport Profile (MPLS-TP) 2000 Operations, Administration, and Maintenance (OAM) 2001 Identifiers Management Information Base (MIB)", RFC 7697, 2002 DOI 10.17487/RFC7697, January 2016, 2003 . 2005 13.2. Informative References 2007 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, 2008 "Introduction and Applicability Statements for Internet- 2009 Standard Management Framework", RFC 3410, 2010 DOI 10.17487/RFC3410, December 2002, 2011 . 2013 [RFC3812] Srinivasan, C., Viswanathan, A., and T. Nadeau, 2014 "Multiprotocol Label Switching (MPLS) Traffic Engineering 2015 (TE) Management Information Base (MIB)", RFC 3812, 2016 DOI 10.17487/RFC3812, June 2004, 2017 . 2019 [G8121] International Telecommunication Union, "Characteristics of 2020 MPLS-TP equipment functional blocks", ITU-T Recommendation 2021 G.8121/Y.1381, April 2016. 2023 [G8151] International Telecommunication Union, "Management aspects 2024 of the MPLS-TP network element", ITU-T Recommendation 2025 G.8151/Y.1374, January 2015. 2027 Authors' Addresses 2029 Kingston Smiler Selvaraj 2030 IpInfusion 2031 RMZ Centennial 2032 Mahadevapura Post 2033 Bangalore - 560048 2034 India 2036 EMail: kingstonsmiler@gmail.com 2038 Venkatesan Mahalingam 2039 Dell Inc. 2040 5450 Great America Parkway 2041 Santa Clara, CA 95054 2042 USA 2044 EMail: venkat.mahalingams@gmail.com 2046 Daniel King 2047 Old Dog Consulting 2048 UK 2050 EMail: daniel@olddog.co.uk 2052 Sam Aldrin 2053 Google, Inc. 2054 1600 Amphitheatre Parkway 2055 Mountain View, CA 2056 USA 2058 EMail: aldrin.ietf@gmail.com 2059 Jeong-dong Ryoo 2060 ETRI 2061 218 Gajeong-ro 2062 Yuseong-gu, Daejeon 34129 2063 South Korea 2065 EMail: ryoo@etri.re.kr