idnits 2.17.1 draft-ietf-pce-disc-mib-04.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** The document seems to lack a License Notice according IETF Trust Provisions of 28 Dec 2009, Section 6.b.i or Provisions of 12 Sep 2009 Section 6.b -- however, there's a paragraph with a matching beginning. Boilerplate error? (You're using the IETF Trust Provisions' Section 6.b License Notice from 12 Feb 2009 rather than one of the newer Notices. See https://trustee.ietf.org/license-info/.) 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 == The document seems to use 'NOT RECOMMENDED' as an RFC 2119 keyword, but does not include the phrase in its RFC 2119 key words list. -- The document seems to contain a disclaimer for pre-RFC5378 work, and may have content which was first submitted before 10 November 2008. The disclaimer is necessary when there are original authors that you have been unable to contact, or if some do not wish to grant the BCP78 rights to the IETF Trust. If you are able to get all authors (current and original) to grant those rights, you can and should remove the disclaimer; otherwise, the disclaimer is needed and you can ignore this comment. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- Couldn't find a document date in the document -- date freshness check skipped. Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) No issues found here. Summary: 1 error (**), 0 flaws (~~), 2 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Internet Engineering Task Force E. Stephan 2 Internet-Draft France Telecom 3 Intended status: Standards Track Q. Zhao 4 Created: October 25, 2009 Huawei Technology 5 Expires: March 25, 2010 D. King 6 Old Dog Consulting 8 Definitions of Managed Objects for Path Computation Element Discovery 9 draft-ietf-pce-disc-mib-04 11 Abstract 13 This memo defines a portion of the Management Information Base (MIB) 14 for use with network management protocols in the Internet community. 15 In particular, it describes objects used for managing Path 16 Computation Elements Discovery. 18 Status of this Memo 20 This Internet-Draft is submitted to IETF in full conformance with 21 the provisions of BCP 78 and BCP 79. 23 Internet-Drafts are working documents of the Internet Engineering 24 Task Force (IETF), its areas, and its working groups. Note that 25 other groups may also distribute working documents as Internet- 26 Drafts. 28 Internet-Drafts are draft documents valid for a maximum of six months 29 and may be updated, replaced, or obsoleted by other documents at any 30 time. It is inappropriate to use Internet-Drafts as reference 31 material or to cite them other than as "work in progress." 33 The list of current Internet-Drafts can be accessed at 34 http://www.ietf.org/ietf/1id-abstracts.txt. 36 The list of Internet-Draft Shadow Directories can be accessed at 37 http://www.ietf.org/shadow.html. 39 Copyright Notice 41 Copyright (c) 2009 IETF Trust and the persons identified as the 42 document authors. All rights reserved. 44 This document is subject to BCP 78 and the IETF Trust's Legal 45 Provisions Relating to IETF Documents in effect on the date of 46 publication of this document (http://trustee.ietf.org/license-info). 47 Please review these documents carefully, as they describe your rights 48 and restrictions with respect to this document. 50 This document may contain material from IETF Documents or IETF 51 Contributions published or made publicly available before November 52 10, 2008. The person(s) controlling the copyright in some of this 53 material may not have granted the IETF Trust the right to allow 54 modifications of such material outside the IETF Standards Process. 55 Without obtaining an adequate license from the person(s) controlling 56 the copyright in such materials, this document may not be modified 57 outside the IETF Standards Process, and derivative works of it may 58 not be created outside the IETF Standards Process, except to format 59 it for publication as an RFC or to translate it into languages other 60 than English. 62 Table of Contents 64 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 65 2. The Internet-Standard Management Framework . . . . . . . . . . 3 66 3. Conventions used in this document . . . . . . . . . . . . . . 3 67 4. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 68 5. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 69 6. Structure of the MIB Module . . . . . . . . . . . . . . . . . 4 70 6.1. The Discovery objects . . . . . . . . . . . . . . . . . . 4 71 6.2. PCEs capabilities objects . . . . . . . . . . . . . . . . 5 72 6.3. PCEs options capabilities objects . . . . . . . . . . . . 5 73 6.4. PCEs Activity Objects . . . . . . . . . . . . . . . . . . 5 74 6.5. The Notification Group . . . . . . . . . . . . . . . . . . 5 75 7. Relationship to Other MIB Modules . . . . . . . . . . . . . . 5 76 7.1. Relationship to IGP MIB modules . . . . . . . . . . . . . 6 77 7.2. MIB modules required for IMPORTS . . . . . . . . . . . . . 6 78 8. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 6 79 9. Security Considerations . . . . . . . . . . . . . . . . . . . 22 80 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 23 81 11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 23 82 11.1. Normative References . . . . . . . . . . . . . . . . . . . 23 83 11.2. Informative References . . . . . . . . . . . . . . . . . . 24 84 Appendix A. Open Issues . . . . . . . . . . . . . . . . . . . . . 24 85 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 24 87 1. Introduction 89 This memo defines a portion of the Management Information Base (MIB) 90 for use with network management protocols in the Internet community. 91 In particular, it describes objects used for managing Path 92 Computation Elements Discovery. 94 For an introduction to the concepts of PCE, see [RFC4655]. 96 2. The Internet-Standard Management Framework 98 For a detailed overview of the documents that describe the current 99 Internet-Standard Management Framework, please refer to section 7 of 100 RFC 3410 [RFC3410]. 102 Managed objects are accessed via a virtual information store, termed 103 the Management Information Base or MIB. MIB objects are generally 104 accessed through the Simple Network Management Protocol (SNMP). 105 Objects in the MIB are defined using the mechanisms defined in the 106 Structure of Management Information (SMI). This memo specifies a MIB 107 module that is compliant to the SMIv2, which is described in STD 58, 108 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 109 [RFC2580]. 111 3. Conventions used in this document 113 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 114 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 115 document are to be interpreted as described in RFC-2119 0. 117 4. Terminology 119 The terminology used in this document is built on notions introduced 120 and discussed in PCE WG documents. The reader should be familiar 121 with these documents 123 Domain: any collection of network elements within a common 124 sphere of address management or path computational 125 responsibility. 127 IGP Area: OSPF Area or ISIS level. 129 PCC: Path Computation Client: any client application requesting 130 a path computation to be performed by a Path Computation 131 Element. 133 PCE: Path Computation Element: an entity (component, 134 application, or network node) that is capable of computing a 135 network path or route based on a network graph, and applying 136 computational constraints. 138 5. Overview 140 [RFC4655] describes the architecture for a PCE-based path computation 141 model for MPLS and GMPLS TE LSPs. The architecture allows the 142 separation of PCE from PCC. It requires that a PCC be aware of the 143 location of one or more PCEs. This relies on a communication 144 protocol between PCC and PCE for automatic and dynamic PCE discovery. 146 [RFC4674] defines the PCE discovery mechanism and information 147 elements which are derived as an extension for OSPF in [RFC5089] and 148 as an extension for ISIS in [RFC5089] . 150 The current MIB module defines the objects the section "6.10.2.1. 151 PCC MIB module " of [RFC4674] identifies as to be disclosed on the 152 management interface of the PCC. 154 6. Structure of the MIB Module 156 This MIB module is arranged into groups. Each group is organized as 157 a set of related objects. The overall structure and assignment of 158 objects to their groups, and the intended purpose of each group, is 159 shown below. 161 6.1. The Discovery objects 163 Objects of pceDiscoveryObjects provide general information on the 164 PCEs discovered and on their status. 166 This includes: 167 - A control to disable the automatic discovery mechanism; 168 - The number of known PCEs; 169 - The number of discovered PCEs; 170 - The pceDiscoveryTable which details information per PCE: 171 - Addresses, discovery Mechanism type; 172 - Discovery time, last activity time; 173 - Congestion and congestion duration. 175 6.2. PCEs capabilities objects 177 These objects report on computation capabilities per PCE as defined 178 in PCE-PATHSCOPE, PCE-DOMAINS and PCE-NEIG-DOMAINS information 179 elements. 181 Objects of pceDiscPathScopeTable collect the computation capabilities 182 and preferences fo the PCEs discovered. 184 Objects of pceDiscDomainTable list the domains for which the PCE 185 discovered have topology visibility and path computation facilities. 187 Objects of pceDiscNeighborDomainTable define domains toward which a 188 PCE can compute path. 190 6.3. PCEs options capabilities objects 192 Objects of pceDiscOptionalCapabilitiesTable provides computation 193 options per PCE as defined in The PCE-CAP-FLAGS information elements. 195 6.4. PCEs Activity Objects 197 The objects of pceDiscActivityTable monitor the activity of the 198 discovery mechanism of each PCE to enable effective analysis of the 199 operation of the protocols. 201 pceDiscActivityTable reports on the activity of the discovery 202 protocol per PCE: 203 o Modification of PCE discovery; 204 o The average and maximum rates of arrival, departure of PCE 205 discovery information; 206 o The number of unacceptable and incomprehensible discovery 207 information exchanges. 209 6.5. The Notification Group 211 This group defines notifications to inform of important events 212 related to the monitoring of the PCE Discovery sessions such as the 213 ending of all the sessions and abnormal rate of unacceptable 214 messages. 216 7. Relationship to Other MIB Modules 218 7.1. Relationship to IGP MIB modules 220 PCE Discovery relies on existing protocols which have specialized MIB 221 objects to monitor their own activities. Consequently this document 222 considers that monitoring underlying protocols in out of the scope of 223 the current MIB module. 225 7.2. MIB modules required for IMPORTS 227 The following MIB module IMPORTS objects from SNMPv2-SMI [RFC2578], 228 SNMPv2-TC [RFC2579], SNMPv2-CONF [RFC2580], and IF-MIB [RFC2863] and 229 also REFERENCEs document RFC0768 [RFC0768] 231 8. Definitions 233 PCE-DISC-STD-MIB DEFINITIONS ::= BEGIN 235 IMPORTS 236 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, 237 Counter32, Unsigned32, Integer32, IpAddress 238 FROM SNMPv2-SMI 239 TimeStamp, 240 TruthValue 242 FROM SNMPv2-TC 243 Ipv6Address 244 FROM IPV6-TC 245 MODULE-COMPLIANCE, 246 OBJECT-GROUP, 247 NOTIFICATION-GROUP 248 FROM SNMPv2-CONF 249 AddressFamilyNumbers 250 FROM IANA-ADDRESS-FAMILY-NUMBERS-MIB 251 IANAipRouteProtocol 252 FROM IANA-RTPROTO-MIB 253 pceStdMIB, PceRoutingDomainID 254 FROM PCE-TC-STD-MIB; -- [xxxx] 255 -- rfc editor replace xxxx with the rfc number 257 pceDiscDraftMIB MODULE-IDENTITY 258 LAST-UPDATED "200810240000Z" -- October 24, 2008 259 ORGANIZATION "Path Computation Element (PCE) Working Group" 260 CONTACT-INFO " 261 Stephan Emile 262 France Telecom 263 Email: emile.stephan@orange-ftgroup.com 264 Email comments directly to the PCE WG Mailing List at pce@ietf.org 265 WG-URL: http://www.ietf.org/html.charters/pce-charter.html 266 " 267 DESCRIPTION 268 "This MIB module defines a collection of objects for managing Path 269 Computation Elements (PCEs) Discovery." 270 ::= { pceStdMIB 2 } 272 pceDiscNotifications OBJECT IDENTIFIER ::= { pceDiscDraftMIB 0 } 274 pceDiscMIBObjects OBJECT IDENTIFIER ::= { pceDiscDraftMIB 1 } 276 pceDiscoveryObjects OBJECT IDENTIFIER ::= { pceDiscMIBObjects 1 } 277 pceDiscoveryAdminStatus OBJECT-TYPE 278 SYNTAX INTEGER { 279 enabled(1), 280 disabled(2) 281 } 282 MAX-ACCESS read-write 283 STATUS current 284 DESCRIPTION 285 "Setting this object to disabled(2) disables the discovery of 286 PCEs. Once disabled, The discovery must be explicitly enabled 287 to restore discovery of PCEs. Setting this object to 288 enabled(1) enables the discovery of PCEs." 289 ::= { pceDiscoveryObjects 1 } 291 pceDiscoveryKnownPCEs OBJECT-TYPE 292 SYNTAX Counter32 293 MAX-ACCESS read-only 294 STATUS current 295 DESCRIPTION 296 "The number of PCEs the PCC is potentially in relation with. 297 This includes PCE manually declared and active PCEs" 298 ::= { pceDiscoveryObjects 2 } 300 pceDiscoveryActivePCEs OBJECT-TYPE 301 SYNTAX Counter32 302 MAX-ACCESS read-only 303 STATUS current 304 DESCRIPTION 305 "The number of active PCEs. 306 The detection of the activity a a PCE depends on the nature 307 discovery mechanism. 308 PCE discovered using PCED information received: 309 The relation between the PCC and a PCE is active while the 310 PCE discovery protocol maintains a communication between the 311 PCC and this PCE. 312 PCE Manually declared: 313 The relation between the PCC and a PCE is active and the 314 discovery mechanism is implementation specific; 315 " 316 ::= { pceDiscoveryObjects 3 } 318 pceDiscoveryTable OBJECT-TYPE 319 SYNTAX SEQUENCE OF PceDiscoveryEntry 320 MAX-ACCESS not-accessible 321 STATUS current 322 DESCRIPTION 323 "Information describing the PCEs discovered." 324 ::= { pceDiscoveryObjects 4 } 326 pceDiscoveryEntry OBJECT-TYPE 327 SYNTAX PceDiscoveryEntry 328 MAX-ACCESS not-accessible 329 STATUS current 330 DESCRIPTION 331 "Information describing general information of each PCE 332 discovered." 333 INDEX { pceDiscoveryIndex } 334 ::= { pceDiscoveryTable 1 } 336 PceDiscoveryEntry ::= SEQUENCE { 337 pceDiscoveryIndex Integer32, 338 pceDiscoveryMechanism IANAipRouteProtocol, 339 pceDiscoveryIPv4Address IpAddress, 340 pceDiscoveryIPv6Address Ipv6Address, 341 pceDiscoveryTime TimeStamp, 342 pceDiscoveryLastUpdated TimeStamp, 343 pceDiscoveryCongestion TruthValue, 344 pceDiscoveryCongestionDuration Unsigned32 345 } 347 pceDiscoveryIndex OBJECT-TYPE 348 SYNTAX Integer32 (1..2147483647) 349 MAX-ACCESS not-accessible 350 STATUS current 351 DESCRIPTION 352 "This object identifies locally the PCE for which this entry 353 contains information." 354 ::= { pceDiscoveryEntry 1 } 356 pceDiscoveryMechanism OBJECT-TYPE 357 SYNTAX IANAipRouteProtocol 358 MAX-ACCESS read-only 359 STATUS current 360 DESCRIPTION 361 "This object identifies the type of discovery mechanism used to 362 discover the PCE. 363 The discovery mechanisms covered by PCE WG at the time of the 364 specification are : 365 other (1), --not specified 366 local (2), -- local interface 367 isIs (9), -- Dual IS-IS 368 ospf (13), -- Open Shortest Path First 369 bgp (14), -- Border Gateway Protocol 370 It does not preclude the usage of another routing protocol 371 numbered by this IANAipRouteProtocol 372 " 373 ::= { pceDiscoveryEntry 2 } 375 pceDiscoveryIPv4Address OBJECT-TYPE 376 SYNTAX IpAddress 377 MAX-ACCESS read-only 378 STATUS current 379 DESCRIPTION 380 "This object is the IP address to be used to reach the PCE. It 381 corresponds to the PCED PCE-ADDRESS. 382 . 383 A value of 0.0.0.0 indicates the absence of this address." 384 ::= { pceDiscoveryEntry 3 } 386 pceDiscoveryIPv6Address OBJECT-TYPE 387 SYNTAX Ipv6Address 388 MAX-ACCESS read-only 389 STATUS current 390 DESCRIPTION 391 "This object is the IPv6 address to be used to reach the PCE. 392 It corresponds to the PCED PCE-ADDRESS. 393 A value of ::0 indicates the absence of this address." 394 ::= { pceDiscoveryEntry 4 } 396 pceDiscoveryTime OBJECT-TYPE 397 SYNTAX TimeStamp 398 MAX-ACCESS read-only 399 STATUS current 400 DESCRIPTION 401 "The value of sysUpTime at the time this entry was created. 402 local entry: the value of sysUpTime at the time the PCC 403 restarted." 404 ::= { pceDiscoveryEntry 5 } 406 pceDiscoveryLastUpdated OBJECT-TYPE 407 SYNTAX TimeStamp 408 MAX-ACCESS read-only 409 STATUS current 410 DESCRIPTION 411 "The value of sysUpTime at the time this entry was last 412 updated. 413 Static entry: if the entry values keep unchanged since the re- 414 initialization of the PCC then this object contains a zero 415 value." 416 ::= { pceDiscoveryEntry 6 } 418 pceDiscoveryCongestion OBJECT-TYPE 419 SYNTAX TruthValue 420 MAX-ACCESS read-only 421 STATUS current 422 DESCRIPTION 423 "This object indicates whether a PCE experiences a processing 424 congestion state or not. 425 " 426 ::= { pceDiscoveryEntry 7 } 428 pceDiscoveryCongestionDuration OBJECT-TYPE 429 SYNTAX Unsigned32 430 MAX-ACCESS read-only 431 STATUS current 432 DESCRIPTION 433 "This object specifies, in seconds, the congestion duration. 434 When the value of pceDiscoveryCongestion is 'false' then this 435 objet MUST be to '0'" 436 ::= { pceDiscoveryEntry 8 } 438 pceDiscCapabilityObjects OBJECT IDENTIFIER ::= { pceDiscMIBObjects 2 439 } 441 -- 443 -- PCE-PATHSCOPE informations elements 445 -- 447 pceDiscPathScopeTable OBJECT-TYPE 448 SYNTAX SEQUENCE OF PceDiscPathScopeEntry 449 MAX-ACCESS not-accessible 450 STATUS current 451 DESCRIPTION 452 "PCEs may be involved in various path computations such that 453 dedicaced to one AS or one area, or specialized in inter AS, 454 inter area or inter layer. This table describe the path 455 computation capacities and preferences of the PCEs discovered." 456 ::= { pceDiscCapabilityObjects 1 } 458 pceDiscPathScopeEntry OBJECT-TYPE 459 SYNTAX PceDiscPathScopeEntry 460 MAX-ACCESS not-accessible 461 STATUS current 462 DESCRIPTION 463 "This object describes the path computation capacities and 464 preferences of the PCE identified with pceDiscoveryIndex." 465 INDEX { pceDiscoveryIndex } 466 ::= { pceDiscPathScopeTable 1 } 468 PceDiscPathScopeEntry ::= SEQUENCE { 469 pceDiscPathScopeIntraArea TruthValue, 470 pceDiscPathScopeInterArea TruthValue, 471 pceDiscPathScopeDefInterArea TruthValue, 472 pceDiscPathScopeInterAS TruthValue, 473 pceDiscPathScopeDefInterAS TruthValue, 474 pceDiscPathScopeInterLayer TruthValue, 475 pceDiscPathScopePrefIntraArea Integer32, 476 pceDiscPathScopePrefInterArea Integer32, 477 pceDiscPathScopePrefInterAS Integer32, 478 pceDiscPathScopePrefIntLayer Integer32 479 } 481 pceDiscPathScopeIntraArea OBJECT-TYPE 482 SYNTAX TruthValue 483 MAX-ACCESS read-only 484 STATUS current 485 DESCRIPTION 486 "Indicates whether the PCE supports the L option of the PATH- 487 SCOPE sub TLV: 488 The value is 'true' if the PCE can compute intra-area path." 489 ::= { pceDiscPathScopeEntry 1 } 491 pceDiscPathScopeInterArea OBJECT-TYPE 492 SYNTAX TruthValue 493 MAX-ACCESS read-only 494 STATUS current 495 DESCRIPTION 496 "Indicates whether the PCE supports the R option of the PATH- 497 SCOPE sub TLV: 498 The value is 'true' if the PCE can act as PCE for inter-area 499 TE LSPs computation." 500 ::= { pceDiscPathScopeEntry 2 } 502 pceDiscPathScopeDefInterArea OBJECT-TYPE 503 SYNTAX TruthValue 504 MAX-ACCESS read-only 505 STATUS current 506 DESCRIPTION 507 "Indicates whether the PCE supports the Rd option of the PATH- 508 SCOPE sub TLV: 509 The value is 'true' if the PCE can act as a default PCE for 510 inter-area TE LSPs computation." 511 ::= { pceDiscPathScopeEntry 3 } 513 pceDiscPathScopeInterAS OBJECT-TYPE 514 SYNTAX TruthValue 515 MAX-ACCESS read-only 516 STATUS current 517 DESCRIPTION 518 "Indicates whether the PCE supports the S option of the PATH- 519 SCOPE sub TLV: 520 The value is 'true' if the PCE can act as PCE for inter-AS 521 TE LSPs computation." 522 ::= { pceDiscPathScopeEntry 4 } 524 pceDiscPathScopeDefInterAS OBJECT-TYPE 525 SYNTAX TruthValue 526 MAX-ACCESS read-only 527 STATUS current 528 DESCRIPTION 529 "Indicates whether the PCE supports the Sd option of the PATH- 530 SCOPE sub TLV: 531 The value is 'true' if the PCE can act as a default PCE for 532 inter-AS TE LSPs computation." 533 ::= { pceDiscPathScopeEntry 5 } 535 pceDiscPathScopeInterLayer OBJECT-TYPE 536 SYNTAX TruthValue 537 MAX-ACCESS read-only 538 STATUS current 539 DESCRIPTION 540 "Indicates whether the PCE supports the Y option of the PATH- 541 SCOPE sub TLV: 542 The value is 'true' if the PCE can compute or take part into 543 the computation of paths across layers." 544 ::= { pceDiscPathScopeEntry 6} 546 pceDiscPathScopePrefIntraArea OBJECT-TYPE 547 SYNTAX Integer32 (0..7) 548 MAX-ACCESS read-only 549 STATUS current 550 DESCRIPTION 551 "Indicates the level of preference of the option of computation 552 'L' compared to other computation options: 553 A value of 7 reflects the highest preference. 554 When the value of PceDiscPathScopeIntraArea is 'false' then 555 this objet MUST be to '0'." 556 ::= { pceDiscPathScopeEntry 7} 558 pceDiscPathScopePrefInterArea OBJECT-TYPE 559 SYNTAX Integer32 (0..7) 560 MAX-ACCESS read-only 561 STATUS current 562 DESCRIPTION 563 "Indicates the level of preference of the option of computation 564 'R' compared to other computation options: 565 A value of 7 reflects the highest preference. 566 When the value of PceDiscPathScopeInterArea is 'false' then 567 this objet MUST be to '0'." 568 ::= { pceDiscPathScopeEntry 8} 570 pceDiscPathScopePrefInterAS OBJECT-TYPE 571 SYNTAX Integer32 (0..7) 572 MAX-ACCESS read-only 573 STATUS current 574 DESCRIPTION 575 "Indicates the level of preference of the option of computation 576 'S' compared to other computation options: 577 A value of 7 reflects the highest preference. 578 When the value of PceDiscPathScopeInterAS is 'false' then 579 this objet MUST be to '0'." 580 ::= { pceDiscPathScopeEntry 9} 582 pceDiscPathScopePrefIntLayer OBJECT-TYPE 583 SYNTAX Integer32 (0..7) 584 MAX-ACCESS read-only 585 STATUS current 586 DESCRIPTION 587 "Indicates the level of preference of the option of computation 588 'Y' compared to other computation options: 589 A value of 7 reflects the highest preference. 590 When the value of PceDiscPathScopeInterLayer is 'false' then 591 this objet MUST be to '0'." 592 ::= { pceDiscPathScopeEntry 10} 594 -- 596 -- PCE-DOMAINS information elements 598 -- 600 pceDiscDomainTable OBJECT-TYPE 601 SYNTAX SEQUENCE OF PceDiscDomainEntry 602 MAX-ACCESS not-accessible 603 STATUS current 604 DESCRIPTION 605 "Information describing the set of domains where the PCE has 606 topology visibility and can compute paths." 607 ::= { pceDiscCapabilityObjects 2 } 609 pceDiscDomainEntry OBJECT-TYPE 610 SYNTAX PceDiscDomainEntry 611 MAX-ACCESS not-accessible 612 STATUS current 613 DESCRIPTION 614 "This information describes a domain where the PCE identified 615 with pceDiscoveryIndex has topology visibility and can compute 616 paths." 617 INDEX { pceDiscoveryIndex, pceDiscDomainIndex } 618 ::= { pceDiscDomainTable 1 } 620 PceDiscDomainEntry ::= SEQUENCE { 621 pceDiscDomainIndex Integer32, 622 pceDiscDomainIDType AddressFamilyNumbers, 623 pceDiscDomainID PceRoutingDomainID 624 } 626 pceDiscDomainIndex OBJECT-TYPE 627 SYNTAX Integer32 (1..2147483647) 628 MAX-ACCESS not-accessible 629 STATUS current 630 DESCRIPTION 631 "This object identifies locally a domain for which the PCE 632 identified by pceDiscoveryIndex has topology visibility and can 633 compute paths. " 634 ::= { pceDiscDomainEntry 1 } 636 pceDiscDomainIDType OBJECT-TYPE 637 SYNTAX AddressFamilyNumbers 638 MAX-ACCESS read-only 639 STATUS current 640 DESCRIPTION 641 "This object identifies the type of the domainID of a PCE- 642 DOMAIN SUB TLV. 643 Acceptable types are : 644 ipV4(1) and ipV6(2) for an OSPF area ID; 645 nsap(3) for and ISIS area ID; 646 asNumber(18) for an BGP AS number" 647 ::= { pceDiscDomainEntry 2 } 649 pceDiscDomainID OBJECT-TYPE 650 SYNTAX PceRoutingDomainID 651 MAX-ACCESS read-only 652 STATUS current 653 DESCRIPTION 654 "The ID (area,AS) of the routing domain for which this entry 655 contains information." 656 ::= { pceDiscDomainEntry 3 } 658 -- 660 -- NEIG-PCE-DOMAINS information elements 662 -- 664 pceDiscNeighborDomainTable OBJECT-TYPE 665 SYNTAX SEQUENCE OF PceDiscNeighborDomainEntry 666 MAX-ACCESS not-accessible 667 STATUS current 668 DESCRIPTION 669 "Information describing the set of destination domains toward 670 which a PCE can compute paths." 671 ::= { pceDiscCapabilityObjects 3 } 673 pceDiscNeighborDomainEntry OBJECT-TYPE 674 SYNTAX PceDiscNeighborDomainEntry 675 MAX-ACCESS not-accessible 676 STATUS current 677 DESCRIPTION 678 "Information describing the destination domains of each PCE." 679 INDEX { pceDiscoveryIndex, pceDiscNeighborDomainIndex } 680 ::= { pceDiscNeighborDomainTable 1 } 682 PceDiscNeighborDomainEntry ::= SEQUENCE { 683 pceDiscNeighborDomainIndex Integer32, 684 pceDiscNeighborDomainIDType AddressFamilyNumbers, 685 pceDiscNeighborDomainID PceRoutingDomainID 686 } 688 pceDiscNeighborDomainIndex OBJECT-TYPE 689 SYNTAX Integer32 (1..2147483647) 690 MAX-ACCESS not-accessible 691 STATUS current 692 DESCRIPTION 693 "This object identifies locally a destination domain toward 694 which a PCE identified by pceDiscoveryIndex can compute path." 695 ::= { pceDiscNeighborDomainEntry 1 } 697 pceDiscNeighborDomainIDType OBJECT-TYPE 698 SYNTAX AddressFamilyNumbers 699 MAX-ACCESS read-only 700 STATUS current 701 DESCRIPTION 702 "This object identifies the type of the routing domain. 703 Acceptable types are : 704 ipV4(1) and ipV6(2) for an OSPF area ID; 705 nsap(3) for and ISIS area ID; 706 asNumber(18) for an BGP AS number" 707 ::= { pceDiscNeighborDomainEntry 2 } 709 pceDiscNeighborDomainID OBJECT-TYPE 710 SYNTAX PceRoutingDomainID 711 MAX-ACCESS read-only 712 STATUS current 713 DESCRIPTION 714 "The ID (area,AS) of the routing domain for which this entry 715 contains information." 716 ::= { pceDiscNeighborDomainEntry 3 } 718 pceDiscOptionalCapabilitiesObjects OBJECT IDENTIFIER ::= { 719 pceDiscMIBObjects 3 } 721 -- PCE-CAP-FLAGS 723 pceDiscOptionalCapabilitiesTable OBJECT-TYPE 724 SYNTAX SEQUENCE OF PceDiscOptionalCapabilitiesEntry 725 MAX-ACCESS not-accessible 726 STATUS current 727 DESCRIPTION 728 "This table describes various capabilities supported by the 729 PCEs discovered, such as path computation options, requests 730 processing options or new options added in the future in IANA 731 registry named 'PCE Capability Flags'." 732 ::= { pceDiscOptionalCapabilitiesObjects 1 } 734 pceDiscOptionalCapabilitiesEntry OBJECT-TYPE 735 SYNTAX PceDiscOptionalCapabilitiesEntry 736 MAX-ACCESS not-accessible 737 STATUS current 738 DESCRIPTION 739 "This objet describes an atomic capability the PCE identified 740 by pceDiscoveryIndex supports. " 741 INDEX { pceDiscoveryIndex } 742 ::= { pceDiscOptionalCapabilitiesTable 1 } 744 PceDiscOptionalCapabilitiesEntry ::= SEQUENCE { 745 pceDiscOptionalCapability Integer32 746 } 748 pceDiscOptionalCapability OBJECT-TYPE 749 SYNTAX Integer32 (0..31) 750 MAX-ACCESS read-only 751 STATUS current 752 DESCRIPTION 753 "This objet describes an atomic option the PCE identified by 754 pceDiscoveryIndex supports. The IANA registry 'PCE Capability 755 Flags' handles current capabilities and the definition of new 756 options in the future. At the time being the value is 757 restricted to one of the following: 758 0 Path computation with GMPLS link constraints; 759 1 Bidirectional path computation; 760 2 Diverse path computation; 761 3 Load-balanced path computation; 762 4 Synchronized path computation; 763 5 Support for multiple objective functions; 764 6 Support for additive path constraints (max hop count, 765 etc.); 766 7 Support for request prioritization; 767 8 Support for multiple requests per message. 769 NOTE: This object type is not enumerated because new options, 770 like p2mp capabilities, may be defined in the future. " 771 ::= { pceDiscOptionalCapabilitiesEntry 1 } 773 -- Activity objects 775 pceDiscActivityObjects OBJECT IDENTIFIER ::= { pceDiscMIBObjects 4 } 777 pceDiscActivityTable OBJECT-TYPE 778 SYNTAX SEQUENCE OF PceDiscActivityEntry 779 MAX-ACCESS not-accessible 780 STATUS current 781 DESCRIPTION 782 "Information describing the discovery mechanisms activities." 783 ::= { pceDiscActivityObjects 1 } 785 pceDiscActivityEntry OBJECT-TYPE 786 SYNTAX PceDiscActivityEntry 787 MAX-ACCESS not-accessible 788 STATUS current 789 DESCRIPTION 790 "This object describes the discovery activity of the PCE 791 identified by pceDiscoveryIndex. " 792 INDEX { pceDiscoveryIndex } 793 ::= { pceDiscActivityTable 1 } 795 PceDiscActivityEntry ::= SEQUENCE { 796 pceDiscActivityTlvReceived Integer32, 797 pceDiscActivityErroredTlvReceived Integer32, 798 pceDiscActivityErroredTlvLastMinutePercentage Integer32, 799 pceDiscActivityErroredTlvRisingThreshold Integer32 800 } 802 pceDiscActivityTlvReceived OBJECT-TYPE 803 SYNTAX Integer32 (1..2147483647) 804 MAX-ACCESS read-only 805 STATUS current 806 DESCRIPTION 807 "This object counts the number of information elements received 808 since the discovery of the PCE." 809 ::= { pceDiscActivityEntry 1 } 811 pceDiscActivityErroredTlvReceived OBJECT-TYPE 812 SYNTAX Integer32 (1..2147483647) 813 MAX-ACCESS read-only 814 STATUS current 815 DESCRIPTION 816 "This object counts the number of Errored information elements 817 received since the discovery of the PCE." 818 ::= { pceDiscActivityEntry 2 } 820 pceDiscActivityErroredTlvLastMinutePercentage OBJECT-TYPE 821 SYNTAX Integer32 (0..100) 822 MAX-ACCESS read-only 823 STATUS current 824 DESCRIPTION 825 "This object reports the percentage of the errored information 826 elements received over a one-minute average." 827 ::= { pceDiscActivityEntry 3 } 829 pceDiscActivityErroredTlvRisingThreshold OBJECT-TYPE 830 SYNTAX Integer32 (0..100) 831 MAX-ACCESS read-write 832 STATUS current 833 DESCRIPTION 834 "This object specifies the percentage of information elements 835 errors limit to be reach before triggering the sending of the 836 notification 'pceDiscAbnormalErroredTlvPercentage'." 837 ::= { pceDiscActivityEntry 4 } 839 -- 841 -- Notification -- 843 -- 845 pceDiscNotAnyPceIdentified NOTIFICATION-TYPE 846 OBJECTS { 847 pceDiscoveryKnownPCEs 848 } 849 STATUS current 850 DESCRIPTION 851 "This notification is sent when the value of 852 'pceDiscoveryKnownPCEs' decreases to zero. 853 This occurs typically when, after modification of 854 configuration, there is no more PCE manually declared and when 855 there is no more PCE discovery sessions configured." 856 ::= { pceDiscNotifications 1 } 858 pceDiscAllPcesInactive NOTIFICATION-TYPE 859 OBJECTS { 860 pceDiscoveryKnownPCEs, 861 pceDiscoveryActivePCEs 862 } 863 STATUS current 864 DESCRIPTION 865 "This notification is sent when the value of 866 'pceDiscoveryActivePCEs' decreases to zero. 867 This occurs when all the PCE discovery sessions come inactive." 868 ::= { pceDiscNotifications 2 } 870 pceDiscAbnormalErroredTlvPercentage NOTIFICATION-TYPE 871 OBJECTS { 872 pceDiscActivityErroredTlvLastMinutePercentage, 873 pceDiscActivityErroredTlvRisingThreshold 874 } 875 STATUS current 876 DESCRIPTION 877 "This notification is sent when the value of 878 'pceDiscActivityErroredTlvLastMinutePercentage' rises over the 879 value of pceDiscActivityErroredTlvRisingThreshold." 880 ::= { pceDiscNotifications 3 } 882 -- 884 -- PCE DISC agents conformance statement 886 -- 888 pceDiscConformance OBJECT IDENTIFIER ::= { pceDiscDraftMIB 2 } 890 pceDiscCompliances OBJECT IDENTIFIER ::= { pceDiscConformance 1 } 892 pceDiscGroups OBJECT IDENTIFIER ::= { pceDiscConformance 2 } 894 -- PCE DISC agent compliance statements 896 pceDiscGeneralPceInformation MODULE-COMPLIANCE 897 STATUS current 898 DESCRIPTION 899 "The compliance statement for SNMP entities that implement only 900 general monitoring information as proposed in the 2nd S. of the 901 section 6.1 of [RFC4674]." 902 MODULE 903 MANDATORY-GROUPS { 904 pceDiscDiscoveryGroup, 905 pceDiscActivityGroup, 906 pceDiscPathScopeGroup, 907 pceDiscDomainsGroup, 908 pceDiscOptionsGroup, 909 pceDiscNotificationGroup 910 } 911 ::= { pceDiscCompliances 1 } 913 pceDiscDiscoveryGroup OBJECT-GROUP 914 OBJECTS { 915 pceDiscoveryAdminStatus, 916 pceDiscoveryKnownPCEs, 917 pceDiscoveryActivePCEs, 918 pceDiscoveryMechanism, 919 pceDiscoveryIPv4Address, 920 pceDiscoveryIPv6Address, 921 pceDiscoveryTime, 922 pceDiscoveryLastUpdated, 923 pceDiscoveryCongestion, 924 pceDiscoveryCongestionDuration 925 } 926 STATUS current 927 DESCRIPTION 928 "Hight level objects for monitoring the PCEs sessions. " 929 ::= { pceDiscGroups 1 } 931 pceDiscActivityGroup OBJECT-GROUP 932 OBJECTS { 933 pceDiscActivityTlvReceived, 934 pceDiscActivityErroredTlvReceived, 935 pceDiscActivityErroredTlvLastMinutePercentage, 936 pceDiscActivityErroredTlvRisingThreshold 937 } 938 STATUS current 939 DESCRIPTION 940 "Objects for monitoring PCEs sessions activity. " 941 ::= { pceDiscGroups 2 } 943 pceDiscPathScopeGroup OBJECT-GROUP 944 OBJECTS { 945 pceDiscPathScopeIntraArea, 946 pceDiscPathScopeInterArea, 947 pceDiscPathScopeDefInterArea, 948 pceDiscPathScopeInterAS, 949 pceDiscPathScopeDefInterAS, 950 pceDiscPathScopeInterLayer, 951 pceDiscPathScopePrefIntraArea, 952 pceDiscPathScopePrefInterArea, 953 pceDiscPathScopePrefInterAS, 954 pceDiscPathScopePrefIntLayer 955 } 956 STATUS current 957 DESCRIPTION 958 "Objects describing the path computation capabilities. " 959 ::= { pceDiscGroups 3 } 961 pceDiscDomainsGroup OBJECT-GROUP 962 OBJECTS { 963 pceDiscDomainIDType, 964 pceDiscDomainID, 965 pceDiscNeighborDomainIDType, 966 pceDiscNeighborDomainID 967 } 968 STATUS current 969 DESCRIPTION 970 "Objects describing the domains the PCEs compute paths on and 971 are in relation with. " 972 ::= { pceDiscGroups 4 } 974 pceDiscOptionsGroup OBJECT-GROUP 975 OBJECTS { 976 pceDiscOptionalCapability 977 } 978 STATUS current 979 DESCRIPTION 980 "Objects describing PCEs options capabilities. " 981 ::= { pceDiscGroups 5 } 983 pceDiscNotificationGroup NOTIFICATION-GROUP 984 NOTIFICATIONS { 985 pceDiscNotAnyPceIdentified, 986 pceDiscAllPcesInactive, 987 pceDiscAbnormalErroredTlvPercentage 988 } 989 STATUS current 990 DESCRIPTION 991 "Set of notifications implemented in this module. " 992 ::= { pceDiscGroups 6 } 994 END 996 9. Security Considerations 998 There are a number of management objects defined in this MIB module 999 with a MAX-ACCESS clause of read-write and/or read-create. Such 1000 objects may be considered sensitive or vulnerable in some network 1001 environments. The support for SET operations in a non-secure 1002 environment without proper protection can have a negative effect on 1003 network operations. These are the tables and objects and their 1004 sensitivity/vulnerability: 1005 o on/off of discovery : Unauthorized changes to 1006 pceDiscoveryAdminStatus could result in a temporary interruption 1007 of the discovery ; 1009 Some of the readable objects in this MIB module (i.e., objects with a 1010 MAX-ACCESS other than not-accessible) may be considered sensitive or 1011 vulnerable in some network environments. It is thus important to 1012 control even GET and/or NOTIFY access to these objects and possibly 1013 to even encrypt the values of these objects when sending them over 1014 the network via SNMP. These are the tables and objects and their 1015 sensitivity/vulnerability: 1016 o IP addresses of PCE. 1018 SNMP versions prior to SNMPv3 did not include adequate security. 1019 Even if the network itself is secure (for example by using IPSec), 1020 even then, there is no control as to who on the secure network is 1021 allowed to access and GET/SET (read/change/create/delete) the objects 1022 in this MIB module. 1024 It is RECOMMENDED that implementers consider the security features as 1025 provided by the SNMPv3 framework (see [RFC3410], section 8), 1026 including full support for the SNMPv3 cryptographic mechanisms (for 1027 authentication and privacy). 1029 Further, deployment of SNMP versions prior to SNMPv3 is NOT 1030 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 1031 enable cryptographic security. It is then a customer/operator 1032 responsibility to ensure that the SNMP entity giving access to an 1033 instance of this MIB module is properly configured to give access to 1034 the objects only to those principals (users) that have legitimate 1035 rights to indeed GET or SET (change/create/delete) them. 1037 10. IANA Considerations 1039 11. References 1041 11.1. Normative References 1043 [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. 1044 Schoenwaelder, Ed., "Structure of Management Information 1045 Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. 1047 [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. 1048 Schoenwaelder, Ed., "Textual Conventions for SMIv2", 1049 STD 58, RFC 2579, April 1999. 1051 [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 1052 "Conformance Statements for SMIv2", STD 58, RFC 2580, 1053 April 1999. 1055 [RFC5089] Le Roux, JL., Vasseur, JP., Ikejiri, Y., and R. Zhang, 1056 "IS-IS Protocol Extensions for Path Computation Element 1057 (PCE) Discovery", RFC 5089, January 2008. 1059 11.2. Informative References 1061 [RFC0768] Postel, J., "User Datagram Protocol", STD 6, RFC 768, 1062 August 1980. 1064 [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group 1065 MIB", RFC 2863, June 2000. 1067 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, 1068 "Introduction and Applicability Statements for Internet- 1069 Standard Management Framework", RFC 3410, December 2002. 1071 [RFC4655] Farrel, A., Vasseur, J., and J. Ash, "A Path Computation 1072 Element (PCE)-Based Architecture", RFC 4655, August 2006. 1074 [RFC4674] Le Roux, J., "Requirements for Path Computation Element 1075 (PCE) Discovery", RFC 4674, October 2006. 1077 Appendix A. Open Issues 1079 This list of open issues should be cleared and removed before this 1080 document hits the IESG. 1082 Author's Address 1084 Stephan Emile 1085 France Telecom 1086 2 avenue Pierre Marzin 1087 Lannion, F-22307 1088 Fax: +33 2 96 05 18 52 1089 Email: emile.stephan@orange-ftgroup.com 1091 Quintin Zhao 1092 Huawei Technology 1093 125 Nagog Technology Park 1094 Acton, MA 01719 1095 US 1096 Email: qzhao@huawei.com 1098 Daniel King 1099 Old Dog Consulting 1100 UK 1101 Email: daniel@olddog.co.uk