idnits 2.17.1 draft-ietf-mpls-tp-linear-protection-mib-08.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 (May 19, 2016) is 2896 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 1855, but no explicit reference was found in the text == Unused Reference: 'RFC3811' is defined on line 1874, 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: November 20, 2016 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 May 19, 2016 16 MPLS Transport Profile Linear Protection MIB 17 draft-ietf-mpls-tp-linear-protection-mib-08 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 November 20, 2016. 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 . . . . . . . . . . . . . . . . . . . . . . . . . 8 74 9. Security Considerations . . . . . . . . . . . . . . . . . . . 38 75 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 39 76 11. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 39 77 12. References . . . . . . . . . . . . . . . . . . . . . . . . . 39 78 12.1. Normative References . . . . . . . . . . . . . . . . . . 39 79 12.2. Informative References . . . . . . . . . . . . . . . . . 40 80 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 41 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 LSPs. 92 At the time of writing, SNMP SET is no longer recommended as a way to 93 configure MPLS networks as was described in RFC 3812 [RFC3812]. 94 However, since the MIB module specified in this document are intended 95 to work in parallel with the MIB module for MPLS specified in 97 [RFC3812], certain objects defined here are specified with MAX-ACCESS 98 of read- write or read-create so that specifications of the base 99 tables in [RFC3812] and the new MIB module in this document is 100 consistent. Although the examples described in Section 7 specify 101 means to configure OAM identifiers for MPLS-TP tunnels, this should 102 be seen as indicating how the MIB values would be returned in the 103 specified circumstances having been 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 Management Information Base or MIB. MIB objects are generally 113 accessed through the Simple Network Management Protocol (SNMP). 114 Objects in the MIB are defined using the mechanisms defined in the 115 Structure of Management Information (SMI). This memo specifies a MIB 116 module that is compliant to the SMIv2, which is described in STD 58, 117 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 118 [RFC2580]. 120 3. Conventions 122 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 123 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 124 document are to be interpreted as described in BCP 14, RFC 2119 125 [RFC2119]. 127 4. Overview 129 RFC 6378 [RFC6378] defines the protocol to provide a linear 130 protection switching mechanism for MPLS transport profile with 131 protection domain as a point-to-point LSP. RFC 7271 [RFC7271] 132 describes alternate mechanisms to perform some of the functions 133 defined in [RFC6378], and also defines additional mechanisms, in 134 order to provide operator control and experience that more closely 135 models the behavior of linear protection seen in other transport 136 networks. Two modes are defined for MPLS-TP linear protection 137 switching: Protection State Coordination (PSC) mode and Automatic 138 Protection Switching (APS) mode as specified in [RFC6378] and 139 [RFC7271], respectively. The detailed protocol specification of MPLS 140 transport profile linear protection is described in [RFC6378] and 141 [RFC7271]. 143 This document specifies a MIB module for the Label Edge Router (LER) 144 that supports MPLS-TP Linear protection as described in [RFC6378] and 146 [RFC7271]. Objects defined in the document are generally applied to 147 both PSC and APS modes. If an object is valid for a particular mode 148 only, it is noted in the description for the object. 150 5. Structure of the MIB Module 152 5.1. Textual Conventions 154 The following new textual conventions are defined in this document: 156 MplsLpsReq 157 MplsLpsFpathPath 158 MplsLpsCommand 159 MplsLpsState 161 5.2. The MPLS-TP Linear Protection Subtree 163 MPLS-LPS-MIB is the MIB module defined in this document, and it is 164 put under mplsStdMIB. 166 5.3. The Notifications Subtree 168 Notifications are defined to inform the management station about 169 switchover, provisioning mismatches, and protocol failures of linear 170 protection domain. The following notifications are defined for this 171 purpose: 173 o The notification, mplsLpsEventSwitchover is to inform the 174 management station about the switchover of the active path. 176 o The notification, mplsLpsEventRevertiveMismatch is to inform the 177 management station about the provisioning mismatch in the 178 revertive mode across the end point of the protection domain. 180 o The notification, mplsLpsEventProtecTypeMismatch is to inform the 181 management station about the provisioning mismatch in protection 182 type, representing both bridge and switching types, across the end 183 point of the protection domain. 185 o The notification, mplsLpsEventCapabilitiesMismatch is to inform 186 the management station about the provisioning mismatch in 187 Capabilities TLVs across the end point of the protection domain. 189 o The notification, mplsLpsEventPathConfigMismatch is to inform the 190 management station about the provisioning mismatch in the 191 protection path configuration for PSC communication. 193 o The notification, mplsLpsEventFopNoResponse is to inform the 194 management station about the failure of protocol due to a lack of 195 response to a traffic switchover request in 50 ms. 197 o The notification, mplsLpsEventFopTimout is to inform the 198 management station about the failure of protocol due to no 199 protocol message received during at least 3.5 times the long PSC 200 message interval. 202 5.4. The Table Structures 204 The MPLS-TP linear protection MIB module has four tables. The tables 205 are as follows 207 o mplsLpsConfigTable 209 This table is used to configure MPLS-TP linear protection domain. 210 The protection domain is identified by mplsLpsConfigDomainName. 211 The other objects in this table can be used to configure 212 properties that are specific to the protection domain. 214 o mplsLpsStatusTable 216 This table provides the current status information of MPLS-TP 217 linear protection domains that have been configured on the system. 218 The entries of mplsLpsStatusTable have an AUGMENTS relationship 219 with the entries of mplsLpsConfigTable. When a protection domain 220 is configured or deleted in the mplsLpsConfigTable, then the 221 corresponding row of that session in the mplsLpsStatusTable is, 222 respectively, automatically created or deleted. 224 o mplsLpsMeConfigTable 226 This table is used to associate the Maintenance Entities (MEs) to 227 the protection domain. The ME is identified by mplsOamIdMegIndex, 228 mplsOamIdMeIndex and mplsOamIdMeMpIndex. 230 o mplsLpsMeStatusTable 232 This table provides the current information about the protection 233 state of MEs that have been configured on the system. When a ME 234 configured or deleted in the mplsLpsMeConfigTable, then the 235 corresponding row of that session in the mplsLpsMeStatusTable is, 236 respectively, automatically created or deleted. 238 6. Relationship to Other MIB Modules 240 6.1. Relationship to the MPLS OAM Maintenance Identifiers MIB Module 242 The mplsLpsMeConfigTable entry is extended by entry in the 243 mplsOamIdMeTable defined in [RFC7697]. Note that the nature of the 244 'extends' relationship is a sparse augmentation so that the entry in 245 the mplsLpsMeConfigTable has the same index values as the entry in 246 the mplsOamIdMeTable. Each time that an entry is created in the 247 mplsOamIdMeTable for which the LER supports MPLS-TP linear protection 248 a row is created automatically in the mplsLpsMeConfigTable. 250 7. Example of Protection Switching Configuration 252 This example considers the protection domain configuration on a head- 253 end LSR to provide protection for a co-routed bidirectional MPLS 254 tunnel. 256 Only relevant objects which are applicable for protection domain 257 identifiers of co-routed MPLS tunnel are illustrated here. 259 In mplsOamIdMegTable: 260 { 261 -- MEG index (Index to the table) 262 mplsOamIdMegIndex = 1, 263 mplsOamIdMegName = "MEG1", 264 mplsOamIdMegOperatorType = ipCompatible (1), 265 mplsOamIdMegServiceType = lsp (1), 266 mplsOamIdMegMpLocation = perNode(1), 267 -- Mandatory parameters needed to activate the row go here 268 mplsOamIdMegRowStatus = createAndGo (4) 269 } 271 This will create an entry in the mplsOamIdMegTable to protect the 272 MPLS tunnel. 274 The following ME table is used to associate the path information to a 275 MEG. 277 In mplsOamIdMeTable: 278 { 279 -- ME index (Index to the table) 280 mplsOamIdMeIndex = 1, 281 -- MP index (Index to the table) 282 mplsOamIdMeMpIndex = 1, 283 mplsOamIdMeName = "ME1", 284 mplsOamIdMeMpIfIndex = 0, 285 -- Source MEP id is derived from the IP compatible MPLS 286 -- tunnel 287 mplsOamIdMeSourceMepIndex = 0, 288 -- Source MEP id is derived from the IP compatible MPLS 289 -- tunnel 290 mplsOamIdMeSinkMepIndex = 0, 291 mplsOamIdMeMpType = mep (1), 292 mplsOamIdMeMepDirection = down (2), 293 mplsOamIdMeProactiveOamPhbTCValue = 0, 294 mplsOamIdMeOnDemandOamPhbTCValue = 0, 295 -- RowPointer MUST point to the first accessible column 296 -- of an MPLS tunnel 297 mplsOamIdMeServicePointer = mplsTunnelName.1.1.1.2, 298 -- Mandatory parameters needed to activate the row go here 299 mplsOamIdMeRowStatus = createAndGo (4) 300 } 302 The below table associates the MEs with protection domains. 304 In mplsLpsConfigTable: 305 mplsLpsConfigEntry ::= SEQUENCE { 306 -- Group index 307 mplsLpsConfigDomainIndex = 1, 308 mplsLpsConfigDomainName = "LPDomain1", 309 mplsLpsConfigMode = psc (1), 310 mplsLpsConfigProtectionType = oneColonOneBidirectional (2), 311 -- Mandatory parameters needed to activate the row go here 312 mplsLpsConfigRowStatus = createAndGo (4) 313 } 315 In mplsLpsMeConfigTable: 316 MplsLpsMeConfigEntry ::= SEQUENCE { 317 -- MEG index (Index to the table) 318 mplsOamIdMegIndex = 1, 319 -- ME index (Index to the table) 320 mplsOamIdMeIndex = 1, 321 -- MP index (Index to the table) 322 mplsOamIdMeMpIndex = 1, 323 -- Domain index 324 mplsLpsMeConfigDomainIndexValue = 1, 325 -- Configuration state 326 mplsLpsMeConfigState = working(1) 327 } 329 8. Definitions 331 MPLS-LPS-MIB DEFINITIONS ::= BEGIN 333 IMPORTS 334 MODULE-IDENTITY, NOTIFICATION-TYPE, OBJECT-TYPE, 335 Counter32, Unsigned32 336 FROM SNMPv2-SMI 338 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 339 FROM SNMPv2-CONF -- RFC 2580 341 TEXTUAL-CONVENTION, RowStatus, TimeStamp, StorageType 342 FROM SNMPv2-TC 344 SnmpAdminString 345 FROM SNMP-FRAMEWORK-MIB 347 IndexIntegerNextFree 348 FROM DIFFSERV-MIB -- RFC 3289 350 mplsStdMIB 351 FROM MPLS-TC-STD-MIB -- RFC 3811 353 mplsOamIdMegIndex, mplsOamIdMeIndex, mplsOamIdMeMpIndex 354 FROM MPLS-OAM-ID-STD-MIB; -- RFC 7697 356 mplsLpsMIB MODULE-IDENTITY 357 LAST-UPDATED "201605190000Z" -- May 19, 2016 358 ORGANIZATION "Multiprotocol Label Switching (MPLS) Working Group" 359 CONTACT-INFO 360 " 361 Kingston Smiler Selvaraj 362 IP Infusion 363 RMZ Centennial 364 Mahadevapura Post 365 Bangalore - 560048 India 366 EMail: kingstonsmiler@gmail.com 368 Venkatesan Mahalingam 369 Dell Inc. 370 5450 Great America Parkway, 371 Santa Clara, CA 95054, USA 372 Email: venkat.mahalingams@gmail.com 374 Vishwas Manral 375 Ionos Corp, 376 4100 Moorpark Ave, 377 San Jose, CA 378 Email: vishwas@ionosnetworks.com 380 Daniel King 381 Old Dog Consulting 382 UK 383 Email:daniel@olddog.co.uk 385 Sam Aldrin 386 Google, Inc. 387 1600 Amphitheatre Parkway 388 Mountain View, CA 389 USA 390 Email: aldrin.ietf@gmail.com 392 Jeong-dong Ryoo 393 ETRI 394 218 Gajeong-ro 395 Yuseong-gu, Daejeon 34129 396 South Korea 397 Email:ryoo@etri.re.kr 398 " 399 DESCRIPTION 400 "This management information module supports the 401 configuration and management of MPLS-TP linear 402 protection domains. " 403 REVISION 404 "201605190000Z" -- May 19, 2016 405 DESCRIPTION 406 "MPLS-TP Protection Switching Domain objects for LSP 407 MEPs" 409 ::= { mplsStdMIB xxx } -- xxx to be replaced with 410 -- correct value 412 -- Top level components of this MIB module. 413 -- Notifications 414 mplsLpsNotifications 415 OBJECT IDENTIFIER ::= { mplsLpsMIB 0 } 417 -- tables, scalars 418 mplsLpsObjects 419 OBJECT IDENTIFIER ::= { mplsLpsMIB 1 } 421 -- conformance 422 mplsLpsConformance 423 OBJECT IDENTIFIER ::= { mplsLpsMIB 2 } 425 MplsLpsReq ::= TEXTUAL-CONVENTION 426 DISPLAY-HINT "1d" 427 STATUS current 428 DESCRIPTION 429 "This Textual Convention describes an object that stores 430 the PSC Request field of the PSC control packet. The values 431 are as follows: 433 1110 434 Lockout of Protection 436 1100 437 Forced Switch 439 1010 440 Signal Fail (SF) 442 0111 443 Signal Degrade (SD) 445 0101 446 Manual Switch 448 0100 449 Wait-to-Restore 451 0011 452 Exercise 454 0010 455 Reverse Request 457 0001 458 Do Not Revert 460 0000 461 No Request" 462 REFERENCE 463 "Section 4.2.2 of RFC6378 and Section 8 of RFC7271" 464 SYNTAX OCTET STRING (SIZE (2)) 466 MplsLpsFpathPath ::= TEXTUAL-CONVENTION 467 DISPLAY-HINT "1x:" 468 STATUS current 469 DESCRIPTION 470 "This Textual Convention describes an object that stores 471 the Fault Path (FPath) field and Data Path (Path) field of 472 the PSC control packet. 474 FPath is located in the first octet and Path is 475 located in the second octet. Bits are numbered from left to 476 right. 478 The value and the interpretation of FPath field is as follows: 480 2-255 481 for future extensions 483 1 484 the anomaly condition is on the working path 486 0 487 the anomaly condition is on the protection path 489 The value and the interpretation of Path field is as follows: 491 2-255 492 for future extensions 494 1 495 protection path is transporting user data traffic 496 0 497 protection path is not transporting user data traffic " 498 REFERENCE 499 "Section 4.2.5 and 4.2.6 of RFC6378" 500 SYNTAX OCTET STRING (SIZE (2)) 502 MplsLpsCommand ::= TEXTUAL-CONVENTION 503 STATUS current 504 DESCRIPTION 505 "This command allows a user to perform any action over a 506 protection domain. If the protection command cannot be 507 executed because an equal or higher priority request is 508 in effect, an inconsistentValue error is returned. 510 The command values are: 512 noCmd 513 This value should be returned by a read request when no 514 command has been written to the object in question since 515 initialization. This value may not be used in a write 516 operation. If noCmd is used in a write operation a 517 wrongValue error is returned. 519 clear 520 Clears all of the commands listed below for the protection 521 domain. 523 lockoutOfProtection 524 Prevents switching traffic to the protection path. 526 forcedSwitch 527 Switches traffic from the working path to the protection path. 529 manualSwitchToWork 530 Switches traffic from the protection path to the working path. 532 manualSwitchToProtect 533 Switches traffic from the working path to the protection path. 535 exercise 536 Used to verify the correct operation of the PSC communication 537 and the integrity of the protection path. This command is not 538 applicable to the PSC mode. 540 freeze 541 This command freezes the protection state and is a local 542 command that is not signaled to the remote node. 543 This command is not applicable to the PSC mode. 545 clearfreeze 546 Clears the local freeze. This command is not applicable to 547 the PSC mode. " 548 REFERENCE 549 "Sections 3.1 and 3.2 of RFC6378 and Sections 4.3 and 6 of 550 RFC7271" 551 SYNTAX INTEGER { 552 noCmd(1), 553 clear(2), 554 lockoutOfProtection(3), 555 forcedSwitch(4), 556 manualSwitchToWork(5), 557 manualSwitchToProtect(6), 558 exercise(7), 559 freeze(8), 560 clearfreeze(9) 561 } 563 MplsLpsState ::= TEXTUAL-CONVENTION 564 STATUS current 565 DESCRIPTION 566 "This Textual Convention describes an object that stores 567 the current state of the PSC state machine. The values 568 are as follows: 570 normal 571 normal state 573 unavLOlocal 574 Unavailable state due to local LO command. 576 unavSFPlocal 577 Unavailable state due to local SF-P. 579 unavSDPlocal 580 Unavailable state due to local SD-P. 582 unavLOremote 583 Unavailable state due to remote LO message. 585 unavSFPremote 586 Unavailable state due to remote SF-P message. 588 unavSDPremote 589 Unavailable state due to remote SD-P message. 591 protfailSFWlocal 592 Protecting Failure state due to local SF-W. 594 protfailSDWlocal 595 Protecting Failure state due to local SD-W. 597 protfailSFWremote 598 Protecting Failure state due to remote SF-W message. 600 protfailSDWremote 601 Protecting Failure state due to remote SD-W message. 603 switadmFSlocal 604 Switching Administrative state due to local FS command. 605 Same as Protecting administrative state due to local FS 606 command in the PSC mode. 608 switadmMSWlocal 609 Switching Administrative state due to local MS-W command 611 switadmMSPlocal 612 Switching Administrative state due to local MS-P command. 613 Same as Protecting administrative state due to local MS 614 command in the PSC mode 616 switadmFSremote 617 Switching Administrative state due to remote FS message. 618 Same as Protecting administrative state due to remote FS 619 message in the PSC mode. 621 switadmMSWremote 622 Switching Administrative state due to remote MS-W message 624 switadmMSPremote 625 Switching Administrative state due to remote MS-P message. 626 Same as Protecting administrative state due to remote MS 627 message in the PSC mode. 629 wtr 630 Wait-to-Restore state 632 dnr 633 Do-not-Revert state 635 exerLocal 636 Exercise state due to local EXER command. 638 exerRemote 639 Exercise state due to remote EXER message." 640 REFERENCE 641 "Section 11 of RFC7271" 643 SYNTAX INTEGER { 644 normal (1), 645 unavLOlocal (2), 646 unavSFPlocal (3), 647 unavSDPlocal (4), 648 unavLOremote (5), 649 unavSFPremote (6), 650 unavSDPremote (7), 651 protfailSFWlocal (8), 652 protfailSDWlocal (9), 653 protfailSFWremote (10), 654 protfailSDWremote (11), 655 switadmFSlocal (12), 656 switadmMSWlocal (13), 657 switadmMSPlocal (14), 658 switadmFSremote (15), 659 switadmMSWremote (16), 660 switadmMSPremote (17), 661 wtr (18), 662 dnr (19), 663 exerLocal (20), 664 exerRemote (21) 665 } 667 -- Start of 668 -- MPLS-TP Linear Protection Switching Configuration Table. 669 -- This table supports the addition, configuration and deletion 670 -- of MPLS-TP linear protection domains. 672 mplsLpsConfigIndexNext OBJECT-TYPE 673 SYNTAX IndexIntegerNextFree (0..4294967295) 674 MAX-ACCESS read-only 675 STATUS current 676 DESCRIPTION 677 "This object contains an unused value for 678 mplsLpsConfigDomainIndex, or a zero to indicate 679 that none exist. Negative values are not allowed, 680 as they do not correspond to valid values of 681 mplsLpsConfigDomainIndex." 682 ::= { mplsLpsObjects 1 } 684 mplsLpsConfigTable OBJECT-TYPE 685 SYNTAX SEQUENCE OF MplsLpsConfigEntry 686 MAX-ACCESS not-accessible 687 STATUS current 688 DESCRIPTION 689 "This table lists the MPLS-TP linear protection domains that 690 have been configured on the system." 692 ::= { mplsLpsObjects 2 } 694 mplsLpsConfigEntry OBJECT-TYPE 695 SYNTAX MplsLpsConfigEntry 696 MAX-ACCESS not-accessible 697 STATUS current 698 DESCRIPTION 699 "A conceptual row in the mplsLpsConfigTable." 700 INDEX { mplsLpsConfigDomainIndex } 701 ::= { mplsLpsConfigTable 1 } 703 MplsLpsConfigEntry ::= SEQUENCE { 704 mplsLpsConfigDomainIndex Unsigned32, 705 mplsLpsConfigDomainName SnmpAdminString, 706 mplsLpsConfigMode INTEGER, 707 mplsLpsConfigProtectionType INTEGER, 708 mplsLpsConfigRevertive INTEGER, 709 mplsLpsConfigSdThreshold Unsigned32, 710 mplsLpsConfigSdBadSeconds Unsigned32, 711 mplsLpsConfigSdGoodSeconds Unsigned32, 712 mplsLpsConfigWaitToRestore Unsigned32, 713 mplsLpsConfigHoldOff Unsigned32, 714 mplsLpsConfigContinualTxInterval Unsigned32, 715 mplsLpsConfigRapidTxInterval Unsigned32, 716 mplsLpsConfigCommand MplsLpsCommand, 717 mplsLpsConfigCreationTime TimeStamp, 718 mplsLpsConfigRowStatus RowStatus, 719 mplsLpsConfigStorageType StorageType 720 } 722 mplsLpsConfigDomainIndex OBJECT-TYPE 723 SYNTAX Unsigned32 (1..4294967295) 724 MAX-ACCESS not-accessible 725 STATUS current 726 DESCRIPTION 727 "Index for the conceptual row identifying a protection domain. 728 Managers should obtain new values for row 729 creation in this table by reading mplsLpsConfigIndexNext." 730 ::= { mplsLpsConfigEntry 1 } 732 mplsLpsConfigDomainName OBJECT-TYPE 733 SYNTAX SnmpAdminString (SIZE (0..32)) 734 MAX-ACCESS read-create 735 STATUS current 736 DESCRIPTION 737 "Textual name represents the MPLS-TP linear protection domain. 738 Each protection domain is identified by a unique protection 739 domain name. " 741 ::= { mplsLpsConfigEntry 2 } 743 mplsLpsConfigMode OBJECT-TYPE 744 SYNTAX INTEGER { 745 psc(1), 746 aps(2) 747 } 748 MAX-ACCESS read-create 749 STATUS current 750 DESCRIPTION 751 "The mode of MPLS-TP linear protection mechanism. This can 752 either be PSC or APS as follows: 754 PSC 755 The Protection State Coordination mode as described in 756 RFC 6378. 758 APS 759 The Automatic Protection Switching mode as described in 760 RFC 7271. 762 This object may not be modified if the associated 763 mplsLpsConfigRowStatus object is equal to active(1). " 764 REFERENCE 765 "Section 9.2 of RFC7271" 766 DEFVAL {psc} 767 ::= { mplsLpsConfigEntry 3 } 769 mplsLpsConfigProtectionType OBJECT-TYPE 770 SYNTAX INTEGER { 771 onePlusOneUnidirectional (1), 772 oneColonOneBidirectional (2), 773 onePlusOneBidirectional (3) 774 } 775 MAX-ACCESS read-create 776 STATUS current 777 DESCRIPTION 778 "The protection architecture type of the Protection domain. 779 This represents both bridge type, which can be 780 either permanent bridge (1+1) or selector bridge (1:1), 781 and switching scheme, which can be 782 either unidirectional or bidirectional. 784 1+1 785 In the 1+1 protection scheme, a fully dedicated protection 786 path is allocated. Data traffic is copied and fed 787 at the source to both the working and the protection path. 788 The traffic on the working and the protection paths is 789 transmitted simultaneously to the sink of the protection 790 domain, where selection between the working and protection 791 paths is performed 793 1:1 794 In the 1:1 scheme, a protection path is allocated to 795 protect against a defect, failure, or a degradation in the 796 working path. In normal conditions, data traffic is 797 transmitted over the working path, while the protection path 798 functions in the idle state. If there is a defect on the 799 working path or a specific administrative request, 800 traffic is switched to the protection path. 802 bidirectional 803 In bidirectional protection scheme, both the directions 804 will be switched simultaneously even if the fault applies 805 to only one direction of the path. 807 unidirectional 808 In unidirectional protection scheme protection switching 809 will be performed independently for each direction of a 810 bidirectional transport path. 812 This object may not be modified if the associated 813 mplsLpsConfigRowStatus object is equal to active(1). " 814 REFERENCE 815 "Section 4.2.3 of RFC6378" 816 DEFVAL {oneColonOneBidirectional} 817 ::= { mplsLpsConfigEntry 4 } 819 mplsLpsConfigRevertive OBJECT-TYPE 820 SYNTAX INTEGER { nonrevertive(1), revertive(2) } 821 MAX-ACCESS read-create 822 STATUS current 823 DESCRIPTION 824 "This object represents the reversion mode of the linear 825 protection domain. The reversion mode of protection 826 mechanism may be either revertive or non-revertive. 828 nonrevertive 829 In non-revertive mode, after a service has been recovered, 830 traffic will be forwarded on the protection path. 832 revertive 833 In revertive mode, after a service has been recovered, 834 traffic will be redirected back onto the original working 835 path. 837 This object may not be modified if the associated 838 mplsLpsConfigRowStatus object is equal to active(1). " 839 REFERENCE 840 "Section 4.2.4 of RFC6378" 841 DEFVAL { revertive } 842 ::= { mplsLpsConfigEntry 5 } 844 mplsLpsConfigSdThreshold OBJECT-TYPE 845 SYNTAX Unsigned32 (0..100) 846 MAX-ACCESS read-create 847 STATUS current 848 DESCRIPTION 849 "This object holds the threshold value of the Signal Degrade 850 defect in percent. 852 In order to detect the Signal Degrade (SD) defect, 853 the MPLS-TP packet loss measurement (LM) is performed 854 every second. 856 If either the packet loss is negative (i.e., there are more 857 packets received than transmitted) or the packet loss ratio 858 (lost packets/transmitted packets) in percent is greater this 859 threshold value, a Bad Second is declared. The SD defect is 860 detected if there are mplsLpsConfigSdBadSeconds consecutive 861 Bad Seconds and cleared if there are 862 mplsLpsConfigSdGoodSeconds consecutive Good Seconds. 864 This object may be modified if the associated 865 mplsLpsConfigRowStatus object is equal to active(1)." 866 REFERENCE 867 "Section 7 of RFC7271" 868 DEFVAL { 30 } 869 ::= { mplsLpsConfigEntry 6 } 871 mplsLpsConfigSdBadSeconds OBJECT-TYPE 872 SYNTAX Unsigned32 (2..10) 873 MAX-ACCESS read-create 874 STATUS current 875 DESCRIPTION 876 "This object holds the number of Bad Seconds to detect the SD. 877 See the description of mplsLpsConfigSdThreshold. 878 This object may be modified if the associated 879 mplsLpsConfigRowStatus object is equal to active(1). 881 This object may be modified if the associated 882 mplsLpsConfigRowStatus object is equal to active(1). " 883 REFERENCE 884 "Section 7 of RFC7271" 886 DEFVAL { 10 } 887 ::= { mplsLpsConfigEntry 7 } 889 mplsLpsConfigSdGoodSeconds OBJECT-TYPE 890 SYNTAX Unsigned32 (2..10) 891 MAX-ACCESS read-create 892 STATUS current 893 DESCRIPTION 894 "This object holds the number of Good Seconds to declare the 895 clearance of SD defect. 896 See the description of mplsLpsConfigSdThreshold. 898 This object may be modified if the associated 899 mplsLpsConfigRowStatus object is equal to active(1)." 900 REFERENCE 901 "Section 7 of RFC7271" 902 DEFVAL { 10 } 903 ::= { mplsLpsConfigEntry 8 } 905 mplsLpsConfigWaitToRestore OBJECT-TYPE 906 SYNTAX Unsigned32 (5..12) 907 UNITS "minutes" 908 MAX-ACCESS read-create 909 STATUS current 910 DESCRIPTION 911 "This object holds the Wait To Restore timer value in seconds. 912 Can be configured in 1 minute steps between 5 and 12 minutes. 913 The WTR timer is used to delay reversion of PSC state 914 to Normal state when recovering from a failure 915 condition on the working path when the protection 916 domain is configured for revertive behavior 918 This object may not be modified if the associated 919 mplsLpsConfigRowStatus object is equal to active(1)." 920 REFERENCE 921 "Section 3.5 of RFC6378" 922 DEFVAL { 5 } 923 ::= { mplsLpsConfigEntry 9 } 925 mplsLpsConfigHoldOff OBJECT-TYPE 926 SYNTAX Unsigned32 (0..100) 927 UNITS "deciseconds" 928 MAX-ACCESS read-create 929 STATUS current 930 DESCRIPTION 931 "The hold-off time in deciseconds. Represents the time 932 between SF/SD condition detection and declaration of 933 an SF/SD request to the protection switching logic. 935 It is intended to avoid unnecessary switching when a lower- 936 layer protection mechanism is in place. 937 Can be configured in steps of 100 milli-seconds. 939 When a new defect or more severe defect occurs at 940 the active path (the path from which the selector selects 941 the user data traffic) and this value is non-zero, 942 the hold-off timer will be started. A defect on the standby 943 path (the path from which the selector does not select the 944 user data traffic) does not trigger the start of the hold-off 945 timer as there is no need for a traffic switchover. 947 This object may not be modified if the associated 948 mplsLpsConfigRowStatus object is equal to active(1). " 949 REFERENCE 950 "Section 3.1 of RFC6378" 951 DEFVAL { 0 } 952 ::= { mplsLpsConfigEntry 10 } 954 mplsLpsConfigContinualTxInterval OBJECT-TYPE 955 SYNTAX Unsigned32 (1..20) 956 UNITS "seconds" 957 MAX-ACCESS read-create 958 STATUS current 959 DESCRIPTION 960 "The Continual Tx Time in Seconds. Represents the time 961 interval to send the continual LPS packet to the other 962 end based on the current state. 964 This object may not be modified if the associated 965 mplsLpsConfigRowStatus object is equal to active(1). " 966 REFERENCE 967 "Section 4.1 of RFC6378" 968 DEFVAL { 5 } 969 ::= { mplsLpsConfigEntry 11 } 971 mplsLpsConfigRapidTxInterval OBJECT-TYPE 972 SYNTAX Unsigned32 (1000..20000) 973 UNITS "micro-seconds" 974 MAX-ACCESS read-create 975 STATUS current 976 DESCRIPTION 977 "The Rapid Tx interval in micro-Seconds. Represents the time 978 interval to send the LPS packet to the other end, when 979 there is a change in state of linear protection domain due 980 to local input. The default value is 3.3 milli-seconds 981 which is 3300 micro-seconds 982 This object may not be modified if the associated 983 mplsLpsConfigRowStatus object is equal to active(1). " 984 REFERENCE 985 "Section 4.1 of RFC6378" 986 DEFVAL { 3300 } 987 ::= { mplsLpsConfigEntry 12 } 989 mplsLpsConfigCommand OBJECT-TYPE 990 SYNTAX MplsLpsCommand 991 MAX-ACCESS read-create 992 STATUS current 993 DESCRIPTION 994 "Allows the initiation of an operator command on 995 the protection domain. 997 When read this object returns the last command written 998 or noCmd if no command has been written 999 since initialization. The return of the last command 1000 written does not imply that this command is currently in 1001 effect. This request may have been preempted by a higher 1002 priority local or remote request. 1004 This object may be modified if the associated 1005 mplsLpsConfigRowStatus object is equal to active(1). " 1006 REFERENCE 1007 "Sections 3.1 and 3.2 of RFC6378 and Sections 4.3 and 6 of 1008 RFC7271" 1009 ::= { mplsLpsConfigEntry 13 } 1011 mplsLpsConfigCreationTime OBJECT-TYPE 1012 SYNTAX TimeStamp 1013 MAX-ACCESS read-only 1014 STATUS current 1015 DESCRIPTION 1016 "The value of sysUpTime at the time the row was created." 1017 ::= { mplsLpsConfigEntry 14 } 1019 mplsLpsConfigRowStatus OBJECT-TYPE 1020 SYNTAX RowStatus 1021 MAX-ACCESS read-create 1022 STATUS current 1023 DESCRIPTION 1024 "This represents the status of the MPLS-TP linear 1025 protection domain entry. This variable is used to 1026 create, modify, and/or delete a row in this table. 1027 An entry may not exist in the active state unless all 1028 objects in the entry have an appropriate value." 1029 ::= { mplsLpsConfigEntry 15 } 1031 mplsLpsConfigStorageType OBJECT-TYPE 1032 SYNTAX StorageType 1033 MAX-ACCESS read-create 1034 STATUS current 1035 DESCRIPTION 1036 "The storage type for this conceptual row. 1037 Conceptual rows having the value 'permanent' need not 1038 allow write-access to any columnar objects in the row." 1039 DEFVAL { nonVolatile } 1040 ::= { mplsLpsConfigEntry 16 } 1042 -- 1043 -- MPLS-TP Linear Protection Switching Status Table 1044 -- This table provides Protection Switching domain statistics. 1045 -- 1047 mplsLpsStatusTable OBJECT-TYPE 1048 SYNTAX SEQUENCE OF MplsLpsStatusEntry 1049 MAX-ACCESS not-accessible 1050 STATUS current 1051 DESCRIPTION 1052 "This table provides status information about MPLS-TP 1053 linear protection domains that have been configured 1054 on the system." 1055 ::= { mplsLpsObjects 3 } 1057 mplsLpsStatusEntry OBJECT-TYPE 1058 SYNTAX MplsLpsStatusEntry 1059 MAX-ACCESS not-accessible 1060 STATUS current 1061 DESCRIPTION 1062 "A conceptual row in the mplsLpsStatusTable." 1063 AUGMENTS { mplsLpsConfigEntry } 1064 ::= { mplsLpsStatusTable 1 } 1066 MplsLpsStatusEntry ::= SEQUENCE { 1067 mplsLpsStatusState MplsLpsState, 1068 mplsLpsStatusReqRcv MplsLpsReq, 1069 mplsLpsStatusReqSent MplsLpsReq, 1070 mplsLpsStatusFpathPathRcv MplsLpsFpathPath, 1071 mplsLpsStatusFpathPathSent MplsLpsFpathPath, 1072 mplsLpsStatusRevertiveMismatch INTEGER, 1073 mplsLpsStatusProtecTypeMismatch INTEGER, 1074 mplsLpsStatusCapabilitiesMismatch INTEGER, 1075 mplsLpsStatusPathConfigMismatch INTEGER, 1076 mplsLpsStatusFopNoResponses Counter32, 1077 mplsLpsStatusFopTimeouts Counter32 1078 } 1079 mplsLpsStatusState OBJECT-TYPE 1080 SYNTAX MplsLpsState 1081 MAX-ACCESS read-only 1082 STATUS current 1083 DESCRIPTION 1084 "The current state of the PSC state machine." 1085 REFERENCE 1086 "Section 11 of RFC7271" 1087 ::= { mplsLpsStatusEntry 1 } 1089 mplsLpsStatusReqRcv OBJECT-TYPE 1090 SYNTAX MplsLpsReq 1091 MAX-ACCESS read-only 1092 STATUS current 1093 DESCRIPTION 1094 "The current value of the PSC Request field received on 1095 the most recent PSC packet." 1096 REFERENCE 1097 "Section 4.2 of RFC6378" 1098 ::= { mplsLpsStatusEntry 2 } 1100 mplsLpsStatusReqSent OBJECT-TYPE 1101 SYNTAX MplsLpsReq 1102 MAX-ACCESS read-only 1103 STATUS current 1104 DESCRIPTION 1105 "The current value of the PSC Request field sent on the 1106 most recent PSC packet." 1107 REFERENCE 1108 "Section 4.2 of RFC6378" 1109 ::= { mplsLpsStatusEntry 3 } 1111 mplsLpsStatusFpathPathRcv OBJECT-TYPE 1112 SYNTAX MplsLpsFpathPath 1113 MAX-ACCESS read-only 1114 STATUS current 1115 DESCRIPTION 1116 "The current value of the FPath and Path fields received 1117 on the most recent PSC packet." 1118 REFERENCE 1119 "Section 4.2 of RFC6378" 1120 ::= { mplsLpsStatusEntry 4 } 1122 mplsLpsStatusFpathPathSent OBJECT-TYPE 1123 SYNTAX MplsLpsFpathPath 1124 MAX-ACCESS read-only 1125 STATUS current 1126 DESCRIPTION 1127 "The current value of the FPath and Path fields sent 1128 on the most recent PSC packet." 1129 REFERENCE 1130 "Section 4.2 of RFC6378" 1131 ::= { mplsLpsStatusEntry 5 } 1133 mplsLpsStatusRevertiveMismatch OBJECT-TYPE 1134 SYNTAX INTEGER {true (1), false (2)} 1135 MAX-ACCESS read-only 1136 STATUS current 1137 DESCRIPTION 1138 "This object indicates the provisioning mismatch in 1139 revertive mode across the protection domain end points. 1140 The value of this object becomes true when a PSC message with 1141 incompatible Revertive field is received, or false 1142 when a PSC message with compatible Revertive field is 1143 received. " 1144 REFERENCE 1145 "Section 12 of RFC7271" 1146 ::= { mplsLpsStatusEntry 6 } 1148 mplsLpsStatusProtecTypeMismatch OBJECT-TYPE 1149 SYNTAX INTEGER {true (1), false (2)} 1150 MAX-ACCESS read-only 1151 STATUS current 1152 DESCRIPTION 1153 "This object indicates the provisioning mismatch in 1154 protection type, representing both bridge and switching types, 1155 across the protection domain end points. 1156 The value of this object becomes true when a PSC message with 1157 incompatible PT field is received, or false 1158 when a PSC message with compatible PT field is received. " 1159 REFERENCE 1160 "Section 12 of RFC7271" 1161 ::= { mplsLpsStatusEntry 7 } 1163 mplsLpsStatusCapabilitiesMismatch OBJECT-TYPE 1164 SYNTAX INTEGER {true (1), false (2)} 1165 MAX-ACCESS read-only 1166 STATUS current 1167 DESCRIPTION 1168 "This object indicates the provisioning mismatch in 1169 Capabilities TLVs across the protection domain end points. 1170 The value of this object becomes true when a PSC message with 1171 incompatible Capabilities TLV field is received, or false 1172 when a PSC message with compatible Capabilities TLV field is 1173 received. 1175 The Capabilities TLV with 0xF8000000 indicates that the APS 1176 mode is used for MPLS-TP linear protection mechanism, 1177 whereas PSC mode uses either the Capabilities TLV with Ox0 1178 or no existence of the Capabilities TLV." 1179 REFERENCE 1180 "Section 12 of RFC7271" 1181 ::= { mplsLpsStatusEntry 8 } 1183 mplsLpsStatusPathConfigMismatch OBJECT-TYPE 1184 SYNTAX INTEGER {true (1), falsmplsOamIdMeMpIndexNexte (2)} 1185 MAX-ACCESS read-only 1186 STATUS current 1187 DESCRIPTION 1188 "This object indicates the provisioning mismatch in the 1189 protection path configuration for PSC communication across 1190 the protection domain end points. 1192 The value of this object becomes true when a PSC message is 1193 received from the working path, or false when a PSC message 1194 is received from the protection path." 1195 REFERENCE 1196 "Section 12 of RFC7271" 1197 ::= { mplsLpsStatusEntry 9 } 1199 mplsLpsStatusFopNoResponses OBJECT-TYPE 1200 SYNTAX Counter32 1201 MAX-ACCESS read-only 1202 STATUS current 1203 DESCRIPTION 1204 "This object holds the number of occurrences of the failure 1205 of protocol due to a lack of response to a traffic switchover 1206 request within in 50 ms. 1208 When there is a traffic switchover due to a local request, 1209 a 50 ms timer is started to detect the failure of protocol 1210 due to no response. If there is no PSC message is received 1211 with the same Path value as in the transmitted PSC message 1212 until the 50 ms timer expires, the failure of protocol due to 1213 no response occurs." 1214 REFERENCE 1215 "Section 12 of RFC7271" 1216 ::= { mplsLpsStatusEntry 10 } 1218 mplsLpsStatusFopTimeouts OBJECT-TYPE 1219 SYNTAX Counter32 1220 MAX-ACCESS read-only 1221 STATUS current 1222 DESCRIPTION 1223 "This object holds the number of occurrences of the failure 1224 of protocol due to no PSC message received during at least 1225 3.5 times the long PSC message interval. 1227 When no PSC message is received on the protection path during 1228 at least 3.5 times the long PSC message interval and there 1229 is no defect on the protection path, the failure of protocol 1230 due to no PSC message occurs." 1231 REFERENCE 1232 "Section 12 of RFC7271" 1233 ::= { mplsLpsStatusEntry 11 } 1235 -- MPLS-TP Linear Protection ME Association Configuration Table 1236 -- This table supports the addition, configuration and deletion 1237 -- of MPLS-TP Linear Protection Maintenance Entities in protection 1238 -- domains. 1240 mplsLpsMeConfigTable OBJECT-TYPE 1241 SYNTAX SEQUENCE OF MplsLpsMeConfigEntry 1242 MAX-ACCESS not-accessible 1243 STATUS current 1244 DESCRIPTION 1245 "This table lists Maintenance Association that have been 1246 configured in Protection domains." 1247 ::= { mplsLpsObjects 4 } 1249 mplsLpsMeConfigEntry OBJECT-TYPE 1250 SYNTAX MplsLpsMeConfigEntry 1251 MAX-ACCESS not-accessible 1252 STATUS current 1253 DESCRIPTION 1254 "A conceptual row in the mplsLpsMeConfigTable. There is 1255 a sparse relationship between the conceptual rows of 1256 this table and mplsOamIdMeTable." 1257 INDEX {mplsOamIdMegIndex, mplsOamIdMeIndex, mplsOamIdMeMpIndex} 1258 ::= { mplsLpsMeConfigTable 1 } 1260 MplsLpsMeConfigEntry ::= SEQUENCE { 1261 mplsLpsMeConfigDomainIndexValue Unsigned32, 1262 mplsLpsMeConfigState INTEGER 1263 } 1265 mplsLpsMeConfigDomainIndexValue OBJECT-TYPE 1266 SYNTAX Unsigned32 (0..4294967295) 1267 MAX-ACCESS read-create 1268 STATUS current 1269 DESCRIPTION 1270 "This object holds the value of Protection domain index wherein 1271 this ME included in. If this ME is not part of any protection 1272 domain then this object contains value 0. " 1273 DEFVAL { 0 } 1274 ::= { mplsLpsMeConfigEntry 1 } 1276 mplsLpsMeConfigState OBJECT-TYPE 1277 SYNTAX INTEGER { working(1), protection(2) } 1278 MAX-ACCESS read-create 1279 STATUS current 1280 DESCRIPTION 1281 "This object represents the operational state of the ME 1282 as either working or protection" 1283 REFERENCE 1284 "Section 4.3 of RFC6378" 1285 ::= { mplsLpsMeConfigEntry 2 } 1287 -- 1288 -- MPLS Linear Protection ME Status Table 1289 -- This table provides Protection Switching ME statistics. 1290 -- 1292 mplsLpsMeStatusTable OBJECT-TYPE 1293 SYNTAX SEQUENCE OF MplsLpsMeStatusEntry 1294 MAX-ACCESS not-accessible 1295 STATUS current 1296 DESCRIPTION 1297 "This table contains status information of all the MEs 1298 that are included in MPLS-TP liear protection domains." 1299 ::= { mplsLpsObjects 5 } 1301 mplsLpsMeStatusEntry OBJECT-TYPE 1302 SYNTAX MplsLpsMeStatusEntry 1303 MAX-ACCESS not-accessible 1304 STATUS current 1305 DESCRIPTION 1306 "A conceptual row in the mplsLpsMeStatusTable." 1307 AUGMENTS { mplsLpsMeConfigEntry } 1308 ::= { mplsLpsMeStatusTable 1 } 1310 MplsLpsMeStatusEntry ::= SEQUENCE { 1311 mplsLpsMeStatusCurrent BITS, 1312 mplsLpsMeStatusSignalDegrades Counter32, 1313 mplsLpsMeStatusSignalFailures Counter32, 1314 mplsLpsMeStatusSwitchovers Counter32, 1315 mplsLpsMeStatusLastSwitchover TimeStamp, 1316 mplsLpsMeStatusSwitchoverSeconds Counter32 1317 } 1318 mplsLpsMeStatusCurrent OBJECT-TYPE 1319 SYNTAX BITS { 1320 localSelectTraffic(0), 1321 localSD(1), 1322 localSF(2) 1323 } 1324 MAX-ACCESS read-only 1325 STATUS current 1326 DESCRIPTION 1327 "Indicates the current state of the ME. 1329 localSelectTraffic 1330 This bit indicates that traffic is being selected from 1331 this ME. 1333 localSD 1334 This bit implies that local signal degrade condition is 1335 in effect on this ME / path. 1337 localSF 1338 This bit implies that local signal failure condition is 1339 in effect on this ME / path." 1340 REFERENCE 1341 "Section 4.3 of RFC6378 and Section 7 of RFC7271" 1342 ::= { mplsLpsMeStatusEntry 1 } 1344 mplsLpsMeStatusSignalDegrades OBJECT-TYPE 1345 SYNTAX Counter32 1346 MAX-ACCESS read-only 1347 STATUS current 1348 DESCRIPTION 1349 "Represents the count of Signal Degrade conditions. 1350 For the detection and clearance of Signal Degrade, 1351 see the description of mplsLpsConfigSdThreshold." 1352 REFERENCE 1353 "Section 7 of RFC7271" 1354 ::= { mplsLpsMeStatusEntry 2 } 1356 mplsLpsMeStatusSignalFailures OBJECT-TYPE 1357 SYNTAX Counter32 1358 MAX-ACCESS read-only 1359 STATUS current 1360 DESCRIPTION 1361 "Represents the count of Signal failure conditions. 1362 This condition occurs when the OAM running on this ME 1363 detects the Signal Fail event." 1364 REFERENCE 1365 "Section 4.3 of RFC6378" 1367 ::= { mplsLpsMeStatusEntry 3 } 1369 mplsLpsMeStatusSwitchovers OBJECT-TYPE 1370 SYNTAX Counter32 1371 MAX-ACCESS read-only 1372 STATUS current 1373 DESCRIPTION 1374 "Represents the count of SwitchOvers happened in this ME. 1376 When the mplsLpsMeConfigState is working, this object will 1377 return the number of times that traffic has been switched 1378 from this working path to the protection path. 1380 When the mplsLpsMeConfigState is protection, this object 1381 will return the number of times that traffic has been 1382 switched back to the working path from this protection path." 1383 REFERENCE 1384 "Section 4.3 of RFC6378" 1385 ::= { mplsLpsMeStatusEntry 4 } 1387 mplsLpsMeStatusLastSwitchover OBJECT-TYPE 1388 SYNTAX TimeStamp 1389 MAX-ACCESS read-only 1390 STATUS current 1391 DESCRIPTION 1392 "This object holds the value of sysUpTime wherein the 1393 last switchover happened. 1395 When the mplsLpsMeConfigState is working, this object 1396 will return the value of sysUpTime when traffic was switched 1397 from this path to the protection path. 1399 If traffic has never switched to the protection path, the 1400 value 0 will be returned. 1402 When the mplsLpsMeConfigState is protection, this object 1403 will return the value of sysUpTime the last time that 1404 traffic was switched back to the working path from this path. 1405 If no traffic has ever switched back to the working path from 1406 this protection path, the value 0 will be returned." 1407 REFERENCE 1408 "Section 4.3 of RFC6378" 1409 ::= { mplsLpsMeStatusEntry 5 } 1411 mplsLpsMeStatusSwitchoverSeconds OBJECT-TYPE 1412 SYNTAX Counter32 1413 UNITS "seconds" 1414 MAX-ACCESS read-only 1415 STATUS current 1416 DESCRIPTION 1417 "The cumulative Protection Switching Duration (PSD) time 1418 in seconds. 1420 For the working path, this is the cumulative number of 1421 seconds that traffic was selected from the protection path. 1423 For the protection path, this is the cumulative number 1424 of seconds that the working path has been used to 1425 select traffic." 1426 REFERENCE 1427 "Section 4.3 of RFC6378" 1428 ::= { mplsLpsMeStatusEntry 6 } 1430 mplsLpsNotificationEnable OBJECT-TYPE 1431 SYNTAX BITS { 1432 switchover(0), 1433 revertiveMismatch(1), 1434 protecTypeMismatch(2), 1435 capabilitiesMismatch(3), 1436 pathConfigMismatch(4), 1437 fopNoResponse(5), 1438 fopTimeout(6) 1439 } 1440 MAX-ACCESS read-write 1441 STATUS current 1442 DESCRIPTION 1443 "Provides the ability to enable and disable notifications 1444 defined in this MIB. 1446 switchover 1447 Indicates mplsLpsEventSwitchover notifications should be 1448 generated. 1450 revertiveMismatch 1451 Indicates mplsLpsEventRevertiveMismatch notifications 1452 should be generated. 1454 protecTypeMismatch 1455 Indicates mplsLpsEventProtecTypeMismatch notifications 1456 should be generated. 1458 capabilitiesMismatch 1459 Indicates mplsLpsEventCapabilitiesMismatch notifications 1460 should be generated. 1462 pathConfigMismatch 1463 Indicates mplsLpsEventPathConfigMismatch notifications 1464 should be generated. 1466 fopNoResponse 1467 Indicates mplsLpsEventFopNoResponse notifications 1468 should be generated. 1470 fopTimeout 1471 Indicates mplsLpsEventFopTimout notifications 1472 should be generated." 1473 REFERENCE 1474 "Section 12 of RFC7271" 1475 DEFVAL { { } } 1476 ::= { mplsLpsObjects 6 } 1478 -- MPLS Linear Protection EVENTS 1480 mplsLpsEventSwitchover NOTIFICATION-TYPE 1481 OBJECTS { mplsLpsMeStatusSwitchovers, mplsLpsMeStatusCurrent } 1482 STATUS current 1483 DESCRIPTION 1484 "An mplsLpsEventSwitchover notification is sent when the 1485 value of an instance of mplsLpsMeStatusSwitchovers 1486 increments." 1487 ::= { mplsLpsNotifications 1 } 1489 mplsLpsEventRevertiveMismatch NOTIFICATION-TYPE 1490 OBJECTS { mplsLpsStatusRevertiveMismatch } 1491 STATUS current 1492 DESCRIPTION 1493 "An mplsLpsEventRevertiveMismatch notification is sent when 1494 the value of mplsLpsStatusRevertiveMismatch changes." 1495 ::= { mplsLpsNotifications 2 } 1497 mplsLpsEventProtecTypeMismatch NOTIFICATION-TYPE 1498 OBJECTS { mplsLpsStatusProtecTypeMismatch } 1499 STATUS current 1500 DESCRIPTION 1501 "An mplsLpsEventProtecTypeMismatch notification is sent 1502 when the value of mplsLpsStatusProtecTypeMismatch changes." 1503 ::= { mplsLpsNotifications 3 } 1505 mplsLpsEventCapabilitiesMismatch NOTIFICATION-TYPE 1506 OBJECTS { mplsLpsStatusCapabilitiesMismatch } 1507 STATUS current 1508 DESCRIPTION 1509 "An mplsLpsEventCapabilitiesMismatch notification is sent 1510 when the value of mplsLpsStatusCapabilitiesMismatch changes." 1511 ::= { mplsLpsNotifications 4 } 1513 mplsLpsEventPathConfigMismatch NOTIFICATION-TYPE 1514 OBJECTS { mplsLpsStatusPathConfigMismatch } 1515 STATUS current 1516 DESCRIPTION 1517 "An mplsLpsEventPathConfigMismatch notification is sent 1518 when the value of mplsLpsStatusPathConfigMismatch changes." 1519 ::= { mplsLpsNotifications 5 } 1521 mplsLpsEventFopNoResponse NOTIFICATION-TYPE 1522 OBJECTS { mplsLpsStatusFopNoResponses } 1523 STATUS current 1524 DESCRIPTION 1525 "An mplsLpsEventFopNoResponse notification is sent when the 1526 value of mplsLpsStatusFopNoResponses increments." 1527 ::= { mplsLpsNotifications 6 } 1529 mplsLpsEventFopTimout NOTIFICATION-TYPE 1530 OBJECTS { mplsLpsStatusFopTimeouts } 1531 STATUS current 1532 DESCRIPTION 1533 "An mplsLpsEventFopTimout notification is sent when the 1534 value of mplsLpsStatusFopTimeouts increments." 1535 ::= { mplsLpsNotifications 7 } 1537 -- End of Notifications. 1539 -- Module Compliance. 1541 mplsLpsCompliances 1542 OBJECT IDENTIFIER ::= { mplsLpsConformance 1 } 1544 mplsLpsGroups 1545 OBJECT IDENTIFIER ::= { mplsLpsConformance 2 } 1547 -- Compliance requirement for fully compliant implementations. 1549 mplsLpsModuleFullCompliance MODULE-COMPLIANCE 1550 STATUS current 1551 DESCRIPTION 1552 "Compliance statement for agents that provide full 1553 support for MPLS-LPS-MIB. Such devices can 1554 provide linear protection and also be configured using 1555 this MIB module." 1556 MODULE -- This module. 1557 MANDATORY-GROUPS { 1558 mplsLpsScalarGroup, 1559 mplsLpsTableGroup, 1560 mplsLpsMeTableGroup 1561 } 1562 GROUP mplsLpsNotificationGroup 1563 DESCRIPTION 1564 "This group is only mandatory for those 1565 implementations which can efficiently implement 1566 the notifications contained in this group." 1567 ::= { mplsLpsCompliances 1 } 1569 -- Compliance requirement for read-only implementations 1571 mplsLpsModuleReadOnlyCompliance MODULE-COMPLIANCE 1572 STATUS current 1573 DESCRIPTION 1574 "Compliance statement for agents that only provide 1575 read-only support for the MPLS-LPS-MIB module." 1577 MODULE -- this module 1579 MANDATORY-GROUPS { 1580 mplsLpsScalarGroup, 1581 mplsLpsTableGroup, 1582 mplsLpsMeTableGroup 1583 } 1584 GROUP mplsLpsNotificationGroup 1585 DESCRIPTION 1586 "This group is only mandatory for those 1587 implementations which can efficiently implement 1588 the notifications contained in this group." 1590 -- mplsLpsConfigTable 1592 OBJECT mplsLpsConfigMode 1593 MIN-ACCESS read-only 1594 DESCRIPTION 1595 "Write access is not required." 1597 OBJECT mplsLpsConfigProtectionType 1598 MIN-ACCESS read-only 1599 DESCRIPTION 1600 "Write access is not required." 1602 OBJECT mplsLpsConfigRevertive 1603 MIN-ACCESS read-only 1604 DESCRIPTION 1605 "Write access is not required." 1607 OBJECT mplsLpsConfigSdThreshold 1608 MIN-ACCESS read-only 1609 DESCRIPTION 1610 "Write access is not required." 1612 OBJECT mplsLpsConfigSdBadSeconds 1613 MIN-ACCESS read-only 1614 DESCRIPTION 1615 "Write access is not required." 1617 OBJECT mplsLpsConfigSdGoodSeconds 1618 MIN-ACCESS read-only 1619 DESCRIPTION 1620 "Write access is not required." 1622 OBJECT mplsLpsConfigWaitToRestore 1623 MIN-ACCESS read-only 1624 DESCRIPTION 1625 "Write access is not required." 1627 OBJECT mplsLpsConfigContinualTxInterval 1628 MIN-ACCESS read-only 1629 DESCRIPTION 1630 "Write access is not required." 1632 OBJECT mplsLpsConfigRapidTxInterval 1633 MIN-ACCESS read-only 1634 DESCRIPTION 1635 "Write access is not required." 1637 OBJECT mplsLpsConfigCommand 1638 MIN-ACCESS read-only 1639 DESCRIPTION 1640 "Write access is not required." 1642 OBJECT mplsLpsConfigRowStatus 1643 SYNTAX RowStatus { active(1) } 1644 MIN-ACCESS read-only 1645 DESCRIPTION 1646 "Write access is not required." 1648 OBJECT mplsLpsConfigStorageType 1649 MIN-ACCESS read-only 1650 DESCRIPTION 1651 "Write access is not required." 1653 -- mplsLpsMeConfigTable 1654 OBJECT mplsLpsMeConfigDomainIndexValue 1655 MIN-ACCESS read-only 1656 DESCRIPTION 1657 "Write access is not required." 1659 OBJECT mplsLpsMeConfigState 1660 MIN-ACCESS read-only 1661 DESCRIPTION 1662 "Write access is not required." 1664 ::= { mplsLpsCompliances 2 } 1666 -- Units of conformance. 1668 mplsLpsScalarGroup OBJECT-GROUP 1669 OBJECTS { 1670 mplsLpsConfigIndexNext, 1671 mplsLpsNotificationEnable 1672 } 1673 STATUS current 1674 DESCRIPTION 1675 "Collection of objects needed for MPLS Linear Protection." 1676 ::= { mplsLpsGroups 1 } 1678 mplsLpsTableGroup OBJECT-GROUP 1679 OBJECTS { 1680 mplsLpsConfigDomainName, 1681 mplsLpsConfigRowStatus, 1682 mplsLpsConfigMode, 1683 mplsLpsConfigProtectionType, 1684 mplsLpsConfigRevertive, 1685 mplsLpsConfigSdThreshold, 1686 mplsLpsConfigSdBadSeconds, 1687 mplsLpsConfigSdGoodSeconds, 1688 mplsLpsConfigWaitToRestore, 1689 mplsLpsConfigHoldOff, 1690 mplsLpsConfigContinualTxInterval, 1691 mplsLpsConfigRapidTxInterval, 1692 mplsLpsConfigCommand, 1693 mplsLpsConfigCreationTime, 1694 mplsLpsConfigStorageType, 1695 mplsLpsStatusState, 1696 mplsLpsStatusReqRcv, 1697 mplsLpsStatusReqSent, 1698 mplsLpsStatusFpathPathRcv, 1699 mplsLpsStatusFpathPathSent, 1700 mplsLpsStatusRevertiveMismatch, 1701 mplsLpsStatusProtecTypeMismatch, 1702 mplsLpsStatusCapabilitiesMismatch, 1703 mplsLpsStatusPathConfigMismatch, 1704 mplsLpsStatusFopNoResponses, 1705 mplsLpsStatusFopTimeouts 1706 } 1707 STATUS current 1708 DESCRIPTION 1709 "Collection of objects needed for MPLS Linear Protection 1710 configuration and statistics." 1711 ::= { mplsLpsGroups 2 } 1713 mplsLpsMeTableGroup OBJECT-GROUP 1714 OBJECTS { 1715 mplsLpsMeConfigDomainIndexValue, 1716 mplsLpsMeConfigState, 1717 mplsLpsMeStatusCurrent, 1718 mplsLpsMeStatusSignalDegrades, 1719 mplsLpsMeStatusSignalFailures, 1720 mplsLpsMeStatusSwitchovers, 1721 mplsLpsMeStatusLastSwitchover, 1722 mplsLpsMeStatusSwitchoverSeconds 1723 } 1724 STATUS current 1725 DESCRIPTION 1726 "Collection of objects needed for MPLS Linear Protection 1727 ME configuration and statistics." 1728 ::= { mplsLpsGroups 3 } 1730 mplsLpsNotificationGroup NOTIFICATION-GROUP 1731 NOTIFICATIONS { 1732 mplsLpsEventSwitchover, 1733 mplsLpsEventRevertiveMismatch, 1734 mplsLpsEventProtecTypeMismatch, 1735 mplsLpsEventCapabilitiesMismatch, 1736 mplsLpsEventPathConfigMismatch, 1737 mplsLpsEventFopNoResponse, 1738 mplsLpsEventFopTimout 1739 } 1740 STATUS current 1741 DESCRIPTION 1742 "Collection of objects needed to implement notifications." 1743 ::= { mplsLpsGroups 4 } 1745 -- MPLS-LPS-MIB module ends 1746 END 1748 9. Security Considerations 1750 There are a number of management objects defined in this MIB module 1751 with a MAX-ACCESS clause of read-write and/or read-create. Such 1752 objects may be considered sensitive or vulnerable in some networks in 1753 a non-secure environment without proper protection can have a 1754 negative effect on network operations. These are the tables and 1755 objects and their sensitivity/vulnerability: 1757 o mplsLpsConfigTable is used to configure MPLS-TP linear protection 1758 domains. Improper manipulation of the objects in this table may 1759 result in different behaviors than network operators have 1760 originally intended, such as delaying traffic switching or causing 1761 a race condition with server layer protection after network 1762 failure (mplsLpsConfigHoldOff), delaying or speeding up reversion 1763 after recovering network failure (mplsLpsConfigWaitToRestore), 1764 unexpected traffic switching (mplsLpsConfigCommand), or 1765 discontinuance of operation of a protection switching control 1766 process (mplsLpsConfigMode, mplsLpsConfigProtectionType). 1768 o mplsLpsMeConfigTable is used to assign each ME either working or 1769 protection path. Improper manipulation of this object may result 1770 in discontinuance of operation of a protection switching control 1771 process. 1773 o In the case of the discontinuance of a protection switching 1774 control process, network operators will be notified. However, the 1775 notification is controlled by mplsLpsNotificationEnable object, 1776 which is read-write. 1778 Some of the readable objects in this MIB module (i.e., objects with a 1779 MAX-ACCESS other than not-accessible) may be considered sensitive or 1780 vulnerable in some network environments. It is thus important to 1781 control even GET and/or NOTIFY access to these objects and possibly 1782 to even encrypt the values of these objects when sending them over 1783 the network via SNMP. These are the tables and objects and their 1784 sensitivity/vulnerability: 1786 o mplsLpsStatusTable and mplsLpsMeStatusTable collectively show the 1787 history and current status of the MPLS-TP linear protection 1788 domains. They can be used to estimate the performances and 1789 qualities of the network being operated with the MPLS-TP linear 1790 protection. If an administrator does not want to reveal this 1791 information, then these tables should be considered sensitive/ 1792 vulnerable. 1794 SNMP versions prior to SNMPv3 did not include adequate security. 1795 Even if the network itself is secure (for example by using IPsec), 1796 there is no control as to who on the secure network is allowed to 1797 access and GET/SET (read/change/create/delete) the objects in this 1798 MIB module. 1800 Implementations SHOULD provide the security features described by the 1801 SNMPv3 framework (see [RFC3410]), and implementations claiming 1802 compliance to the SNMPv3 standard MUST include full support for 1803 authentication and privacy via the User-based Security Model (USM) 1804 RFC 3414 [RFC3414] with the AES cipher algorithm RFC 3826 [RFC3826]. 1805 Implementations MAY also provide support for the Transport Security 1806 Model (TSM) RFC 5591 [RFC5591] in combination with a secure transport 1807 such as SSH RFC 5592 [RFC5592] or TLS/DTLS RFC 6353 [RFC6353]. 1809 Further, deployment of SNMP versions prior to SNMPv3 is not 1810 recommended. Instead, it is RECOMMENDED to deploy SNMPv3 and to 1811 enable cryptographic security. It is then a customer/operator 1812 responsibility to ensure that the SNMP entity giving access to an 1813 instance of this MIB module is properly configured to give access to 1814 the objects only to those principals (users) that have legitimate 1815 rights to indeed GET or SET (change/create/delete) them. 1817 10. IANA Considerations 1819 IANA is requested to assign an OID for the MIB module from the "MIB 1820 Transmission Group - MPLS STD" sub-registry of the "Internet-standard 1821 MIB - Transmission Group" registry for the MPLS Linear Protection MIB 1822 module specified in this document. 1824 11. Acknowledgments 1826 The authors wish to thank Joan Cucchiara for her review as MIB 1827 Doctor, Joan's detailed comments were of great help for improving the 1828 quality of this document. 1830 12. References 1832 12.1. Normative References 1834 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1835 Requirement Levels", BCP 14, RFC 2119, 1836 DOI 10.17487/RFC2119, March 1997, 1837 . 1839 [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. 1840 Schoenwaelder, Ed., "Structure of Management Information 1841 Version 2 (SMIv2)", STD 58, RFC 2578, 1842 DOI 10.17487/RFC2578, April 1999, 1843 . 1845 [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. 1846 Schoenwaelder, Ed., "Textual Conventions for SMIv2", 1847 STD 58, RFC 2579, DOI 10.17487/RFC2579, April 1999, 1848 . 1850 [RFC2580] McCloghrie, K., Ed., Perkins, D., Ed., and J. 1851 Schoenwaelder, Ed., "Conformance Statements for SMIv2", 1852 STD 58, RFC 2580, DOI 10.17487/RFC2580, April 1999, 1853 . 1855 [RFC3289] Baker, F., Chan, K., and A. Smith, "Management Information 1856 Base for the Differentiated Services Architecture", 1857 RFC 3289, DOI 10.17487/RFC3289, May 2002, 1858 . 1860 12.2. Informative References 1862 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, 1863 "Introduction and Applicability Statements for Internet- 1864 Standard Management Framework", RFC 3410, 1865 DOI 10.17487/RFC3410, December 2002, 1866 . 1868 [RFC3414] Blumenthal, U. and B. Wijnen, "User-based Security Model 1869 (USM) for version 3 of the Simple Network Management 1870 Protocol (SNMPv3)", STD 62, RFC 3414, 1871 DOI 10.17487/RFC3414, December 2002, 1872 . 1874 [RFC3811] Nadeau, T., Ed. and J. Cucchiara, Ed., "Definitions of 1875 Textual Conventions (TCs) for Multiprotocol Label 1876 Switching (MPLS) Management", RFC 3811, 1877 DOI 10.17487/RFC3811, June 2004, 1878 . 1880 [RFC3812] Srinivasan, C., Viswanathan, A., and T. Nadeau, 1881 "Multiprotocol Label Switching (MPLS) Traffic Engineering 1882 (TE) Management Information Base (MIB)", RFC 3812, 1883 DOI 10.17487/RFC3812, June 2004, 1884 . 1886 [RFC3826] Blumenthal, U., Maino, F., and K. McCloghrie, "The 1887 Advanced Encryption Standard (AES) Cipher Algorithm in the 1888 SNMP User-based Security Model", RFC 3826, 1889 DOI 10.17487/RFC3826, June 2004, 1890 . 1892 [RFC5591] Harrington, D. and W. Hardaker, "Transport Security Model 1893 for the Simple Network Management Protocol (SNMP)", 1894 STD 78, RFC 5591, DOI 10.17487/RFC5591, June 2009, 1895 . 1897 [RFC5592] Harrington, D., Salowey, J., and W. Hardaker, "Secure 1898 Shell Transport Model for the Simple Network Management 1899 Protocol (SNMP)", RFC 5592, DOI 10.17487/RFC5592, June 1900 2009, . 1902 [RFC6353] Hardaker, W., "Transport Layer Security (TLS) Transport 1903 Model for the Simple Network Management Protocol (SNMP)", 1904 STD 78, RFC 6353, DOI 10.17487/RFC6353, July 2011, 1905 . 1907 [RFC6378] Weingarten, Y., Ed., Bryant, S., Osborne, E., Sprecher, 1908 N., and A. Fulignoli, Ed., "MPLS Transport Profile (MPLS- 1909 TP) Linear Protection", RFC 6378, DOI 10.17487/RFC6378, 1910 October 2011, . 1912 [RFC7271] Ryoo, J., Ed., Gray, E., Ed., van Helvoort, H., 1913 D'Alessandro, A., Cheung, T., and E. Osborne, "MPLS 1914 Transport Profile (MPLS-TP) Linear Protection to Match the 1915 Operational Expectations of Synchronous Digital Hierarchy, 1916 Optical Transport Network, and Ethernet Transport Network 1917 Operators", RFC 7271, DOI 10.17487/RFC7271, June 2014, 1918 . 1920 [RFC7697] Pan, P., Aldrin, S., Venkatesan, M., Sampath, K., Nadeau, 1921 T., and S. Boutros, "MPLS Transport Profile (MPLS-TP) 1922 Operations, Administration, and Maintenance (OAM) 1923 Identifiers Management Information Base (MIB)", RFC 7697, 1924 DOI 10.17487/RFC7697, January 2016, 1925 . 1927 Authors' Addresses 1929 Kingston Smiler Selvaraj 1930 IpInfusion 1931 RMZ Centennial 1932 Mahadevapura Post 1933 Bangalore - 560048 1934 India 1936 EMail: kingstonsmiler@gmail.com 1937 Venkatesan Mahalingam 1938 Dell Inc. 1939 5450 Great America Parkway 1940 Santa Clara, CA 95054 1941 USA 1943 EMail: venkat.mahalingams@gmail.com 1945 Vishwas Manral 1946 Nano Sec 1947 599 Fairchild Drive 1948 Mountain View, CA 1949 USA 1951 EMail: vishwas@nanosec.io 1953 Daniel King 1954 Old Dog Consulting 1955 UK 1957 EMail: daniel@olddog.co.uk 1959 Sam Aldrin 1960 Google, Inc. 1961 1600 Amphitheatre Parkway 1962 Mountain View, CA 1963 USA 1965 EMail: aldrin.ietf@gmail.com 1967 Jeong-dong Ryoo 1968 ETRI 1969 218 Gajeong-ro 1970 Yuseong-gu, Daejeon 34129 1971 South Korea 1973 EMail: ryoo@etri.re.kr