idnits 2.17.1 draft-ietf-mpls-tp-linear-protection-mib-05.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 03, 2015) is 3182 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Outdated reference: A later version (-11) exists of draft-ietf-mpls-tp-oam-id-mib-08 Summary: 0 errors (**), 0 flaws (~~), 2 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet Engineering Task Force Kingston Smiler Selvaraj 3 Internet-Draft IpInfusion 4 Intended status: Standards Track M.Venkatesan 5 Expires: February 04, 2016 Dell Inc. 6 V. Manral 7 Ionos Corp. 8 Daniel King 9 Old Dog Consulting 10 Sam Aldrin 11 Google, Inc. 12 August 03, 2015 14 MPLS Transport Profile Linear Protection MIB 15 draft-ietf-mpls-tp-linear-protection-mib-05 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 MPLS Transport Profile (MPLS-TP) Linear 22 Protection. 24 Status of This Memo 26 This Internet-Draft is submitted to IETF 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), its areas, and its working groups. Note that 31 other groups may also distribute working documents as Internet- 32 Drafts. 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 The list of current Internet-Drafts can be accessed at 40 http://www.ietf.org/ietf/1id-abstracts.txt. 42 The list of Internet-Draft Shadow Directories can be accessed at 43 http://www.ietf.org/shadow.html. 45 This Internet-Draft will expire on February 04, 2016. 47 Copyright and License Notice 49 Copyright (c) 2015 IETF Trust and the persons identified as the 50 document authors. All rights reserved. 52 This document is subject to BCP 78 and the IETF Trust's Legal 53 Provisions Relating to IETF Documents 54 (http://trustee.ietf.org/license-info) in effect on the date of 55 publication of this document. Please review these documents 56 carefully, as they describe your rights and restrictions with respect 57 to this document. Code Components extracted from this document must 58 include Simplified BSD License text as described in Section 4.e of 59 the Trust Legal Provisions and are provided without warranty as 60 described in the Simplified BSD License. 62 Table of Contents 64 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 65 2. The Internet-Standard Management Framework . . . . . . . . . . 3 66 3. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 3 67 4. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 68 5. Structure of the MIB Module . . . . . . . . . . . . . . . . . 4 69 5.1. Textual Conventions . . . . . . . . . . . . . . . . . . . 4 70 5.2. The MPLS TP Linear Protection Subtree . . . . . . . . . . . 4 71 5.3. The Notifications Subtree . . . . . . . . . . . . . . . . . 4 72 5.4. The Table Structures . . . . . . . . . . . . . . . . . . . 4 73 6. Relationship to Other MIB Modules . . . . . . . . . . . . . . 5 74 6.1. Relationship to the MPLS OAM maintenance identifiers MIB 75 module . . . . . . . . . . . . . . . . . . . . . . . . . . 5 76 7. Example of Protection switching configuration for MPLS-TP TE 77 tunnel . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 78 8. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 7 79 9. Security Considerations . . . . . . . . . . . . . . . . . . . 26 80 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 27 81 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 28 82 11.1. Normative References . . . . . . . . . . . . . . . . . . 28 83 11.2. Informative References . . . . . . . . . . . . . . . . . 29 84 12. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 30 85 13. Author's Address . . . . . . . . . . . . . . . . . . . . . . . 30 87 1. Introduction 89 This memo defines a portion of the Management Information Base (MIB) 90 for use with network management protocols. In particular it defines 91 objects for managing MPLS Transport Profile (MPLS-TP) Linear 92 Protection. 94 This MIB module should be used for configuring and managing the MPLS 95 TP linear protection for MPLS TP LSPs. 97 At the time of writing, SNMP SET is no longer recommended as a way to 98 configure MPLS networks as was described in [RFC3812]. However, 99 since the MIB modules specified in this document are intended to work 100 in parallel with the MIB modules for MPLS specified in [RFC3812], 101 certain objects defined here are specified with MAX-ACCESS of read- 102 write or read-create so that specifications of the base tables in 103 [RFC3812] and the new MIB modules in this document are consistent. 104 Although the examples described in Section 7 specify means to 105 configure OAM identifiers for MPLS-TP tunnels, this should be seen as 106 indicating how the MIB values would be returned in the specified 107 circumstances having been configured by alternative means. 109 2. The Internet-Standard Management Framework 111 For a detailed overview of the documents that describe the current 112 Internet-Standard Management Framework, please refer to section 7 of 113 RFC 3410 [RFC3410]. 115 Managed objects are accessed via a virtual information store, termed 116 the Management Information Base or MIB. MIB objects are generally 117 accessed through the Simple Network Management Protocol (SNMP). 118 Objects in the MIB are defined using the mechanisms defined in the 119 Structure of Management Information (SMI). This memo specifies a MIB 120 module that is compliant to the SMIv2, which is described in STD 58, 121 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 122 [RFC2580]. 124 3. Conventions 126 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 127 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 128 document are to be interpreted as described in RFC 2119 [RFC2119]. 130 4. Overview 132 [RFC6378] defines the protocol to provide a linear protection 133 switching mechanism for MPLS transport profile with protection 134 domain as point-to-point LSP. The detailed protocol specification of 135 MPLS transport profile linear protection is described in [RFC6378]. 136 This document specifies a MIB module for the LER that supports MPLS 137 TP Linear protection and a MIB module that defines textual 138 conventions. 140 5. Structure of the MIB Module 142 5.1. Textual Conventions 144 The following new textual conventions are defined in a separate MIB 145 module in this document 147 MplsLpsReq 148 MplsLpsFpathPath 149 MplsLpsCommand 151 5.2. The MPLS TP Linear Protection Subtree 153 MPLS-LPS-MIB is the MIB module defined in this document, and it is 154 put under mplsStdMIB. 156 5.3. The Notifications Subtree 158 Notifications are defined to inform the management station about 159 switchover and mode mismatch of linear protection switching group. 160 Two notifications are defined for this purpose. The notification, 161 mplsLpsEventSwitchover is to inform the management station about the 162 switchover of the active path and the notification 163 mplsLpsEventModeMismatch is to inform the management station about 164 the mismatch in the revertive mode across the end point of the 165 protection domain. 167 5.4. The Table Structures 169 The MPLS TP Linear protection MIB module has four tables. The tables 170 are as follows 172 o mplsLpsConfigTable 174 This table is used to configure MPLS TP Linear protection 175 switching Group. The protection switching group is identified by 176 mplsLpsConfigGroupName. The other attributes in this table can be 177 used to configure properties that are specific to the protection 178 switching group. 180 o mplsLpsStatusTable 181 This table provides the current status information of mpls linear 182 protection groups that have been configured on the system. When a 183 protection group is configured or deleted in the 184 mplsLpsConfigTable, then the corresponding row of that session in 185 the mplsLpsStatusTable is, respectively, automatically created or 186 deleted. 188 o mplsLpsMeConfigTable 190 This table is used to associate the Maintenance Entities (MEs) to 191 the protection switching group. The ME is identified by 192 mplsOamIdMegIndex, mplsOamIdMeIndex and mplsOamIdMeMpIndex. 194 o mplsLpsMeStatusTable 196 This table provides the current information about the protection 197 state of MEs that have been configured on the system. When a 198 ME configured or deleted in the mplsLpsMeConfigTable, then the 199 corresponding row of that session in the mplsLpsMeStatusTable 200 is, respectively, automatically created or deleted. 202 6. Relationship to Other MIB Modules 204 6.1. Relationship to the MPLS OAM maintenance identifiers MIB module 206 The mplsLpsMeConfigTable entry is extended by entry in the 207 mplsOamIdMeTable [MPLS-OAM-ID-STD-MIB] defined in draft-ietf-mpls-tp- 208 oam-id-mib. Note that the nature of the 'extends' relationship is a 209 sparse augmentation so that the entry in the mplsLpsMeConfigTable has 210 the same index values as the entry in the mplsOamIdMeTable. Each time 211 that an entry is created in the mplsOamIdMeTable for which the LER 212 supports MPLS TP Linear protection a row is created automatically in 213 the mplsLpsMeConfigTable. 215 7. Example of Protection switching configuration for MPLS-TP TE tunnel 217 This example considers the protection group configuration on a 218 head-end LSR to provide protection for a co-routed bidirectional 219 MPLS tunnel. 220 Only relevant objects which are applicable for protection group 221 identifiers of co-routed MPLS tunnel are illustrated here. 223 In mplsOamIdMegTable: 224 { 225 -- MEG index (Index to the table) 226 mplsOamIdMegIndex = 1, 227 mplsOamIdMegName = "MEG1", 228 mplsOamIdMegOperatorType = ipCompatible (1), 229 mplsOamIdMegServiceType = lsp (1), 230 mplsOamIdMegMpLocation = perNode(1), 231 -- Mandatory parameters needed to activate the row go here 232 mplsOamIdMegRowStatus = createAndGo (4) 233 } 235 This will create an entry in the mplsOamIdMegTable to protect 236 the MPLS tunnel. 238 The following ME table is used to associate the path information 239 to a MEG. 241 In mplsOamIdMeTable: 242 { 243 -- ME index (Index to the table) 244 mplsOamIdMeIndex = 1, 245 -- MP index (Index to the table) 246 mplsOamIdMeMpIndex = 1, 247 mplsOamIdMeName = "ME1", 248 mplsOamIdMeMpIfIndex = 0, 249 -- Source MEP id is derived from the IP compatible MPLS 250 -- tunnel 251 mplsOamIdMeSourceMepIndex = 0, 252 -- Source MEP id is derived from the IP compatible MPLS 253 -- tunnel 254 mplsOamIdMeSinkMepIndex = 0, 255 mplsOamIdMeMpType = mep (1), 256 mplsOamIdMeMepDirection = down (2), 257 mplsOamIdMeProactiveOamPhbTCValue = 0, 258 mplsOamIdMeOnDemandOamPhbTCValue = 0, 259 -- RowPointer MUST point to the first accessible column 260 -- of an MPLS tunnel 261 mplsOamIdMeServicePointer = mplsTunnelName.1.1.1.2, 262 -- Mandatory parameters needed to activate the row go here 263 mplsOamIdMeRowStatus = createAndGo (4) 264 } 266 The below table associates the MEs with protection switching 267 groups. 268 In mplsLpsConfigTable: 269 mplsLpsConfigEntry ::= SEQUENCE { 270 -- Group index 271 mplsLpsConfigGroupIndex = 1, 272 mplsLpsConfigGroupName = "PGGroup1", 273 mplsLpsConfigMode = onePlusOne (1), 274 -- Mandatory parameters needed to activate the row go here 275 mplsLpsConfigRowStatus = createAndGo (4) 276 } 277 In mplsLpsMeConfigTable: 278 MplsLpsMeConfigEntry ::= SEQUENCE { 279 -- MEG index (Index to the table) 280 mplsOamIdMegIndex = 1, 281 -- ME index 282 mplsOamIdMeIndex = 1, 283 -- MP index (Index to the table) 284 mplsOamIdMeMpIndex = 1, 285 -- Group index 286 mplsLpsMeConfigGroupIndex = 1, 287 -- Configuration state 288 mplsLpsMeConfigState = primary(1) 289 } 291 8. Definitions 292 MPLS-LPS-MIB DEFINITIONS ::= BEGIN 294 IMPORTS 295 MODULE-IDENTITY, NOTIFICATION-TYPE, OBJECT-TYPE, 296 Gauge32, Counter32, Integer32, Unsigned32 297 FROM SNMPv2-SMI 298 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 299 FROM SNMPv2-CONF -- [RFC2580] 300 TEXTUAL-CONVENTION, RowStatus, 301 TimeStamp, StorageType 302 FROM SNMPv2-TC 303 SnmpAdminString 305 FROM SNMP-FRAMEWORK-MIB 306 mplsStdMIB 307 FROM MPLS-TC-STD-MIB -- [RFC3811] 308 mplsOamIdMegIndex, mplsOamIdMeIndex, mplsOamIdMeMpIndex 309 FROM MPLS-OAM-ID-STD-MIB; 311 mplsLpsMIB MODULE-IDENTITY 312 LAST-UPDATED "201508030000Z" -- August 03, 2015 313 ORGANIZATION "Multiprotocol Label Switching (MPLS) Working Group" 314 CONTACT-INFO 316 " 317 Kingston Smiler 318 IP Infusion 319 RMZ Centennial 320 Mahadevapura Post 321 Bangalore - 560048 India 322 EMail: kingstonsmiler@gmail.com 323 Venkatesan Mahalingam 324 Dell Inc. 325 5450 Great America Parkway, 326 Santa Clara, CA 95054, USA 327 Email: venkat.mahalingams@gmail.com 329 Vishwas Manral 330 Ionos Corp, 331 4100 Moorpark Ave, 332 San Jose, CA 333 Email: vishwas@ionosnetworks.com 335 Daniel King 336 Old Dog Consulting 337 UK 338 Email:daniel@olddog.co.uk 340 Sam Aldrin 341 Google, Inc. 342 1600 Amphitheatre Parkway 343 Mountain View, CA 344 USA 345 Email: aldrin.ietf@gmail.com" 346 DESCRIPTION 347 "This management information module supports the 348 configuration and management of MPLS TP linear 349 protection groups. " 350 REVISION 351 "201508030000Z" -- August 03, 2015 352 DESCRIPTION 353 "MPLS Protection Switching Group objects for LSP 354 MEPs" 356 ::= { mplsStdMIB xxx } -- xxx to be replaced with 357 -- correct value 359 -- Top level components of this MIB module. 360 -- Notifications 361 mplsLpsNotifications 362 OBJECT IDENTIFIER ::= { mplsLpsMIB 0 } 363 -- tables, scalars 364 mplsLpsObjects 365 OBJECT IDENTIFIER ::= { mplsLpsMIB 1 } 366 -- conformance 368 mplsLpsConformance 369 OBJECT IDENTIFIER ::= { mplsLpsMIB 2 } 371 MplsLpsReq ::= TEXTUAL-CONVENTION 372 STATUS current 373 DESCRIPTION 374 "This Textual Convention describes an object that stores 375 the PSC Request field of the PSC control packet. The values 376 are as follows 378 1110 Lockout of Protection 379 1100 Forced Switch 380 1010 Signal Fail (SF) 381 0111 Signal Degrade (SD) 382 0101 Manual Switch 383 0100 Wait-to-Restore 384 0001 Do Not Revert 385 0000 No Request" 386 REFERENCE 387 "Section 4.2.2 of RFC6378" 388 SYNTAX OCTET STRING (SIZE (2)) 390 MplsLpsFpathPath ::= TEXTUAL-CONVENTION 391 STATUS current 392 DESCRIPTION 393 "This Textual Convention describes an object that stores 394 the Fault Path (FPath) field and Data Path (Path) field of 395 the PSC control packet. 397 FPath is located in the first octet and Path is 398 located in the second octet. Bits are numbered from left to 399 right. 401 The value and the interpretation of FPath field is as follows 403 2-255 for future extensions 404 1 the anomaly condition is on the working path 405 0 the anomaly condition is on the protection path 407 The value and the interpretation of Path field is as follows 409 2-255 for future extensions 410 1 protection path is transporting user data traffic 411 0 protection path is not transporting user data traffic 412 " 413 REFERENCE 414 "Section 4.2.5 and 4.2.6 of RFC6378" 415 SYNTAX OCTET STRING (SIZE (2)) 417 MplsLpsCommand ::= TEXTUAL-CONVENTION 418 STATUS current 419 DESCRIPTION 420 "This command allows a user to perform any action over ME. 421 If the protection command cannot be executed because an 422 equal or higher priority request is in effect, an 423 inconsistentValue error is returned. 425 The command values are: 427 noCmd 429 This value should be returned by a read request when no command 430 has been written to the object in question since 431 initialization. This value may not be used in a write 432 operation. If noCmd is used in a write operation a wrongValue 433 error is returned. 435 clear 437 Clears all of the commands listed below for the specified ME. 439 lockoutOfProtection 441 Prevents any of the working ME from switching to the protection 442 ME. The specified ME should be the protection ME, otherwise an 443 inconsistentValue error is returned. 445 forcedSwitchWorkToProtect 447 Switches the specified working ME to the protection path. 448 If the protection ME is specified an inconsistentValue 449 error is returned. 451 manualSwitchWorkToProtect 453 Switches the specified working ME to the protection ME. 454 If the protection ME is specified an inconsistentValue 455 error is returned." 457 SYNTAX INTEGER { 458 noCmd(1), 459 clear(2), 460 lockoutOfProtection(3), 461 forcedSwitchWorkToProtect(4), 462 manualSwitchWorkToProtect(5) 463 } 465 -- Start of MPLS Transport Profile Protection Switching 466 -- Table 467 -- MPLS TP Protection Switching Configuration Table 468 -- This table supports the addition, configuration and deletion 469 -- of MPLS TP Protection Switching groups. 471 mplsLpsConfigGroups OBJECT-TYPE 472 SYNTAX Gauge32 473 MAX-ACCESS read-only 474 STATUS current 475 DESCRIPTION 476 "The object hold the count of MPLS Protection Switching 477 groups. This count includes all rows in mplsLpsConfigTable, 478 regardless of the value of mplsLpsConfigRowStatus." 479 ::= { mplsLpsObjects 1 } 481 mplsLpsConfigTable OBJECT-TYPE 482 SYNTAX SEQUENCE OF MplsLpsConfigEntry 483 MAX-ACCESS not-accessible 484 STATUS current 485 DESCRIPTION 486 "This table lists the mpls linear protection groups that 487 have been configured on the system." 488 ::= { mplsLpsObjects 2 } 490 mplsLpsConfigEntry OBJECT-TYPE 491 SYNTAX MplsLpsConfigEntry 492 MAX-ACCESS not-accessible 493 STATUS current 494 DESCRIPTION 495 "A conceptual row in the mplsLpsConfigTable." 496 INDEX { mplsLpsConfigGroupIndex } 497 ::= { mplsLpsConfigTable 1 } 499 MplsLpsConfigEntry ::= SEQUENCE { 500 mplsLpsConfigGroupIndex Unsigned32, 501 mplsLpsConfigGroupName SnmpAdminString, 502 mplsLpsConfigMode INTEGER, 503 mplsLpsConfigRevertive INTEGER, 504 mplsLpsConfigProtectionScheme INTEGER, 505 mplsLpsConfigSdThreshold Integer32, 506 mplsLpsConfigWaitToRestore Integer32, 507 mplsLpsConfigContinualTxInterval Integer32, 508 mplsLpsConfigRapidTxInterval Integer32, 509 mplsLpsConfigCreationTime TimeStamp, 510 mplsLpsConfigRowStatus RowStatus, 511 mplsLpsConfigStorageType StorageType 513 } 515 mplsLpsConfigGroupIndex OBJECT-TYPE 516 SYNTAX Unsigned32 517 MAX-ACCESS not-accessible 518 STATUS current 519 DESCRIPTION 520 "Index for the conceptual row identifying a protection group." 521 ::= { mplsLpsConfigEntry 1 } 523 mplsLpsConfigGroupName OBJECT-TYPE 524 SYNTAX SnmpAdminString (SIZE (1..32)) 525 MAX-ACCESS read-create 526 STATUS current 527 DESCRIPTION 528 "Textual name represents the mpls tp protection group. 529 Each Protection Group is identified by a unique 530 protection group name. " 531 ::= { mplsLpsConfigEntry 2 } 533 mplsLpsConfigMode OBJECT-TYPE 534 SYNTAX INTEGER { 535 onePlusOne(1), 536 oneColonOne(2) 537 } 538 MAX-ACCESS read-create 539 STATUS current 540 DESCRIPTION 541 "The architectural mode of the Protection group. This can 542 either be 1+1, 1:1. 544 1+1 546 In the 1+1 protection scheme, a fully dedicated 547 protection entity is allocated. Data traffic is copied 548 and fed at the source to both the working and the 549 protection entities. The traffic on the working and the 550 protection entities is transmitted simultaneously to 551 the sink of the protection domain, where selection 552 between the working and protection entities is performed 554 1:1 556 In the 1:1 scheme, a protection path is allocated to 557 protect against a defect, failure, or a degradation in a 558 working path. In normal conditions, data traffic is 559 transmitted over the working entity, while the 560 protection entity functions in the idle state. If there 561 is a defect on the working entity or a specific 562 administrative request, traffic is switched to the 563 protection entity." 565 DEFVAL {onePlusOne} 566 ::= { mplsLpsConfigEntry 3 } 568 mplsLpsConfigRevertive OBJECT-TYPE 569 SYNTAX INTEGER { nonrevertive(1), revertive(2) } 570 MAX-ACCESS read-create 571 STATUS current 572 DESCRIPTION 573 "This object represents the reversion mode of the Linear 574 Protection Switching group. The reversion mode of 575 protection mechanism may be either revertive or 576 non-revertive. 578 nonrevertive 580 In non-revertive mode, after a service has been 581 recovered, traffic will be forwarded on the recovery 582 path. 584 revertive 586 In revertive mode, after a service has been 587 recovered, traffic will be redirected back onto the 588 original working path." 590 DEFVAL { nonrevertive } 591 ::= { mplsLpsConfigEntry 4 } 593 mplsLpsConfigProtectionScheme OBJECT-TYPE 594 SYNTAX INTEGER { bidirectional(1), unidirectional(2) } 595 MAX-ACCESS read-create 596 STATUS current 597 DESCRIPTION 598 "The object represents the operational scheme of 599 protection switching group. The protection scheme may 600 either be unidirectional or bidirectional. 602 bidirectional 604 In bidirectional protection scheme, both the directions 605 will be switched simultaneously even if the fault 606 applies to only one direction of the path. 608 unidirectional 609 In unidirectional protection scheme protection switching 610 will be performed independently for each direction of a 611 bidirectional transport path 613 This object may not be modified if the associated 614 mplsLpsConfigRowStatus object is equal to active(1). " 616 DEFVAL {bidirectional} 617 ::= { mplsLpsConfigEntry 5 } 619 mplsLpsConfigSdThreshold OBJECT-TYPE 620 SYNTAX Integer32 (1..9) 621 MAX-ACCESS read-create 622 STATUS current 623 DESCRIPTION 624 "This object holds the threshold value of the Signal 625 Degrade. 627 When the MPLS DM OAM reaches this threshold value, the 628 Signal Degrade event will be given to this 629 protection domain. 631 This object may be modified if the associated 632 mplsLpsConfigRowStatus object is equal to active(1)." 633 ::= { mplsLpsConfigEntry 6 } 635 mplsLpsConfigWaitToRestore OBJECT-TYPE 636 SYNTAX Integer32 (0..720) 637 UNITS "seconds" 638 MAX-ACCESS read-create 640 STATUS current 641 DESCRIPTION 642 "This object hold the Wait To Restore timer value in 643 seconds. 644 The WTR timer is used to delay reversion of PSC state 645 to Normal state when recovering from a failure 646 condition on the working path when the protection 647 domain is configured for revertive behavior 649 This object may not be modified if the associated 650 mplsLpsConfigRowStatus object is equal to active(1)." 651 DEFVAL { 300 } 652 ::= { mplsLpsConfigEntry 7 } 654 mplsLpsConfigContinualTxInterval OBJECT-TYPE 655 SYNTAX Integer32 (1..20) 656 UNITS "seconds" 657 MAX-ACCESS read-create 658 STATUS current 659 DESCRIPTION 660 "The Continual Tx Time in Seconds. Represents the time 661 interval to send the continual LPS packet to the other 662 end based on the current state." 663 DEFVAL { 5 } 664 ::= { mplsLpsConfigEntry 8 } 666 mplsLpsConfigRapidTxInterval OBJECT-TYPE 667 SYNTAX Integer32 (1000..20000) 668 UNITS "micro-seconds" 669 MAX-ACCESS read-create 670 STATUS current 671 DESCRIPTION 672 "The Rapid Tx interval in micro-Seconds. Represents the time 673 interval to send the LPS packet to the other end, when 674 there is a change in state of Linear Protection domain due 675 to local input. The default value is 3.3 milli-seconds 676 which is 3300 micro-seconds" 677 DEFVAL { 3300 } 678 ::= { mplsLpsConfigEntry 9 } 680 mplsLpsConfigCreationTime OBJECT-TYPE 681 SYNTAX TimeStamp 682 MAX-ACCESS read-only 683 STATUS current 684 DESCRIPTION 685 "The value of sysUpTime at the time the row was 686 created." 687 ::= { mplsLpsConfigEntry 10 } 689 mplsLpsConfigRowStatus OBJECT-TYPE 690 SYNTAX RowStatus 691 MAX-ACCESS read-create 692 STATUS current 693 DESCRIPTION 694 "This represents the status of the MPLS TP Linear 695 Protection group Entry. This variable is used to 696 create, modify, and/or delete a row in this table. 697 An entry may not exist in the active state unless all 698 objects in the entry have an appropriate value." 699 ::= { mplsLpsConfigEntry 11 } 701 mplsLpsConfigStorageType OBJECT-TYPE 702 SYNTAX StorageType 703 MAX-ACCESS read-create 704 STATUS current 705 DESCRIPTION 706 "The storage type for this conceptual row. 707 Conceptual rows having the value 'permanent' need not 708 allow write-access to any columnar objects in the row." 709 DEFVAL { nonVolatile } 710 ::= { mplsLpsConfigEntry 12 } 712 -- 713 -- MPLS TP Linear Protection Switching Status Table 714 -- 715 -- This table provides Protection Switching group statistics. 716 -- 718 mplsLpsStatusTable OBJECT-TYPE 719 SYNTAX SEQUENCE OF MplsLpsStatusEntry 721 MAX-ACCESS not-accessible 722 STATUS current 723 DESCRIPTION 724 "This table provides status information about mpls 725 linear protection groups that have been configured 726 on the system." 727 ::= { mplsLpsObjects 3 } 729 mplsLpsStatusEntry OBJECT-TYPE 730 SYNTAX MplsLpsStatusEntry 731 MAX-ACCESS not-accessible 732 STATUS current 733 DESCRIPTION 734 "A conceptual row in the mplsLpsStatusTable." 735 AUGMENTS { mplsLpsConfigEntry } 736 ::= { mplsLpsStatusTable 1 } 738 MplsLpsStatusEntry ::= SEQUENCE { 739 mplsLpsStatusReqRcv MplsLpsReq, 740 mplsLpsStatusReqSent MplsLpsReq, 741 mplsLpsStatusFpathPathRcv MplsLpsFpathPath, 742 mplsLpsStatusFpathPathSent MplsLpsFpathPath, 743 mplsLpsStatusModeMismatches Counter32 744 } 746 mplsLpsStatusReqRcv OBJECT-TYPE 747 SYNTAX MplsLpsReq 748 MAX-ACCESS read-only 749 STATUS current 750 DESCRIPTION 751 "The current value of the PSC Request field received on 752 more recent PSC packet." 753 ::= { mplsLpsStatusEntry 1 } 755 mplsLpsStatusReqSent OBJECT-TYPE 756 SYNTAX MplsLpsReq 757 MAX-ACCESS read-only 758 STATUS current 759 DESCRIPTION 760 "The current value of the PSC Request field sent on the 761 more recent PSC packet." 762 ::= { mplsLpsStatusEntry 2 } 764 mplsLpsStatusFpathPathRcv OBJECT-TYPE 765 SYNTAX MplsLpsFpathPath 766 MAX-ACCESS read-only 767 STATUS current 768 DESCRIPTION 769 "The current value of the FPath and Path fields received 770 on more recent PSC packet." 771 ::= { mplsLpsStatusEntry 3 } 773 mplsLpsStatusFpathPathSent OBJECT-TYPE 774 SYNTAX MplsLpsFpathPath 775 MAX-ACCESS read-only 776 STATUS current 777 DESCRIPTION 778 "The current value of the FPath and Path fields sent 779 on more recent PSC packet." 780 ::= { mplsLpsStatusEntry 4 } 782 mplsLpsStatusModeMismatches OBJECT-TYPE 783 SYNTAX Counter32 784 MAX-ACCESS read-only 785 STATUS current 786 DESCRIPTION 787 "This object holds number of occurrences of mismatch in 788 revertive mode across the protection domain end points." 789 ::= { mplsLpsStatusEntry 5 } 791 -- MPLS Linear Protection ME Association Configuration Table 792 -- This table supports the addition, configuration and deletion 793 -- of MPLS Linear Protection Maintenance Entities in Protection 794 -- Switching groups. 796 mplsLpsMeConfigTable OBJECT-TYPE 798 SYNTAX SEQUENCE OF MplsLpsMeConfigEntry 799 MAX-ACCESS not-accessible 800 STATUS current 801 DESCRIPTION 802 "This table lists Maintenance Association that have been 803 configured in Protection groups." 804 ::= { mplsLpsObjects 4 } 806 mplsLpsMeConfigEntry OBJECT-TYPE 807 SYNTAX MplsLpsMeConfigEntry 808 MAX-ACCESS not-accessible 809 STATUS current 810 DESCRIPTION 811 "A conceptual row in the mplsLpsMeConfigTable." 812 INDEX {mplsOamIdMegIndex, mplsOamIdMeIndex, mplsOamIdMeMpIndex} 813 ::= { mplsLpsMeConfigTable 1 } 815 MplsLpsMeConfigEntry ::= SEQUENCE { 816 mplsLpsMeConfigGroupIndex Unsigned32, 817 mplsLpsMeConfigState INTEGER, 818 mplsLpsMeConfigCommand MplsLpsCommand, 819 mplsLpsMeConfigHoldOff Integer32 820 } 822 mplsLpsMeConfigGroupIndex OBJECT-TYPE 823 SYNTAX Unsigned32 824 MAX-ACCESS not-accessible 825 STATUS current 826 DESCRIPTION 827 "This object holds the Protection group index wherein 828 this ME included in. If this ME is not part of any protection 829 group then this object contains value 0. " 830 DEFVAL { 0 } 831 ::= { mplsLpsMeConfigEntry 1 } 833 mplsLpsMeConfigState OBJECT-TYPE 834 SYNTAX INTEGER { primary(1), backup(2) } 836 MAX-ACCESS read-create 837 STATUS current 838 DESCRIPTION 839 "This object represents the operational state of the ME 840 as either primary or backup" 841 ::= { mplsLpsMeConfigEntry 2 } 843 mplsLpsMeConfigCommand OBJECT-TYPE 844 SYNTAX MplsLpsCommand 845 MAX-ACCESS read-write 846 STATUS current 847 DESCRIPTION 849 "Allows the initiation of an MPLS Linear protection command on 850 the protection group and the ME specified by the index values. 851 When read this object returns the last command written 852 or noCmd if no command has been written to this ME 853 since initialization. The return of the last command 854 written does not imply that this command is currently in 855 effect. This request may have been preempted by a higher 856 priority local or remote request. 858 The value lockoutOfProtection should only be applied to the 859 protection path / ME since that switch command prevents any 860 of the working path / ME from switching to the protection path. 861 Following the same logic, forcedSwitchWorkToProtect and 862 manualSwitchWorkToProtect should only be applied to a working 863 ME." 864 ::= { mplsLpsMeConfigEntry 3 } 866 mplsLpsMeConfigHoldOff OBJECT-TYPE 867 SYNTAX Integer32 (0..10000) 868 UNITS "milli-seconds" 869 MAX-ACCESS read-create 870 STATUS current 871 DESCRIPTION 872 "The hold-off time in milliseconds. Represents the time 874 between SF/SD condition detection and declaration of 875 an SF/SD request to the protection switching logic. 876 It is intended to avoid unnecessary switching when a lower- 877 layer protection mechanism is in place. 878 Can be configured in steps of 100" 879 DEFVAL { 0 } 880 ::= { mplsLpsMeConfigEntry 4 } 882 -- MPLS Linear Protection ME Status Table 883 -- This table provides Protection Switching ME statistics. 885 mplsLpsMeStatusTable OBJECT-TYPE 886 SYNTAX SEQUENCE OF MplsLpsMeStatusEntry 887 MAX-ACCESS not-accessible 888 STATUS current 889 DESCRIPTION 890 "This table contains status information of all the ME 891 that are included in MPLS Protection groups." 892 ::= { mplsLpsObjects 5 } 894 mplsLpsMeStatusEntry OBJECT-TYPE 895 SYNTAX MplsLpsMeStatusEntry 896 MAX-ACCESS not-accessible 897 STATUS current 898 DESCRIPTION 899 "A conceptual row in the mplsLpsMeStatusTable." 900 AUGMENTS { mplsLpsMeConfigEntry } 901 ::= { mplsLpsMeStatusTable 1 } 903 MplsLpsMeStatusEntry ::= SEQUENCE { 904 mplsLpsMeStatusCurrent BITS, 905 mplsLpsMeStatusSignalDegrades Counter32, 906 mplsLpsMeStatusSignalFailures Counter32, 907 mplsLpsMeStatusSwitchovers Counter32, 908 mplsLpsMeStatusLastSwitchover TimeStamp, 909 mplsLpsMeStatusSwitchoverSeconds Counter32 910 } 912 mplsLpsMeStatusCurrent OBJECT-TYPE 913 SYNTAX BITS { 914 localLockedOut(0), 915 localSd(1), 916 localSf(2), 917 localSwitched(3), 918 localWtr(4), 919 remoteLockedout(5), 920 remoteSd(6), 921 remoteSf(7), 922 remoteSwitched(8), 923 remoteWtr(9) 924 } 925 MAX-ACCESS read-only 926 STATUS current 927 DESCRIPTION 928 "Indicates the current state of the MA. 930 localLockedOut 932 This bit, when it is set on a working ME or working path 933 indicates that the working path is prevented from 934 switching to the protection path because of local request. 935 When it is set on protection / backup path, this bit 936 indicates that none of the working path can switch 937 to the protection path. 939 localSd 941 This bit implies that local signal degrade condition is 942 in effect on this ME / path. 944 localSf 946 This bit implies that local signal failure condition is 947 in effect on this ME / path. 949 localSwitched 951 This bit is only applicable to the working ME / path. 952 It implies that the working path is currently switched 953 to the protection path because of local request. 955 local wtr 957 This bit implies that local Wait-to-Restore state is 958 in effect. 960 remoteLockedOut 962 This bit, when it is set on a working ME or working path 963 indicates that the working path is prevented from 964 switching to the protection path because of remote request. 965 When it is set on protection / backup path, this bit 966 indicates that none of the working path can switch 967 to the protection path. 969 remoteSd 971 This bit implies that remote signal degrade condition is 972 in effect on this ME / path. 974 remoteSf 976 This bit implies that remote signal failure condition is 977 in effect on this ME / path. 979 remoteSwitched 981 This bit is only applicable to the working ME / path. 982 It implies that the working path is currently switched 983 to the protection path because of remote request. 985 remoteWtr 987 This bit implies that remote Wait-to-Restore state is 988 in effect." 989 ::= { mplsLpsMeStatusEntry 1 } 991 mplsLpsMeStatusSignalDegrades OBJECT-TYPE 992 SYNTAX Counter32 993 MAX-ACCESS read-only 994 STATUS current 995 DESCRIPTION 996 "Represents the count of Signal Degrade conditions. 997 This condition occurs when the DM exceeds the 998 currently configured value of the relevant instance of 999 mplsLpsConfigSdThreshold." 1000 ::= { mplsLpsMeStatusEntry 2 } 1002 mplsLpsMeStatusSignalFailures OBJECT-TYPE 1004 SYNTAX Counter32 1005 MAX-ACCESS read-only 1006 STATUS current 1007 DESCRIPTION 1008 "Represents the count of Signal failure conditions. 1009 This condition occurs when the OAM running on this MA 1010 detects the Signal Fail event." 1011 ::= { mplsLpsMeStatusEntry 3 } 1013 mplsLpsMeStatusSwitchovers OBJECT-TYPE 1014 SYNTAX Counter32 1015 MAX-ACCESS read-only 1016 STATUS current 1017 DESCRIPTION 1018 "Represents the count of SwitchOvers happened in this 1019 MA. 1021 When the mplsLpsMeConfigState is primary, this 1022 object will return the number of times this path 1023 has switched to the protection path. 1025 When the mplsLpsMeConfigState is backup, this object 1026 will return the number of times that any working paths 1027 has been switched back to the working path from this 1028 protection path." 1029 ::= { mplsLpsMeStatusEntry 4 } 1031 mplsLpsMeStatusLastSwitchover OBJECT-TYPE 1032 SYNTAX TimeStamp 1033 MAX-ACCESS read-only 1034 STATUS current 1035 DESCRIPTION 1036 "This object holds the value of sysUpTime wherein the 1037 last switchover happened. 1039 When the mplsLpsMeConfigState is primary, this object 1040 will return the value of sysUpTime when this path last 1041 completed a switchover. If this path has never switched 1042 to the protection line, the value 0 will be returned. 1044 When the mplsLpsMeConfigState is backup, this object 1045 will return the value of sysUpTime the last time that 1046 a working path was switched back to the working path 1047 from this protection path. If no working path has ever 1048 switched back to the working path from this protection 1049 path, the value 0 will be returned." 1051 ::= { mplsLpsMeStatusEntry 5 } 1053 mplsLpsMeStatusSwitchoverSeconds OBJECT-TYPE 1054 SYNTAX Counter32 1055 MAX-ACCESS read-only 1056 STATUS current 1057 DESCRIPTION 1058 "The cumulative Protection Switching Duration (PSD) time 1059 in seconds. 1061 ForM a working path, this is the cumulative number of 1062 seconds that traffic was carried on the protection 1063 path. 1065 For the protection path, this is the cumulative number 1066 of seconds that the protection path has been used to 1067 carry any working path traffic." 1069 ::= { mplsLpsMeStatusEntry 6 } 1071 mplsLpsNotificationEnable OBJECT-TYPE 1072 SYNTAX BITS { 1073 switchover(0), 1074 modeMismatch(1) 1075 } 1076 MAX-ACCESS read-write 1077 STATUS current 1079 DESCRIPTION 1080 "Provides the ability to enable and disable notifications 1081 defined in this MIB. 1083 switchover 1085 Indicates mplsLpsEventSwitchover notifications 1086 should be generated. 1088 modeMismatch 1090 Indicates mplsLpsEventModeMismatch notifications 1091 should be generated." 1093 DEFVAL { { } } 1094 ::= { mplsLpsObjects 6 } 1096 -- MPLS Linear Protection EVENTS 1098 mplsLpsEventSwitchover NOTIFICATION-TYPE 1099 OBJECTS { mplsLpsMeStatusSwitchovers, mplsLpsMeStatusCurrent } 1100 STATUS current 1101 DESCRIPTION 1102 "An mplsLpsEventSwitchover notification is sent when the 1103 value of an instance of mplsLpsMeStatusSwitchovers increments." 1104 ::= { mplsLpsNotifications 1 } 1106 mplsLpsEventModeMismatch NOTIFICATION-TYPE 1107 OBJECTS { mplsLpsStatusModeMismatches } 1108 STATUS current 1109 DESCRIPTION 1110 "An mplsLpsEventModeMismatch notification is sent when the 1111 value of an instance of mplsLpsStatusModeMismatches increments." 1113 ::= { mplsLpsNotifications 2 } 1115 -- End of Notifications. 1117 -- Module Compliance. 1119 mplsLpsCompliances 1120 OBJECT IDENTIFIER ::= { mplsLpsConformance 1 } 1122 mplsLpsGroups 1123 OBJECT IDENTIFIER ::= { mplsLpsConformance 2 } 1125 -- Compliance requirement for fully compliant implementations. 1127 mplsLpsModuleFullCompliance MODULE-COMPLIANCE 1129 STATUS current 1130 DESCRIPTION "Compliance statement for agents that provide full 1131 support for MPLS-LPS-MIB. Such devices can 1132 provide linear protection and also be configured using 1133 this MIB module." 1135 MODULE -- This module. 1136 MANDATORY-GROUPS { 1137 mplsLpsScalarGroup, 1138 mplsLpsConfigTableGroup, 1139 mplsLpsMeTableGroup 1140 } 1142 GROUP mplsLpsNotificationGroup 1143 DESCRIPTION "This group is only mandatory for those 1144 implementations which can efficiently implement 1145 the notifications contained in this group." 1147 ::= { mplsLpsCompliances 1 } 1149 -- Units of conformance. 1151 mplsLpsScalarGroup OBJECT-GROUP 1152 OBJECTS { 1153 mplsLpsConfigGroups, 1154 mplsLpsNotificationEnable 1155 } 1156 STATUS current 1157 DESCRIPTION 1158 "Collection of objects needed for MPLS Linear Protection." 1159 ::= { mplsLpsGroups 1 } 1161 mplsLpsConfigTableGroup OBJECT-GROUP 1162 OBJECTS { 1163 mplsLpsConfigGroupName, 1164 mplsLpsConfigRowStatus, 1165 mplsLpsConfigMode, 1166 mplsLpsConfigRevertive, 1167 mplsLpsConfigProtectionScheme, 1168 mplsLpsConfigSdThreshold, 1169 mplsLpsConfigWaitToRestore, 1170 mplsLpsConfigContinualTxInterval, 1171 mplsLpsConfigRapidTxInterval, 1172 mplsLpsConfigCreationTime, 1173 mplsLpsConfigStorageType, 1174 mplsLpsStatusReqRcv, 1175 mplsLpsStatusReqSent, 1177 mplsLpsStatusFpathPathRcv, 1178 mplsLpsStatusFpathPathSent, 1179 mplsLpsStatusModeMismatches 1180 } 1181 STATUS current 1182 DESCRIPTION 1183 "Collection of objects needed for MPLS Linear Protection 1184 configuration and statistics." 1185 ::= { mplsLpsGroups 2 } 1187 mplsLpsMeTableGroup OBJECT-GROUP 1188 OBJECTS { 1189 mplsLpsMeConfigState, 1190 mplsLpsMeConfigCommand, 1191 mplsLpsMeConfigHoldOff, 1192 mplsLpsMeStatusCurrent, 1193 mplsLpsMeStatusSignalDegrades, 1194 mplsLpsMeStatusSignalFailures, 1195 mplsLpsMeStatusSwitchovers, 1196 mplsLpsMeStatusLastSwitchover, 1197 mplsLpsMeStatusSwitchoverSeconds 1198 } 1199 STATUS current 1200 DESCRIPTION 1201 "Collection of objects needed for MPLS Linear Protection 1202 ME configuration and statistics." 1203 ::= { mplsLpsGroups 3 } 1205 mplsLpsNotificationGroup NOTIFICATION-GROUP 1206 NOTIFICATIONS { 1207 mplsLpsEventSwitchover, 1209 mplsLpsEventModeMismatch 1210 } 1211 STATUS current 1212 DESCRIPTION 1213 "Collection of objects needed to implement notifications." 1214 ::= { mplsLpsGroups 4 } 1216 -- MPLS-LPS-MIB module ends 1217 END 1219 9. Security Considerations 1221 There are a number of management objects defined in this MIB module 1222 with a MAX-ACCESS clause of read-write and/or read-create. Such 1223 objects may be considered sensitive or vulnerable in some networks in 1224 a non-secure environment without proper protection can have a 1225 negative effect on network operations. These are the tables and 1226 objects and their sensitivity/vulnerability: 1228 Some of the readable objects in this MIB module (i.e., objects with a 1229 MAX-ACCESS other than not-accessible) may be considered sensitive or 1230 vulnerable in some network environments. It is thus important to 1231 control even GET and/or NOTIFY access to these objects and possibly 1232 to even encrypt the values of these objects when sending them over 1233 the network via SNMP. These are the tables and objects and their 1234 sensitivity/vulnerability: 1236 - mplsLpsConfigTable, mplsLpsStatusTable, mplsLpsMeConfigTable and 1237 mplsLpsMeStatusTable collectively show the MPLS Linear Protection 1238 characteristics. If an Administrator does not want to reveal this 1239 information, then these tables should be considered 1240 sensitive/vulnerable. 1242 SNMP versions prior to SNMPv3 did not include adequate security. Even 1243 if the network itself is secure (for example by using IPsec), there 1244 is no control as to who on the secure network is allowed to access 1245 and GET/SET (read/change/create/delete) the objects in this MIB 1246 module. 1248 Implementations SHOULD provide the security features described by 1249 the SNMPv3 framework (see [RFC3410]), and implementations claiming 1250 compliance to the SNMPv3 standard MUST include full support for 1251 authentication and privacy via the User-based Security Model (USM) 1252 [RFC3414] with the AES cipher algorithm [RFC3826]. Implementations 1253 MAY also provide support for the Transport Security Model (TSM) 1254 [RFC5591] in combination with a secure transport such as SSH 1255 [RFC5592] or TLS/DTLS [RFC6353]. 1257 Further, deployment of SNMP versions prior to SNMPv3 is not 1258 recommended. Instead, it is RECOMMENDED to deploy SNMPv3 and to 1259 enable cryptographic security. It is then a customer/operator 1260 responsibility to ensure that the SNMP entity giving access to an 1261 instance of this MIB module is properly configured to give access to 1262 the objects only to those principals (users) that have legitimate 1263 rights to indeed GET or SET (change/create/delete) them. 1265 10. IANA Considerations 1267 IANA is requested to assign an OID for the MIB module from the "MIB 1268 Transmission Group - MPLS STD" sub-registry of the "Internet-standard 1269 MIB - Transmission Group" registry for the MPLS Linear Protection MIB 1270 module specified in this document. 1272 11. References 1274 11.1. Normative References 1276 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1277 Requirement Levels", BCP 14, RFC 2119, March 1997. 1279 [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. 1280 Schoenwaelder, Ed., "Structure of Management 1281 Information Version 2 (SMIv2)", STD 58, RFC 2578, 1282 April 1999. 1284 [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. 1285 Schoenwaelder, Ed., "Textual Conventions for SMIv2", 1286 STD 58, RFC 2579, April 1999. 1288 [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 1289 "Conformance Statements for SMIv2", STD 58, RFC 2580, 1290 April 1999. 1292 11.2. Informative References 1294 [RFC3410] J. Case, R. Mundy, D. pertain, B.Stewart, "Introduction and 1295 Applicability Statement for Internet Standard Management 1296 Framework", RFC 3410, December 2002. 1298 [RFC3414] Blumenthal, U. and B. Wijnen, "User-based Security 1299 Model(USM) for version 3 of the Simple Network Management 1300 Protocol (SNMPv3)", STD 62, RFC 3414, December 2002. 1302 [RFC3811] Nadeau, T., Ed., and J. Cucchiara, Ed., "Definitions of 1303 Textual Conventions (TCs) for Multiprotocol Label Switching 1304 (MPLS) Management", RFC 3811, June 2004. 1306 [RFC3812] Srinivasan, C., Viswanathan, A., and T. Nadeau, 1307 "Multiprotocol Label Switching (MPLS) Traffic Engineering 1308 (TE) Management Information Base (MIB)", RFC 3812, June 1309 2004. 1311 [RFC3826] Blumenthal, U., F. Maino and K. McCloghrie, "The Advanced 1312 Encryption Standard (AES) Cipher Algorithm in the SNMP 1313 User-based Security Model", RFC 3826, June 2004. 1315 [RFC5591] Harrington, D. and W. Hardaker, "Transport Security Model 1316 for the Simple Network Management Protocol(SNMP)",RFC 5591, 1317 June 2009. 1319 [RFC5592] Harrington, D., Salowey, J., and W. Hardaker, "Secure Shell 1320 Transport Model for the Simple Network Management Protocol 1321 (SNMP)", RFC 5592, June 2009. 1323 [RFC6353] Hardaker, W., "Transport Layer Security (TLS) Transport 1324 Model for the Simple Network Management Protocol (SNMP)", 1325 STD 78, RFC 6353, July 2011. 1327 [RFC6378] Weingarten, Y., Osborne, E., Sprecher, N., Fulignoli, 1328 A., Ed., and Y. Weingarten, Ed., "MPLS-TP Linear 1329 Protection", October 2011. 1331 [MPLS-OAM-ID-STD-MIB] Sam Aldrin, M.Venkatesan, Kannan KV Sampath, 1332 Thomas D. Nadeau, Sami Boutros, Ping Pan, 1333 "MPLS-TP Operations, Administration, and 1334 Management (OAM) Identifiers Management 1335 Information Base (MIB)", ID 1336 draft-ietf-mpls-tp-oam-id-mib-08, February 2015. 1338 12. Acknowledgments 1340 The authors wish to thank Joan Cucchiara for her review as MIB 1341 Doctor, Joan's detailed comments were of great help for improving the 1342 quality of this document. 1344 13. Author's Address 1346 Kingston Smiler 1347 IP Infusion 1348 RMZ Centennial 1349 Mahadevapura Post 1350 Bangalore - 560048 India 1351 EMail: kingstonsmiler@gmail.com 1353 Venkatesan Mahalingam 1354 Dell Inc. 1355 5450 Great America Parkway, 1356 Santa Clara, CA 95054, USA 1357 Email: venkat.mahalingams@gmail.com 1359 Vishwas Manral 1360 Ionos Corp, 1361 4100 Moorpark Ave, 1362 San Jose, CA 1363 Email: vishwas@ionosnetworks.com 1365 Daniel King 1366 Old Dog Consulting 1367 UK 1368 Email:daniel@olddog.co.uk 1370 Sam Aldrin 1371 Google, Inc. 1372 1600 Amphitheatre Parkway 1373 Mountain View, CA 1374 USA 1375 Email: aldrin.ietf@gmail.com"