idnits 2.17.1 draft-dhody-pce-pcep-pathkey-mib-05.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == Line 176 has weird spacing: '...ddrType ipv4...' == The document doesn't use any RFC 2119 keywords, yet seems to have RFC 2119 boilerplate text. -- The document date (July 4, 2013) is 3941 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: 'RFC2579' is defined on line 852, but no explicit reference was found in the text == Unused Reference: 'RFC2863' is defined on line 860, but no explicit reference was found in the text == Unused Reference: 'RFC3411' is defined on line 863, but no explicit reference was found in the text == Unused Reference: 'RFC3813' is defined on line 872, but no explicit reference was found in the text == Outdated reference: A later version (-11) exists of draft-ietf-pce-pcep-mib-04 Summary: 0 errors (**), 0 flaws (~~), 8 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: January 5, 2014 Huawei Technology 6 D. King 7 Old Dog Consulting 8 July 4, 2013 10 Management Information Base (MIB) for the PCE Communications Protocol 11 (PCEP) for Path-Key based Confidentiality in Inter-Domain Path 12 Computation. 13 draft-dhody-pce-pcep-pathkey-mib-05 15 Abstract 17 This memo defines an experimental portion of the Management 18 Information Base (MIB) for use with network management protocols in 19 the Internet community. In particular, it describes managed objects 20 for modeling of the Path Computation Element communication Protocol 21 (PCEP)for communications between a Path Computation Client (PCC)and a 22 Path Computation Element (PCE), or between two PCEs when path-key- 23 based confidentiality in inter-domain path computation is requested. 25 Status of This Memo 27 This Internet-Draft is submitted in full conformance with the 28 provisions of BCP 78 and BCP 79. 30 Internet-Drafts are working documents of the Internet Engineering 31 Task Force (IETF). Note that other groups may also distribute 32 working documents as Internet-Drafts. The list of current Internet- 33 Drafts is at http://datatracker.ietf.org/drafts/current/. 35 Internet-Drafts are draft documents valid for a maximum of six months 36 and may be updated, replaced, or obsoleted by other documents at any 37 time. It is inappropriate to use Internet-Drafts as reference 38 material or to cite them other than as "work in progress." 40 This Internet-Draft will expire on January 5, 2014. 42 Copyright Notice 44 Copyright (c) 2013 IETF Trust and the persons identified as the 45 document authors. All rights reserved. 47 This document is subject to BCP 78 and the IETF Trust's Legal 48 Provisions Relating to IETF Documents 49 (http://trustee.ietf.org/license-info) in effect on the date of 50 publication of this document. Please review these documents 51 carefully, as they describe your rights and restrictions with respect 52 to this document. Code Components extracted from this document must 53 include Simplified BSD License text as described in Section 4.e of 54 the Trust Legal Provisions and are provided without warranty as 55 described in the Simplified BSD License. 57 Table of Contents 59 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 60 1.1. Requirements Language . . . . . . . . . . . . . . . . . . 3 61 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 62 3. The Internet-Standard Management Framework . . . . . . . . . . 4 63 4. PCEP Pathkey MIB Module Architecture . . . . . . . . . . . . . 4 64 4.1. Relations to other MIB modules . . . . . . . . . . . . . . 4 65 5. Example of the PCEP PathKey MIB module usage . . . . . . . . . 5 66 6. Object definitions . . . . . . . . . . . . . . . . . . . . . . 6 67 6.1. PCEP-PATHKEY-MIB . . . . . . . . . . . . . . . . . . . . . 6 68 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 20 69 8. Security Considerations . . . . . . . . . . . . . . . . . . . 20 70 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 20 71 9.1. Normative References . . . . . . . . . . . . . . . . . . . 20 72 9.2. Informative References . . . . . . . . . . . . . . . . . . 21 74 1. Introduction 76 The Path Computation Element (PCE) defined in [RFC4655] is an entity 77 that is capable of computing a network path or route based on a 78 network graph, and applying computational constraints. A Path 79 Computation Client (PCC) may make requests to a PCE for paths to be 80 computed. 82 The PCE communication protocol (PCEP) is designed as a communication 83 protocol between PCCs and PCEs for path computations and is defined 84 in [RFC5440]. 86 If confidentiality is required between domains, Path-Key-Based 87 mechanism is described in [RFC5520]. For preserving the 88 confidentiality of the "Confidential Path Segment (CPS)"; the PCE 89 returns a path containing a loose hop in place of the segment that 90 must be kept confidential. 92 [PCEP-MIB] defines a portion of the MIB for use with network 93 management protocols in the Internet community that can be used to 94 manage PCEP communications between a PCC and a PCE, or between two 95 PCEs. This memo describes MIB for path-key-based confidentiality in 96 inter-domain path computations. 98 1.1. Requirements Language 100 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 101 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 102 document are to be interpreted as described in [RFC2119]. 104 2. Terminology 106 This document uses the terminology defined in [RFC4655], [RFC5440] 107 and [RFC5520]. The following terminology is used in this document. 109 Domain: Any collection of network elements within a common sphere of 110 address management or path computational responsibility. Examples 111 of domains include Interior Gateway Protocol (IGP) areas and 112 Autonomous Systems (ASs). 114 IGP: Interior Gateway Protocol. Either of the two routing 115 protocols, Open Shortest Path First (OSPF) or Intermediate System 116 to Intermediate System (IS-IS). 118 3. The Internet-Standard Management Framework 120 For a detailed overview of the documents that describe the current 121 Internet-Standard Management Framework, please refer to section 7 of 122 [RFC3410]. 124 Managed objects are accessed via a virtual information store, termed 125 the Management Information Base or MIB. MIB objects are generally 126 accessed through the Simple Network Management Protocol (SNMP). 127 Objects in the MIB are defined using the mechanisms defined in the 128 Structure of Management Information (SMI). This memo specifies a MIB 129 module that is compliant to the SMIv2, which is described in STD 58, 130 RFC 2578 [RFC2578] and STD 58, RFC 2580 [RFC2580]. 132 4. PCEP Pathkey MIB Module Architecture 134 The PCEP Pathkey MIB will contain the following information: 136 o PCEP Pathkey counters, timers and configurations 138 o PCEP Pathkey table of Confidential Path Segment (CPS) related 139 information. 141 The PCEP Pathkey MIB has no role when PCEP peer is PCC. 143 4.1. Relations to other MIB modules 145 The PCEP Pathkey MIB imports the following textual conventions from 146 the MPLS-TC-STD-MIB defined in [RFC3811]: 148 o MplsPathIndex 150 o TeHopAddressType 152 o TeHopAddress 154 o TeHopAddressUnnum 156 The PCEP Pathkey MIB imports the following textual conventions from 157 the INET-ADDRESS-MIB defined in [RFC4001]: 159 o InetAddressType 161 o InetAddress 163 5. Example of the PCEP PathKey MIB module usage 165 In this section we provide an example to showcase the relationship 166 between pcePcepPathKeyTable and pcePcepPathKeyHopTable described in 167 Section 6. While this example is not meant to illustrate every 168 permutation of the MIB, nor in its entirety, it is intended as an aid 169 to understand some of the key concepts. It is meant to be read after 170 going through the MIB itself. 172 pcePcepPathKeyTable of the PCEP-PATHKEY-MIB module: 173 { 174 pcePcepPathKey (4512), 175 pcePcepPathKeyCPSIndex (1), 176 pcePcepPathKeyReqSrcAddrType ipv4 (1), 177 pcePcepPathKeyReqSrcAddr (1.1.1.1), 178 pcePcepPathKeyRequestId (10), 179 pcePcepPathKeyRetrieved (1), 180 pcePcepPathKeyRtrAddrType ipv4 (1), 181 pcePcepPathKeyRtrAddr (2.2.2.2), 182 pcePcepPathKeyDiscardTime (10), 183 pcePcepPathKeyReuseTime (30) 184 } 186 Entries of pcePcepPathKeyHopTable of the PCEP-PATHKEY-MIB module: 187 { 188 pcePcepPathKeyHopListIndex 1, 189 pcePcepPathKeyHopIndex 1, 190 pcePcepPathKeyHopAddrType ipv4 (1), 191 pcePcepPathKeyHopIpAddr "192.168.100.1", 192 pcePcepPathKeyHopIpPrefixLen 32, 193 pcePcepPathKeyHopAddrUnnum 0, 194 } 195 { 196 pcePcepPathKeyHopListIndex 1, 197 pcePcepPathKeyHopIndex 2, 198 pcePcepPathKeyHopAddrType ipv4 (1), 199 pcePcepPathKeyHopIpAddr "192.168.100.2", 200 pcePcepPathKeyHopIpPrefixLen 32, 201 pcePcepPathKeyHopAddrUnnum 0 202 } 204 The pcePcepPathKeyTable is the table for all the Path-Keys generated 205 by PCE. To access the CPS hidden by path-key pcePcepPathKey (4512), 206 index pcePcepPathKeyCPSIndex (1) is used in pcePcepPathKeyHopTable to 207 find the hop list (pcePcepPathKeyHopListIndex). To access each hop 208 of the path another index pcePcepPathKeyHopIndex is used along with 209 pcePcepPathKeyHopListIndex. 211 6. Object definitions 213 6.1. PCEP-PATHKEY-MIB 215 PCEP-PATHKEY-MIB DEFINITIONS ::= BEGIN 217 IMPORTS 218 MODULE-IDENTITY, 219 OBJECT-TYPE, 220 mib-2, 221 NOTIFICATION-TYPE, 222 Unsigned32, 223 Counter32 224 FROM SNMPv2-SMI -- RFC 2578 225 TruthValue, 226 TimeStamp 227 FROM SNMPv2-TC -- RFC 2579 228 MODULE-COMPLIANCE, 229 OBJECT-GROUP, 230 NOTIFICATION-GROUP 231 FROM SNMPv2-CONF -- RFC 2580 232 MplsPathIndex, 233 TeHopAddressType, 234 TeHopAddress, 235 TeHopAddressUnnum 236 FROM MPLS-TC-STD-MIB -- RFC 3811 237 InetAddressType, 238 InetAddress 239 FROM INET-ADDRESS-MIB -- RFC 4001 241 pcePcepPathkeyMIB MODULE-IDENTITY 242 LAST-UPDATED 243 "201307031200Z" -- July 03, 2013 244 ORGANIZATION 245 "IETF Path Computation Element (PCE) Working Group" 246 CONTACT-INFO 247 "Email: pce@ietf.org 248 WG charter 249 http://www.ietf.org/html.charters/pce-charter.html" 251 DESCRIPTION 253 "This MIB module defines a collection of objects for managing PCE 254 communication protocol(PCEP) for Path-Key-Based Inter-Domain Path 255 Computation" 257 -- Revision history 258 REVISION 259 "201307031200Z" -- 03 July 2013 12:00:00 EST 260 DESCRIPTION 261 " 262 Main Changes from -04 draft : 263 1. Aligment with the updates in PCEP-MIB draft 264 2. Editorial Changes. 266 REVISION 267 "201208171200Z" -- 17 Aug 2012 12:00:00 EST 268 DESCRIPTION 269 " 270 Main Changes from -03 draft : 271 1. Adding of DEFVAL for some objects. 272 2. Editorial Changes. 274 REVISION 275 "201202221200Z" -- 22 Feb 2012 12:00:00 EST 276 DESCRIPTION 277 " 278 Main Changes from -02 draft : 279 1. Editorial Changes. 280 2. Updated Contact Information. 282 REVISION 283 "201109051200Z" -- 05 Sept 2011 12:00:00 EST 284 DESCRIPTION 285 " 286 Main Changes from -01 draft : 287 1. Added pcePcepPathKeyCPSIndex. 288 2. Added pcePcepPathKeyHopListIndex. 289 3. Removed pcePcepPathKeyHopNum. 290 4. Updated Contact Information. 292 REVISION 293 "201103081200Z" -- 08 Mar 2011 12:00:00 EST 294 DESCRIPTION 295 " 296 Main Changes from -00 draft : 297 1. Added HopTable to store the CPS hops. 298 2. Added Path Key Creation Time. 300 REVISION 301 "201009171200Z" -- 17 Sep 2010 12:00:00 EST 302 DESCRIPTION 304 "draft-00 version" 305 ::= { experimental 9999 } -- 307 pcePcepPathKeyNotifications OBJECT IDENTIFIER ::= 308 { pcePcepPathkeyMIB 0 } 309 pcePcepPathKeyMIBObjects OBJECT IDENTIFIER ::= 310 { pcePcepPathkeyMIB 1 } 311 pcePcepPathKeyConformance OBJECT IDENTIFIER ::= 312 { pcePcepPathkeyMIB 2 } 313 pcePcepPathKeyObjects OBJECT IDENTIFIER ::= 314 { pcePcepPathKeyMIBObjects 1 } 316 -- 318 -- PCE Pathkey Objects 320 -- 322 pcePcepPathKeyDiscardTimer OBJECT-TYPE 323 SYNTAX Unsigned32 324 UNITS "minutes" 325 MAX-ACCESS read-only 326 STATUS mandatory 327 DESCRIPTION 328 "The value which indicates a period of time after the 329 expiration of which a PCE can discard unwanted 330 path-keys and CPS." 331 DEFVAL {10} 332 ::= { pcePcepPathKeyObjects 1 } 334 pcePcepPathKeyReUseTimer OBJECT-TYPE 335 SYNTAX Unsigned32 336 UNITS "minutes" 337 MAX-ACCESS read-only 338 STATUS mandatory 339 DESCRIPTION 340 "The value which indicates a period of time which 341 should expire before an old path-key could be 342 reused for a new CPS." 343 DEFVAL {30} 344 ::= { pcePcepPathKeyObjects 2 } 346 pcePcepPathKeyRetainStatus OBJECT-TYPE 347 SYNTAX INTEGER { 348 enabled(1), 349 disabled(2) 350 } 351 MAX-ACCESS read-only 352 STATUS optional 353 DESCRIPTION 354 "The path-key retain status of this PCE to retain the 355 path-key and CPS after retrieval." 356 DEFVAL {disabled(2)} 357 ::= { pcePcepPathKeyObjects 3 } 359 pcePcepPathKeysGenerated OBJECT-TYPE 360 SYNTAX Counter32 361 MAX-ACCESS read-only 362 STATUS mandatory 363 DESCRIPTION 364 "The number of path-keys generated by this PCE." 365 ::= { pcePcepPathKeyObjects 4 } 367 pcePcepPathKeyExpandUn OBJECT-TYPE 368 SYNTAX Counter32 369 MAX-ACCESS read-only 370 STATUS mandatory 371 DESCRIPTION 372 "The number of attempts to expand an unknown 373 path-key." 374 ::= { pcePcepPathKeyObjects 5 } 376 pcePcepPathKeyExpandExp OBJECT-TYPE 377 SYNTAX Counter32 378 MAX-ACCESS read-only 379 STATUS mandatory 380 DESCRIPTION 381 "The number of attempts to expand an expired 382 path-key." 383 ::= { pcePcepPathKeyObjects 6 } 385 pcePcepPathKeyExpandSame OBJECT-TYPE 386 SYNTAX Counter32 387 MAX-ACCESS read-only 388 STATUS optional 389 DESCRIPTION 390 "The number of attempts to expand the same 391 path-key." 392 ::= { pcePcepPathKeyObjects 7 } 394 pcePcepPathKeyExpNoExpansion OBJECT-TYPE 395 SYNTAX Counter32 396 MAX-ACCESS read-only 397 STATUS optional 398 DESCRIPTION 399 "The number of path-keys expired without any attempt 400 to expand it." 401 ::= { pcePcepPathKeyObjects 8 } 403 pcePcepPathKeyExpansionSuccess OBJECT-TYPE 404 SYNTAX Counter32 405 MAX-ACCESS read-only 406 STATUS optional 407 DESCRIPTION 408 "The number of path-key expansion requests (PCReq) 409 which had successful retrieval." 410 ::= { pcePcepPathKeyObjects 9 } 412 pcePcepPathKeyExpansionFailures OBJECT-TYPE 413 SYNTAX Counter32 414 MAX-ACCESS read-only 415 STATUS optional 416 DESCRIPTION 417 "The number of path-key expansion requests (PCReq) 418 which had failed retrieval." 419 ::= { pcePcepPathKeyObjects 10 } 421 pcePcepPathKeyConfig OBJECT-TYPE 422 SYNTAX INTEGER { 423 enabled(1), 424 disabled(2) 425 } 426 MAX-ACCESS read-only 427 STATUS mandatory 428 DESCRIPTION 429 "Path-key based confidentiality is enabled." 430 DEFVAL {disabled(2)} 431 ::= { pcePcepPathKeyObjects 11 } 433 pcePcepPathKeyTable OBJECT-TYPE 434 SYNTAX SEQUENCE OF pcePcepPathKeyEntry 435 MAX-ACCESS not-accessible 436 STATUS current 437 DESCRIPTION 438 "This table contains information about the 439 Pathkey CPS of PCE. Applicable only when 440 pcePcepPathKeyConfig is enabled(1)." 441 ::= { pcePcepPathKeyObjects 12 } 443 pcePcepPathKeyEntry OBJECT-TYPE 444 SYNTAX pcePcepPathKeyEntry 445 MAX-ACCESS not-accessible 446 STATUS current 447 DESCRIPTION 448 "An entry in this table represents a path-key and 449 CPS. An entry is only created when a path-key is 450 generated by PCE during inter-domain path 451 computation." 453 INDEX { pcePcepPathKey } 455 ::= { pcePcepPathKeyTable 1 } 457 pcePcepPathKeyEntry ::= SEQUENCE { 458 pcePcepPathKey Unsigned32, 459 pcePcepPathKeyCPSIndex MplsPathIndex, 460 pcePcepPathKeyReqSrcAddrType InetAddressType, 461 pcePcepPathKeyReqSrcAddr InetAddress, 462 pcePcepPathKeyRequestId Unsigned32, 463 pcePcepPathKeyRetrieved INTEGER, 464 pcePcepPathKeyRtrAddrType InetAddressType, 465 pcePcepPathKeyRtrAddr InetAddress, 466 pcePcepPathKeyCreationTime TimeStamp, 467 pcePcepPathKeyDiscardTime Unsigned32, 468 pcePcepPathKeyReuseTime Unsigned32, 469 } 471 pcePcepPathKey OBJECT-TYPE 472 SYNTAX Unsigned32 (1..65535) 473 MAX-ACCESS read-only 474 STATUS mandatory 475 DESCRIPTION 476 "The path-key value to identify a CPS." 477 ::= { pcePcepPathKeyEntry 1 } 479 pcePcepPathKeyCPSIndex OBJECT-TYPE 480 SYNTAX MplsPathIndex 481 MAX-ACCESS read-only 482 STATUS mandatory 483 DESCRIPTION 484 "The HopList index of the CPS. This index 485 is used to expand Hops in 486 pcePcepPathKeyHopTable." 487 ::= { pcePcepPathKeyEntry 2 } 489 pcePcepPathKeyReqSrcAddrType OBJECT-TYPE 490 SYNTAX InetAddressType 491 MAX-ACCESS read-only 492 STATUS mandatory 493 DESCRIPTION 494 "The type of the PCEP peer Internet address. 495 This object specifies how the value of the 496 pcePcepPathKeyReqSrcAddr object should be 497 interpreted." 498 ::= { pcePcepPathKeyEntry 3 } 500 pcePcepPathKeyReqSrcAddr OBJECT-TYPE 501 SYNTAX InetAddress 502 MAX-ACCESS read-only 503 STATUS mandatory 504 DESCRIPTION 505 "The Internet address of the PCEP peer that 506 issued the original request that led to the 507 creation of the path-key. 508 The type is given by 509 pcePcepPathKeyReqSrcAddrType " 510 ::= { pcePcepPathKeyEntry 4 } 512 pcePcepPathKeyRequestId OBJECT-TYPE 513 SYNTAX Unsigned32 514 MAX-ACCESS read-only 515 STATUS mandatory 516 DESCRIPTION 517 "The request ID of the original PCReq that led 518 to the creation of the path-key." 519 ::= { pcePcepPathKeyEntry 5 } 521 pcePcepPathKeyRetrieved OBJECT-TYPE 522 SYNTAX INTEGER { 523 TRUE(1), 524 FALSE(2) 525 } 526 MAX-ACCESS read-only 527 STATUS mandatory 528 DESCRIPTION 529 "It specifies whether the path-key is retrieved 530 or not." 531 ::= { pcePcepPathKeyEntry 6 } 533 pcePcepPathKeyRtrAddrType OBJECT-TYPE 534 SYNTAX InetAddressType 535 MAX-ACCESS read-only 536 STATUS mandatory 537 DESCRIPTION 538 "The type of the PCEP peer Internet address. 539 This object specifies how the value of the 540 pcePcepPathKeyRtrAddr object should be 541 interpreted. Applicable only when 542 pcePcepPathKeyRetrieved is TRUE(1)." 543 ::= { pcePcepPathKeyEntry 7 } 545 pcePcepPathKeyRtrAddr OBJECT-TYPE 546 SYNTAX InetAddress 547 MAX-ACCESS read-only 548 STATUS mandatory 549 DESCRIPTION 550 "The Internet address of the PCEP peer that 551 issued the path-key expansion or retrieval. 552 Applicable only when pcePcepPathKeyRetrieved 553 is TRUE(1). The type is given by 554 pcePcepPathKeyRtrAddrType." 555 ::= { pcePcepPathKeyEntry 8 } 557 pcePcepPathKeyCreationTime OBJECT-TYPE 558 SYNTAX TimeStamp 559 MAX-ACCESS read-only 560 STATUS mandatory 561 DESCRIPTION 562 "The value of sysUpTime at which Path Key 563 was generated by PCE." 564 ::= { pcePcepPathKeyEntry 9 } 566 pcePcepPathKeyDiscardTime OBJECT-TYPE 567 SYNTAX Unsigned32 568 UNIT "seconds" 569 MAX-ACCESS read-only 570 STATUS mandatory 571 DESCRIPTION 572 "The time after which the path segment associated 573 with the path-key will be discarded." 574 ::= { pcePcepPathKeyEntry 10 } 576 pcePcepPathKeyReuseTime OBJECT-TYPE 577 SYNTAX Unsigned32 578 UNIT "seconds" 579 MAX-ACCESS read-only 580 STATUS mandatory 581 DESCRIPTION 582 "The time after which the path-key will be available 583 for re-use." 584 ::= { pcePcepPathKeyEntry 11 } 586 pcePcepPathKeyHopTable OBJECT-TYPE 587 SYNTAX SEQUENCE OF pcePcepPathKeyHopEntry 588 MAX-ACCESS not-accessible 589 STATUS current 590 DESCRIPTION 591 "This table contains information about the 592 Pathkey Hop in the CPS of PCE." 593 ::= { pcePcepPathKeyObjects 12 } 595 pcePcepPathKeyHopEntry OBJECT-TYPE 596 SYNTAX pcePcepPathKeyHopEntry 597 MAX-ACCESS not-accessible 598 STATUS current 599 DESCRIPTION 600 "An entry in this table represents a Hop in the CPS. 601 An entry is only created when a path-key generated 602 by PCE during inter-domain computation." 603 INDEX { pcePcepPathKeyHopListIndex, 604 pcePcepPathKeyHopIndex } 606 ::= { pcePcepPathKeyHopTable 1 } 608 pcePcepPathKeyHopEntry ::= SEQUENCE { 609 pcePcepPathKeyHopListIndex MplsPathIndex, 610 pcePcepPathKeyHopIndex MplsPathIndex, 611 pcePcepPathKeyHopAddrType TeHopAddressType, 612 pcePcepPathKeyHopIpAddr TeHopAddress, 613 pcePcepPathKeyHopIpPrefixLen InetAddressPrefixLength, 614 pcePcepPathKeyHopAddrUnnum TeHopAddressUnnum, 615 } 617 pcePcepPathKeyHopListIndex OBJECT-TYPE 618 SYNTAX MplsPathIndex 619 MAX-ACCESS read-only 620 STATUS mandatory 621 DESCRIPTION 622 "The primary index into this table identifying a 623 particular CPS. All hops in the CPS will have the 624 same ListIndex. This corresponds to 625 pcePcepPathKeyCPSIndex in pcePcepPathKeyEntry." 627 ::= { pcePcepPathKeyHopEntry 1 } 629 pcePcepPathKeyHopIndex OBJECT-TYPE 630 SYNTAX MplsPathIndex 631 MAX-ACCESS read-only 632 STATUS mandatory 633 DESCRIPTION 634 "The secondry index into this table identifying a 635 particular Hop in the CPS." 637 ::= { pcePcepPathKeyHopEntry 2 } 639 pcePcepPathKeyHopAddrType OBJECT-TYPE 640 SYNTAX TeHopAddressType 641 MAX-ACCESS read-only 642 STATUS mandatory 643 DESCRIPTION 644 "The Hop Address Type of this CPS hop. Only 645 ipv4(1), ipv6(2) and unnum(4) are allowed." 646 DEFVAL { ipv4 } 647 ::= { pcePcepPathKeyHopEntry 3 } 649 pcePcepPathKeyHopIpAddr OBJECT-TYPE 650 SYNTAX TeHopAddress 651 MAX-ACCESS read-only 652 STATUS mandatory 653 DESCRIPTION 654 "The Hop Address for this CPS hop. 655 The type of this address is determined by the 656 value of the corresponding 657 pcePcepPathKeyHopAddrType." 658 DEFVAL { '00000000'h } -- IPv4 address 0.0.0.0 659 ::= { pcePcepPathKeyHopEntry 4 } 661 pcePcepPathKeyHopIpPrefixLen OBJECT-TYPE 662 SYNTAX InetAddressPrefixLength 663 MAX-ACCESS read-only 664 STATUS current 665 DESCRIPTION 666 "pcePcepPathKeyHopAddrType if set to ipv4(1) or 667 ipv6(2), then this value will contain an 668 appropriate prefix length for the IP address in 669 object pcePcepPathKeyHopIpAddr. Otherwise this 670 value is irrelevant and should be ignored." 671 DEFVAL { 32 } 672 ::= { pcePcepPathKeyHopEntry 5 } 674 pcePcepPathKeyHopAddrUnnum OBJECT-TYPE 675 SYNTAX TeHopAddressUnnum 676 MAX-ACCESS read-only 677 STATUS current 678 DESCRIPTION 679 "If pcePcepPathKeyHopAddrType is set to unnum(4), 680 then this value will contain the interface 681 identifier of the unnumbered interface for this 682 hop. This object should be used in conjunction 683 with pcePcepPathKeyHopIpAddr which would contain 684 the LSR Router ID in this case." 685 ::= { pcePcepPathKeyHopEntry 6 } 687 --- 689 --- Notifications 691 --- 693 pcePcepPathKeyExpandUnNtf NOTIFICATION-TYPE 694 OBJECTS { 695 pcePcepPathKeyExpandUn 696 } 697 STATUS mandatory 698 DESCRIPTION 699 "This notification is sent when an attempt to expand 700 an unknown path-key is made. The value of the 701 counter pcePcepPathKeyExpandUn is also increased at 702 this time." 703 ::= { pcePcepPathKeyNotifications 1 } 705 pcePcepPathKeyExpandExpNtf NOTIFICATION-TYPE 706 OBJECTS { 707 pcePcepPathKeyExpandExp 708 } 709 STATUS mandatory 710 DESCRIPTION 711 "This notification is sent when an attempt to expand 712 an expired path-key is made. The value of the 713 counter pcePcepPathKeyExpandExp is also increased 714 at this time." 715 ::= { pcePcepPathKeyNotifications 2 } 717 pcePcepPathKeyExpandSameNtf NOTIFICATION-TYPE 718 OBJECTS { 719 pcePcepPathKeyExpandSame 720 } 721 STATUS optional 722 DESCRIPTION 723 "This notification is sent when a duplicate attempt 724 to expand the same path-key is made. The value of 725 the counter pcePcepPathKeyExpandSame is also 726 increased at this time." 727 ::= { pcePcepPathKeyNotifications 3 } 729 pcePcepPathKeyExpNoExpansionNtf NOTIFICATION-TYPE 730 OBJECTS { 731 pcePcepPathKeyExpNoExpansion 732 } 733 STATUS optional 734 DESCRIPTION 735 "This notification is sent when path-key expires 736 without any attempt to expand it. The value of 737 the counter pcePcepPathKeyExpNoExpansion is also 738 increased at this time." 739 ::= { pcePcepPathKeyNotifications 4 } 741 --**************************************************************** 742 -- Module Conformance Statement 743 --**************************************************************** 745 pcePcepPathKeyGroups 746 OBJECT IDENTIFIER ::= { pcePcepPathKeyConformance 1 } 748 pcePcepPathKeyCompliances 749 OBJECT IDENTIFIER ::= { pcePcepPathKeyConformance 2 } 751 -- 752 -- Read-Only Compliance 753 -- 755 pcePcepPathKeyModuleReadOnlyCompliance MODULE-COMPLIANCE 756 STATUS current 757 DESCRIPTION 758 "The Module is implemented with support 759 for read-only. In other words, only monitoring 760 is available by implementing this 761 MODULE-COMPLIANCE." 763 MODULE -- this module 764 MANDATORY-GROUPS 765 { pcePcepPathKeyGeneralGroup, 766 pcePcepPathKeyNotificationsGroup 767 } 768 ::= { pcePcepPathKeyCompliances 1 } 770 -- units of conformance 771 pcePcepPathKeyGeneralGroup OBJECT-GROUP 772 OBJECTS { 773 pcePcepPathKeyDiscardTimer, 774 pcePcepPathKeyReUseTimer, 775 pcePcepPathKeysGenerated, 776 pcePcepPathKeyExpandUn, 777 pcePcepPathKeyExpandExp, 778 pcePcepPathKeyConfig, 779 pcePcepPathKey, 780 pcePcepPathKeyCPSIndex, 781 pcePcepPathKeyReqSrcAddrType, 782 pcePcepPathKeyReqSrcAddr, 783 pcePcepPathKeyRequestId, 784 pcePcepPathKeyRetrieved, 785 pcePcepPathKeyRtrAddrType, 786 pcePcepPathKeyRtrAddr, 787 pcePcepPathKeyCreationTime, 788 pcePcepPathKeyDiscardTime, 789 pcePcepPathKeyReuseTime, 790 pcePcepPathKeyHopListIndex, 791 pcePcepPathKeyHopIndex, 792 pcePcepPathKeyHopAddrType, 793 pcePcepPathKeyHopIpAddr, 794 pcePcepPathKeyHopIpPrefixLen, 795 pcePcepPathKeyHopAddrUnnum, 796 } 797 STATUS current 798 DESCRIPTION 799 "Objects that apply to all PCEP Pathkey MIB 800 implementations." 802 ::= { pcePcepPathKeyGroups 1 } 804 pcePcepPathKeyNotificationsGroup NOTIFICATION-GROUP 805 NOTIFICATIONS { pcePcepPathKeyExpandUnNtf, 806 pcePcepPathKeyExpandExpNtf 807 } 808 STATUS current 809 DESCRIPTION 810 "The notifications for a PCEP Pathkey MIB 811 implementation." 812 ::= { pcePcepPathKeyGroups 2 } 814 END 816 7. IANA Considerations 818 The MIB module in this document uses the following IANA-assigned 819 OBJECT IDENTIFIER values recorded in the SMI Numbers registry: 821 Descriptor OBJECT IDENTIFIER value 822 ---------- ----------------------- 823 pcePcepPathkeyMIB { mib-2 XXX } 825 Editor's Note (to be removed prior to publication): the IANA is 826 requested to assign a value for "XXX" under the 'mib-2' subtree and 827 to record the assignment in the SMI Numbers registry. When the 828 assignment has been made, the RFC Editor is asked to replace "XXX" 829 (here and in the MIB module) with the assigned value and to remove 830 this note. 832 8. Security Considerations 834 [PCEP-MIB] describes the security consideration related to the PCE 835 MIB module, which are applicable to PCE Path-Key MIB defined in this 836 document. Further [RFC5520] describes various security consideration 837 when dealing with Path-Key. Since this MIB contains confidential 838 path segment, care should be taken to maintain the confidentiality 839 during SNMP MIB operations. 841 9. References 843 9.1. Normative References 845 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 846 Requirement Levels", BCP 14, RFC 2119, March 1997. 848 [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. 849 Schoenwaelder, Ed., "Structure of Management Information 850 Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. 852 [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. 853 Schoenwaelder, Ed., "Textual Conventions for SMIv2", 854 STD 58, RFC 2579, April 1999. 856 [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 857 "Conformance Statements for SMIv2", STD 58, RFC 2580, 858 April 1999. 860 [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group 861 MIB", RFC 2863, June 2000. 863 [RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An 864 Architecture for Describing Simple Network Management 865 Protocol (SNMP) Management Frameworks", STD 62, RFC 3411, 866 December 2002. 868 [RFC3811] Nadeau, T. and J. Cucchiara, "Definitions of Textual 869 Conventions (TCs) for Multiprotocol Label Switching 870 (MPLS) Management", RFC 3811, June 2004. 872 [RFC3813] Srinivasan, C., Viswanathan, A., and T. Nadeau, 873 "Multiprotocol Label Switching (MPLS) Label Switching 874 Router (LSR) Management Information Base (MIB)", 875 RFC 3813, June 2004. 877 [RFC4001] Daniele, M., Haberman, B., Routhier, S., and J. 878 Schoenwaelder, "Textual Conventions for Internet Network 879 Addresses", RFC 4001, February 2005. 881 [RFC5440] Vasseur, JP. and JL. Le Roux, "Path Computation Element 882 (PCE) Communication Protocol (PCEP)", RFC 5440, 883 March 2009. 885 9.2. Informative References 887 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, 888 "Introduction and Applicability Statements for Internet- 889 Standard Management Framework", RFC 3410, December 2002. 891 [RFC4655] Farrel, A., Vasseur, J., and J. Ash, "A Path Computation 892 Element (PCE)-Based Architecture", RFC 4655, August 2006. 894 [RFC5520] Bradford, R., Vasseur, JP., and A. Farrel, "Preserving 895 Topology Confidentiality in Inter-Domain Path Computation 896 Using a Path-Key-Based Mechanism", RFC 5520, April 2009. 898 [PCEP-MIB] Kiran Koushik, A S., Emile, S., Zhao, Q., King, D., and 899 J. Hardwick, "PCE communication protocol(PCEP) Management 900 Information Base (draft-ietf-pce-pcep-mib-04)", 901 February 2013. 903 Authors' Addresses 905 Dhruv Dhody 906 Huawei Technology 907 Leela Palace 908 Bangalore, Karnataka 560008 909 INDIA 911 EMail: dhruv.dhody@huawei.com 913 Udayasree Palle 914 Huawei Technology 915 Leela Palace 916 Bangalore, Karnataka 560008 917 INDIA 919 EMail: udayasree.palle@huawei.com 921 Quintin Zhao 922 Huawei Technology 923 125 Nagog Technology Park 924 Acton, MA 01719 925 US 927 EMail: quintin.zhao@huawei.com 929 Daniel King 930 Old Dog Consulting 931 UK 933 EMail: daniel@olddog.co.uk