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