idnits 2.17.1 draft-dhody-pce-pcep-pathkey-mib-07.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 (Feburary 2014) is 3779 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 864, but no explicit reference was found in the text == Unused Reference: 'RFC2863' is defined on line 872, but no explicit reference was found in the text == Unused Reference: 'RFC3411' is defined on line 875, but no explicit reference was found in the text == Unused Reference: 'RFC3813' is defined on line 884, 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: August 10, 2014 Huawei Technology 6 D. King 7 Old Dog Consulting 8 Feburary 2014 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-07 15 Abstract 17 This memo defines a portion of the Management Information Base (MIB) 18 for use with network management protocols in the Internet community. 19 In particular, it describes managed objects for modeling of the Path 20 Computation Element communication Protocol (PCEP) for communications 21 between a Path Computation Client (PCC) and a Path Computation 22 Element (PCE), or between two PCEs when path-key-based 23 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 August 10, 2014. 42 Copyright Notice 44 Copyright (c) 2014 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 . . . . . . . . . . . . . . . . . . . . . . . . 2 60 1.1. Requirements Language . . . . . . . . . . . . . . . . . . 3 61 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 62 3. The Internet-Standard Management Framework . . . . . . . . . 3 63 4. PCEP Pathkey MIB Module Architecture . . . . . . . . . . . . 3 64 4.1. Relations to other MIB modules . . . . . . . . . . . . . 4 65 5. Example of the PCEP PathKey MIB module usage . . . . . . . . 4 66 6. Object definitions . . . . . . . . . . . . . . . . . . . . . 5 67 6.1. PCEP-PATHKEY-MIB . . . . . . . . . . . . . . . . . . . . 5 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 214 PCEP-PATHKEY-MIB DEFINITIONS ::= BEGIN 216 IMPORTS 217 MODULE-IDENTITY, 218 OBJECT-TYPE, 219 mib-2, 220 NOTIFICATION-TYPE, 221 Unsigned32, 222 Counter32 223 FROM SNMPv2-SMI -- RFC 2578 224 TruthValue, 225 TimeStamp 226 FROM SNMPv2-TC -- RFC 2579 227 MODULE-COMPLIANCE, 228 OBJECT-GROUP, 229 NOTIFICATION-GROUP 230 FROM SNMPv2-CONF -- RFC 2580 231 MplsPathIndex, 232 TeHopAddressType, 233 TeHopAddress, 234 TeHopAddressUnnum 235 FROM MPLS-TC-STD-MIB -- RFC 3811 236 InetAddressType, 237 InetAddress 238 FROM INET-ADDRESS-MIB -- RFC 4001 240 pcePcepPathkeyMIB MODULE-IDENTITY 241 LAST-UPDATED 242 "201402061200Z" -- Feburary 06, 2014 243 ORGANIZATION 244 "IETF Path Computation Element (PCE) Working Group" 245 CONTACT-INFO 246 "Email: pce@ietf.org 247 WG charter 248 http://www.ietf.org/html.charters/pce-charter.html" 250 DESCRIPTION 252 "This MIB module defines a collection of objects for managing PCE 253 communication protocol(PCEP) for Path-Key-Based Inter-Domain Path 254 Computation" 256 Copyright (C) The IETF Trust (2014). This version of this MIB module 257 is part of RFC YYYY; see the RFC itself for full legal notices. 259 -- RFC Ed,: replace YYYY with actual RFC number & remove this note 260 -- Revision history 261 REVISION 262 "201402061200Z" -- 06 Feburary 2014 12:00:00 EST 263 DESCRIPTION 264 " 265 Main Changes from -06 draft : 266 1. Align to changes in base PCEP MIB." 267 REVISION 268 "201401031200Z" -- 03 January 2014 12:00:00 EST 269 DESCRIPTION 270 " 271 Main Changes from -05 draft : 272 1. Editorial Changes." 273 REVISION 274 "201307031200Z" -- 03 July 2013 12:00:00 EST 275 DESCRIPTION 276 " 277 Main Changes from -04 draft : 278 1. Aligment with the updates in PCEP-MIB draft 279 2. Editorial Changes." 280 REVISION 281 "201208171200Z" -- 17 Aug 2012 12:00:00 EST 282 DESCRIPTION 283 " 284 Main Changes from -03 draft : 285 1. Adding of DEFVAL for some objects. 286 2. Editorial Changes." 287 REVISION 288 "201202221200Z" -- 22 Feb 2012 12:00:00 EST 289 DESCRIPTION 290 " 291 Main Changes from -02 draft : 292 1. Editorial Changes. 293 2. Updated Contact Information." 294 REVISION 295 "201109051200Z" -- 05 Sept 2011 12:00:00 EST 296 DESCRIPTION 297 " 298 Main Changes from -01 draft : 299 1. Added pcePcepPathKeyCPSIndex. 300 2. Added pcePcepPathKeyHopListIndex. 301 3. Removed pcePcepPathKeyHopNum. 302 4. Updated Contact Information." 303 REVISION 304 "201103081200Z" -- 08 Mar 2011 12:00:00 EST 305 DESCRIPTION 306 " 307 Main Changes from -00 draft : 308 1. Added HopTable to store the CPS hops. 309 2. Added Path Key Creation Time." 311 REVISION 312 "201009171200Z" -- 17 Sep 2010 12:00:00 EST 313 DESCRIPTION 314 "Initial version, published as RFC YYYY." 315 -- RFC Ed.: replace YYYY with actual RFC number & remove this note 316 ::= { mib-2 XXX } 317 -- RFC Ed.: replace XXX with IANA-assigned number & remove this note 319 pcePcepPathKeyNotifications OBJECT IDENTIFIER ::= 320 { pcePcepPathkeyMIB 0 } 321 pcePcepPathKeysObjects OBJECT IDENTIFIER ::= 322 { pcePcepPathkeyMIB 1 } 323 pcePcepPathKeyConformance OBJECT IDENTIFIER ::= 324 { pcePcepPathkeyMIB 2 } 325 pcePcepPathKeyObjects OBJECT IDENTIFIER ::= 326 { pcePcepPathKeysObjects 1 } 328 -- 330 -- PCE Pathkey Objects 332 -- 334 pcePcepPathKeyDiscardTimer 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 after the 341 expiration of which a PCE can discard unwanted 342 path-keys and CPS." 343 DEFVAL {10} 344 ::= { pcePcepPathKeyObjects 1 } 346 pcePcepPathKeyReUseTimer OBJECT-TYPE 347 SYNTAX Unsigned32 348 UNITS "minutes" 349 MAX-ACCESS read-only 350 STATUS mandatory 351 DESCRIPTION 352 "The value which indicates a period of time which 353 should expire before an old path-key could be 354 reused for a new CPS." 355 DEFVAL {30} 356 ::= { pcePcepPathKeyObjects 2 } 358 pcePcepPathKeyRetainStatus OBJECT-TYPE 359 SYNTAX INTEGER { 360 enabled(1), 361 disabled(2) 362 } 363 MAX-ACCESS read-only 364 STATUS optional 365 DESCRIPTION 366 "The path-key retain status of this PCE to retain the 367 path-key and CPS after retrieval." 368 DEFVAL {disabled(2)} 369 ::= { pcePcepPathKeyObjects 3 } 371 pcePcepPathKeysGenerated OBJECT-TYPE 372 SYNTAX Counter32 373 MAX-ACCESS read-only 374 STATUS mandatory 375 DESCRIPTION 376 "The number of path-keys generated by this PCE." 377 ::= { pcePcepPathKeyObjects 4 } 379 pcePcepPathKeyExpandUn OBJECT-TYPE 380 SYNTAX Counter32 381 MAX-ACCESS read-only 382 STATUS mandatory 383 DESCRIPTION 384 "The number of attempts to expand an unknown 385 path-key." 386 ::= { pcePcepPathKeyObjects 5 } 388 pcePcepPathKeyExpandExp OBJECT-TYPE 389 SYNTAX Counter32 390 MAX-ACCESS read-only 391 STATUS mandatory 392 DESCRIPTION 393 "The number of attempts to expand an expired 394 path-key." 395 ::= { pcePcepPathKeyObjects 6 } 397 pcePcepPathKeyExpandSame OBJECT-TYPE 398 SYNTAX Counter32 399 MAX-ACCESS read-only 400 STATUS optional 401 DESCRIPTION 402 "The number of attempts to expand the same 403 path-key." 404 ::= { pcePcepPathKeyObjects 7 } 406 pcePcepPathKeyExpNoExpansion OBJECT-TYPE 407 SYNTAX Counter32 408 MAX-ACCESS read-only 409 STATUS optional 410 DESCRIPTION 411 "The number of path-keys expired without any attempt 412 to expand it." 413 ::= { pcePcepPathKeyObjects 8 } 415 pcePcepPathKeyExpansionSuccess OBJECT-TYPE 416 SYNTAX Counter32 417 MAX-ACCESS read-only 418 STATUS optional 419 DESCRIPTION 420 "The number of path-key expansion requests (PCReq) 421 which had successful retrieval." 422 ::= { pcePcepPathKeyObjects 9 } 424 pcePcepPathKeyExpansionFailures OBJECT-TYPE 425 SYNTAX Counter32 426 MAX-ACCESS read-only 427 STATUS optional 428 DESCRIPTION 429 "The number of path-key expansion requests (PCReq) 430 which had failed retrieval." 431 ::= { pcePcepPathKeyObjects 10 } 433 pcePcepPathKeyConfig OBJECT-TYPE 434 SYNTAX INTEGER { 435 enabled(1), 436 disabled(2) 437 } 438 MAX-ACCESS read-only 439 STATUS mandatory 440 DESCRIPTION 441 "Path-key based confidentiality is enabled." 442 DEFVAL {disabled(2)} 443 ::= { pcePcepPathKeyObjects 11 } 445 pcePcepPathKeyTable OBJECT-TYPE 446 SYNTAX SEQUENCE OF pcePcepPathKeyEntry 447 MAX-ACCESS not-accessible 448 STATUS current 449 DESCRIPTION 450 "This table contains information about the 451 Pathkey CPS of PCE. Applicable only when 452 pcePcepPathKeyConfig is enabled(1)." 453 ::= { pcePcepPathKeyObjects 12 } 455 pcePcepPathKeyEntry OBJECT-TYPE 456 SYNTAX pcePcepPathKeyEntry 457 MAX-ACCESS not-accessible 458 STATUS current 459 DESCRIPTION 460 "An entry in this table represents a path-key and 461 CPS. An entry is only created when a path-key is 462 generated by PCE during inter-domain path 463 computation." 465 INDEX { pcePcepPathKey } 467 ::= { pcePcepPathKeyTable 1 } 469 pcePcepPathKeyEntry ::= SEQUENCE { 470 pcePcepPathKey Unsigned32, 471 pcePcepPathKeyCPSIndex MplsPathIndex, 472 pcePcepPathKeyReqSrcAddrType InetAddressType, 473 pcePcepPathKeyReqSrcAddr InetAddress, 474 pcePcepPathKeyRequestId Unsigned32, 475 pcePcepPathKeyRetrieved INTEGER, 476 pcePcepPathKeyRtrAddrType InetAddressType, 477 pcePcepPathKeyRtrAddr InetAddress, 478 pcePcepPathKeyCreationTime TimeStamp, 479 pcePcepPathKeyDiscardTime Unsigned32, 480 pcePcepPathKeyReuseTime Unsigned32, 481 } 483 pcePcepPathKey OBJECT-TYPE 484 SYNTAX Unsigned32 (1..65535) 485 MAX-ACCESS read-only 486 STATUS mandatory 487 DESCRIPTION 488 "The path-key value to identify a CPS." 489 ::= { pcePcepPathKeyEntry 1 } 491 pcePcepPathKeyCPSIndex OBJECT-TYPE 492 SYNTAX MplsPathIndex 493 MAX-ACCESS read-only 494 STATUS mandatory 495 DESCRIPTION 496 "The HopList index of the CPS. This index 497 is used to expand Hops in 498 pcePcepPathKeyHopTable." 499 ::= { pcePcepPathKeyEntry 2 } 501 pcePcepPathKeyReqSrcAddrType OBJECT-TYPE 502 SYNTAX InetAddressType 503 MAX-ACCESS read-only 504 STATUS mandatory 505 DESCRIPTION 506 "The type of the PCEP peer Internet address. 507 This object specifies how the value of the 508 pcePcepPathKeyReqSrcAddr object should be 509 interpreted." 510 ::= { pcePcepPathKeyEntry 3 } 512 pcePcepPathKeyReqSrcAddr OBJECT-TYPE 513 SYNTAX InetAddress 514 MAX-ACCESS read-only 515 STATUS mandatory 516 DESCRIPTION 517 "The Internet address of the PCEP peer that 518 issued the original request that led to the 519 creation of the path-key. 520 The type is given by 521 pcePcepPathKeyReqSrcAddrType " 522 ::= { pcePcepPathKeyEntry 4 } 524 pcePcepPathKeyRequestId OBJECT-TYPE 525 SYNTAX Unsigned32 526 MAX-ACCESS read-only 527 STATUS mandatory 528 DESCRIPTION 529 "The request ID of the original PCReq that led 530 to the creation of the path-key." 531 ::= { pcePcepPathKeyEntry 5 } 533 pcePcepPathKeyRetrieved OBJECT-TYPE 534 SYNTAX INTEGER { 535 TRUE(1), 536 FALSE(2) 537 } 538 MAX-ACCESS read-only 539 STATUS mandatory 540 DESCRIPTION 541 "It specifies whether the path-key is retrieved 542 or not." 543 ::= { pcePcepPathKeyEntry 6 } 545 pcePcepPathKeyRtrAddrType OBJECT-TYPE 546 SYNTAX InetAddressType 547 MAX-ACCESS read-only 548 STATUS mandatory 549 DESCRIPTION 550 "The type of the PCEP peer Internet address. 551 This object specifies how the value of the 552 pcePcepPathKeyRtrAddr object should be 553 interpreted. Applicable only when 554 pcePcepPathKeyRetrieved is TRUE(1)." 555 ::= { pcePcepPathKeyEntry 7 } 557 pcePcepPathKeyRtrAddr OBJECT-TYPE 558 SYNTAX InetAddress 559 MAX-ACCESS read-only 560 STATUS mandatory 561 DESCRIPTION 562 "The Internet address of the PCEP peer that 563 issued the path-key expansion or retrieval. 564 Applicable only when pcePcepPathKeyRetrieved 565 is TRUE(1). The type is given by 566 pcePcepPathKeyRtrAddrType." 567 ::= { pcePcepPathKeyEntry 8 } 569 pcePcepPathKeyCreationTime OBJECT-TYPE 570 SYNTAX TimeStamp 571 MAX-ACCESS read-only 572 STATUS mandatory 573 DESCRIPTION 574 "The value of sysUpTime at which Path Key 575 was generated by PCE." 576 ::= { pcePcepPathKeyEntry 9 } 578 pcePcepPathKeyDiscardTime OBJECT-TYPE 579 SYNTAX Unsigned32 580 UNIT "seconds" 581 MAX-ACCESS read-only 582 STATUS mandatory 583 DESCRIPTION 584 "The time after which the path segment associated 585 with the path-key will be discarded." 586 ::= { pcePcepPathKeyEntry 10 } 588 pcePcepPathKeyReuseTime OBJECT-TYPE 589 SYNTAX Unsigned32 590 UNIT "seconds" 591 MAX-ACCESS read-only 592 STATUS mandatory 593 DESCRIPTION 594 "The time after which the path-key will be available 595 for re-use." 596 ::= { pcePcepPathKeyEntry 11 } 598 pcePcepPathKeyHopTable OBJECT-TYPE 599 SYNTAX SEQUENCE OF pcePcepPathKeyHopEntry 600 MAX-ACCESS not-accessible 601 STATUS current 602 DESCRIPTION 603 "This table contains information about the 604 Pathkey Hop in the CPS of PCE." 605 ::= { pcePcepPathKeyObjects 12 } 607 pcePcepPathKeyHopEntry OBJECT-TYPE 608 SYNTAX pcePcepPathKeyHopEntry 609 MAX-ACCESS not-accessible 610 STATUS current 611 DESCRIPTION 612 "An entry in this table represents a Hop in the CPS. 613 An entry is only created when a path-key generated 614 by PCE during inter-domain computation." 615 INDEX { pcePcepPathKeyHopListIndex, 616 pcePcepPathKeyHopIndex } 618 ::= { pcePcepPathKeyHopTable 1 } 620 pcePcepPathKeyHopEntry ::= SEQUENCE { 621 pcePcepPathKeyHopListIndex MplsPathIndex, 622 pcePcepPathKeyHopIndex MplsPathIndex, 623 pcePcepPathKeyHopAddrType TeHopAddressType, 624 pcePcepPathKeyHopIpAddr TeHopAddress, 625 pcePcepPathKeyHopIpPrefixLen InetAddressPrefixLength, 626 pcePcepPathKeyHopAddrUnnum TeHopAddressUnnum, 627 } 629 pcePcepPathKeyHopListIndex OBJECT-TYPE 630 SYNTAX MplsPathIndex 631 MAX-ACCESS read-only 632 STATUS mandatory 633 DESCRIPTION 634 "The primary index into this table identifying a 635 particular CPS. All hops in the CPS will have the 636 same ListIndex. This corresponds to 637 pcePcepPathKeyCPSIndex in pcePcepPathKeyEntry." 639 ::= { pcePcepPathKeyHopEntry 1 } 641 pcePcepPathKeyHopIndex OBJECT-TYPE 642 SYNTAX MplsPathIndex 643 MAX-ACCESS read-only 644 STATUS mandatory 645 DESCRIPTION 646 "The secondry index into this table identifying a 647 particular Hop in the CPS." 649 ::= { pcePcepPathKeyHopEntry 2 } 651 pcePcepPathKeyHopAddrType OBJECT-TYPE 652 SYNTAX TeHopAddressType 653 MAX-ACCESS read-only 654 STATUS mandatory 655 DESCRIPTION 656 "The Hop Address Type of this CPS hop. Only 657 ipv4(1), ipv6(2) and unnum(4) are allowed." 658 DEFVAL { ipv4 } 659 ::= { pcePcepPathKeyHopEntry 3 } 661 pcePcepPathKeyHopIpAddr OBJECT-TYPE 662 SYNTAX TeHopAddress 663 MAX-ACCESS read-only 664 STATUS mandatory 665 DESCRIPTION 666 "The Hop Address for this CPS hop. 667 The type of this address is determined by the 668 value of the corresponding 669 pcePcepPathKeyHopAddrType." 670 DEFVAL { '00000000'h } -- IPv4 address 0.0.0.0 671 ::= { pcePcepPathKeyHopEntry 4 } 673 pcePcepPathKeyHopIpPrefixLen OBJECT-TYPE 674 SYNTAX InetAddressPrefixLength 675 MAX-ACCESS read-only 676 STATUS current 677 DESCRIPTION 678 "pcePcepPathKeyHopAddrType if set to ipv4(1) or 679 ipv6(2), then this value will contain an 680 appropriate prefix length for the IP address in 681 object pcePcepPathKeyHopIpAddr. Otherwise this 682 value is irrelevant and should be ignored." 683 DEFVAL { 32 } 684 ::= { pcePcepPathKeyHopEntry 5 } 686 pcePcepPathKeyHopAddrUnnum OBJECT-TYPE 687 SYNTAX TeHopAddressUnnum 688 MAX-ACCESS read-only 689 STATUS current 690 DESCRIPTION 691 "If pcePcepPathKeyHopAddrType is set to unnum(4), 692 then this value will contain the interface 693 identifier of the unnumbered interface for this 694 hop. This object should be used in conjunction 695 with pcePcepPathKeyHopIpAddr which would contain 696 the LSR Router ID in this case." 697 ::= { pcePcepPathKeyHopEntry 6 } 699 --- 701 --- Notifications 703 --- 705 pcePcepPathKeyExpandUnNtf NOTIFICATION-TYPE 706 OBJECTS { 707 pcePcepPathKeyExpandUn 708 } 709 STATUS mandatory 710 DESCRIPTION 711 "This notification is sent when an attempt to expand 712 an unknown path-key is made. The value of the 713 counter pcePcepPathKeyExpandUn is also increased at 714 this time." 715 ::= { pcePcepPathKeyNotifications 1 } 717 pcePcepPathKeyExpandExpNtf NOTIFICATION-TYPE 718 OBJECTS { 719 pcePcepPathKeyExpandExp 720 } 721 STATUS mandatory 722 DESCRIPTION 723 "This notification is sent when an attempt to expand 724 an expired path-key is made. The value of the 725 counter pcePcepPathKeyExpandExp is also increased 726 at this time." 727 ::= { pcePcepPathKeyNotifications 2 } 729 pcePcepPathKeyExpandSameNtf NOTIFICATION-TYPE 730 OBJECTS { 731 pcePcepPathKeyExpandSame 732 } 733 STATUS optional 734 DESCRIPTION 735 "This notification is sent when a duplicate attempt 736 to expand the same path-key is made. The value of 737 the counter pcePcepPathKeyExpandSame is also 738 increased at this time." 739 ::= { pcePcepPathKeyNotifications 3 } 741 pcePcepPathKeyExpNoExpansionNtf NOTIFICATION-TYPE 742 OBJECTS { 743 pcePcepPathKeyExpNoExpansion 744 } 745 STATUS optional 746 DESCRIPTION 747 "This notification is sent when path-key expires 748 without any attempt to expand it. The value of 749 the counter pcePcepPathKeyExpNoExpansion is also 750 increased at this time." 751 ::= { pcePcepPathKeyNotifications 4 } 753 --**************************************************************** 754 -- Module Conformance Statement 755 --**************************************************************** 757 pcePcepPathKeyGroups 758 OBJECT IDENTIFIER ::= { pcePcepPathKeyConformance 1 } 760 pcePcepPathKeyCompliances 761 OBJECT IDENTIFIER ::= { pcePcepPathKeyConformance 2 } 763 -- 764 -- Read-Only Compliance 765 -- 767 pcePcepPathKeyModuleReadOnlyCompliance MODULE-COMPLIANCE 768 STATUS current 769 DESCRIPTION 770 "The Module is implemented with support 771 for read-only. In other words, only monitoring 772 is available by implementing this 773 MODULE-COMPLIANCE." 775 MODULE -- this module 776 MANDATORY-GROUPS 777 { pcePcepPathKeyGeneralGroup, 778 pcePcepPathKeyNotificationsGroup 779 } 780 ::= { pcePcepPathKeyCompliances 1 } 782 -- units of conformance 783 pcePcepPathKeyGeneralGroup OBJECT-GROUP 784 OBJECTS { 785 pcePcepPathKeyDiscardTimer, 786 pcePcepPathKeyReUseTimer, 787 pcePcepPathKeysGenerated, 788 pcePcepPathKeyExpandUn, 789 pcePcepPathKeyExpandExp, 790 pcePcepPathKeyConfig, 791 pcePcepPathKey, 792 pcePcepPathKeyCPSIndex, 793 pcePcepPathKeyReqSrcAddrType, 794 pcePcepPathKeyReqSrcAddr, 795 pcePcepPathKeyRequestId, 796 pcePcepPathKeyRetrieved, 797 pcePcepPathKeyRtrAddrType, 798 pcePcepPathKeyRtrAddr, 799 pcePcepPathKeyCreationTime, 800 pcePcepPathKeyDiscardTime, 801 pcePcepPathKeyReuseTime, 802 pcePcepPathKeyHopListIndex, 803 pcePcepPathKeyHopIndex, 804 pcePcepPathKeyHopAddrType, 805 pcePcepPathKeyHopIpAddr, 806 pcePcepPathKeyHopIpPrefixLen, 807 pcePcepPathKeyHopAddrUnnum, 808 } 809 STATUS current 810 DESCRIPTION 811 "Objects that apply to all PCEP Pathkey MIB 812 implementations." 814 ::= { pcePcepPathKeyGroups 1 } 816 pcePcepPathKeyNotificationsGroup NOTIFICATION-GROUP 817 NOTIFICATIONS { pcePcepPathKeyExpandUnNtf, 818 pcePcepPathKeyExpandExpNtf 819 } 820 STATUS current 821 DESCRIPTION 822 "The notifications for a PCEP Pathkey MIB 823 implementation." 824 ::= { pcePcepPathKeyGroups 2 } 826 END 828 7. IANA Considerations 830 The MIB module in this document uses the following IANA-assigned 831 OBJECT IDENTIFIER values recorded in the SMI Numbers registry: 833 Descriptor OBJECT IDENTIFIER value 834 ---------- ----------------------- 835 pcePcepPathkeyMIB { mib-2 XXX } 837 Editor's Note (to be removed prior to publication): the IANA is 838 requested to assign a value for "XXX" under the 'mib-2' subtree and 839 to record the assignment in the SMI Numbers registry. When the 840 assignment has been made, the RFC Editor is asked to replace "XXX" 841 (here and in the MIB module) with the assigned value and to remove 842 this note. 844 8. Security Considerations 846 [PCEP-MIB] describes the security consideration related to the PCE 847 MIB module, which are applicable to PCE Path-Key MIB defined in this 848 document. Further [RFC5520] describes various security consideration 849 when dealing with Path-Key. Since this MIB contains confidential path 850 segment, care should be taken to maintain the confidentiality during 851 SNMP MIB operations. 853 9. References 855 9.1. Normative References 857 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 858 Requirement Levels", BCP 14, RFC 2119, March 1997. 860 [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. 861 Schoenwaelder, Ed., "Structure of Management Information 862 Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. 864 [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. 865 Schoenwaelder, Ed., "Textual Conventions for SMIv2", STD 866 58, RFC 2579, April 1999. 868 [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 869 "Conformance Statements for SMIv2", STD 58, RFC 2580, 870 April 1999. 872 [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group 873 MIB", RFC 2863, June 2000. 875 [RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An 876 Architecture for Describing Simple Network Management 877 Protocol (SNMP) Management Frameworks", STD 62, RFC 3411, 878 December 2002. 880 [RFC3811] Nadeau, T. and J. Cucchiara, "Definitions of Textual 881 Conventions (TCs) for Multiprotocol Label Switching (MPLS) 882 Management", RFC 3811, June 2004. 884 [RFC3813] Srinivasan, C., Viswanathan, A., and T. Nadeau, 885 "Multiprotocol Label Switching (MPLS) Label Switching 886 Router (LSR) Management Information Base (MIB)", RFC 3813, 887 June 2004. 889 [RFC4001] Daniele, M., Haberman, B., Routhier, S., and J. 890 Schoenwaelder, "Textual Conventions for Internet Network 891 Addresses", RFC 4001, February 2005. 893 [RFC5440] Vasseur, JP. and JL. Le Roux, "Path Computation Element 894 (PCE) Communication Protocol (PCEP)", RFC 5440, March 895 2009. 897 9.2. Informative References 899 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, 900 "Introduction and Applicability Statements for Internet- 901 Standard Management Framework", RFC 3410, December 2002. 903 [RFC4655] Farrel, A., Vasseur, J., and J. Ash, "A Path Computation 904 Element (PCE)-Based Architecture", RFC 4655, August 2006. 906 [RFC5520] Bradford, R., Vasseur, JP., and A. Farrel, "Preserving 907 Topology Confidentiality in Inter-Domain Path Computation 908 Using a Path-Key-Based Mechanism", RFC 5520, April 2009. 910 [PCEP-MIB] 911 Kiran Koushik, A., Emile, S., Zhao, Q., King, D., and J. 912 Hardwick, "PCE communication protocol(PCEP) Management 913 Information Base (draft-ietf-pce-pcep-mib-04)", July 2013. 915 Authors' Addresses 916 Dhruv Dhody 917 Huawei Technology 918 Leela Palace 919 Bangalore, Karnataka 560008 920 INDIA 922 EMail: dhruv.ietf@gmail.com 924 Udayasree Palle 925 Huawei Technology 926 Leela Palace 927 Bangalore, Karnataka 560008 928 INDIA 930 EMail: udayasree.palle@huawei.com 932 Quintin Zhao 933 Huawei Technology 934 125 Nagog Technology Park 935 Acton, MA 01719 936 US 938 EMail: quintin.zhao@huawei.com 940 Daniel King 941 Old Dog Consulting 942 UK 944 EMail: daniel@olddog.co.uk