idnits 2.17.1 draft-dhody-pce-pcep-pathkey-mib-01.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 845: '... It is RECOMMENDED that implementers...' RFC 2119 keyword, line 851: '... 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 (March 11, 2011) is 4794 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) == Missing Reference: 'RFC 5520' is mentioned on line 93, but not defined == Unused Reference: 'RFC5520' is defined on line 913, but no explicit reference was found in the text Summary: 1 error (**), 0 flaws (~~), 4 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: September 12, 2011 Huawei Technology 6 D. King 7 Old Dog Consulting 8 March 11, 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-01 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 September 12, 2011. 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 September 12, 2011. 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 . . . . 19 74 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 20 75 8. Security Considerations . . . . . . . . . . . . . . . . . . . 20 76 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 21 77 9.1. Normative References . . . . . . . . . . . . . . . . . . . 21 78 9.2. Informative References . . . . . . . . . . . . . . . . . . 22 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 [RFC 5520]. 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 pcePcepPathKeyFirstHopIndex (1), 175 pcePcepPathKeyHopNum (2), 176 pcePcepPathKeyRequestSource (x.x.x.x), 177 pcePcepPathKeyRequestId (10), 178 pcePcepPathKeyRetrieved (1), 179 pcePcepPathKeyRetrieveSource (y.y.y.y), 180 pcePcepPathKeyDiscardTime (10), 181 pcePcepPathKeyReuseTime (30) 182 } 184 pcePcepPathKeyHopTable 1 of the PCE-PCEP-PATHKEY-DRAFT-MIB module : 185 { 186 pcePcepPathKeyHopIndex 1, 187 pcePcepPathKeyHopAddrType ipv4 (1), 188 pcePcepPathKeyHopIpAddr "192.168.100.1", 189 pcePcepPathKeyHopIpPrefixLen 32, 190 pcePcepPathKeyHopType strict (2) 191 } 192 { 193 pcePcepPathKeyHopIndex 2, 194 pcePcepPathKeyHopAddrType ipv4 (1), 195 pcePcepPathKeyHopIpAddr "192.168.100.2", 196 pcePcepPathKeyHopIpPrefixLen 32, 197 pcePcepPathKeyHopType strict (2) 198 } 200 6. Object definitions 202 6.1. PCE-PCEP-PATHKEY-DRAFT-MIB 204 This MIB module makes references to the following documents. 206 [RFC2578], [RFC2580], [RFC3411], [RFC2863], [RFC3813]. 208 PCE-PCEP-PATHKEY-DRAFT-MIB DEFINITIONS ::= BEGIN 210 IMPORTS 211 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, 212 Unsigned32, 213 Counter32, 214 OCTET STRING, 215 experimental 216 FROM SNMPv2-SMI -- [RFC2578] 218 TimeStamp 219 FROM SNMPv2-TC -- [RFC2579] 221 PcePcepIdentifier, 222 FROM PCE-TC-STD-MIB 224 MplsLSPID, MplsPathIndex, TeHopAddressType, 225 TeHopAddress, TeHopAddressUnnum 226 FROM MPLS-TC-STD-MIB -- [RFC3811] 228 MODULE-COMPLIANCE, 229 OBJECT-GROUP, 230 NOTIFICATION-GROUP 231 FROM SNMPv2-CONF; -- [RFC2580] 233 pcePcepPathkeyDraftMIB MODULE-IDENTITY 234 LAST-UPDATED "201103081200Z" --Mar 8, 2011 235 ORGANIZATION "Path Computation Element (PCE) Working Group" 236 CONTACT-INFO " 238 Dhruv Dhody 239 Udayasree Palle 240 Quintin Zhao 241 Huawei Technology 242 Daniel King 243 OldDog Consulting 245 EMail: dhruvd@huawei.com 246 EMail: udayasreepalle@huawei.com 247 EMail: qzhao@huawei.com 248 EMail: daniel@oldog.co.uk 249 EMail comments directly to the PCE WG Mailing List at pce@ietf.org 250 WG-URL: http://www.ietf.org/html.charters/pce-charter.html 251 " 253 DESCRIPTION 254 "This MIB module defines a collection of objects for managing PCE 255 communication protocol(PCEP) for Path-Key-Based Inter-Domain Path 256 Computation" 258 -- Revision history 260 REVISION 261 "201103081200Z" -- 08 Mar 2011 12:00:00 EST 262 DESCRIPTION 263 " 264 Main Changes from -00 draft : 265 1. Added HopTable to store the CPS hops. 266 2. Added Path Key Creation Time. 268 REVISION 269 "201009171200Z" -- 17 Sep 2010 12:00:00 EST 270 DESCRIPTION 272 "draft-00 version" 273 ::= { experimental 9999 } -- 275 -- Notifications -- 277 pcePcepPathKeyNotifications OBJECT IDENTIFIER ::= 278 { pcePcepPathKeyDraftMIB 0 } 280 pcePcepPathKeyMIBObjects OBJECT IDENTIFIER ::= 281 { pcePcepPathKeyDraftMIB 1 } 282 pcePcepPathKeyConformance OBJECT IDENTIFIER ::= 283 { pcePcepPathKeyDraftMIB 2 } 285 pcePcepPathKeyObjects OBJECT IDENTIFIER ::= 286 { pcePcepPathKeyMIBObjects 1 } 288 -- 290 -- PCE Pathkey Objects 292 -- 293 pcePcepPathKeyDiscardTimer OBJECT-TYPE 294 SYNTAX Unsigned32 295 UNITS "minutes" 296 MAX-ACCESS read-write 297 STATUS mandatory 298 DESCRIPTION 299 "The value which indicates a period of time after the 300 expiration of which a PCE discard unwanted path-keys." 301 ::= { pcePcepPathKeyObjects 1 } 303 pcePcepPathKeyReUseTimer 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 which 310 should expire before an old path-key could be 311 reused for a new CPS." 312 ::= { pcePcepPathKeyObjects 2 } 314 pcePcepPathKeyRetainStatus OBJECT-TYPE 315 SYNTAX INTEGER { 316 enabled(1), 317 disabled(2) 318 } 319 MAX-ACCESS read-write 320 STATUS optional 321 DESCRIPTION 322 "The path-key retain status of this PCE to retain the 323 path-key and CPS for debugging purposes." 324 ::= { pcePcepPathKeyObjects 3 } 326 pcePcepPathKeysGenerated OBJECT-TYPE 327 SYNTAX Counter32 328 MAX-ACCESS read-only 329 STATUS mandatory 330 DESCRIPTION 331 "The number of path-keys generated by this PCE." 332 ::= { pcePcepPathKeyObjects 4 } 334 pcePcepPathKeyExpandUnknown OBJECT-TYPE 335 SYNTAX Counter32 336 MAX-ACCESS read-only 337 STATUS mandatory 338 DESCRIPTION 339 "The number of attempts to expand an unknown 340 path-key." 341 ::= { pcePcepPathKeyObjects 5 } 343 pcePcepPathKeyExpandExpired OBJECT-TYPE 344 SYNTAX Counter32 345 MAX-ACCESS read-only 346 STATUS mandatory 347 DESCRIPTION 348 "The number of attempts to expand an expired 349 path-key." 350 ::= { pcePcepPathKeyObjects 6 } 352 pcePcepPathKeyExpandSame OBJECT-TYPE 353 SYNTAX Counter32 354 MAX-ACCESS read-only 355 STATUS optional 356 DESCRIPTION 357 "The number of attempts to expand the same 358 path-key." 359 ::= { pcePcepPathKeyObjects 7 } 361 pcePcepPathKeyExpiredNoExpansion OBJECT-TYPE 362 SYNTAX Counter32 363 MAX-ACCESS read-only 364 STATUS optional 365 DESCRIPTION 366 "The number of path-keys expired without any attempt 367 to expand it." 368 ::= { pcePcepPathKeyObjects 8 } 370 pcePcepPathKeyExpansionSuccess OBJECT-TYPE 371 SYNTAX Counter32 372 MAX-ACCESS read-only 373 STATUS optional 374 DESCRIPTION 375 "The number of path-key expansion requests (PCReq) 376 which had successful retrieval." 377 ::= { pcePcepPathKeyObjects 9 } 379 pcePcepPathKeyExpansionFailures OBJECT-TYPE 380 SYNTAX Counter32 381 MAX-ACCESS read-only 382 STATUS optional 383 DESCRIPTION 384 "The number of path-key expansion requests (PCReq) 385 which had failed retrieval." 386 ::= { pcePcepPathKeyObjects 10 } 388 pcePcepPathKeyConfig OBJECT-TYPE 389 SYNTAX INTEGER { 390 enabled(1), 391 disabled(2) 392 } 393 MAX-ACCESS read-write 394 STATUS mandatory 395 DESCRIPTION 396 "The path-key based inter domain computation 397 configuration." 398 ::= { pcePcepPathKeyObjects 11 } 400 pcePcepPathKeyTable OBJECT-TYPE 401 SYNTAX SEQUENCE OF pcePcepPathKeyEntry 402 MAX-ACCESS not-accessible 403 STATUS current 404 DESCRIPTION 405 "This table contains information about the 406 Pathkey CPS of PCE." 407 ::= { pcePcepPathKeyObjects 12 } 409 pcePcepPathKeyEntry OBJECT-TYPE 410 SYNTAX pcePcepPathKeyEntry 411 MAX-ACCESS not-accessible 412 STATUS current 413 DESCRIPTION 414 "An entry in this table represents a path-key and CPS. 415 An entry is only created when a path-key generated by 416 PCE during inter-domain computation." 418 INDEX { pcePcepPathKey } 420 ::= { pcePcepPathKeyTable 1 } 422 pcePcepPathKeyEntry ::= SEQUENCE { 423 pcePcepPathKey Unsigned32, 424 pcePcepPathKeyFirstHopIndex MplsPathIndex, 425 pcePcepPathKeyHopNum Unsigned32, 426 pcePcepPathKeyRequestSource PcePcepIdentifier, 427 pcePcepPathKeyRequestId Unsigned32, 428 pcePcepPathKeyRetrieved INTEGER, 429 pcePcepPathKeyRetrieveSource PcePcepIdentifier, 430 pcePcepPathKeyCreationTime TimeStamp, 431 pcePcepPathKeyDiscardTime Unsigned32, 432 pcePcepPathKeyReuseTime Unsigned32, 433 } 435 pcePcepPathKey OBJECT-TYPE 436 SYNTAX Unsigned32 437 MAX-ACCESS read-only 438 STATUS mandatory 439 DESCRIPTION 440 "The path-key value to identify a CPS." 441 ::= { pcePcepPathKeyEntry 1 } 443 pcePcepPathKeyFirstHopIndex OBJECT-TYPE 444 SYNTAX MplsPathIndex 445 MAX-ACCESS read-only 446 STATUS mandatory 447 DESCRIPTION 448 "The Hop index of the first Hop in the CPS. This 449 index along with pcePcepPathKeyHopNum is used to 450 traverse the Hops in the CPS." 451 ::= { pcePcepPathKeyEntry 2 } 453 pcePcepPathKeyHopNum OBJECT-TYPE 454 SYNTAX Unsigned32 455 MAX-ACCESS read-only 456 STATUS mandatory 457 DESCRIPTION 458 "The number of Hops in this CPS. This number along 459 with pcePcepPathKeyFirstHopIndex is used to 460 traverse the Hops in the CPS." 461 ::= { pcePcepPathKeyEntry 3 } 463 pcePcepPathKeyRequestSource OBJECT-TYPE 464 SYNTAX PcePcepIdentifier 465 MAX-ACCESS read-only 466 STATUS mandatory 467 DESCRIPTION 468 "Source that issued the original request that led 469 to the creation of the path-key." 470 ::= { pcePcepPathKeyEntry 4 } 472 pcePcepPathKeyRequestId OBJECT-TYPE 473 SYNTAX Unsigned32 474 MAX-ACCESS read-only 475 STATUS mandatory 476 DESCRIPTION 477 "The request ID of the original PCReq that led 478 to the creation of the path-key." 479 ::= { pcePcepPathKeyEntry 5 } 481 pcePcepPathKeyRetrieved OBJECT-TYPE 482 SYNTAX INTEGER { 483 TRUE(1), 484 FALSE(2) 485 } 486 MAX-ACCESS read-only 487 STATUS mandatory 488 DESCRIPTION 489 "It specifies whether the path-key is retrieved 490 or not." 491 ::= { pcePcepPathKeyEntry 6 } 493 pcePcepPathKeyRetrieveSource OBJECT-TYPE 494 SYNTAX PcePcepIdentifier 495 MAX-ACCESS read-only 496 STATUS mandatory 497 DESCRIPTION 498 "If the path-key is retrieved then by which 499 PCC." 500 ::= { pcePcepPathKeyEntry 7 } 502 pcePcepPathKeyCreationTime OBJECT-TYPE 503 SYNTAX TimeStamp 504 MAX-ACCESS read-only 505 STATUS mandatory 506 DESCRIPTION 507 "The value of sysUpTime at which Path Key 508 was generated by PCE." 509 ::= { pcePcepPathKeyEntry 8 } 511 pcePcepPathKeyDiscardTime OBJECT-TYPE 512 SYNTAX Unsigned32 513 MAX-ACCESS read-only 514 STATUS mandatory 515 DESCRIPTION 516 "The time after which the path segment associated 517 with the path-key will be discarded." 518 ::= { pcePcepPathKeyEntry 9 } 520 pcePcepPathKeyReuseTime OBJECT-TYPE 521 SYNTAX Unsigned32 522 MAX-ACCESS read-only 523 STATUS mandatory 524 DESCRIPTION 525 "The time after which the path-key will be available 526 for re-use." 527 ::= { pcePcepPathKeyEntry 10 } 529 pcePcepPathKeyHopTable OBJECT-TYPE 530 SYNTAX SEQUENCE OF pcePcepPathKeyHopEntry 531 MAX-ACCESS not-accessible 532 STATUS current 533 DESCRIPTION 534 "This table contains information about the 535 Pathkey Hop in the CPS of PCE." 536 ::= { pcePcepPathKeyObjects 13 } 538 pcePcepPathKeyHopEntry OBJECT-TYPE 539 SYNTAX pcePcepPathKeyHopEntry 540 MAX-ACCESS not-accessible 541 STATUS current 542 DESCRIPTION 543 "An entry in this table represents a Hop in the CPS. 544 An entry is only created when a path-key generated by 545 PCE during inter-domain computation." 547 INDEX { pcePcepPathKeyHopIndex } 549 ::= { pcePcepPathKeyHopTable 1 } 551 pcePcepPathKeyHopEntry ::= SEQUENCE { 552 pcePcepPathKeyHopIndex MplsPathIndex, 553 pcePcepPathKeyHopAddrType TeHopAddressType, 554 pcePcepPathKeyHopIpAddr TeHopAddress, 555 pcePcepPathKeyHopIpPrefixLen InetAddressPrefixLength, 556 pcePcepPathKeyHopAddrUnnum TeHopAddressUnnum, 557 pcePcepPathKeyHopLspId MplsLSPID, 558 pcePcepPathKeyHopType INTEGER, 559 } 561 pcePcepPathKeyHopIndex OBJECT-TYPE 562 SYNTAX MplsPathIndex 563 MAX-ACCESS read-only 564 STATUS mandatory 565 DESCRIPTION 566 "The index into this table identifying a particular 567 Hop. All Hops in the CPS are added sequentially into 568 the table. The first hop index and number of Hops are 569 used for traversing the table." 571 ::= { pcePcepPathKeyHopEntry 1 } 573 pcePcepPathKeyHopAddrType OBJECT-TYPE 574 SYNTAX TeHopAddressType 575 MAX-ACCESS read-only 576 STATUS mandatory 577 DESCRIPTION 578 "The Hop Address Type of this CPS hop. 579 Note that lspid(5) is a valid option only 580 for tunnels signaled via CRLDP." 581 DEFVAL { ipv4 } 582 ::= { pcePcepPathKeyHopEntry 2 } 584 pcePcepPathKeyHopIpAddr OBJECT-TYPE 585 SYNTAX TeHopAddress 586 MAX-ACCESS read-only 587 STATUS mandatory 588 DESCRIPTION 589 "The Hop Address for this CPS hop. 590 The type of this address is determined by the 591 value of the corresponding pcePcepPathKeyHopAddrType." 592 DEFVAL { '00000000'h } -- IPv4 address 0.0.0.0 593 ::= { pcePcepPathKeyHopEntry 3 } 595 pcePcepPathKeyHopIpPrefixLen OBJECT-TYPE 596 SYNTAX InetAddressPrefixLength 597 MAX-ACCESS read-only 598 STATUS current 599 DESCRIPTION 600 "If pcePcepPathKeyHopAddrType is set to ipv4(1) or 601 ipv6(2), then this value will contain an 602 appropriate prefix length for the IP address in 603 object pcePcepPathKeyHopIpAddr. Otherwise this value 604 is irrelevant and should be ignored." 605 DEFVAL { 32 } 606 ::= { pcePcepPathKeyHopEntry 4 } 608 pcePcepPathKeyHopAddrUnnum OBJECT-TYPE 609 SYNTAX TeHopAddressUnnum 610 MAX-ACCESS read-only 611 STATUS current 612 DESCRIPTION 613 "If pcePcepPathKeyHopAddrType is set to unnum(4), 614 then this value will contain the interface 615 identifier of the unnumbered interface for this 616 hop. This object should be used in conjunction 617 with pcePcepPathKeyHopIpAddr which would contain 618 the LSR Router ID in this case." 619 ::= { pcePcepPathKeyHopEntry 5 } 621 pcePcepPathKeyHopLspId OBJECT-TYPE 622 SYNTAX MplsLSPID 623 MAX-ACCESS read-only 624 STATUS current 625 DESCRIPTION 626 "If pcePcepPathKeyHopAddrType is set to lspid(5), 627 then this value will contain the LSPID of a tunnel 628 of this hop. The present tunnel being configured is 629 tunneled through this hop (using label stacking). 630 This object is otherwise insignificant and should 631 contain a value of 0 to indicate this fact." 632 ::= { pcePcepPathKeyHopEntry 6 } 634 pcePcepPathKeyHopType OBJECT-TYPE 635 SYNTAX INTEGER { 636 strict(1), 637 loose(2) 638 } 639 MAX-ACCESS read-only 640 STATUS mandatory 641 DESCRIPTION 642 "Denotes whether this hop is routed in a 643 strict or loose fashion. " 644 DEFVAL { strict } 645 ::= { pcePcepPathKeyHopEntry 7 } 647 --- 649 --- Notifications 651 --- 653 pcePcepPathKeyExpandUnknownNtf NOTIFICATION-TYPE 654 OBJECTS { 655 pcePcepPathKeyExpandUnknown 656 } 657 STATUS mandatory 658 DESCRIPTION 659 "This notification is sent when an attempt to expand an 660 unknown path-key is made. The value of the counter 661 pcePcepPathKeyExpandUnknown is also increased at this 662 time." 663 ::= { pcePcepPathKeyNotifications 1 } 665 pcePcepPathKeyExpandExpiredNtf NOTIFICATION-TYPE 666 OBJECTS { 667 pcePcepPathKeyExpandExpired 668 } 669 STATUS mandatory 670 DESCRIPTION 671 "This notification is sent when an attempt to expand an 672 expired path-key is made. The value of the counter 673 pcePcepPathKeyExpandExpired is also increased at this 674 time." 675 ::= { pcePcepPathKeyNotifications 2 } 677 pcePcepPathKeyExpandSameNtf NOTIFICATION-TYPE 678 OBJECTS { 679 pcePcepPathKeyExpandSame 680 } 681 STATUS optional 682 DESCRIPTION 683 "This notification is sent when a duplicate attempt to 684 expand the same path-key is made. The value of the 685 counter pcePcepPathKeyExpandSame is also increased at 686 this time." 687 ::= { pcePcepPathKeyNotifications 3 } 689 pcePcepPathKeyExpiredNoExpansionNtf NOTIFICATION-TYPE 690 OBJECTS { 691 pcePcepPathKeyExpiredNoExpansion 692 } 693 STATUS optional 694 DESCRIPTION 695 "This notification is sent when path-key expires without 696 any attempt to expand it. The value of the counter 697 pcePcepPathKeyExpiredNoExpansion is also increased at 698 this time." 699 ::= { pcePcepPathKeyNotifications 4 } 701 --**************************************************************** 702 -- Module Conformance Statement 703 --**************************************************************** 705 pcePcepPathKeyGroups 706 OBJECT IDENTIFIER ::= { pcePcepPathKeyConformance 1 } 708 pcePcepPathKeyCompliances 709 OBJECT IDENTIFIER ::= { pcePcepPathKeyConformance 2 } 711 -- 712 -- Full Compliance 713 -- 715 pcePcepPathKeyModuleFullCompliance MODULE-COMPLIANCE 716 STATUS current 717 DESCRIPTION 718 "The Module is implemented with support 719 for read-create and read-write. In other 720 words, both monitoring and configuration 721 are available when using this MODULE-COMPLIANCE." 723 MODULE -- this module 724 MANDATORY-GROUPS { pcePcepPathKeyGeneralGroup, 725 pcePcepPathKeyNotificationsGroup 726 } 728 ::= { pcePcepPathKeyCompliances 1 } 730 -- 731 -- Read-Only Compliance 732 -- 734 pcePcepPathKeyModuleReadOnlyCompliance MODULE-COMPLIANCE 735 STATUS current 736 DESCRIPTION 737 "The Module is implemented with support 738 for read-only. In other words, only monitoring 739 is available by implementing this MODULE-COMPLIANCE." 741 MODULE -- this module 742 MANDATORY-GROUPS { pcePcepPathKeyGeneralGroup, 743 pcePcepPathKeyNotificationsGroup 744 } 745 ::= { pcePcepPathKeyCompliances 2 } 747 -- units of conformance 748 pcePcepPathKeyGeneralGroup OBJECT-GROUP 749 OBJECTS { 750 pcePcepPathKeyDiscardTimer, 751 pcePcepPathKeyReUseTimer, 752 pcePcepPathKeysGenerated, 753 pcePcepPathKeyExpandUnknown, 754 pcePcepPathKeyExpandExpired, 755 pcePcepPathKeyConfig, 756 pcePcepPathKey, 757 pcePcepPathKeyFirstHopIndex, 758 pcePcepPathKeyHopNum, 759 pcePcepPathKeyRequestSource, 760 pcePcepPathKeyRequestId, 761 pcePcepPathKeyRetrieved, 762 pcePcepPathKeyRetrieveSource, 763 pcePcepPathKeyCreationTime, 764 pcePcepPathKeyDiscardTime, 765 pcePcepPathKeyReuseTime, 766 pcePcepPathKeyHopIndex, 767 pcePcepPathKeyHopAddrType, 768 pcePcepPathKeyHopIpAddr, 769 pcePcepPathKeyHopIpPrefixLen, 770 pcePcepPathKeyHopType 771 } 772 STATUS current 773 DESCRIPTION 774 "Objects that apply to all PCEP Pathkey MIB 775 implementations." 777 ::= { pcePcepPathKeyGroups 1 } 779 pcePcepPathKeyNotificationsGroup NOTIFICATION-GROUP 780 NOTIFICATIONS { pcePcepPathKeyExpandUnknownNtf, 781 pcePcepPathKeyExpandExpiredNtf 782 } 783 STATUS current 785 DESCRIPTION 786 "The notifications for a PCEP Pathkey MIB implementation." 787 ::= { pcePcepPathKeyGroups 2 } 789 END 791 6.2. Objects for inclusion in module PCE-PCEP-DRAFT-MIB 793 Following object maybe moved to [PCE-PCEP-DRAFT-MIB] after consensus 794 with the authors and working group. 796 pcePcepPathKeyConfig 798 7. IANA Considerations 800 TBD 802 8. Security Considerations 804 This MIB module can be used for configuration of certain objects, and 805 anything that can be configured can be incorrectly configured, with 806 potentially disastrous results. 808 There are a number of management objects defined in this MIB module 809 with a MAX-ACCESS clause of read-create. Such objects may be 810 considered sensitive or vulnerable in some network environments. The 811 support for SET operations in a non-secure environment without proper 812 protection can have a negatie effect on network operations. These 813 are the tables and objects and their sensitivity/vulnerability: 815 o pcePcepPathKeyDiscardTimer: Setting this value incorrectly may 816 cause the expiration of Pathkey before attempt to retrieve the 817 CPS. 819 o pcePcepPathKeyReUseTimer: Setting this value incorrectly may cause 820 the re-use of pathkey which may not guarantee the uniqueness of 821 path-key values. 823 The user of the PCE-PCEP-PATHKEY-DRAFT-MIB module must therefore be 824 aware that support for SET operations in a non-secure environment 825 without proper protection can have a negative effect on network 826 operations. 828 The readable objects in the PCE-PCEP-PATHKEY-DRAFT-MIB module (i.e., 829 those with MAX-ACCESS other than not-accessible) may be considered 830 sensitive in some environments since, collectively, they provide 831 information about the amount and frequency of path computation 832 requests and responses within the network and can reveal some aspects 833 of their configuration. 835 In such environments it is important to control also GET and NOTIFY 836 access to these objects and possibly even to encrypt their values 837 when sending them over the network via SNMP. 839 SNMP versions prior to SNMPv3 did not include adequate security. 840 Even if the network itself is secure (for example by using IPsec), 841 even then, there is no control as to who on the secure network is 842 allowed to access and GET/SET (read/change/create/delete) the objects 843 in this MIB module. 845 It is RECOMMENDED that implementers consider the security features as 846 provided by the SNMPv3 framework (see [RFC3410], section 8), 847 including full support for the SNMPv3 cryptographic mechanisms (for 848 authentication and privacy). 850 Further, deployment of SNMP versions prior to SNMPv3 is NOT 851 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 852 enable cryptographic security. It is then a customer/operator 853 responsibility to ensure that the SNMP entity giving access to an 854 instance of this MIB module is properly configured to give access to 855 the objects only to those principals (users) that have legitimate 856 rights to indeed GET or SET (change/create/delete) them. 858 9. References 860 9.1. Normative References 862 [RFC2578] McCloghrie, k., Perkins, D., Schoenwaelder, J., 863 Case, J., Rose, M., and S. Waldbusser, 864 "Structure of Management Information Version 2 865 (SMIv2)", April 1999. 867 [RFC2579] McCloghrie, k., Perkins, D., Schoenwaelder, J., 868 Case, J., Rose, M., and S. Waldbusser, "Textual 869 Conventions for SMIv2", April 1999. 871 [RFC2580] McCloghrie, k., Perkins, D., Schoenwaelder, J., 872 Case, J., Rose, M., and S. Waldbusser, 873 "Conformance Statements for SMIv2", April 1999. 875 [RFC2863] McCloghrie, k. and F. Kastenholz, "The 876 Interfaces Group MIB", June 2000. 878 [RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An 879 Architecture for Describing Simple Network 880 Management Protocol (SNMP) Management 881 Frameworks", December 2002. 883 [RFC3811] Nadeau, T. and J. Cucchiara, "Definition of 884 Textual Conventions and for Multiprotocol Label 885 Switching (MPLS) Management", June 2004. 887 [RFC3813] Srinivasan, C., Viswanathan, A., and T. Nadeau, 888 "MPLS Multiprotocol Label Switching (MPLS) 889 Label Switch Router Management Information 890 Base", June 2004. 892 [RFC5440] Ayyangar, A ., Farrel, A ., Oki, E., Atlas, A., 893 Dolganow, A., Ikejiri, Y., Kumaki, K., Vasseur, 894 J., and J. Roux, "Path Computation Element 895 (PCE) communication Protocol (PCEP)", 896 March 2009. 898 9.2. Informative References 900 [PCE-PCEP-DRAFT-MIB] Kiran Koushik, A S., Stephan, E., Zhao, Q., and 901 D. King, "PCE communication protocol(PCEP) 902 Management Information Base", July 2010. 904 [RFC3410] Case, J ., Mundy, R., Partain, D., and B. 905 Stewart, "Introduction and Applicability 906 Statements for Internet-Standard Management 907 Framework", December 2002. 909 [RFC4655] Farrel, A., Vasseur, J., and J. Ash, "A Path 910 Computation Element (PCE)-Based Architecture", 911 August 2006. 913 [RFC5520] Bradford, R., Vasseur, JP., and A. Farrel, 914 "Preserving Topology Confidentiality in Inter- 915 Domain Path Computation Using a Path-Key-Based 916 Mechanism", April 2009. 918 Authors' Addresses 920 Dhruv Dhody 921 Huawei Technology 922 Leela Palace 923 Bangalore, Karnataka 560008 924 INDIA 926 EMail: dhruvd@huawei.com 928 Udayasree Palle 929 Huawei Technology 930 Leela Palace 931 Bangalore, Karnataka 560008 932 INDIA 934 EMail: Udayasreepalle@huawei.com 935 Quintin Zhao 936 Huawei Technology 937 125 Nagog Technology Park 938 Acton, MA 01719 939 US 941 EMail: qzhao@huawei.com 943 Daniel King 944 Old Dog Consulting 945 UK 947 EMail: daniel@olddog.co.uk