idnits 2.17.1 draft-dhody-pce-pcep-pathkey-mib-08.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == 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 (August 4, 2014) is 3546 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 879, but no explicit reference was found in the text == Unused Reference: 'RFC2863' is defined on line 887, but no explicit reference was found in the text == Unused Reference: 'RFC3411' is defined on line 890, but no explicit reference was found in the text == Unused Reference: 'RFC3813' is defined on line 899, but no explicit reference was found in the text == Outdated reference: A later version (-11) exists of draft-ietf-pce-pcep-mib-09 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: February 5, 2015 Huawei Technology 6 D. King 7 Old Dog Consulting 8 August 4, 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-08 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 February 5, 2015. 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 . . . . . . . . . . . . . . . . . . . . . 21 69 8. Security Considerations . . . . . . . . . . . . . . . . . . . 21 70 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 21 71 9.1. Normative References . . . . . . . . . . . . . . . . . . 21 72 9.2. Informative References . . . . . . . . . . . . . . . . . 22 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 "201408051200Z" -- August 05, 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 260 this note 261 -- Revision history 262 REVISION 263 "201408051200Z" -- 05 August 2014 12:00:00 EST 264 DESCRIPTION 265 " 266 Main Changes from -07 draft : 267 1. Editorial Changes." 268 REVISION 269 "201402061200Z" -- 06 February 2014 12:00:00 EST 270 DESCRIPTION 271 " 272 Main Changes from -06 draft : 273 1. Align to changes in base PCEP MIB." 274 REVISION 275 "201401031200Z" -- 03 January 2014 12:00:00 EST 276 DESCRIPTION 277 " 278 Main Changes from -05 draft : 279 1. Editorial Changes." 280 REVISION 281 "201307031200Z" -- 03 July 2013 12:00:00 EST 282 DESCRIPTION 283 " 284 Main Changes from -04 draft : 285 1. Aligment with the updates in PCEP-MIB draft 286 2. Editorial Changes." 287 REVISION 288 "201208171200Z" -- 17 Aug 2012 12:00:00 EST 289 DESCRIPTION 290 " 291 Main Changes from -03 draft : 292 1. Adding of DEFVAL for some objects. 293 2. Editorial Changes." 294 REVISION 295 "201202221200Z" -- 22 Feb 2012 12:00:00 EST 296 DESCRIPTION 297 " 298 Main Changes from -02 draft : 299 1. Editorial Changes. 300 2. Updated Contact Information." 301 REVISION 302 "201109051200Z" -- 05 Sept 2011 12:00:00 EST 303 DESCRIPTION 304 " 305 Main Changes from -01 draft : 306 1. Added pcePcepPathKeyCPSIndex. 307 2. Added pcePcepPathKeyHopListIndex. 308 3. Removed pcePcepPathKeyHopNum. 309 4. Updated Contact Information." 311 REVISION 312 "201103081200Z" -- 08 Mar 2011 12:00:00 EST 313 DESCRIPTION 314 " 315 Main Changes from -00 draft : 316 1. Added HopTable to store the CPS hops. 317 2. Added Path Key Creation Time." 318 REVISION 319 "201009171200Z" -- 17 Sep 2010 12:00:00 EST 320 DESCRIPTION 321 "Initial version, published as RFC YYYY." 322 -- RFC Ed.: replace YYYY with actual RFC number & remove 323 this note 324 ::= { mib-2 XXX } 325 -- RFC Ed.: replace XXX with IANA-assigned number & remove 326 this note 328 pcePcepPathKeyNotifications OBJECT IDENTIFIER ::= 329 { pcePcepPathkeyMIB 0 } 330 pcePcepPathKeysObjects OBJECT IDENTIFIER ::= 331 { pcePcepPathkeyMIB 1 } 332 pcePcepPathKeyConformance OBJECT IDENTIFIER ::= 333 { pcePcepPathkeyMIB 2 } 334 pcePcepPathKeyObjects OBJECT IDENTIFIER ::= 335 { pcePcepPathKeysObjects 1 } 337 -- 339 -- PCE Pathkey Objects 341 -- 343 pcePcepPathKeyDiscardTimer OBJECT-TYPE 344 SYNTAX Unsigned32 345 UNITS "minutes" 346 MAX-ACCESS read-only 347 STATUS mandatory 348 DESCRIPTION 349 "The value which indicates a period of time after the 350 expiration of which a PCE can discard unwanted 351 path-keys and CPS." 352 DEFVAL {10} 353 ::= { pcePcepPathKeyObjects 1 } 355 pcePcepPathKeyReUseTimer OBJECT-TYPE 356 SYNTAX Unsigned32 357 UNITS "minutes" 358 MAX-ACCESS read-only 359 STATUS mandatory 360 DESCRIPTION 361 "The value which indicates a period of time which 362 should expire before an old path-key could be 363 reused for a new CPS." 364 DEFVAL {30} 365 ::= { pcePcepPathKeyObjects 2 } 367 pcePcepPathKeyRetainStatus OBJECT-TYPE 368 SYNTAX INTEGER { 369 enabled(1), 370 disabled(2) 371 } 372 MAX-ACCESS read-only 373 STATUS optional 374 DESCRIPTION 375 "The path-key retain status of this PCE to retain the 376 path-key and CPS after retrieval." 377 DEFVAL {disabled(2)} 378 ::= { pcePcepPathKeyObjects 3 } 380 pcePcepPathKeysGenerated OBJECT-TYPE 381 SYNTAX Counter32 382 MAX-ACCESS read-only 383 STATUS mandatory 384 DESCRIPTION 385 "The number of path-keys generated by this PCE." 386 ::= { pcePcepPathKeyObjects 4 } 388 pcePcepPathKeyExpandUn OBJECT-TYPE 389 SYNTAX Counter32 390 MAX-ACCESS read-only 391 STATUS mandatory 392 DESCRIPTION 393 "The number of attempts to expand an unknown 394 path-key." 395 ::= { pcePcepPathKeyObjects 5 } 397 pcePcepPathKeyExpandExp OBJECT-TYPE 398 SYNTAX Counter32 399 MAX-ACCESS read-only 400 STATUS mandatory 401 DESCRIPTION 402 "The number of attempts to expand an expired 403 path-key." 404 ::= { pcePcepPathKeyObjects 6 } 406 pcePcepPathKeyExpandSame OBJECT-TYPE 407 SYNTAX Counter32 408 MAX-ACCESS read-only 409 STATUS optional 410 DESCRIPTION 411 "The number of attempts to expand the same 412 path-key." 413 ::= { pcePcepPathKeyObjects 7 } 415 pcePcepPathKeyExpNoExpansion OBJECT-TYPE 416 SYNTAX Counter32 417 MAX-ACCESS read-only 418 STATUS optional 419 DESCRIPTION 420 "The number of path-keys expired without any attempt 421 to expand it." 422 ::= { pcePcepPathKeyObjects 8 } 424 pcePcepPathKeyExpansionSuccess 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 successful retrieval." 431 ::= { pcePcepPathKeyObjects 9 } 433 pcePcepPathKeyExpansionFailures OBJECT-TYPE 434 SYNTAX Counter32 435 MAX-ACCESS read-only 436 STATUS optional 437 DESCRIPTION 438 "The number of path-key expansion requests (PCReq) 439 which had failed retrieval." 440 ::= { pcePcepPathKeyObjects 10 } 442 pcePcepPathKeyConfig OBJECT-TYPE 443 SYNTAX INTEGER { 444 enabled(1), 445 disabled(2) 446 } 447 MAX-ACCESS read-only 448 STATUS mandatory 449 DESCRIPTION 450 "Path-key based confidentiality is enabled." 451 DEFVAL {disabled(2)} 452 ::= { pcePcepPathKeyObjects 11 } 454 pcePcepPathKeyTable OBJECT-TYPE 455 SYNTAX SEQUENCE OF pcePcepPathKeyEntry 456 MAX-ACCESS not-accessible 457 STATUS current 458 DESCRIPTION 459 "This table contains information about the 460 Pathkey CPS of PCE. Applicable only when 461 pcePcepPathKeyConfig is enabled(1)." 462 ::= { pcePcepPathKeyObjects 12 } 464 pcePcepPathKeyEntry OBJECT-TYPE 465 SYNTAX pcePcepPathKeyEntry 466 MAX-ACCESS not-accessible 467 STATUS current 468 DESCRIPTION 469 "Represents a path-key and CPS entry. An entry is 470 only created when a path-key is 471 generated by PCE during inter-domain path 472 computation." 474 INDEX { pcePcepPathKey } 476 ::= { pcePcepPathKeyTable 1 } 478 pcePcepPathKeyEntry ::= SEQUENCE { 479 pcePcepPathKey Unsigned32, 480 pcePcepPathKeyCPSIndex MplsPathIndex, 481 pcePcepPathKeyReqSrcAddrType InetAddressType, 482 pcePcepPathKeyReqSrcAddr InetAddress, 483 pcePcepPathKeyRequestId Unsigned32, 484 pcePcepPathKeyRetrieved INTEGER, 485 pcePcepPathKeyRtrAddrType InetAddressType, 486 pcePcepPathKeyRtrAddr InetAddress, 487 pcePcepPathKeyCreationTime TimeStamp, 488 pcePcepPathKeyDiscardTime Unsigned32, 489 pcePcepPathKeyReuseTime Unsigned32, 490 } 492 pcePcepPathKey OBJECT-TYPE 493 SYNTAX Unsigned32 (1..65535) 494 MAX-ACCESS read-only 495 STATUS mandatory 496 DESCRIPTION 497 "The path-key value to identify a CPS." 498 ::= { pcePcepPathKeyEntry 1 } 500 pcePcepPathKeyCPSIndex OBJECT-TYPE 501 SYNTAX MplsPathIndex 502 MAX-ACCESS read-only 503 STATUS mandatory 504 DESCRIPTION 505 "The HopList index of the CPS. This index 506 is used to expand Hops in 507 pcePcepPathKeyHopTable." 508 ::= { pcePcepPathKeyEntry 2 } 510 pcePcepPathKeyReqSrcAddrType OBJECT-TYPE 511 SYNTAX InetAddressType 512 MAX-ACCESS read-only 513 STATUS mandatory 514 DESCRIPTION 515 "The type of the PCEP peer Internet address. 516 This object specifies how the value of the 517 pcePcepPathKeyReqSrcAddr object should be 518 interpreted." 519 ::= { pcePcepPathKeyEntry 3 } 521 pcePcepPathKeyReqSrcAddr OBJECT-TYPE 522 SYNTAX InetAddress 523 MAX-ACCESS read-only 524 STATUS mandatory 525 DESCRIPTION 526 "The Internet address of the PCEP peer that 527 issued the original request that led to the 528 creation of the path-key. 529 The type is given by 530 pcePcepPathKeyReqSrcAddrType " 531 ::= { pcePcepPathKeyEntry 4 } 533 pcePcepPathKeyRequestId OBJECT-TYPE 534 SYNTAX Unsigned32 535 MAX-ACCESS read-only 536 STATUS mandatory 537 DESCRIPTION 538 "The request ID of the original PCReq that led 539 to the creation of the path-key." 540 ::= { pcePcepPathKeyEntry 5 } 542 pcePcepPathKeyRetrieved OBJECT-TYPE 543 SYNTAX INTEGER { 544 TRUE(1), 545 FALSE(2) 546 } 547 MAX-ACCESS read-only 548 STATUS mandatory 549 DESCRIPTION 550 "It specifies whether the path-key is retrieved 551 or not." 552 ::= { pcePcepPathKeyEntry 6 } 554 pcePcepPathKeyRtrAddrType OBJECT-TYPE 555 SYNTAX InetAddressType 556 MAX-ACCESS read-only 557 STATUS mandatory 558 DESCRIPTION 559 "The type of the PCEP peer Internet address. 560 This object specifies how the value of the 561 pcePcepPathKeyRtrAddr object should be 562 interpreted. Applicable only when 563 pcePcepPathKeyRetrieved is TRUE(1)." 564 ::= { pcePcepPathKeyEntry 7 } 566 pcePcepPathKeyRtrAddr OBJECT-TYPE 567 SYNTAX InetAddress 568 MAX-ACCESS read-only 569 STATUS mandatory 570 DESCRIPTION 571 "The Internet address of the PCEP peer that 572 issued the path-key expansion or retrieval. 573 Applicable only when pcePcepPathKeyRetrieved 574 is TRUE(1). The type is given by 575 pcePcepPathKeyRtrAddrType." 576 ::= { pcePcepPathKeyEntry 8 } 578 pcePcepPathKeyCreationTime OBJECT-TYPE 579 SYNTAX TimeStamp 580 MAX-ACCESS read-only 581 STATUS mandatory 582 DESCRIPTION 583 "The value of sysUpTime at which Path Key 584 was generated by PCE." 585 ::= { pcePcepPathKeyEntry 9 } 587 pcePcepPathKeyDiscardTime OBJECT-TYPE 588 SYNTAX Unsigned32 589 UNIT "seconds" 590 MAX-ACCESS read-only 591 STATUS mandatory 592 DESCRIPTION 593 "The time after which the path segment associated 594 with the path-key will be discarded." 595 ::= { pcePcepPathKeyEntry 10 } 597 pcePcepPathKeyReuseTime OBJECT-TYPE 598 SYNTAX Unsigned32 599 UNIT "seconds" 600 MAX-ACCESS read-only 601 STATUS mandatory 602 DESCRIPTION 603 "The time after which the path-key will be available 604 for re-use." 605 ::= { pcePcepPathKeyEntry 11 } 607 pcePcepPathKeyHopTable OBJECT-TYPE 608 SYNTAX SEQUENCE OF pcePcepPathKeyHopEntry 609 MAX-ACCESS not-accessible 610 STATUS current 611 DESCRIPTION 612 "This table contains information about the 613 Pathkey Hop in the CPS of PCE." 614 ::= { pcePcepPathKeyObjects 12 } 616 pcePcepPathKeyHopEntry OBJECT-TYPE 617 SYNTAX pcePcepPathKeyHopEntry 618 MAX-ACCESS not-accessible 619 STATUS current 620 DESCRIPTION 621 "An entry in this table represents a Hop in the CPS. 622 An entry is only created when a path-key generated 623 by PCE during inter-domain computation." 624 INDEX { pcePcepPathKeyHopListIndex, 625 pcePcepPathKeyHopIndex } 627 ::= { pcePcepPathKeyHopTable 1 } 629 pcePcepPathKeyHopEntry ::= SEQUENCE { 630 pcePcepPathKeyHopListIndex MplsPathIndex, 631 pcePcepPathKeyHopIndex MplsPathIndex, 632 pcePcepPathKeyHopAddrType TeHopAddressType, 633 pcePcepPathKeyHopIpAddr TeHopAddress, 634 pcePcepPathKeyHopIpPrefixLen InetAddressPrefixLength, 635 pcePcepPathKeyHopAddrUnnum TeHopAddressUnnum, 636 } 638 pcePcepPathKeyHopListIndex OBJECT-TYPE 639 SYNTAX MplsPathIndex 640 MAX-ACCESS read-only 641 STATUS mandatory 642 DESCRIPTION 643 "The primary index into pcePcepPathKeyHopEntry table 644 identifying a particular CPS. All hops in the CPS 645 will have the same ListIndex. This corresponds to 646 pcePcepPathKeyCPSIndex in pcePcepPathKeyEntry." 648 ::= { pcePcepPathKeyHopEntry 1 } 650 pcePcepPathKeyHopIndex OBJECT-TYPE 651 SYNTAX MplsPathIndex 652 MAX-ACCESS read-only 653 STATUS mandatory 654 DESCRIPTION 655 "The secondry index into pcePcepPathKeyHopEntry 656 table identifying a particular Hop in the CPS." 658 ::= { pcePcepPathKeyHopEntry 2 } 660 pcePcepPathKeyHopAddrType OBJECT-TYPE 661 SYNTAX TeHopAddressType 662 MAX-ACCESS read-only 663 STATUS mandatory 664 DESCRIPTION 665 "The Hop Address Type of this CPS hop. Only 666 ipv4(1), ipv6(2) and unnum(4) are allowed." 667 DEFVAL { ipv4 } 668 ::= { pcePcepPathKeyHopEntry 3 } 670 pcePcepPathKeyHopIpAddr OBJECT-TYPE 671 SYNTAX TeHopAddress 672 MAX-ACCESS read-only 673 STATUS mandatory 674 DESCRIPTION 675 "The Hop Address for this CPS hop. 676 The type of this address is determined by the 677 value of the corresponding 678 pcePcepPathKeyHopAddrType." 679 DEFVAL { '00000000'h } -- IPv4 address 0.0.0.0 680 ::= { pcePcepPathKeyHopEntry 4 } 682 pcePcepPathKeyHopIpPrefixLen OBJECT-TYPE 683 SYNTAX InetAddressPrefixLength 684 MAX-ACCESS read-only 685 STATUS current 686 DESCRIPTION 687 "pcePcepPathKeyHopAddrType if set to ipv4(1) or 688 ipv6(2), then this value will contain an 689 appropriate prefix length for the IP address in 690 object pcePcepPathKeyHopIpAddr. Otherwise this 691 value is irrelevant and should be ignored." 692 DEFVAL { 32 } 693 ::= { pcePcepPathKeyHopEntry 5 } 695 pcePcepPathKeyHopAddrUnnum OBJECT-TYPE 696 SYNTAX TeHopAddressUnnum 697 MAX-ACCESS read-only 698 STATUS current 699 DESCRIPTION 700 "If pcePcepPathKeyHopAddrType is set to unnum(4), 701 then this value will contain the interface 702 identifier of the unnumbered interface for this 703 hop. This object should be used in conjunction 704 with pcePcepPathKeyHopIpAddr which would contain 705 the LSR Router ID in this case." 706 ::= { pcePcepPathKeyHopEntry 6 } 708 --- 710 --- Notifications 712 --- 714 pcePcepPathKeyExpandUnNtf NOTIFICATION-TYPE 715 OBJECTS { 716 pcePcepPathKeyExpandUn 717 } 718 STATUS mandatory 719 DESCRIPTION 720 "This notification is sent when an attempt to expand 721 an unknown path-key is made. The value of the 722 counter pcePcepPathKeyExpandUn is also increased at 723 this time." 724 ::= { pcePcepPathKeyNotifications 1 } 726 pcePcepPathKeyExpandExpNtf NOTIFICATION-TYPE 727 OBJECTS { 728 pcePcepPathKeyExpandExp 729 } 730 STATUS mandatory 731 DESCRIPTION 732 "This notification is sent when an attempt to expand 733 an expired path-key is made. The value of the 734 counter pcePcepPathKeyExpandExp is also increased 735 at this time." 736 ::= { pcePcepPathKeyNotifications 2 } 738 pcePcepPathKeyExpandSameNtf NOTIFICATION-TYPE 739 OBJECTS { 740 pcePcepPathKeyExpandSame 741 } 742 STATUS optional 743 DESCRIPTION 744 "This notification is sent when a duplicate attempt 745 to expand the same path-key is made. The value of 746 the counter pcePcepPathKeyExpandSame is also 747 increased at this time." 748 ::= { pcePcepPathKeyNotifications 3 } 750 pcePcepPathKeyExpNoExpansionNtf NOTIFICATION-TYPE 751 OBJECTS { 752 pcePcepPathKeyExpNoExpansion 753 } 754 STATUS optional 755 DESCRIPTION 756 "This notification is sent when path-key expires 757 without any attempt to expand it. The value of 758 the counter pcePcepPathKeyExpNoExpansion is also 759 increased at this time." 760 ::= { pcePcepPathKeyNotifications 4 } 762 --**************************************************************** 763 -- Module Conformance Statement 764 --**************************************************************** 766 pcePcepPathKeyGroups 767 OBJECT IDENTIFIER ::= { pcePcepPathKeyConformance 1 } 769 pcePcepPathKeyCompliances 770 OBJECT IDENTIFIER ::= { pcePcepPathKeyConformance 2 } 772 -- 773 -- Read-Only Compliance 774 -- 776 pcePcepPathKeyModuleReadOnlyCompliance MODULE-COMPLIANCE 777 STATUS current 778 DESCRIPTION 779 "The Module is implemented with support 780 for read-only. In other words, only monitoring 781 is available by implementing this 782 MODULE-COMPLIANCE." 784 MODULE -- this module 785 MANDATORY-GROUPS 786 { pcePcepPathKeyGeneralGroup, 787 pcePcepPathKeyNotificationsGroup 788 } 789 ::= { pcePcepPathKeyCompliances 1 } 791 -- units of conformance 792 pcePcepPathKeyGeneralGroup OBJECT-GROUP 793 OBJECTS { 794 pcePcepPathKeyDiscardTimer, 795 pcePcepPathKeyReUseTimer, 796 pcePcepPathKeysGenerated, 797 pcePcepPathKeyExpandUn, 798 pcePcepPathKeyExpandExp, 799 pcePcepPathKeyConfig, 800 pcePcepPathKey, 801 pcePcepPathKeyCPSIndex, 802 pcePcepPathKeyReqSrcAddrType, 803 pcePcepPathKeyReqSrcAddr, 804 pcePcepPathKeyRequestId, 805 pcePcepPathKeyRetrieved, 806 pcePcepPathKeyRtrAddrType, 807 pcePcepPathKeyRtrAddr, 808 pcePcepPathKeyCreationTime, 809 pcePcepPathKeyDiscardTime, 810 pcePcepPathKeyReuseTime, 811 pcePcepPathKeyHopListIndex, 812 pcePcepPathKeyHopIndex, 813 pcePcepPathKeyHopAddrType, 814 pcePcepPathKeyHopIpAddr, 815 pcePcepPathKeyHopIpPrefixLen, 816 pcePcepPathKeyHopAddrUnnum, 817 } 818 STATUS current 819 DESCRIPTION 820 "Objects that apply to all PCEP Pathkey MIB 821 implementations." 823 ::= { pcePcepPathKeyGroups 1 } 825 pcePcepPathKeyNotificationsGroup NOTIFICATION-GROUP 826 NOTIFICATIONS { pcePcepPathKeyExpandUnNtf, 827 pcePcepPathKeyExpandExpNtf 828 } 829 STATUS current 830 DESCRIPTION 831 "The notifications for a PCEP Pathkey MIB 832 implementation." 833 ::= { pcePcepPathKeyGroups 2 } 835 END 837 7. IANA Considerations 839 The MIB module in this document uses the following IANA-assigned 840 OBJECT IDENTIFIER values recorded in the SMI Numbers registry: 842 Descriptor OBJECT IDENTIFIER value 843 ---------- ----------------------- 844 pcePcepPathkeyMIB { mib-2 XXX } 846 Editor's Note (to be removed prior to publication): the IANA is 847 requested to assign a value for "XXX" under the 'mib-2' subtree and 848 to record the assignment in the SMI Numbers registry. When the 849 assignment has been made, the RFC Editor is asked to replace "XXX" 850 (here and in the MIB module) with the assigned value and to remove 851 this note. 853 8. Security Considerations 855 [PCEP-MIB] describes the security consideration related to the PCE 856 MIB module, which are applicable to PCE Path-Key MIB defined in this 857 document. Further [RFC5520] describes various security consideration 858 when dealing with Path-Key. Since this MIB contains confidential path 859 segment, care should be taken to maintain the confidentiality during 860 SNMP MIB operations. 862 Security features described by the SNMPv3 framework [RFC3410] like 863 User-based Security Model (USM) [RFC3414] with the AES cipher 864 algorithm [RFC3826] and Transport Security Model (TSM) [RFC5591] in 865 combination with a secure transport such as SSH [RFC5592] or TLS/DTLS 866 [RFC6353]. should be supported. 868 9. References 870 9.1. Normative References 872 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 873 Requirement Levels", BCP 14, RFC 2119, March 1997. 875 [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. 876 Schoenwaelder, Ed., "Structure of Management Information 877 Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. 879 [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. 880 Schoenwaelder, Ed., "Textual Conventions for SMIv2", STD 881 58, RFC 2579, April 1999. 883 [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 884 "Conformance Statements for SMIv2", STD 58, RFC 2580, 885 April 1999. 887 [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group 888 MIB", RFC 2863, June 2000. 890 [RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An 891 Architecture for Describing Simple Network Management 892 Protocol (SNMP) Management Frameworks", STD 62, RFC 3411, 893 December 2002. 895 [RFC3811] Nadeau, T. and J. Cucchiara, "Definitions of Textual 896 Conventions (TCs) for Multiprotocol Label Switching (MPLS) 897 Management", RFC 3811, June 2004. 899 [RFC3813] Srinivasan, C., Viswanathan, A., and T. Nadeau, 900 "Multiprotocol Label Switching (MPLS) Label Switching 901 Router (LSR) Management Information Base (MIB)", RFC 3813, 902 June 2004. 904 [RFC4001] Daniele, M., Haberman, B., Routhier, S., and J. 905 Schoenwaelder, "Textual Conventions for Internet Network 906 Addresses", RFC 4001, February 2005. 908 [RFC5440] Vasseur, JP. and JL. Le Roux, "Path Computation Element 909 (PCE) Communication Protocol (PCEP)", RFC 5440, March 910 2009. 912 [PCEP-MIB] 913 Koushik, K., Emile, S., Zhao, Q., King, D., and J. 914 Hardwick, "Path Computation Element Protocol (PCEP) 915 Management Information Base", draft-ietf-pce-pcep-mib-09 916 (work in progress), July 2014. 918 9.2. Informative References 920 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, 921 "Introduction and Applicability Statements for Internet- 922 Standard Management Framework", RFC 3410, December 2002. 924 [RFC3414] Blumenthal, U. and B. Wijnen, "User-based Security Model 925 (USM) for version 3 of the Simple Network Management 926 Protocol (SNMPv3)", STD 62, RFC 3414, December 2002. 928 [RFC3826] Blumenthal, U., Maino, F., and K. McCloghrie, "The 929 Advanced Encryption Standard (AES) Cipher Algorithm in the 930 SNMP User-based Security Model", RFC 3826, June 2004. 932 [RFC4655] Farrel, A., Vasseur, J., and J. Ash, "A Path Computation 933 Element (PCE)-Based Architecture", RFC 4655, August 2006. 935 [RFC5520] Bradford, R., Vasseur, JP., and A. Farrel, "Preserving 936 Topology Confidentiality in Inter-Domain Path Computation 937 Using a Path-Key-Based Mechanism", RFC 5520, April 2009. 939 [RFC5591] Harrington, D. and W. Hardaker, "Transport Security Model 940 for the Simple Network Management Protocol (SNMP)", STD 941 78, RFC 5591, June 2009. 943 [RFC5592] Harrington, D., Salowey, J., and W. Hardaker, "Secure 944 Shell Transport Model for the Simple Network Management 945 Protocol (SNMP)", RFC 5592, June 2009. 947 [RFC6353] Hardaker, W., "Transport Layer Security (TLS) Transport 948 Model for the Simple Network Management Protocol (SNMP)", 949 STD 78, RFC 6353, July 2011. 951 Authors' Addresses 953 Dhruv Dhody 954 Huawei Technology 955 Leela Palace 956 Bangalore, Karnataka 560008 957 INDIA 959 EMail: dhruv.ietf@gmail.com 961 Udayasree Palle 962 Huawei Technology 963 Leela Palace 964 Bangalore, Karnataka 560008 965 INDIA 967 EMail: udayasree.palle@huawei.com 969 Quintin Zhao 970 Huawei Technology 971 125 Nagog Technology Park 972 Acton, MA 01719 973 US 975 EMail: quintin.zhao@huawei.com 976 Daniel King 977 Old Dog Consulting 978 UK 980 EMail: daniel@olddog.co.uk