idnits 2.17.1 draft-zhao-pce-pcep-p2mp-mib-05.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack a both a reference to RFC 2119 and the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. RFC 2119 keyword, line 830: '... It is RECOMMENDED that implementers...' RFC 2119 keyword, line 836: '... RECOMMENDED. Instead, it is RECOMM...' Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == Line 181 has weird spacing: '...yStatus enab...' -- The document date (August 17, 2012) is 4271 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) -- Obsolete informational reference (is this intentional?): RFC 6006 (Obsoleted by RFC 8306) == Outdated reference: A later version (-11) exists of draft-ietf-pce-pcep-mib-03 Summary: 1 error (**), 0 flaws (~~), 3 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 PCE Working Group Q. Zhao 3 Internet-Draft D. Dhody 4 Intended status: Standards Track U. Palle 5 Expires: February 18, 2013 Huawei Technology 6 D. King 7 Old Dog Consulting 8 August 17, 2012 10 Management Information Base for the PCE Communications Protocol (PCEP) 11 When Requesting Point-to-Multipoint Services 12 draft-zhao-pce-pcep-p2mp-mib-05 14 Abstract 16 This memo defines an experimental portion of the Management 17 Information Base for use with network management protocols in the 18 Internet community. In particular, it describes managed objects for 19 modeling of the Path Computation Element communication Protocol 20 (PCEP) for communications between a Path Computation Client (PCC) and 21 a Path Computation Element (PCE), or between two PCEs when point-to- 22 multipoint services are requested. 24 Status of This Memo 26 This Internet-Draft is submitted in full conformance with the 27 provisions of BCP 78 and BCP 79. 29 Internet-Drafts are working documents of the Internet Engineering 30 Task Force (IETF). Note that other groups may also distribute 31 working documents as Internet-Drafts. The list of current Internet- 32 Drafts is at http://datatracker.ietf.org/drafts/current/. 34 Internet-Drafts are draft documents valid for a maximum of six months 35 and may be updated, replaced, or obsoleted by other documents at any 36 time. It is inappropriate to use Internet-Drafts as reference 37 material or to cite them other than as "work in progress." 39 This Internet-Draft will expire on February 18, 2013. 41 Copyright Notice 43 Copyright (c) 2012 IETF Trust and the persons identified as the 44 document authors. All rights reserved. 46 This document is subject to BCP 78 and the IETF Trust's Legal 47 Provisions Relating to IETF Documents 48 (http://trustee.ietf.org/license-info) in effect on the date of 49 publication of this document. Please review these documents 50 carefully, as they describe your rights and restrictions with respect 51 to this document. Code Components extracted from this document must 52 include Simplified BSD License text as described in Section 4.e of 53 the Trust Legal Provisions and are provided without warranty as 54 described in the Simplified BSD License. 56 Table of Contents 58 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 59 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 60 3. The Internet-Standard Management Framework . . . . . . . . . . 4 61 4. PCEP P2MP MIB Module Architecture . . . . . . . . . . . . . . 4 62 5. Example of the PCEP P2MP MIB module usage . . . . . . . . . . 5 63 6. Object definitions . . . . . . . . . . . . . . . . . . . . . . 5 64 6.1. PCE-PCEP-P2MP-DRAFT-MIB . . . . . . . . . . . . . . . . . 5 65 6.2. Objects for inclusion in module PCE-PCEP-DRAFT-MIB . . . . 18 66 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 19 67 8. Security Considerations . . . . . . . . . . . . . . . . . . . 19 68 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 20 69 9.1. Normative References . . . . . . . . . . . . . . . . . . . 20 70 9.2. Informative References . . . . . . . . . . . . . . . . . . 20 72 1. Introduction 74 The Path Computation Element (PCE) defined in [RFC4655] is an entity 75 that is capable of computing a network path or route based on a 76 network graph, and applying computational constraints. A Path 77 Computation Client (PCC) may make requests to a PCE for paths to be 78 computed. 80 A P2MP LSP is comprised of multiple source-to-leaf (S2L) sub-LSPs. 81 These S2L sub-LSPs are set up between ingress and egress LSRs and are 82 appropriately combined by the branch LSRs using computation results 83 from the PCE to determine the path of a P2MP TE LSP. 85 The PCE communication protocol (PCEP) is designed as a communication 86 protocol between PCCs and PCEs for point-to-point (P2P) path 87 computations and is defined in [RFC5440]. [RFC6006] explains how to 88 extend the PCEP protocol for P2MP scenario. 90 [PCE-PCEP-DRAFT-MIB] defines a portion of the Management Information 91 Base (MIB) for use with network management protocols in the Internet 92 community for P2P path computations. 94 This memo defines an experimental portion of the Management 95 Information Base for use with network management protocols in the 96 Internet community. In particular, it describes managed objects for 97 modeling of Path Computation Element communication Protocol (PCEP) 98 [RFC5440] for communications between a Path Computation Client 99 (PCC)and a Path Computation Element (PCE), or between two PCEs in 100 P2MP scenarios. 102 Some objects maybe moved to [PCE-PCEP-DRAFT-MIB] after consensus with 103 the authors and working group, these are defined in Section 6.2. 105 2. Terminology 107 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 LSP: Label Switched Path. 120 MIB: Management Information Base. 122 PCC: Path Computation Client: any client application requesting a 123 path computation to be performed by a Path Computation Element. 125 PCE: Path Computation Element. An entity (component, application, 126 or network node) that is capable of computing a network path or 127 route based on a network graph and applying computational 128 constraints. 130 PCEP: Path Computation Element Communication Protocol. 132 P2MP: Point-to-Multipoint. 134 P2P: Point-to-Point. 136 SMI: Structure of Management Information. 138 SNMP: Simple Network Management Protocol. 140 3. The Internet-Standard Management Framework 142 For a detailed overview of the documents that describe the current 143 Internet-Standard Management Framework, please refer to section 7 of 144 [RFC3410]. 146 Managed objects are accessed via a virtual information store, termed 147 the Management Information Base or MIB. MIB objects are generally 148 accessed through the Simple Network Management Protocol (SNMP). 149 Objects in the MIB are defined using the mechanisms defined in the 150 Structure of Management Information (SMI). This memo specifies a MIB 151 module that is compliant to the SMIv2, which is described in STD 58, 152 RFC 2578 [RFC2578] and STD 58, RFC 2580 [RFC2580]. 154 4. PCEP P2MP MIB Module Architecture 156 The PCEP P2MP MIB is just an extension of the existing architecture 157 defined in [PCE-PCEP-DRAFT-MIB] by adding additional objects which 158 are either common to P2P and P2MP or which are specific to P2MP. All 159 these new objects are added into the two new tables 160 (pcePcepExtSessionTable and pcePcepExtClientTable) defined in this 161 new MIB module. The relationship among the two new tables to the two 162 existing tables in [PCE-PCEP-DRAFT-MIB] are shown in the following 163 figure: 165 pcePcepSessionTable <-------- pcePcepExtSessionTable 166 pcePcepClientTable <-------- pcePcepExtClientTable 168 An arrow in the figure above shows that the MIB table pointed from 169 contains a reference to the MIB table pointed to. 171 5. Example of the PCEP P2MP MIB module usage 173 In this section we provide an example (pcePcepExtClientTable 1) of 174 using the MIB objects described in Section 6 to monitor. While this 175 example is not meant to illustrate every permutation of the MIB, it 176 is intended as an aid to understanding some of the key concepts. It 177 is meant to be read after going through the MIB itself. 179 pcePcepExtClientTable 1 of the PCE-PCEP-P2MP-DRAFT-MIB module : 180 { 181 pcePcepClientP2mpCapabilityStatus enable(1), 182 pcePcepClientOverloadStatus resumed(2), 183 pcePcepClientOverloadDuration (10), 184 } 186 6. Object definitions 188 6.1. PCE-PCEP-P2MP-DRAFT-MIB 190 This MIB module makes references to the following documents. 192 [RFC2578], [RFC2580], [RFC3411], [RFC2863], [RFC3813], 193 [PCE-PCEP-DRAFT-MIB]. 195 PCE-PCEP-P2MP-DRAFT-MIB DEFINITIONS ::= BEGIN 197 IMPORTS 198 MODULE-IDENTITY, OBJECT-TYPE, 199 Unsigned32, 200 Counter32, 201 experimental 202 FROM SNMPv2-SMI -- [RFC2578] 204 pcePcepClientPcepId, pcePcepClientIndex, 205 pcePcepPeerPcepId 206 FROM PCE-PCEP-DRAFT-MIB 208 MODULE-COMPLIANCE, 209 OBJECT-GROUP, 210 FROM SNMPv2-CONF; -- [RFC2580] 212 pcePcepP2mpDraftMIB MODULE-IDENTITY 213 LAST-UPDATED "201208171200Z" -- Aug 17, 2012 214 ORGANIZATION "Path Computation Element (PCE) Working Group" 215 CONTACT-INFO " 217 Quintin Zhao 218 Dhruv Dhody 219 Udayasree Palle 220 Huawei Technology 221 Daniel King 222 OldDog Consulting 224 EMail: quintin.zhao@huawei.com 225 EMail: dhruv.dhody@huawei.com 226 EMail: udayasree.palle@huawei.com 227 EMail: daniel@oldog.co.uk 228 EMail comments directly to the PCE WG Mailing List at pce@ietf.org 229 WG-URL: http://www.ietf.org/html.charters/pce-charter.html 230 " 232 DESCRIPTION 234 "This extended MIB module defines a collection of objects for 235 managing PCE communication protocol(PCEP) when point-to-multipoint 236 services are requested" 238 -- Revision history 239 REVISION 240 "201208171200Z" -- 17 Aug 2012 12:00:00 EST 241 DESCRIPTION 242 " 243 Main Changes from -04 draft : 244 1. Editorial Changes. 246 REVISION 247 "201202221200Z" -- 22 Feb 2012 12:00:00 EST 248 DESCRIPTION 249 " 250 Main Changes from -03 draft : 251 1. Editorial Changes. 252 2. Updated Contact Information. 254 REVISION 255 "201109201200Z" -- 20 Sept 2011 12:00:00 EST 256 DESCRIPTION 257 " 258 Changes from -02 draft : 259 1. Correction of Unsigned32 to Counter32. 261 2. Update Email Address of the author(s) 263 REVISION 264 "201103211200Z" -- 21 Mar 2011 12:00:00 EST 265 DESCRIPTION 266 " 267 Changes from -01 draft : 268 1. Correction of spelling mistakes in the document. 269 2. Addition in Terminology section 271 REVISION 272 "201009151200Z" -- 15 Sep 2010 12:00:00 EST 273 DESCRIPTION 274 " 275 Changes from -00 draft : 276 1. Removed pathkey objects as these objects to be made as 277 a new MIB module for pathkey. As per section 6.2 of 278 [RFC5520]. 279 2. Rearrangement of the sections for better understanding 280 3. Addition of STATUS (optional or mandatory) in the 281 definitions 282 4. Addition of section 6.2 to gather all objects which may 283 be moved to [PCE-PCEP-DRAFT-MIB]" 285 REVISION 286 "201007051200Z" -- July 05 2010 12:00:00 EST 287 DESCRIPTION 289 "draft-00 version" 290 ::= { experimental 9999 } -- 292 pcePcepExtMIBObjects OBJECT IDENTIFIER ::= { pcePcepExtDraftMIB 0 } 293 pcePcepExtConformance OBJECT IDENTIFIER ::= { pcePcepExtDraftMIB 1 } 294 pcePcepExtClientObjects OBJECT IDENTIFIER ::= { pcePcepExtMIBObjects 295 1 } 297 -- 299 -- PCE Extended Client Objects 301 -- 302 pcePcepClientVersionnumber OBJECT-TYPE 303 SYNTAX Unsigned32 304 MAX-ACCESS read-only 305 STATUS optional 306 DESCRIPTION 307 "The current version number of the PCEP protocol is 1." 308 ::= { pcePcepExtClientObjects 1 } 310 pcePcepExtClientTable OBJECT-TYPE 311 SYNTAX SEQUENCE OF PcePcepClientEntry 312 MAX-ACCESS not-accessible 313 STATUS current 314 DESCRIPTION 315 "This table contains information about the 316 PCEP Client." 317 ::= { pcePcepExtClientObjects 2 } 319 pcePcepExtClientEntry OBJECT-TYPE 320 SYNTAX PcePcepClientEntry 321 MAX-ACCESS not-accessible 322 STATUS current 323 DESCRIPTION 324 "An entry in this table represents a PCEP client. 325 An entry can be created by a network administrator 326 or by an SNMP agent as instructed by PCEP." 328 INDEX { pcePcepClientPcepId, 329 pcePcepClientIndex, 330 pcePcepPeerPcepId } 332 ::= { pcePcepExtClientTable 1 } 334 PcePcepExtClientEntry ::= SEQUENCE { 335 pcePcepClientP2mpCapabilityStatus INTEGER, 336 pcePcepClientOverloadStatus INTEGER, 337 pcePcepClientOverloadDuration Unsigned32 338 } 340 pcePcepClientP2mpCapabilityStatus OBJECT-TYPE 341 SYNTAX INTEGER { 342 enable (1), 343 disable(2) 344 } 345 MAX-ACCESS read-only 346 STATUS mandatory 347 DESCRIPTION 348 "The P2MP capability status of this PCEP client." 349 ::= { pcePcepExtClientEntry 1 } 351 pcePcepClientOverloadStatus OBJECT-TYPE 352 SYNTAX INTEGER { 353 overloaded(1), 354 resumed(2) 355 } 356 MAX-ACCESS read-only 357 STATUS optional 358 DESCRIPTION 359 "The Overload status of this PCE client." 360 ::= { pcePcepExtClientEntry 2 } 362 pcePcepClientOverloadDuration OBJECT-TYPE 363 SYNTAX Unsigned32 364 UNITS "seconds" 365 MAX-ACCESS read-only 366 STATUS optional 367 DESCRIPTION 368 "The period of time during which no further request should 369 be sent to the PCE client. Once this period of time has 370 elapsed, the PCE client should no longer be considered in 371 a congested state." 372 ::= { pcePcepExtClientEntry 3 } 374 pcePcepExtSessionObjects OBJECT IDENTIFIER ::= { pcePcepExtMIBObjects 375 2 } 377 -- 379 -- The PCEP Ext Sessions Table 381 -- 383 pcePcepExtSessionTable OBJECT-TYPE 384 SYNTAX SEQUENCE OF pcePcepExtSessionEntry 385 MAX-ACCESS not-accessible 386 STATUS current 387 DESCRIPTION 388 "A table of extended sessions characteristics between 389 PCEP clients. Each row in this table represents a 390 single session." 391 ::= { pcePcepExtSessionObjects 1 } 393 pcePcepExtSessionEntry OBJECT-TYPE 394 SYNTAX pcePcepExtSessionEntry 395 MAX-ACCESS not-accessible 396 STATUS current 397 DESCRIPTION 398 "An entry in this table represents information on a 399 single session between two PCEP clients. 400 The information contained in a row is read-only." 402 ::= { pcePcepExtSessionTable 1 } 404 PcePcepExtSessionEntry ::= SEQUENCE { 405 pcePcepSessionP2mpPCReqMessagesSent Counter32, 406 pcePcepSessionP2mpPCRepMessagesSent Counter32, 407 pcePcepSessionP2mpPCReqMessagesReceived Counter32, 408 pcePcepSessionP2mpPCRepMessagesReceived Counter32, 409 pcePcepSessionP2mpAddLeaves Counter32, 410 pcePcepSessionP2mpRemoveLeaves Counter32, 411 pcePcepSessionP2mpModifyLeaves Counter32, 412 pcePcepSessionP2mpUnchangedLeaves Counter32, 413 pcePcepSessionTotalMessagesSent Counter32, 414 pcePcepSessionOpenMessagesSent Counter32, 415 pcePcepSessionKeepaliveMessagesSent Counter32, 416 pcePcepSessionPCNtfMessagesSent Counter32, 417 pcePcepSessionPCErrMessagesSent Counter32, 418 pcePcepSessionTotalMessagesReceived Counter32, 419 pcePcepSessionOpenMessagesReceived Counter32, 420 pcePcepSessionKeepaliveMessagesReceived Counter32, 421 pcePcepSessionPCNtfMessagesReceived Counter32, 422 pcePcepSessionPCErrMessagesReceived Counter32, 423 pcePcepSessionIntraDomainRequest Counter32, 424 pcePcepSessionInterDomainRequest Counter32, 425 pcePcepSessionSuccessComps Counter32, 426 pcePcepSessionNoReply Counter32, 427 pcePcepSessionSyncronization Counter32, 428 pcePcepSessionReoptimization Counter32, 429 pcePcepSessionFragmentation Counter32, 430 pcePcepSessionP2pPCReqMessagesSent Counter32, 431 pcePcepSessionP2pPCRepMessagesSent Counter32, 432 pcePcepSessionP2pPCReqMessagesReceived Counter32, 433 pcePcepSessionP2pPCRepMessagesReceived Counter32, 434 } 436 pcePcepSessionP2mpPCReqMessagesSent OBJECT-TYPE 437 SYNTAX Counter32 438 MAX-ACCESS read-only 439 STATUS mandatory 440 DESCRIPTION 441 "The number of P2MP Request messages sent on this 442 session." 443 ::= { pcePcepExtSessionEntry 1 } 445 pcePcepSessionP2mpPCRepMessagesSent OBJECT-TYPE 446 SYNTAX Counter32 447 MAX-ACCESS read-only 448 STATUS mandatory 449 DESCRIPTION 450 "The number of P2MP Reply messages sent on this session." 451 ::= { pcePcepExtSessionEntry 2 } 453 pcePcepSessionP2mpPCReqMessagesReceived OBJECT-TYPE 454 SYNTAX Counter32 455 MAX-ACCESS read-only 456 STATUS mandatory 457 DESCRIPTION 458 "The number of P2MP Request messages received on this 459 session." 460 ::= { pcePcepExtSessionEntry 3 } 462 pcePcepSessionP2mpPCRepMessagesReceived OBJECT-TYPE 463 SYNTAX Counter32 464 MAX-ACCESS read-only 465 STATUS mandatory 466 DESCRIPTION 467 "The number of P2MP Reply messages received on this 468 session." 469 ::= { pcePcepExtSessionEntry 4 } 471 pcePcepSessionP2mpAddLeaves OBJECT-TYPE 472 SYNTAX Counter32 473 MAX-ACCESS read-only 474 STATUS mandatory 475 DESCRIPTION 476 "The number of leaves to be Added (Type1) for the 477 total P2MP requests (PCReq message) received by 478 the PCE." 479 ::= { pcePcepExtSessionEntry 5 } 481 pcePcepSessionP2mpRemoveLeaves OBJECT-TYPE 482 SYNTAX Counter32 483 MAX-ACCESS read-only 484 STATUS mandatory 485 DESCRIPTION 486 "The number of leaves to be Removed (Type2) for the 487 total P2MP requests (PCReq message) received by the 488 PCE." 489 ::= { pcePcepExtSessionEntry 6 } 491 pcePcepSessionP2mpModifyLeaves OBJECT-TYPE 492 SYNTAX Counter32 493 MAX-ACCESS read-only 494 STATUS mandatory 495 DESCRIPTION 496 "The number of leaves to be Modified (Type3) for the 497 total P2MP requests (PCReq message) received by the 498 PCE." 499 ::= { pcePcepExtSessionEntry 7 } 501 pcePcepSessionP2mpUnchangedLeaves OBJECT-TYPE 502 SYNTAX Counter32 503 MAX-ACCESS read-only 504 STATUS mandatory 505 DESCRIPTION 506 "The number of leaves not to be changed (Type4) for 507 the total P2MP requests (PCReq message) received 508 by the PCE." 509 ::= { pcePcepExtSessionEntry 8 } 511 pcePcepSessionTotalMessagesSent OBJECT-TYPE 512 SYNTAX Counter32 513 MAX-ACCESS read-only 514 STATUS mandatory 515 DESCRIPTION 516 "The total number of PCEP messages sent on this 517 session." 518 ::= { pcePcepExtSessionEntry 9 } 520 pcePcepSessionOpenMessagesSent OBJECT-TYPE 521 SYNTAX Counter32 522 MAX-ACCESS read-only 523 STATUS mandatory 524 DESCRIPTION 525 "The number of Open messages sent on this session." 526 ::= { pcePcepExtSessionEntry 10 } 528 pcePcepSessionKeepaliveMessagesSent OBJECT-TYPE 529 SYNTAX Counter32 530 MAX-ACCESS read-only 531 STATUS mandatory 532 DESCRIPTION 533 "The number of Keepalive messages sent on this session." 534 ::= { pcePcepExtSessionEntry 11 } 536 pcePcepSessionPCNtfMessagesSent OBJECT-TYPE 537 SYNTAX Counter32 538 MAX-ACCESS read-only 539 STATUS mandatory 540 DESCRIPTION 541 "The number of PCNtf messages sent on this session." 542 ::= { pcePcepExtSessionEntry 12 } 544 pcePcepSessionPCErrMessagesSent OBJECT-TYPE 545 SYNTAX Counter32 546 MAX-ACCESS read-only 547 STATUS mandatory 548 DESCRIPTION 549 "The number of PCErr messages sent on this session." 550 ::= { pcePcepExtSessionEntry 13 } 552 pcePcepSessionTotalMessagesReceived OBJECT-TYPE 553 SYNTAX Counter32 554 MAX-ACCESS read-only 555 STATUS mandatory 556 DESCRIPTION 557 "The total number of PCEP messages received on this 558 session." 559 ::= { pcePcepExtSessionEntry 14 } 561 pcePcepSessionOpenMessagesReceived OBJECT-TYPE 562 SYNTAX Counter32 563 MAX-ACCESS read-only 564 STATUS mandatory 565 DESCRIPTION 566 "The number of Open messages received on this 567 session." 568 ::= { pcePcepExtSessionEntry 15 } 570 pcePcepSessionKeepaliveMessagesReceived OBJECT-TYPE 571 SYNTAX Counter32 572 MAX-ACCESS read-only 573 STATUS mandatory 574 DESCRIPTION 575 "The number of Keepalive messages received on this 576 session." 577 ::= { pcePcepExtSessionEntry 16 } 579 pcePcepSessionPCNtfMessagesReceived OBJECT-TYPE 580 SYNTAX Counter32 581 MAX-ACCESS read-only 582 STATUS mandatory 583 DESCRIPTION 584 "The number of PCNtf messages received on this 585 session." 586 ::= { pcePcepExtSessionEntry 17 } 588 pcePcepSessionPCErrMessagesReceived OBJECT-TYPE 589 SYNTAX Counter32 590 MAX-ACCESS read-only 591 STATUS mandatory 592 DESCRIPTION 593 "The number of PCErr messages received on this 594 session." 595 ::= { pcePcepExtSessionEntry 18 } 597 pcePcepSessionIntraDomainRequest OBJECT-TYPE 598 SYNTAX Counter32 599 MAX-ACCESS read-only 600 STATUS optional 601 DESCRIPTION 602 "The number of requests sent for the Intra-Domain 603 path computation." 604 ::= { pcePcepExtSessionEntry 19 } 606 pcePcepSessionInterDomainRequest OBJECT-TYPE 607 SYNTAX Counter32 608 MAX-ACCESS read-only 609 STATUS optional 610 DESCRIPTION 611 "The number of requests sent for the Inter-Domain path 612 computation." 613 ::= { pcePcepExtSessionEntry 20 } 615 pcePcepSessionSuccessComps OBJECT-TYPE 616 SYNTAX Counter32 617 MAX-ACCESS read-only 618 STATUS optional 619 DESCRIPTION 620 "The number of requests which had successful 621 computations. In case of PCC-PCE session, it is core 622 computation value and in case of PCE-PCE session, it 623 is transit computation value." 624 ::= { pcePcepExtSessionEntry 21 } 626 pcePcepSessionNoReply OBJECT-TYPE 627 SYNTAX Counter32 628 MAX-ACCESS read-only 629 STATUS optional 630 DESCRIPTION 631 " The number of requests which had not been replied 632 either success or failure." 633 ::= { pcePcepExtSessionEntry 22 } 635 pcePcepSessionSyncronization OBJECT-TYPE 636 SYNTAX Counter32 637 MAX-ACCESS read-only 638 STATUS optional 639 DESCRIPTION 640 "The number of synchronized path computation requests 641 that can be either dependent or independent." 642 ::= { pcePcepExtSessionEntry 23 } 644 pcePcepSessionReoptimization OBJECT-TYPE 645 SYNTAX Counter32 646 MAX-ACCESS read-only 647 STATUS optional 648 DESCRIPTION 649 "The number of requests for Reoptimization." 650 ::= { pcePcepExtSessionEntry 24 } 652 pcePcepSessionFragmentation OBJECT-TYPE 653 SYNTAX Counter32 654 MAX-ACCESS read-only 655 STATUS optional 656 DESCRIPTION 657 "The number of packets of a PCReq / PCRep 658 message which had been fragmented." 659 ::= { pcePcepExtSessionEntry 25 } 661 pcePcepSessionP2pPCReqMessagesSent OBJECT-TYPE 662 SYNTAX Counter32 663 MAX-ACCESS read-only 664 STATUS mandatory 665 DESCRIPTION 666 "The number of P2P Request messages sent on this 667 session." 668 ::= { pcePcepExtSessionEntry 26 } 670 pcePcepSessionP2pPCRepMessagesSent OBJECT-TYPE 671 SYNTAX Counter32 672 MAX-ACCESS read-only 673 STATUS mandatory 674 DESCRIPTION 675 "The number of P2P Reply messages sent on this session." 676 ::= { pcePcepExtSessionEntry 27 } 678 pcePcepSessionP2pPCReqMessagesReceived OBJECT-TYPE 679 SYNTAX Counter32 680 MAX-ACCESS read-only 681 STATUS mandatory 682 DESCRIPTION 683 "The number of P2P PCReq messages received on this 684 session." 685 ::= { pcePcepExtSessionEntry 28 } 687 pcePcepSessionP2pPCRepMessagesReceived OBJECT-TYPE 688 SYNTAX Counter32 689 MAX-ACCESS read-only 690 STATUS mandatory 691 DESCRIPTION 692 "The number of P2P PCRep messages received on this 693 session." 694 ::= { pcePcepExtSessionEntry 29 } 696 --**************************************************************** 697 -- Module Conformance Statement 698 --**************************************************************** 700 pcePcepExtGroups 701 OBJECT IDENTIFIER ::= { pcePcepExtConformance 1 } 703 pcePcepExtCompliances 704 OBJECT IDENTIFIER ::= { pcePcepExtConformance 2 } 706 -- 707 -- Full Compliance 708 -- 710 pcePcepExtModuleFullCompliance MODULE-COMPLIANCE 711 STATUS current 712 DESCRIPTION 713 "The Module is implemented with support 714 for read-create and read-write. In other 715 words, both monitoring and configuration 716 are available when using this MODULE-COMPLIANCE." 718 MODULE -- this module 719 MANDATORY-GROUPS { pcePcepExtGeneralGroup, 720 } 722 ::= { pcePcepExtCompliances 1 } 724 -- 725 -- Read-Only Compliance 726 -- 728 pcePcepExtModuleReadOnlyCompliance MODULE-COMPLIANCE 729 STATUS current 730 DESCRIPTION 731 "The Module is implemented with support 732 for read-only. In other words, only monitoring 733 is available by implementing this MODULE-COMPLIANCE." 735 MODULE -- this module 736 MANDATORY-GROUPS { pcePcepExtGeneralGroup, 737 } 738 ::= { pcePcepExtCompliances 2 } 740 -- units of conformance 741 pcePcepExtGeneralGroup OBJECT-GROUP 742 OBJECTS { 744 pcePcepClientP2mpCapabilityStatus, 745 pcePcepSessionP2mpPCReqMessagesSent, 746 pcePcepSessionP2mpPCRepMessagesSent, 747 pcePcepSessionP2mpPCReqMessagesReceived, 748 pcePcepSessionP2mpPCRepMessagesReceived, 749 pcePcepSessionP2mpAddLeaves, 750 pcePcepSessionP2mpRemoveLeaves, 751 pcePcepSessionP2mpModifyLeaves, 752 pcePcepSessionP2mpUnchangedLeaves, 753 pcePcepSessionTotalMessagesSent, 754 pcePcepSessionOpenMessagesSent, 755 pcePcepSessionKeepaliveMessagesSent, 756 pcePcepSessionPCNtfMessagesSent, 757 pcePcepSessionPCErrMessagesSent, 758 pcePcepSessionTotalMessagesReceived, 759 pcePcepSessionOpenMessagesReceived, 760 pcePcepSessionKeepaliveMessagesReceived, 761 pcePcepSessionPCNtfMessagesReceived, 762 pcePcepSessionPCErrMessagesReceived, 763 pcePcepSessionP2pPCReqMessagesSent, 764 pcePcepSessionP2pPCRepMessagesSent, 765 pcePcepSessionP2pPCReqMessagesReceived, 766 pcePcepSessionP2pPCRepMessagesReceived 767 } 768 STATUS current 769 DESCRIPTION 770 "Objects that apply to all PCEP P2MP MIB implementations." 772 ::= { pcePcepExtGroups 1 } 774 END 776 6.2. Objects for inclusion in module PCE-PCEP-DRAFT-MIB 778 Following are the objects maybe moved to [PCE-PCEP-DRAFT-MIB] after 779 consensus with the authors and working group. 781 pcePcepClientVersionnumber, 782 pcePcepClientP2mpCapabilityStatus, 783 pcePcepClientOverloadStatus, 784 pcePcepClientOverloadDuration, 785 pcePcepSessionTotalMessagesSent, 786 pcePcepSessionOpenMessagesSent, 787 pcePcepSessionKeepaliveMessagesSent, 788 pcePcepSessionPCNtfMessagesSent, 789 pcePcepSessionPCErrMessagesSent, 790 pcePcepSessionTotalMessagesReceived, 791 pcePcepSessionOpenMessagesReceived, 792 pcePcepSessionKeepaliveMessagesReceived, 793 pcePcepSessionPCNtfMessagesReceived, 794 pcePcepSessionPCErrMessagesReceived, 795 pcePcepSessionIntraDomainRequest, 796 pcePcepSessionInterDomainRequest, 797 pcePcepSessionSuccessComps, 798 pcePcepSessionNoReply, 799 pcePcepSessionSyncronization, 800 pcePcepSessionReoptimization, 801 pcePcepSessionFragmentation, 802 pcePcepSessionP2pPCReqMessagesSent, 803 pcePcepSessionP2pPCRepMessagesSent, 804 pcePcepSessionP2pPCReqMessagesReceived, 805 pcePcepSessionP2pPCRepMessagesReceived 807 7. IANA Considerations 809 TBD 811 8. Security Considerations 813 The readable objects in the PCE-PCEP-P2MP-DRAFT-MIB module (i.e., 814 those with MAX-ACCESS other than not-accessible) may be considered 815 sensitive in some environments since, collectively, they provide 816 information about the amount and frequency of path computation 817 requests and responses within the network and can reveal some aspects 818 of their configuration. 820 In such environments it is important to control also GET and NOTIFY 821 access to these objects and possibly even to encrypt their values 822 when sending them over the network via SNMP. 824 SNMP versions prior to SNMPv3 did not include adequate security. 825 Even if the network itself is secure (for example by using IPsec), 826 even then, there is no control as to who on the secure network is 827 allowed to access and GET/SET (read/change/create/delete) the objects 828 in this MIB module. 830 It is RECOMMENDED that implementers consider the security features as 831 provided by the SNMPv3 framework (see [RFC3410], section 8), 832 including full support for the SNMPv3 cryptographic mechanisms (for 833 authentication and privacy). 835 Further, deployment of SNMP versions prior to SNMPv3 is NOT 836 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 837 enable cryptographic security. It is then a customer/operator 838 responsibility to ensure that the SNMP entity giving access to an 839 instance of this MIB module is properly configured to give access to 840 the objects only to those principals (users) that have legitimate 841 rights to indeed GET or SET (change/create/delete) them. 843 9. References 845 9.1. Normative References 847 [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. 848 Schoenwaelder, Ed., "Structure of Management 849 Information Version 2 (SMIv2)", STD 58, 850 RFC 2578, April 1999. 852 [RFC2580] McCloghrie, K., Perkins, D., and J. 853 Schoenwaelder, "Conformance Statements for 854 SMIv2", STD 58, RFC 2580, April 1999. 856 [RFC2863] McCloghrie, K. and F. Kastenholz, "The 857 Interfaces Group MIB", RFC 2863, June 2000. 859 [RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An 860 Architecture for Describing Simple Network 861 Management Protocol (SNMP) Management 862 Frameworks", STD 62, RFC 3411, December 2002. 864 [RFC3813] Srinivasan, C., Viswanathan, A., and T. Nadeau, 865 "Multiprotocol Label Switching (MPLS) Label 866 Switching Router (LSR) Management Information 867 Base (MIB)", RFC 3813, June 2004. 869 [RFC5440] Vasseur, JP. and JL. Le Roux, "Path Computation 870 Element (PCE) Communication Protocol (PCEP)", 871 RFC 5440, March 2009. 873 9.2. Informative References 875 [RFC3410] Case, J., Mundy, R., Partain, D., and B. 876 Stewart, "Introduction and Applicability 877 Statements for Internet-Standard Management 878 Framework", RFC 3410, December 2002. 880 [RFC4655] Farrel, A., Vasseur, J., and J. Ash, "A Path 881 Computation Element (PCE)-Based Architecture", 882 RFC 4655, August 2006. 884 [RFC5520] Bradford, R., Vasseur, JP., and A. Farrel, 885 "Preserving Topology Confidentiality in Inter- 886 Domain Path Computation Using a Path-Key-Based 887 Mechanism", RFC 5520, April 2009. 889 [RFC6006] Zhao, Q., King, D., Verhaeghe, F., Takeda, T., 890 Ali, Z., and J. Meuric, "Extensions to the Path 891 Computation Element Communication Protocol 892 (PCEP) for Point-to-Multipoint Traffic 893 Engineering Label Switched Paths", RFC 6006, 894 September 2010. 896 [PCE-PCEP-DRAFT-MIB] Kiran Koushik, A S., Stephan, E., Zhao, Q., 897 King, D., and J. Hardwick, "PCE communication 898 protocol(PCEP) Management Information Base 899 (draft-ietf-pce-pcep-mib-03)", July 2012. 901 Authors' Addresses 903 Quintin Zhao 904 Huawei Technology 905 125 Nagog Technology Park 906 Acton, MA 01719 907 US 909 EMail: quintin.zhao@huawei.com 911 Dhruv Dhody 912 Huawei Technology 913 Leela Palace 914 Bangalore, Karnataka 560008 915 INDIA 917 EMail: dhruv.dhody@huawei.com 918 Udayasree Palle 919 Huawei Technology 920 Leela Palace 921 Bangalore, Karnataka 560008 922 INDIA 924 EMail: udayasree.palle@huawei.com 926 Daniel King 927 Old Dog Consulting 928 UK 930 EMail: daniel@olddog.co.uk