idnits 2.17.1 draft-dhody-pce-pcep-pathkey-mib-02.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: ---------------------------------------------------------------------------- == The page length should not exceed 58 lines per page, but there was 1 longer page, the longest (page 2) being 71 lines Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack a both a reference to RFC 2119 and the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. RFC 2119 keyword, line 855: '... It is RECOMMENDED that implementers...' RFC 2119 keyword, line 861: '... RECOMMENDED. Instead, it is RECOMM...' Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (September 5, 2011) is 4611 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) No issues found here. Summary: 1 error (**), 0 flaws (~~), 2 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 PCE Working Group D. Dhody 3 Internet-Draft U. Palle 4 Intended status: Standards Track Q. Zhao 5 Expires: March 8, 2012 Huawei Technology 6 D. King 7 Old Dog Consulting 8 September 5, 2011 10 Management Information Base for the PCE Communications Protocol (PCEP) 11 for Path-Key-Based Inter-Domain Path Computation 12 draft-dhody-pce-pcep-pathkey-mib-02 14 Abstract 16 This memo defines an experimental portion of the Management 17 Information Base for use with network management protocols in the 18 Internet community. In particular, it describes managed objects for 19 modeling of the Path Computation Element communication Protocol 20 (PCEP)for communications between a Path Computation Client (PCC)and a 21 Path Computation Element (PCE), or between two PCEs when path-key- 22 based inter-domain path computation is requested. 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 March 8, 2012. 47 Copyright Notice 49 Copyright (c) 2010 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 This Internet-Draft will expire on March 8, 2012. 64 Table of Contents 66 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 67 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 68 3. The Internet-Standard Management Framework . . . . . . . . . . 4 69 4. PCEP Pathkey MIB Module Architecture . . . . . . . . . . . . . 4 70 5. Example of the PCEP PathKey MIB module usage . . . . . . . . . 4 71 6. Object definitions . . . . . . . . . . . . . . . . . . . . . . 5 72 6.1. PCE-PCEP-PATHKEY-DRAFT-MIB . . . . . . . . . . . . . . . . 5 73 6.2. Objects for inclusion in module PCE-PCEP-DRAFT-MIB . . . . 18 74 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 19 75 8. Security Considerations . . . . . . . . . . . . . . . . . . . 19 76 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 20 77 9.1. Normative References . . . . . . . . . . . . . . . . . . . 20 78 9.2. Informative References . . . . . . . . . . . . . . . . . . 21 80 1. Introduction 82 The Path Computation Element (PCE) defined in [RFC4655] is an entity 83 that is capable of computing a network path or route based on a 84 network graph, and applying computational constraints. A Path 85 Computation Client (PCC) may make requests to a PCE for paths to be 86 computed. 88 The PCE communication protocol (PCEP) is designed as a communication 89 protocol between PCCs and PCEs for point-to-point (P2P) path 90 computations and is defined in [RFC5440]. 92 If confidentiality is required between domains, Path-Key-Based 93 mechanism is described in [RFC5520]. For preserving the 94 confidentiality of the "Confidential Path Segment (CPS)";the PCE 95 returns a path containing a loose hop in place of the segment that 96 must be kept confidential. 98 [PCE-PCEP-DRAFT-MIB] defines a portion of the Management Information 99 Base (MIB) for use with network management protocols in the Internet 100 community for P2P path computations. 102 This memo defines an experimental portion of the Management 103 Information Base for use with network management protocols in the 104 Internet community. In particular, it describes managed objects for 105 modeling of Path Computation Element communication Protocol 106 (PCEP)[RFC5440] for communications between a Path Computation Client 107 (PCC)and a Path Computation Element (PCE), or between two PCEs in 108 path-key-based inter-domain path computations. 110 Some objects maybe moved to [PCE-PCEP-DRAFT-MIB] after consensus with 111 the authors and working group, these are defined in section 6.2. 113 2. Terminology 115 The following terminology is used in this document. 117 CPS: Confidential Path Segment. A segment of a path that contains 118 nodes and links that the AS policy requires to not be disclosed 119 outside the AS. 121 Domain: Any collection of network elements within a common sphere of 122 address management or path computational responsibility. Examples 123 of domains include Interior Gateway Protocol (IGP) areas and 124 Autonomous Systems (ASs). 126 IGP: Interior Gateway Protocol. Either of the two routing 127 protocols, Open Shortest Path First (OSPF) or Intermediate System 128 to Intermediate System (IS-IS). 130 PCC: Path Computation Client: any client application requesting a 131 path computation to be performed by a Path Computation Element. 133 PCE: Path Computation Element. An entity (component, application, 134 or network node) that is capable of computing a network path or 135 route based on a network graph and applying computational 136 constraints. 138 P2P: Point-to-Point 140 3. The Internet-Standard Management Framework 142 For a detailed overview of the documents that describe the current 143 Internet-Standard Management Framework, please refer to section 7 of 144 RFC 3410 [RFC3410]. 146 Managed objects are accessed via a virtual information store, termed 147 the Management Information Base or MIB. MIB objects are generally 148 accessed through the Simple Network Management Protocol (SNMP). 149 Objects in the MIB are defined using the mechanisms defined in the 150 Structure of Management Information (SMI). This memo specifies a MIB 151 module that is compliant to the SMIv2, which is described in STD 152 58,RFC 2578 [RFC2578] and STD 58, RFC 2580 [RFC2580]. 154 4. PCEP Pathkey MIB Module Architecture 156 The PCEP Pathkey MIB will contain the following information: 158 o PCEP Pathkey counters, timers and configurations 160 o PCEP Pathkey table of CPS related information. 162 5. Example of the PCEP PathKey MIB module usage 164 In this section we provide an example (pcePcepPathKeyTable 1) of 165 using the MIB objects described in Section 6 (Object definitions) to 166 monitor. While this example is not meant to illustrate every 167 permutation of the MIB, it is intended as an aid to understanding 168 some of the key concepts. It is meant to be read after going through 169 the MIB itself. 171 pcePcepPathKeyTable 1 of the PCE-PCEP-PATHKEY-DRAFT-MIB module : 172 { 173 pcePcepPathKey (4512), 174 pcePcepPathKeyCPSIndex (1), 175 pcePcepPathKeyRequestSource (x.x.x.x), 176 pcePcepPathKeyRequestId (10), 177 pcePcepPathKeyRetrieved (1), 178 pcePcepPathKeyRetrieveSource (y.y.y.y), 179 pcePcepPathKeyDiscardTime (10), 180 pcePcepPathKeyReuseTime (30) 181 } 183 pcePcepPathKeyHopTable 1 of the PCE-PCEP-PATHKEY-DRAFT-MIB module : 184 { 185 pcePcepPathKeyHopListIndex 1, 186 pcePcepPathKeyHopIndex 1, 187 pcePcepPathKeyHopAddrType ipv4 (1), 188 pcePcepPathKeyHopIpAddr "192.168.100.1", 189 pcePcepPathKeyHopIpPrefixLen 32, 190 pcePcepPathKeyHopType strict (2) 191 } 192 { 193 pcePcepPathKeyHopListIndex 1, 194 pcePcepPathKeyHopIndex 2, 195 pcePcepPathKeyHopAddrType ipv4 (1), 196 pcePcepPathKeyHopIpAddr "192.168.100.2", 197 pcePcepPathKeyHopIpPrefixLen 32, 198 pcePcepPathKeyHopType strict (2) 199 } 201 6. Object definitions 203 6.1. PCE-PCEP-PATHKEY-DRAFT-MIB 205 This MIB module makes references to the following documents. 207 [RFC2578], [RFC2580], [RFC3411], [RFC2863], [RFC3813]. 209 PCE-PCEP-PATHKEY-DRAFT-MIB DEFINITIONS ::= BEGIN 211 IMPORTS 212 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, 213 Unsigned32, 214 Counter32, 215 OCTET STRING, 216 experimental 217 FROM SNMPv2-SMI -- [RFC2578] 219 TimeStamp 220 FROM SNMPv2-TC -- [RFC2579] 222 PcePcepIdentifier, 223 FROM PCE-TC-STD-MIB 225 MplsLSPID, MplsPathIndex, TeHopAddressType, 226 TeHopAddress, TeHopAddressUnnum 227 FROM MPLS-TC-STD-MIB -- [RFC3811] 229 MODULE-COMPLIANCE, 230 OBJECT-GROUP, 231 NOTIFICATION-GROUP 232 FROM SNMPv2-CONF; -- [RFC2580] 234 pcePcepPathkeyDraftMIB MODULE-IDENTITY 235 LAST-UPDATED "201109051200Z" -- Sept 5, 2011 236 ORGANIZATION "Path Computation Element (PCE) Working Group" 237 CONTACT-INFO " 239 Dhruv Dhody 240 Udayasree Palle 241 Quintin Zhao 242 Huawei Technology 243 Daniel King 244 OldDog Consulting 246 EMail: dhruv.dhody@huawei.com 247 EMail: udayasreepalle@huawei.com 248 EMail: quintin.zhao@huawei.com 249 EMail: daniel@oldog.co.uk 250 EMail comments directly to the PCE WG Mailing List at pce@ietf.org 251 WG-URL: http://www.ietf.org/html.charters/pce-charter.html 252 " 254 DESCRIPTION 255 "This MIB module defines a collection of objects for managing PCE 256 communication protocol(PCEP) for Path-Key-Based Inter-Domain Path 257 Computation" 259 -- Revision history 260 REVISION 261 "201109051200Z" -- 05 Sept 2011 12:00:00 EST 262 DESCRIPTION 263 " 264 Main Changes from -01 draft : 265 1. Added pcePcepPathKeyCPSIndex. 266 2. Added pcePcepPathKeyHopListIndex. 267 3. Removed pcePcepPathKeyHopNum. 268 4. Updated Contact Information. 270 REVISION 271 "201103081200Z" -- 08 Mar 2011 12:00:00 EST 272 DESCRIPTION 273 " 274 Main Changes from -00 draft : 275 1. Added HopTable to store the CPS hops. 276 2. Added Path Key Creation Time. 278 REVISION 279 "201009171200Z" -- 17 Sep 2010 12:00:00 EST 280 DESCRIPTION 282 "draft-00 version" 283 ::= { experimental 9999 } -- 285 -- Notifications -- 287 pcePcepPathKeyNotifications OBJECT IDENTIFIER ::= 288 { pcePcepPathKeyDraftMIB 0 } 290 pcePcepPathKeyMIBObjects OBJECT IDENTIFIER ::= 291 { pcePcepPathKeyDraftMIB 1 } 292 pcePcepPathKeyConformance OBJECT IDENTIFIER ::= 293 { pcePcepPathKeyDraftMIB 2 } 295 pcePcepPathKeyObjects OBJECT IDENTIFIER ::= 296 { pcePcepPathKeyMIBObjects 1 } 298 -- 300 -- PCE Pathkey Objects 302 -- 303 pcePcepPathKeyDiscardTimer OBJECT-TYPE 304 SYNTAX Unsigned32 305 UNITS "minutes" 306 MAX-ACCESS read-write 307 STATUS mandatory 308 DESCRIPTION 309 "The value which indicates a period of time after the 310 expiration of which a PCE discard unwanted path-keys." 311 ::= { pcePcepPathKeyObjects 1 } 313 pcePcepPathKeyReUseTimer OBJECT-TYPE 314 SYNTAX Unsigned32 315 UNITS "minutes" 316 MAX-ACCESS read-write 317 STATUS mandatory 318 DESCRIPTION 319 "The value which indicates a period of time which 320 should expire before an old path-key could be 321 reused for a new CPS." 322 ::= { pcePcepPathKeyObjects 2 } 324 pcePcepPathKeyRetainStatus OBJECT-TYPE 325 SYNTAX INTEGER { 326 enabled(1), 327 disabled(2) 328 } 329 MAX-ACCESS read-write 330 STATUS optional 331 DESCRIPTION 332 "The path-key retain status of this PCE to retain the 333 path-key and CPS for debugging purposes." 334 ::= { pcePcepPathKeyObjects 3 } 336 pcePcepPathKeysGenerated OBJECT-TYPE 337 SYNTAX Counter32 338 MAX-ACCESS read-only 339 STATUS mandatory 340 DESCRIPTION 341 "The number of path-keys generated by this PCE." 342 ::= { pcePcepPathKeyObjects 4 } 344 pcePcepPathKeyExpandUnknown OBJECT-TYPE 345 SYNTAX Counter32 346 MAX-ACCESS read-only 347 STATUS mandatory 348 DESCRIPTION 349 "The number of attempts to expand an unknown 350 path-key." 351 ::= { pcePcepPathKeyObjects 5 } 353 pcePcepPathKeyExpandExpired OBJECT-TYPE 354 SYNTAX Counter32 355 MAX-ACCESS read-only 356 STATUS mandatory 357 DESCRIPTION 358 "The number of attempts to expand an expired 359 path-key." 360 ::= { pcePcepPathKeyObjects 6 } 362 pcePcepPathKeyExpandSame OBJECT-TYPE 363 SYNTAX Counter32 364 MAX-ACCESS read-only 365 STATUS optional 366 DESCRIPTION 367 "The number of attempts to expand the same 368 path-key." 369 ::= { pcePcepPathKeyObjects 7 } 371 pcePcepPathKeyExpiredNoExpansion OBJECT-TYPE 372 SYNTAX Counter32 373 MAX-ACCESS read-only 374 STATUS optional 375 DESCRIPTION 376 "The number of path-keys expired without any attempt 377 to expand it." 378 ::= { pcePcepPathKeyObjects 8 } 380 pcePcepPathKeyExpansionSuccess OBJECT-TYPE 381 SYNTAX Counter32 382 MAX-ACCESS read-only 383 STATUS optional 384 DESCRIPTION 385 "The number of path-key expansion requests (PCReq) 386 which had successful retrieval." 387 ::= { pcePcepPathKeyObjects 9 } 389 pcePcepPathKeyExpansionFailures OBJECT-TYPE 390 SYNTAX Counter32 391 MAX-ACCESS read-only 392 STATUS optional 393 DESCRIPTION 394 "The number of path-key expansion requests (PCReq) 395 which had failed retrieval." 396 ::= { pcePcepPathKeyObjects 10 } 398 pcePcepPathKeyConfig OBJECT-TYPE 399 SYNTAX INTEGER { 400 enabled(1), 401 disabled(2) 402 } 403 MAX-ACCESS read-write 404 STATUS mandatory 405 DESCRIPTION 406 "The path-key based inter domain computation 407 configuration." 408 ::= { pcePcepPathKeyObjects 11 } 410 pcePcepPathKeyTable OBJECT-TYPE 411 SYNTAX SEQUENCE OF pcePcepPathKeyEntry 412 MAX-ACCESS not-accessible 413 STATUS current 414 DESCRIPTION 415 "This table contains information about the 416 Pathkey CPS of PCE." 417 ::= { pcePcepPathKeyObjects 12 } 419 pcePcepPathKeyEntry OBJECT-TYPE 420 SYNTAX pcePcepPathKeyEntry 421 MAX-ACCESS not-accessible 422 STATUS current 423 DESCRIPTION 424 "An entry in this table represents a path-key and CPS. 425 An entry is only created when a path-key generated by 426 PCE during inter-domain computation." 428 INDEX { pcePcepPathKey } 430 ::= { pcePcepPathKeyTable 1 } 432 pcePcepPathKeyEntry ::= SEQUENCE { 433 pcePcepPathKey Unsigned32, 434 pcePcepPathKeyCPSIndex MplsPathIndex, 435 pcePcepPathKeyRequestSource PcePcepIdentifier, 436 pcePcepPathKeyRequestId Unsigned32, 437 pcePcepPathKeyRetrieved INTEGER, 438 pcePcepPathKeyRetrieveSource PcePcepIdentifier, 439 pcePcepPathKeyCreationTime TimeStamp, 440 pcePcepPathKeyDiscardTime Unsigned32, 441 pcePcepPathKeyReuseTime Unsigned32, 442 } 444 pcePcepPathKey OBJECT-TYPE 445 SYNTAX Unsigned32 446 MAX-ACCESS read-only 447 STATUS mandatory 448 DESCRIPTION 449 "The path-key value to identify a CPS." 450 ::= { pcePcepPathKeyEntry 1 } 452 pcePcepPathKeyCPSIndex OBJECT-TYPE 453 SYNTAX MplsPathIndex 454 MAX-ACCESS read-only 455 STATUS mandatory 456 DESCRIPTION 457 "The HopList index of the CPS. This index 458 is used to expand Hops in 459 pcePcepPathKeyHopTable." 460 ::= { pcePcepPathKeyEntry 2 } 462 pcePcepPathKeyRequestSource OBJECT-TYPE 463 SYNTAX PcePcepIdentifier 464 MAX-ACCESS read-only 465 STATUS mandatory 466 DESCRIPTION 467 "Source that issued the original request that led 468 to the creation of the path-key." 469 ::= { pcePcepPathKeyEntry 3 } 471 pcePcepPathKeyRequestId OBJECT-TYPE 472 SYNTAX Unsigned32 473 MAX-ACCESS read-only 474 STATUS mandatory 475 DESCRIPTION 476 "The request ID of the original PCReq that led 477 to the creation of the path-key." 478 ::= { pcePcepPathKeyEntry 4 } 480 pcePcepPathKeyRetrieved OBJECT-TYPE 481 SYNTAX INTEGER { 482 TRUE(1), 483 FALSE(2) 484 } 485 MAX-ACCESS read-only 486 STATUS mandatory 487 DESCRIPTION 488 "It specifies whether the path-key is retrieved 489 or not." 490 ::= { pcePcepPathKeyEntry 5 } 492 pcePcepPathKeyRetrieveSource OBJECT-TYPE 493 SYNTAX PcePcepIdentifier 494 MAX-ACCESS read-only 495 STATUS mandatory 496 DESCRIPTION 497 "If the path-key is retrieved then by which 498 PCC." 499 ::= { pcePcepPathKeyEntry 6 } 501 pcePcepPathKeyCreationTime OBJECT-TYPE 502 SYNTAX TimeStamp 503 MAX-ACCESS read-only 504 STATUS mandatory 505 DESCRIPTION 506 "The value of sysUpTime at which Path Key 507 was generated by PCE." 508 ::= { pcePcepPathKeyEntry 7 } 510 pcePcepPathKeyDiscardTime OBJECT-TYPE 511 SYNTAX Unsigned32 512 MAX-ACCESS read-only 513 STATUS mandatory 514 DESCRIPTION 515 "The time after which the path segment associated 516 with the path-key will be discarded." 517 ::= { pcePcepPathKeyEntry 8 } 519 pcePcepPathKeyReuseTime OBJECT-TYPE 520 SYNTAX Unsigned32 521 MAX-ACCESS read-only 522 STATUS mandatory 523 DESCRIPTION 524 "The time after which the path-key will be available 525 for re-use." 526 ::= { pcePcepPathKeyEntry 9 } 528 pcePcepPathKeyHopTable OBJECT-TYPE 529 SYNTAX SEQUENCE OF pcePcepPathKeyHopEntry 530 MAX-ACCESS not-accessible 531 STATUS current 532 DESCRIPTION 533 "This table contains information about the 534 Pathkey Hop in the CPS of PCE." 535 ::= { pcePcepPathKeyObjects 13 } 537 pcePcepPathKeyHopEntry OBJECT-TYPE 538 SYNTAX pcePcepPathKeyHopEntry 539 MAX-ACCESS not-accessible 540 STATUS current 541 DESCRIPTION 542 "An entry in this table represents a Hop in the CPS. 543 An entry is only created when a path-key generated by 544 PCE during inter-domain computation." 546 INDEX { pcePcepPathKeyHopListIndex, 547 pcePcepPathKeyHopIndex } 549 ::= { pcePcepPathKeyHopTable 1 } 551 pcePcepPathKeyHopEntry ::= SEQUENCE { 552 pcePcepPathKeyHopListIndex MplsPathIndex, 553 pcePcepPathKeyHopIndex MplsPathIndex, 554 pcePcepPathKeyHopAddrType TeHopAddressType, 555 pcePcepPathKeyHopIpAddr TeHopAddress, 556 pcePcepPathKeyHopIpPrefixLen InetAddressPrefixLength, 557 pcePcepPathKeyHopAddrUnnum TeHopAddressUnnum, 558 pcePcepPathKeyHopLspId MplsLSPID, 559 pcePcepPathKeyHopType INTEGER, 560 } 562 pcePcepPathKeyHopListIndex OBJECT-TYPE 563 SYNTAX MplsPathIndex 564 MAX-ACCESS read-only 565 STATUS mandatory 566 DESCRIPTION 567 "The primary index into this table identifying a 568 particular CPS. All hops in the CPS will have the 569 same ListIndex. This corresponds to 570 pcePcepPathKeyCPSIndex in pcePcepPathKeyEntry." 572 ::= { pcePcepPathKeyHopEntry 1 } 574 pcePcepPathKeyHopIndex OBJECT-TYPE 575 SYNTAX MplsPathIndex 576 MAX-ACCESS read-only 577 STATUS mandatory 578 DESCRIPTION 579 "The secondry index into this table identifying a 580 particular Hop." 582 ::= { pcePcepPathKeyHopEntry 2 } 584 pcePcepPathKeyHopAddrType OBJECT-TYPE 585 SYNTAX TeHopAddressType 586 MAX-ACCESS read-only 587 STATUS mandatory 588 DESCRIPTION 589 "The Hop Address Type of this CPS hop. 590 Note that lspid(5) is a valid option only 591 for tunnels signaled via CRLDP." 592 DEFVAL { ipv4 } 593 ::= { pcePcepPathKeyHopEntry 2 } 595 pcePcepPathKeyHopIpAddr OBJECT-TYPE 596 SYNTAX TeHopAddress 597 MAX-ACCESS read-only 598 STATUS mandatory 599 DESCRIPTION 600 "The Hop Address for this CPS hop. 601 The type of this address is determined by the 602 value of the corresponding pcePcepPathKeyHopAddrType." 603 DEFVAL { '00000000'h } -- IPv4 address 0.0.0.0 604 ::= { pcePcepPathKeyHopEntry 4 } 606 pcePcepPathKeyHopIpPrefixLen OBJECT-TYPE 607 SYNTAX InetAddressPrefixLength 608 MAX-ACCESS read-only 609 STATUS current 610 DESCRIPTION 611 "If pcePcepPathKeyHopAddrType is set to ipv4(1) or 612 ipv6(2), then this value will contain an 613 appropriate prefix length for the IP address in 614 object pcePcepPathKeyHopIpAddr. Otherwise this value 615 is irrelevant and should be ignored." 616 DEFVAL { 32 } 617 ::= { pcePcepPathKeyHopEntry 5 } 619 pcePcepPathKeyHopAddrUnnum OBJECT-TYPE 620 SYNTAX TeHopAddressUnnum 621 MAX-ACCESS read-only 622 STATUS current 623 DESCRIPTION 624 "If pcePcepPathKeyHopAddrType is set to unnum(4), 625 then this value will contain the interface 626 identifier of the unnumbered interface for this 627 hop. This object should be used in conjunction 628 with pcePcepPathKeyHopIpAddr which would contain 629 the LSR Router ID in this case." 630 ::= { pcePcepPathKeyHopEntry 6 } 632 pcePcepPathKeyHopLspId OBJECT-TYPE 633 SYNTAX MplsLSPID 634 MAX-ACCESS read-only 635 STATUS current 636 DESCRIPTION 637 "If pcePcepPathKeyHopAddrType is set to lspid(5), 638 then this value will contain the LSPID of a tunnel 639 of this hop. The present tunnel being configured is 640 tunneled through this hop (using label stacking). 641 This object is otherwise insignificant and should 642 contain a value of 0 to indicate this fact." 643 ::= { pcePcepPathKeyHopEntry 7 } 645 pcePcepPathKeyHopType OBJECT-TYPE 646 SYNTAX INTEGER { 647 strict(1), 648 loose(2) 649 } 650 MAX-ACCESS read-only 651 STATUS mandatory 652 DESCRIPTION 653 "Denotes whether this hop is routed in a 654 strict or loose fashion. " 655 DEFVAL { strict } 656 ::= { pcePcepPathKeyHopEntry 8 } 658 --- 660 --- Notifications 662 --- 663 pcePcepPathKeyExpandUnknownNtf NOTIFICATION-TYPE 664 OBJECTS { 665 pcePcepPathKeyExpandUnknown 666 } 667 STATUS mandatory 668 DESCRIPTION 669 "This notification is sent when an attempt to expand an 670 unknown path-key is made. The value of the counter 671 pcePcepPathKeyExpandUnknown is also increased at this 672 time." 673 ::= { pcePcepPathKeyNotifications 1 } 675 pcePcepPathKeyExpandExpiredNtf NOTIFICATION-TYPE 676 OBJECTS { 677 pcePcepPathKeyExpandExpired 678 } 679 STATUS mandatory 680 DESCRIPTION 681 "This notification is sent when an attempt to expand an 682 expired path-key is made. The value of the counter 683 pcePcepPathKeyExpandExpired is also increased at this 684 time." 685 ::= { pcePcepPathKeyNotifications 2 } 687 pcePcepPathKeyExpandSameNtf NOTIFICATION-TYPE 688 OBJECTS { 689 pcePcepPathKeyExpandSame 690 } 691 STATUS optional 692 DESCRIPTION 693 "This notification is sent when a duplicate attempt to 694 expand the same path-key is made. The value of the 695 counter pcePcepPathKeyExpandSame is also increased at 696 this time." 697 ::= { pcePcepPathKeyNotifications 3 } 699 pcePcepPathKeyExpiredNoExpansionNtf NOTIFICATION-TYPE 700 OBJECTS { 701 pcePcepPathKeyExpiredNoExpansion 702 } 703 STATUS optional 704 DESCRIPTION 705 "This notification is sent when path-key expires without 706 any attempt to expand it. The value of the counter 707 pcePcepPathKeyExpiredNoExpansion is also increased at 708 this time." 709 ::= { pcePcepPathKeyNotifications 4 } 711 --**************************************************************** 712 -- Module Conformance Statement 713 --**************************************************************** 715 pcePcepPathKeyGroups 716 OBJECT IDENTIFIER ::= { pcePcepPathKeyConformance 1 } 718 pcePcepPathKeyCompliances 719 OBJECT IDENTIFIER ::= { pcePcepPathKeyConformance 2 } 721 -- 722 -- Full Compliance 723 -- 725 pcePcepPathKeyModuleFullCompliance MODULE-COMPLIANCE 726 STATUS current 727 DESCRIPTION 728 "The Module is implemented with support 729 for read-create and read-write. In other 730 words, both monitoring and configuration 731 are available when using this MODULE-COMPLIANCE." 733 MODULE -- this module 734 MANDATORY-GROUPS { pcePcepPathKeyGeneralGroup, 735 pcePcepPathKeyNotificationsGroup 736 } 738 ::= { pcePcepPathKeyCompliances 1 } 740 -- 741 -- Read-Only Compliance 742 -- 744 pcePcepPathKeyModuleReadOnlyCompliance MODULE-COMPLIANCE 745 STATUS current 746 DESCRIPTION 747 "The Module is implemented with support 748 for read-only. In other words, only monitoring 749 is available by implementing this MODULE-COMPLIANCE." 751 MODULE -- this module 752 MANDATORY-GROUPS { pcePcepPathKeyGeneralGroup, 753 pcePcepPathKeyNotificationsGroup 754 } 755 ::= { pcePcepPathKeyCompliances 2 } 757 -- units of conformance 758 pcePcepPathKeyGeneralGroup OBJECT-GROUP 759 OBJECTS { 760 pcePcepPathKeyDiscardTimer, 761 pcePcepPathKeyReUseTimer, 762 pcePcepPathKeysGenerated, 763 pcePcepPathKeyExpandUnknown, 764 pcePcepPathKeyExpandExpired, 765 pcePcepPathKeyConfig, 766 pcePcepPathKey, 767 pcePcepPathKeyCPSIndex, 768 pcePcepPathKeyRequestSource, 769 pcePcepPathKeyRequestId, 770 pcePcepPathKeyRetrieved, 771 pcePcepPathKeyRetrieveSource, 772 pcePcepPathKeyCreationTime, 773 pcePcepPathKeyDiscardTime, 774 pcePcepPathKeyReuseTime, 775 pcePcepPathKeyHopListIndex, 776 pcePcepPathKeyHopIndex, 777 pcePcepPathKeyHopAddrType, 778 pcePcepPathKeyHopIpAddr, 779 pcePcepPathKeyHopIpPrefixLen, 780 pcePcepPathKeyHopType 781 } 782 STATUS current 783 DESCRIPTION 784 "Objects that apply to all PCEP Pathkey MIB 785 implementations." 787 ::= { pcePcepPathKeyGroups 1 } 789 pcePcepPathKeyNotificationsGroup NOTIFICATION-GROUP 790 NOTIFICATIONS { pcePcepPathKeyExpandUnknownNtf, 791 pcePcepPathKeyExpandExpiredNtf 792 } 793 STATUS current 795 DESCRIPTION 796 "The notifications for a PCEP Pathkey MIB implementation." 797 ::= { pcePcepPathKeyGroups 2 } 799 END 801 6.2. Objects for inclusion in module PCE-PCEP-DRAFT-MIB 803 Following object maybe moved to [PCE-PCEP-DRAFT-MIB] after consensus 804 with the authors and working group. 806 pcePcepPathKeyConfig 808 7. IANA Considerations 810 TBD 812 8. Security Considerations 814 This MIB module can be used for configuration of certain objects, and 815 anything that can be configured can be incorrectly configured, with 816 potentially disastrous results. 818 There are a number of management objects defined in this MIB module 819 with a MAX-ACCESS clause of read-create. Such objects may be 820 considered sensitive or vulnerable in some network environments. The 821 support for SET operations in a non-secure environment without proper 822 protection can have a negatie effect on network operations. These 823 are the tables and objects and their sensitivity/vulnerability: 825 o pcePcepPathKeyDiscardTimer: Setting this value incorrectly may 826 cause the expiration of Pathkey before attempt to retrieve the 827 CPS. 829 o pcePcepPathKeyReUseTimer: Setting this value incorrectly may cause 830 the re-use of pathkey which may not guarantee the uniqueness of 831 path-key values. 833 The user of the PCE-PCEP-PATHKEY-DRAFT-MIB module must therefore be 834 aware that support for SET operations in a non-secure environment 835 without proper protection can have a negative effect on network 836 operations. 838 The readable objects in the PCE-PCEP-PATHKEY-DRAFT-MIB module (i.e., 839 those with MAX-ACCESS other than not-accessible) may be considered 840 sensitive in some environments since, collectively, they provide 841 information about the amount and frequency of path computation 842 requests and responses within the network and can reveal some aspects 843 of their configuration. 845 In such environments it is important to control also GET and NOTIFY 846 access to these objects and possibly even to encrypt their values 847 when sending them over the network via SNMP. 849 SNMP versions prior to SNMPv3 did not include adequate security. 850 Even if the network itself is secure (for example by using IPsec), 851 even then, there is no control as to who on the secure network is 852 allowed to access and GET/SET (read/change/create/delete) the objects 853 in this MIB module. 855 It is RECOMMENDED that implementers consider the security features as 856 provided by the SNMPv3 framework (see [RFC3410], section 8), 857 including full support for the SNMPv3 cryptographic mechanisms (for 858 authentication and privacy). 860 Further, deployment of SNMP versions prior to SNMPv3 is NOT 861 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 862 enable cryptographic security. It is then a customer/operator 863 responsibility to ensure that the SNMP entity giving access to an 864 instance of this MIB module is properly configured to give access to 865 the objects only to those principals (users) that have legitimate 866 rights to indeed GET or SET (change/create/delete) them. 868 9. References 870 9.1. Normative References 872 [RFC2578] McCloghrie, k., Perkins, D., Schoenwaelder, J., 873 Case, J., Rose, M., and S. Waldbusser, 874 "Structure of Management Information Version 2 875 (SMIv2)", April 1999. 877 [RFC2579] McCloghrie, k., Perkins, D., Schoenwaelder, J., 878 Case, J., Rose, M., and S. Waldbusser, "Textual 879 Conventions for SMIv2", April 1999. 881 [RFC2580] McCloghrie, k., Perkins, D., Schoenwaelder, J., 882 Case, J., Rose, M., and S. Waldbusser, 883 "Conformance Statements for SMIv2", April 1999. 885 [RFC2863] McCloghrie, k. and F. Kastenholz, "The 886 Interfaces Group MIB", June 2000. 888 [RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An 889 Architecture for Describing Simple Network 890 Management Protocol (SNMP) Management 891 Frameworks", December 2002. 893 [RFC3811] Nadeau, T. and J. Cucchiara, "Definition of 894 Textual Conventions and for Multiprotocol Label 895 Switching (MPLS) Management", June 2004. 897 [RFC3813] Srinivasan, C., Viswanathan, A., and T. Nadeau, 898 "MPLS Multiprotocol Label Switching (MPLS) 899 Label Switch Router Management Information 900 Base", June 2004. 902 [RFC5440] Ayyangar, A ., Farrel, A ., Oki, E., Atlas, A., 903 Dolganow, A., Ikejiri, Y., Kumaki, K., Vasseur, 904 J., and J. Roux, "Path Computation Element 905 (PCE) communication Protocol (PCEP)", 906 March 2009. 908 9.2. Informative References 910 [PCE-PCEP-DRAFT-MIB] Kiran Koushik, A S., Stephan, E., Zhao, Q., and 911 D. King, "PCE communication protocol(PCEP) 912 Management Information Base", July 2010. 914 [RFC3410] Case, J ., Mundy, R., Partain, D., and B. 915 Stewart, "Introduction and Applicability 916 Statements for Internet-Standard Management 917 Framework", December 2002. 919 [RFC4655] Farrel, A., Vasseur, J., and J. Ash, "A Path 920 Computation Element (PCE)-Based Architecture", 921 August 2006. 923 [RFC5520] Bradford, R., Vasseur, JP., and A. Farrel, 924 "Preserving Topology Confidentiality in Inter- 925 Domain Path Computation Using a Path-Key-Based 926 Mechanism", April 2009. 928 Authors' Addresses 930 Dhruv Dhody 931 Huawei Technology 932 Leela Palace 933 Bangalore, Karnataka 560008 934 INDIA 936 EMail: dhruv.dhody@huawei.com 938 Udayasree Palle 939 Huawei Technology 940 Leela Palace 941 Bangalore, Karnataka 560008 942 INDIA 944 EMail: Udayasreepalle@huawei.com 945 Quintin Zhao 946 Huawei Technology 947 125 Nagog Technology Park 948 Acton, MA 01719 949 US 951 EMail: quintin.zhao@huawei.com 953 Daniel King 954 Old Dog Consulting 955 UK 957 EMail: daniel@olddog.co.uk