idnits 2.17.1 draft-kkoushik-pce-pcep-mib-02.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** It looks like you're using RFC 3978 boilerplate. You should update this to the boilerplate described in the IETF Trust License Policy document (see https://trustee.ietf.org/license-info), which is required now. -- Found old boilerplate from RFC 3978, Section 5.1 on line 15. -- Found old boilerplate from RFC 3978, Section 5.5, updated by RFC 4748 on line 1037. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 1048. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 1057. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 1063. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust Copyright Line does not match the current year -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (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) == Missing Reference: 'RFC2119' is mentioned on line 80, but not defined == Missing Reference: 'BCP14' is mentioned on line 87, but not defined == Missing Reference: 'RFC3411' is mentioned on line 154, but not defined == Missing Reference: 'RFC2863' is mentioned on line 155, but not defined == Missing Reference: 'RFC4001' is mentioned on line 155, but not defined == Missing Reference: 'RFC4265' is mentioned on line 155, but not defined == Missing Reference: 'RFC3813' is mentioned on line 155, but not defined == Unused Reference: 'PCEP' is defined on line 980, but no explicit reference was found in the text -- Possible downref: Non-RFC (?) normative reference: ref. 'PCEP' Summary: 1 error (**), 0 flaws (~~), 10 warnings (==), 8 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Internet Draft A S Kiran Koushik 2 Expires: May 2009 Cisco Systems, Inc. 3 E. Stephan 4 France Telecom 6 PCE communication protocol(PCEP) Management Information Base 8 draft-kkoushik-pce-pcep-mib-02.txt 10 Status of This Memo 12 By submitting this Internet-Draft, each author represents that any 13 applicable patent or other IPR claims of which he or she is aware 14 have been or will be disclosed, and any of which he or she becomes 15 aware will be disclosed, in accordance with Section 6 of BCP 79. 17 Internet-Drafts are working documents of the Internet Engineering 18 Task Force (IETF), its areas, and its working groups. Note that 19 other groups may also distribute working documents as Internet- 20 Drafts. 22 Internet-Drafts are draft documents valid for a maximum of six months 23 and may be updated, replaced, or obsoleted by other documents at any 24 time. It is inappropriate to use Internet-Drafts as reference 25 material or to cite them other than as "work in progress." 27 The list of current Internet-Drafts can be accessed at 28 http://www.ietf.org/1id-abstracts.html 30 The list of Internet-Draft Shadow Directories can be accessed at 31 http://www.ietf.org/shadow.html 33 Copyright Notice 35 Copyright (C) The IETF Trust (2008). 37 Abstract 39 This memo defines an experimental portion of the Management 40 Information Base for use with network management protocols in the 41 Internet community. In particular, it describes managed objects 42 for modeling of Path Computation Element communication 43 Protocol (PCEP) for communications between a Path Computation Client 44 (PCC) and a Path Computation Element (PCE), or between two PCEs. 46 draft-kkoushik-pce-pcep-mib-02 PCE-PCEP-MIB Nov 3, 2008 48 Table of Contents 50 Abstract............................................................1 51 1 Introduction...................................................2 52 2 Terminology....................................................2 53 3 The Internet-Standard Management Framework.....................3 54 4 PCEP MIB modules Architecture..................................3 55 4.1 Relations to other MIB modules.................................3 56 5 Example of the PCEP MIB modules usage .........................3 57 6 Object definitions.............................................4 58 6.1 PCE-PCEP-DRAFT-MIB.............................................4 59 7 Security considerations.......................................20 60 8 IANA Considerations...........................................20 61 9 References....................................................20 62 9.1 Normative References..........................................20 63 9.2 Informative References........................................20 64 10 Acknowledgement ..............................................21 65 11 Author's Addresses............................................21 67 1 Introduction 69 This memo defines a portion of the Management Information Base 70 (MIB) for use with network management protocols in the Internet 71 community. In particular, it defines a MIB module that can be 72 used to manage Path Computation Element communication 73 Protocol (PCEP) for communications between a Path Computation Client 74 (PCC) and a Path Computation Element (PCE), or between two PCEs. 76 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL 77 NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and 78 "OPTIONAL" in this document are to be interpreted as described in 79 [RFC2119]. 81 Conventions used in this document 83 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL 84 NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and 85 "OPTIONAL" in this document are to be interpreted as described in 86 RFC-2119 [BCP14]. 88 2 Terminology 90 The terminology used in this document is built on notions introduced 91 and discussed in PCE WG documents. The reader should be familiar 92 with these documents 94 Domain: 95 any collection of network elements within a common sphere of 96 address management or path computational responsibility. 98 draft-kkoushik-pce-pcep-mib-02 PCE-PCEP-MIB Nov 3, 2008 100 IGP Area: 101 OSPF Area or ISIS level. 103 PCC: 104 Path Computation Client: any client application requesting a path 105 computation to be performed by a Path Computation Element. 107 PCE: 108 Path Computation Element: an entity (component, application, or 109 network node) that is capable of computing a network path or route 110 based on a network graph, and applying computational 111 constraints. 113 PCEP Client: 114 A PCEP client represents a PCE or a PCC for network management 115 purposes. 117 3 The Internet-Standard Management Framework 119 For a detailed overview of the documents that describe the current 120 Internet-Standard Management Framework, please refer to section 7 121 of RFC 3410 [RFC3410]. 123 Managed objects are accessed via a virtual information store, 124 termed the Management Information Base or MIB. MIB objects are 125 generally accessed through the Simple Network Management Protocol 126 (SNMP). Objects in the MIB are defined using the mechanisms 127 defined in the Structure of Management Information (SMI). This 128 memo specifies a MIB module that is compliant to the SMIv2, which 129 is described in STD 58,RFC 2578 [RFC2578], STD 58, RFC 2579 130 [RFC2579] and STD 58, RFC 2580 [RFC2580]. 132 4. PCEP MIB Module Architecture 134 The PCEP MIB will contain the following information: 135 a. PCEP client configuration and status. 136 b. PCEP peer configuration and information. 137 c. PCEP session configuration and information. 138 d. Notifications to indicate PCEP session changes. 140 4.1. Relations to other MIB modules 142 TBD 144 5 Example of the PCEP MIB module usage 145 draft-kkoushik-pce-pcep-mib-02 PCE-PCEP-MIB Nov 3, 2008 147 TBD 149 6 Object definitions 151 6.1 PCE-PCEP-DRAFT-MIB 153 This MIB module makes references to the following documents. 154 [RFC2578], [RFC2579], [RFC2580], [RFC3411], 155 [RFC2863], [RFC4001], [RFC4265] and [RFC3813]. 157 PCE-PCEP-DRAFT-MIB DEFINITIONS ::= BEGIN 159 IMPORTS 160 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, 161 Counter32, Unsigned32, Gauge32, Integer32, IpAddress, 162 experimental 163 FROM SNMPv2-SMI 165 RowStatus, TimeInterval, TruthValue, 166 TimeStamp, StorageType,TEXTUAL-CONVENTION 167 FROM SNMPv2-TC -- [RFC2579] 169 InetAddressPrefixLength, 170 InetAddressType, 171 InetAddress, 172 InetPortNumber 173 FROM INET-ADDRESS-MIB 175 MODULE-COMPLIANCE, 176 OBJECT-GROUP, 177 NOTIFICATION-GROUP 178 FROM SNMPv2-CONF; 180 pcePcepDraftMIB MODULE-IDENTITY 181 LAST-UPDATED "200811030000Z" --Nov 3, 2008 182 ORGANIZATION "Path Computation Element (PCE) Working Group" 183 CONTACT-INFO " 184 A S Kiran Koushik 185 Cisco Systems Inc. 186 Stephan Emile 187 France Telecom DR&D 188 Email: kkoushik@cisco.com 189 Email: emile.stephan@orange-ft.com 190 Email comments directly to the PCE WG Mailing List at pce@ietf.org 191 WG-URL: http://www.ietf.org/html.charters/pce-charter.html 192 " 194 DESCRIPTION 195 draft-kkoushik-pce-pcep-mib-02 PCE-PCEP-MIB Nov 3, 2008 197 "This MIB module defines a collection of objects for managing 198 PCE communication protocol(PCEP)." 200 -- Revision history 202 REVISION 203 "200811031200Z" -- Nov 03 2008 12:00:00 EST 204 DESCRIPTION 205 "Changes from -01- draft include support for the following 206 in the MIB : 207 o The SyncTimer, 208 o The maximum number of sessions that can be setup, 209 o Request timer: amount of time a PCC waits for a reply 210 before resending its path computation requests 211 (potentially to an alternate PCE). 212 o The MAX-UNKNOWN-REQUESTS 213 o The MAX-UNKNOWN-MESSAGES 214 o Response time (minimum, average and maximum), on a 215 per PCE Peer basis, 216 o PCEP Session failures, 217 o Amount of time the session has been in active state, 218 o Number of corrupted messages, 219 o Number of failed computations, 221 Changes from -00- draft : 222 1. Clarified the notion of PCEP Client. 223 2. Added new objects to the PCEP client and session tables 224 to manage PCEP protocol as in section 8 of 225 draft-ietf-pce-pcep-08.txt 226 3. Did not add all the objects to manage the recommendations 227 in draft-ietf-pce-pcep-08.txt to control the complexity of 228 the MIB." 230 REVISION 231 "200702201200Z" -- 20 Feb 2007 12:00:00 EST 232 DESCRIPTION 233 "draft-00 version" 234 ::= { experimental 9999 } -- 236 -- Textual Conventions used in this MIB module -- 237 PcePcepIdentifier ::= TEXTUAL-CONVENTION 238 DISPLAY-HINT "1d.1d.1d.1d:1d:1d" 239 STATUS current 240 DESCRIPTION 241 "The LDP identifier is a six octet 242 quantity which is used to identify a 243 PCE client." 245 draft-kkoushik-pce-pcep-mib-02 PCE-PCEP-MIB Nov 3, 2008 247 SYNTAX OCTET STRING (SIZE (6)) 249 -- Notifications -- 251 pcePcepNotifications OBJECT IDENTIFIER ::= { pcePcepDraftMIB 0 } 253 pcePcepMIBObjects OBJECT IDENTIFIER ::= { pcePcepDraftMIB 1 } 254 pcePcepConformance OBJECT IDENTIFIER ::= { pcePcepDraftMIB 2 } 256 pcePcepClientObjects OBJECT IDENTIFIER ::= { pcePcepMIBObjects 1 } 258 -- 259 -- PCE Client Objects 260 -- 262 pcePcepClientLastChange OBJECT-TYPE 263 SYNTAX TimeStamp 264 MAX-ACCESS read-only 265 STATUS current 266 DESCRIPTION 267 "The value of sysUpTime at the time of the most 268 recent addition or deletion of an entry 269 to/from the pcePcepClientTable/pcePcepClientStatsTable, or 270 the most recent change in value of any objects in the 271 pcePcepClientTable. 273 If no such changes have occurred since the last 274 re-initialization of the local management subsystem, 275 then this object contains a zero value." 276 ::= { pcePcepClientObjects 1 } 278 pcePcepClientIndexNext OBJECT-TYPE 279 SYNTAX Unsigned32 280 MAX-ACCESS read-only 281 STATUS current 282 DESCRIPTION 283 "This object contains an appropriate value to 284 be used for pcePcepClientIndex when creating 285 entries in the pcePcepClientTable. The value 286 0 indicates that no unassigned entries are 287 available." 288 ::= { pcePcepClientObjects 2 } 290 pcePcepClientTable OBJECT-TYPE 291 SYNTAX SEQUENCE OF PcePcepClientEntry 292 MAX-ACCESS not-accessible 293 STATUS current 294 DESCRIPTION 296 draft-kkoushik-pce-pcep-mib-02 PCE-PCEP-MIB Nov 3, 2008 298 "This table contains information about the 299 PCEP Client." 300 ::= { pcePcepClientObjects 3 } 302 pcePcepClientEntry OBJECT-TYPE 303 SYNTAX PcePcepClientEntry 304 MAX-ACCESS not-accessible 305 STATUS current 306 DESCRIPTION 307 "An entry in this table represents a PCEP client. 308 An entry can be created by a network administrator 309 or by an SNMP agent as instructed by PCEP." 310 INDEX { pcePcepClientPcepId, pcePcepClientIndex } 311 ::= { pcePcepClientTable 1 } 313 PcePcepClientEntry ::= SEQUENCE { 314 pcePcepClientPcepId PcePcepIdentifier, 315 pcePcepClientIndex Unsigned32, 316 pcePcepClientAdminStatus INTEGER, 317 pcePcepClientOperStatus INTEGER, 318 pcePcepClientTcpPort InetPortNumber, 319 pcePcepClientKeepAliveTimer Unsigned32, 320 pcePcepClientStorageType StorageType, 321 pcePcepClientRowStatus RowStatus, 322 pcePcepClientDeadTimer Unsigned32 323 } 325 pcePcepClientPcepId OBJECT-TYPE 326 SYNTAX PcePcepIdentifier 327 MAX-ACCESS not-accessible 328 STATUS current 329 DESCRIPTION 330 "The PCEP client identifier." 331 ::= { pcePcepClientEntry 1 } 333 pcePcepClientIndex OBJECT-TYPE 334 SYNTAX Unsigned32 335 MAX-ACCESS not-accessible 336 STATUS current 337 DESCRIPTION 338 "This index is used to uniquely identify the PCEP client. 339 Before creating a row in this table, 340 the 'pcePcepClientIndexNext' object should be retrieved. 341 That value should be used for the value of this index 342 when creating a row in this table. NOTE: if a value 343 of zero (0) is retrieved, that indicates that no rows 344 can be created in this table at this time." 346 draft-kkoushik-pce-pcep-mib-02 PCE-PCEP-MIB Nov 3, 2008 348 ::= { pcePcepClientEntry 2 } 350 pcePcepClientAdminStatus OBJECT-TYPE 351 SYNTAX INTEGER { 352 enable(1), 353 disable(2) 354 } 355 MAX-ACCESS read-create 356 STATUS current 357 DESCRIPTION 358 "The administrative status of this PCEP Client. 359 If this object is changed from 'enable' to 'disable' 360 and this entity has already attempted to establish 361 contact with a Peer, then all contact with that 362 Peer is lost and all information from that Peer 363 needs to be removed from the MIB. (This implies 364 that the network management subsystem should clean 365 up any related entry in the pcePcepPeerTable. This 366 further implies that a 'tear-down' for that session 367 is issued and the session and all information related 368 to that session cease to exist). 370 At this point the operator is able to change values 371 which are related to this entity. 373 When the admin status is set back to 'enable', then 374 this Entity will attempt to establish a new session 375 with the Peer." 377 DEFVAL { enable } 378 ::= { pcePcepClientEntry 4 } 380 pcePcepClientOperStatus OBJECT-TYPE 381 SYNTAX INTEGER { 382 unknown(1), 383 enabled(2), 384 disabled(3) 385 } 386 MAX-ACCESS read-only 387 STATUS current 388 DESCRIPTION 389 "The operational status of this PCEP client. 391 The value of unknown(1) indicates that the 392 operational status cannot be determined at 393 this time. The value of unknown should be 394 a transient condition before changing 395 to enabled(2) or disabled(3)." 397 draft-kkoushik-pce-pcep-mib-02 PCE-PCEP-MIB Nov 3, 2008 399 ::= { pcePcepClientEntry 5 } 401 pcePcepClientTcpPort OBJECT-TYPE 402 SYNTAX InetPortNumber 403 MAX-ACCESS read-create 404 STATUS current 405 DESCRIPTION 406 "The TCP Port for 407 PCEP. The default value is the well-known 408 value of this port." -- To be assigned by IANA 409 ::= { pcePcepClientEntry 6 } 411 pcePcepClientKeepAliveTimer OBJECT-TYPE 412 SYNTAX Unsigned32 (1..65535) 413 UNITS "seconds" 414 MAX-ACCESS read-create 415 STATUS current 416 DESCRIPTION 417 "The integer value which is the proposed keep 418 alive timer for this PCEP client." 419 ::= { pcePcepClientEntry 7 } 421 pcePcepClientStorageType OBJECT-TYPE 422 SYNTAX StorageType 423 MAX-ACCESS read-create 424 STATUS current 426 DESCRIPTION 427 "The storage type for this conceptual row. 428 Conceptual rows having the value 'permanent(4)' 429 need not allow write-access to any columnar 430 objects in the row." 431 DEFVAL{ nonVolatile } 432 ::= { pcePcepClientEntry 8 } 434 pcePcepClientRowStatus OBJECT-TYPE 435 SYNTAX RowStatus 436 MAX-ACCESS read-create 437 STATUS current 438 DESCRIPTION 439 "The status of this conceptual row. All writable 440 objects in this row may be modified at any 441 time, however, as described in detail in 442 the section entitled, 'Changing Values After 443 Session Establishment', and again described 444 in the DESCRIPTION clause of the 445 pcePcepClientAdminStatus object, if a session 446 has been initiated with a Peer, changing objects 448 draft-kkoushik-pce-pcep-mib-02 PCE-PCEP-MIB Nov 3, 2008 450 in this table will wreak havoc with the session 451 and interrupt traffic. To repeat again: 452 the recommended procedure is to 453 set the pcePcepClientAdminStatus to down, thereby 454 explicitly causing a session to be torn down. Then, 455 change objects in this entry, then set 456 the pcePcepClientAdminStatus to enable, 457 which enables a new session to be initiated." 458 ::= { pcePcepClientEntry 9 } 460 pcePcepClientDeadTimer OBJECT-TYPE 461 SYNTAX Unsigned32 (4..262140) 462 UNITS "seconds" 463 MAX-ACCESS read-create 464 STATUS current 465 DESCRIPTION 466 "The value which indicates a period of 467 time after the expiration of which a PCEP peer 468 declares the session down if no PCEP message 469 has been received. The Deadtimer value is recommended to 470 be 4 times the Keepalive value." 471 ::= { pcePcepClientEntry 10 } 473 -- 474 -- The PCEP Client Statistics Table 475 -- TBD 476 -- 478 -- 479 -- The PCEP Peer Table 480 -- 482 pcePcepSessionObjects OBJECT IDENTIFIER ::= { pcePcepMIBObjects 3 } 484 pcePcepPeerLastChange OBJECT-TYPE 485 SYNTAX TimeStamp 486 MAX-ACCESS read-only 487 STATUS current 488 DESCRIPTION 489 "The value of sysUpTime at the time of the most 490 recent addition or deletion to/from the 491 pcePcepPeerTable/pcePcepSessionTable." 492 ::= { pcePcepSessionObjects 1 } 494 pcePcepPeerTable OBJECT-TYPE 495 SYNTAX SEQUENCE OF PcePcepPeerEntry 496 MAX-ACCESS not-accessible 497 STATUS current 499 draft-kkoushik-pce-pcep-mib-02 PCE-PCEP-MIB Nov 3, 2008 501 DESCRIPTION 502 "Information about PCEP peers known by Entities in 503 the pcePcepClientTable. The information in this table 504 is based on information from the Client-Peer interaction 505 during session initialization but is not appropriate 506 for the pcePcepSessionTable, because objects in this 507 table may or may not be used in session establishment." 508 ::= { pcePcepSessionObjects 2 } 510 pcePcepPeerEntry OBJECT-TYPE 511 SYNTAX PcePcepPeerEntry 512 MAX-ACCESS not-accessible 513 STATUS current 514 DESCRIPTION 515 "Information about a single Peer which is related 516 to a Session. This table is augmented by 517 the pcePcepSessionTable." 518 INDEX { pcePcepClientPcepId, 519 pcePcepClientIndex, 520 pcePcepPeerPcepId } 521 ::= { pcePcepPeerTable 1 } 523 PcePcepPeerEntry ::= SEQUENCE { 524 pcePcepPeerPcepId PcePcepIdentifier, 525 pcePcepPeerTransportAddrType InetAddressType, 526 pcePcepPeerTransportAddr InetAddress 527 } 529 pcePcepPeerPcepId OBJECT-TYPE 530 SYNTAX PcePcepIdentifier 531 MAX-ACCESS not-accessible 532 STATUS current 533 DESCRIPTION 534 "The PCEP identifier of this PCE Peer." 535 ::= { pcePcepPeerEntry 1 } 537 pcePcepPeerTransportAddrType OBJECT-TYPE 538 SYNTAX InetAddressType 539 MAX-ACCESS read-only 540 STATUS current 541 DESCRIPTION 542 "The type of the Internet address for the 543 pcePcepPeerTransportAddr object. The PCEP 544 specification describes this as being either 545 an IPv4 Transport Address or IPv6 Transport 547 This object specifies how the value of the 548 pcePcepPeerTransportAddr object should be 550 draft-kkoushik-pce-pcep-mib-02 PCE-PCEP-MIB Nov 3, 2008 552 interpreted." 553 ::= { pcePcepPeerEntry 2 } 555 pcePcepPeerTransportAddr OBJECT-TYPE 556 SYNTAX InetAddress 557 MAX-ACCESS read-only 558 STATUS current 559 DESCRIPTION 560 "The Internet address advertised by the peer. 562 The type of this address is specified by the 563 value of the pcePcepPeerTransportAddrType 564 object." 565 ::= { pcePcepPeerEntry 3 } 567 pcePcepPeerResponseTime OBJECT-TYPE 568 SYNTAX Unsigned32 (1..65535) 569 UNITS "seconds" 570 MAX-ACCESS read-only 571 STATUS current 572 DESCRIPTION 573 "The Average response time for this PCEP peer." 574 ::= { pcePcepPeerEntry 4 } 576 -- 577 -- The PCEP Sessions Table 578 -- 580 pcePcepSessionMax OBJECT-TYPE 581 SYNTAX Unsigned32 582 MAX-ACCESS read-only 583 STATUS current 584 DESCRIPTION 585 "The maximum number of sessions that can be setup 586 on this PCEP client." 587 ::= { pcePcepSessionObjects 3 } 589 pcePcepSessionMaxUnknownRequests OBJECT-TYPE 590 SYNTAX Unsigned32 591 MAX-ACCESS read-only 592 STATUS current 593 DESCRIPTION 594 "The maximum number of unknown requests that any session 595 on this PCEP client is willing to accept." 596 ::= { pcePcepSessionObjects 4 } 598 pcePcepSessionMaxUnknownMsgs OBJECT-TYPE 599 draft-kkoushik-pce-pcep-mib-02 PCE-PCEP-MIB Nov 3, 2008 601 SYNTAX Unsigned32 602 MAX-ACCESS read-only 603 STATUS current 604 DESCRIPTION 605 "The maximum number of unknown messages that any session 606 on this PCEP client is willing to accept." 607 ::= { pcePcepSessionObjects 5 } 609 pcePcepSessionFailures OBJECT-TYPE 610 SYNTAX Unsigned32 611 MAX-ACCESS read-only 612 STATUS current 613 DESCRIPTION 614 "The number of failed sessions on this client." 615 ::= { pcePcepSessionObjects 6 } 617 pcePcepSessionTable OBJECT-TYPE 618 SYNTAX SEQUENCE OF PcePcepSessionEntry 619 MAX-ACCESS not-accessible 620 STATUS current 621 DESCRIPTION 622 "A table of Sessions between PCEP clients. 623 This table AUGMENTS the pcePcepPeerTable. 624 Each row in this table represents a single session." 625 ::= { pcePcepSessionObjects 7 } 627 pcePcepSessionEntry OBJECT-TYPE 628 SYNTAX PcePcepSessionEntry 629 MAX-ACCESS not-accessible 630 STATUS current 631 DESCRIPTION 632 "An entry in this table represents information on a 633 single session between two PCEP clients. 634 The information contained in a row is read-only." 636 AUGMENTS { pcePcepPeerEntry } 637 ::= { pcePcepSessionTable 1 } 639 PcePcepSessionEntry ::= SEQUENCE { 640 pcePcepSessionStateLastChange TimeStamp, 641 pcePcepSessionState INTEGER, 642 pcePcepSessionKeepAliveHoldTimeRem TimeInterval, 643 pcePcepSessionKeepAliveTime Unsigned32, 644 pcePcepSessionDiscontinuityTime TimeStamp, 645 pcePcepSessionSpeakerRole INTEGER, 646 pcePcepSessionSyncTime Unsigned32, 647 pcePcepSessionActiveTime Unsigned32, 648 pcePcepSessionCorruptedMsgs Unsigned32, 650 draft-kkoushik-pce-pcep-mib-02 PCE-PCEP-MIB Nov 3, 2008 652 pcePcepSessionFailedComps Unsigned32 653 } 655 pcePcepSessionStateLastChange OBJECT-TYPE 656 SYNTAX TimeStamp 657 MAX-ACCESS read-only 658 STATUS current 659 DESCRIPTION 660 "The value of sysUpTime at the time this 661 Session entered its current state as 662 denoted by the pcePcepSessionState 663 object." 664 ::= { pcePcepSessionEntry 1 } 666 pcePcepSessionState OBJECT-TYPE 667 SYNTAX INTEGER { 668 sessionUp(1), 669 keepWait(2), 670 openWait(3), 671 tcpPending(4), 672 idle(5) 673 } 674 MAX-ACCESS read-only 675 STATUS current 676 DESCRIPTION 677 "The current state of the session, all of the 678 states 1 to 5 are based on the state machine 679 for session negotiation behavior." 680 ::= { pcePcepSessionEntry 2 } 682 pcePcepSessionKeepAliveHoldTimeRem OBJECT-TYPE 683 SYNTAX TimeInterval 684 MAX-ACCESS read-only 685 STATUS current 686 DESCRIPTION 687 "The keep alive hold time remaining for 688 this session." 689 ::= { pcePcepSessionEntry 3 } 691 pcePcepSessionKeepAliveTime OBJECT-TYPE 692 SYNTAX Unsigned32 (1..65535) 693 UNITS "seconds" 694 MAX-ACCESS read-only 695 STATUS current 696 DESCRIPTION 697 "The negotiated KeepAlive Time which 698 represents the amount of seconds between 699 keep alive messages. The 701 draft-kkoushik-pce-pcep-mib-02 PCE-PCEP-MIB Nov 3, 2008 703 pcePcepClientKeepAliveHoldTimer 704 related to this Session is the 705 value that was proposed as the 706 KeepAlive Time for this session 708 This value is negotiated during 709 session initialization between 710 the entity's proposed value 711 (i.e., the value configured in 712 pcePcepClientKeepAliveHoldTimer) 713 and the peer's proposed 714 KeepAlive Hold Timer value. 715 This value is the smaller 716 of the two proposed values." 717 ::= { pcePcepSessionEntry 4 } 719 pcePcepSessionDiscontinuityTime OBJECT-TYPE 720 SYNTAX TimeStamp 721 MAX-ACCESS read-only 722 STATUS current 723 DESCRIPTION 724 "The value of sysUpTime on the most recent occasion 725 at which any one or more of this session's counters 726 suffered a discontinuity. The relevant counters are 727 the specific instances associated with this session 728 of any Counter32 object contained in the 729 pcePcepSessionStatsTable. 731 The initial value of this object is the value of 732 sysUpTime when the entry was created in this table. 734 Also, a command generator can distinguish when a session 735 between a given Entity and Peer goes away and a new 736 session is established. This value would change and 737 thus indicate to the command generator that this is a 738 different session." 739 ::= { pcePcepSessionEntry 5 } 741 pcePcepSessionSpeakerRole OBJECT-TYPE 742 SYNTAX INTEGER { 743 pcc(1), 744 pce(2), 745 pccandpce(3) 746 } 747 MAX-ACCESS read-only 748 STATUS current 749 DESCRIPTION 750 "The value of this object indicates the PCEP 752 draft-kkoushik-pce-pcep-mib-02 PCE-PCEP-MIB Nov 3, 2008 754 speaker role in this session." 755 ::= { pcePcepSessionEntry 6 } 757 pcePcepSessionSyncTime OBJECT-TYPE 758 SYNTAX Unsigned32 (1..65535) 759 UNITS "seconds" 760 MAX-ACCESS read-only 761 STATUS current 762 DESCRIPTION 763 "The value of SYNC timer is used in the case 764 of synchronized path computation request using 765 the SVEC object. 767 Consider the case where a PCReq message is received 768 by a PCE that contains the SVEC object referring to 769 M synchronized path computation requests. If after 770 the expiration of the SYNC timer all the M path 771 computation requests have not been received, 772 a protocol error is triggered and the PCE MUST cancel 773 the whole set of path computation requests. 775 The aim of the SyncTimer is to avoid the storage 776 of unused synchronized request should one of them get 777 lost for some reasons (e.g a misbehaving PCC)." 779 DEFVAL { 60 } 780 ::= { pcePcepSessionEntry 7 } 782 pcePcepSessionRequestTime OBJECT-TYPE 783 SYNTAX Unsigned32 (1..65535) 784 UNITS "seconds" 785 MAX-ACCESS read-only 786 STATUS current 787 DESCRIPTION 788 "The maximum amount of time a PCC waits for a 789 reply before resending its path computation requests 790 (potentially to an alternate PCE)." 791 ::= { pcePcepSessionEntry 8 } 793 pcePcepSessionActiveTime OBJECT-TYPE 794 SYNTAX Unsigned32 (1..65535) 795 UNITS "seconds" 796 MAX-ACCESS read-only 797 STATUS current 798 DESCRIPTION 799 "The amount of time this session has been active 800 since creation or a discontinuity." 801 ::= { pcePcepSessionEntry 9 } 803 draft-kkoushik-pce-pcep-mib-02 PCE-PCEP-MIB Nov 3, 2008 805 pcePcepSessionCorruptedMsgs OBJECT-TYPE 806 SYNTAX Unsigned32 807 MAX-ACCESS read-only 808 STATUS current 809 DESCRIPTION 810 "The number of corrupted messages received on this 811 session." 812 ::= { pcePcepSessionEntry 10 } 814 pcePcepSessionCorruptedMsgs OBJECT-TYPE 815 SYNTAX Unsigned32 816 MAX-ACCESS read-only 817 STATUS current 818 DESCRIPTION 819 "The number of requests which had failed 820 computations." 821 ::= { pcePcepSessionEntry 11 } 823 --- 824 --- Notifications 825 --- 827 pcePcepSessionUp NOTIFICATION-TYPE 828 OBJECTS { 829 pcePcepSessionState, 830 pcePcepSessionDiscontinuityTime 831 } 832 STATUS current 833 DESCRIPTION 834 "This notification is sent when the 835 value of 'pcePcepSessionState' enters 836 the 'sessionUp(1)' state." 837 ::= { pcePcepNotifications 1 } 839 pcePcepSessionDown NOTIFICATION-TYPE 840 OBJECTS { 841 pcePcepSessionState, 842 pcePcepSessionDiscontinuityTime 844 } 845 STATUS current 846 DESCRIPTION 847 "This notification is sent when the 848 value of 'pcePcepSessionState' leaves 849 the 'sessionUp(1)' state." 850 ::= { pcePcepNotifications 2 } 852 draft-kkoushik-pce-pcep-mib-02 PCE-PCEP-MIB Nov 3, 2008 854 --**************************************************************** 855 -- Module Conformance Statement 856 --**************************************************************** 858 pcePcepGroups 859 OBJECT IDENTIFIER ::= { pcePcepConformance 1 } 861 pcePcepCompliances 862 OBJECT IDENTIFIER ::= { pcePcepConformance 2 } 864 -- 865 -- Full Compliance 866 -- 868 pcePcepModuleFullCompliance MODULE-COMPLIANCE 869 STATUS current 870 DESCRIPTION 871 "The Module is implemented with support 872 for read-create and read-write. In other 874 words, both monitoring and configuration 875 are available when using this MODULE-COMPLIANCE." 877 MODULE -- this module 878 MANDATORY-GROUPS { pcePcepGeneralGroup, 879 pcePcepNotificationsGroup 880 } 882 ::= { pcePcepCompliances 1 } 884 -- 885 -- Read-Only Compliance 886 -- 888 pcePcepModuleReadOnlyCompliance MODULE-COMPLIANCE 889 STATUS current 890 DESCRIPTION 891 "The Module is implemented with support 892 for read-only. In other words, only monitoring 893 is available by implementing this MODULE-COMPLIANCE." 895 MODULE -- this module 896 MANDATORY-GROUPS { pcePcepGeneralGroup, 897 pcePcepNotificationsGroup 898 } 900 ::= { pcePcepCompliances 2 } 902 draft-kkoushik-pce-pcep-mib-02 PCE-PCEP-MIB Nov 3, 2008 904 -- units of conformance 906 pcePcepGeneralGroup OBJECT-GROUP 907 OBJECTS { 908 pcePcepClientLastChange, 909 pcePcepClientIndexNext, 910 pcePcepClientAdminStatus, 911 pcePcepClientOperStatus, 912 pcePcepClientTcpPort, 913 pcePcepClientKeepAliveTimer, 914 pcePcepClientStorageType, 915 pcePcepClientRowStatus, 916 pcePcepPeerLastChange, 917 pcePcepPeerTransportAddrType, 918 pcePcepPeerTransportAddr, 919 pcePcepSessionStateLastChange, 920 pcePcepSessionState, 921 pcePcepSessionKeepAliveHoldTimeRem, 922 pcePcepSessionKeepAliveTime, 923 pcePcepSessionDiscontinuityTime, 924 pcePcepClientDeadTimer, 925 pcePcepSessionMax, 926 pcePcepSessionSpeakerRole, 927 pcePcepClientSyncTime, 928 pcePcepClientRequestTime, 929 pcePcepSessionMaxUnknownRequests, 930 pcePcepSessionMaxUnknownMsgs, 931 pcePcepSessionSessionFailures, 932 pcePcepSessionActiveTime, 933 pcePcepSessionCorruptedMsgs, 934 pcePcepSessionFailedComps 935 } 936 STATUS current 937 DESCRIPTION 938 "Objects that apply to all PCEP MIB implementations." 940 ::= { pcePcepGroups 1 } 942 pcePcepNotificationsGroup NOTIFICATION-GROUP 943 NOTIFICATIONS { pcePcepSessionUp, 944 pcePcepSessionDown 945 } 946 STATUS current 947 DESCRIPTION 948 "The notifications for a PCEP MIB implementation." 949 ::= { pcePcepGroups 2 } 950 END 951 draft-kkoushik-pce-pcep-mib-02 PCE-PCEP-MIB Nov 3, 2008 953 7. Security Considerations 955 These MIB modules can be used for configuration of certain objects, 956 and anything that can be configured can be incorrectly configured, 957 with potentially disastrous results. 959 There are a number of management objects defined in these MIB modules 960 with a MAX-ACCESS clause of read-write and/or read-create. Such 961 objects may be considered sensitive or vulnerable in some network 962 environments. The support for SET operations in a non-secure 963 environment without proper protection can have a negative effect on 964 network operations. These are the tables and objects and their 965 sensitivity/vulnerability: 966 TBD 968 8. IANA Considerations 970 -- (Note to RFC-Editor:) 971 -- We request that you assign contiguous RFC numbers to the 972 -- IANA is requested to root MIB objects in the MIB module 973 -- contained in this document under the transmission subtree. 974 -- 976 9. References 978 9.1 Normative References 980 [PCEP] Path Computation Element (PCE) communication Protocol 981 (PCEP), 982 JP. Vasseur, JL. Le Roux 984 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 985 J., Rose, M., and S. Waldbusser, "Structure of 986 Management Information Version 2 (SMIv2)", STD 58, RFC 987 2578, April 1999. 989 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 990 J., Rose, M., and S. Waldbusser, "Textual Conventions 991 for SMIv2", STD 58, RFC 2579, April 1999. 993 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 994 J., Rose, M., and S. Waldbusser, "Conformance Statements 995 for SMIv2", STD 58, RFC 2580, April 1999. 997 9.2. Informative References 999 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, 1000 draft-kkoushik-pce-pcep-mib-02 PCE-PCEP-MIB Nov 3, 2008 1002 "Introduction and Applicability Statements for 1003 Internet-Standard Management Framework", RFC 3410, 1004 December 2002. 1006 10. Acknowledgement 1008 The authors would like to thank Santanu Mazumder and Meral 1009 Shirazipour for their valuable input. 1011 11. Authors' Addresses 1013 A S Kiran Koushik 1014 Cisco Systems Inc. 1015 Email: kkoushik@cisco.com 1017 Stephan Emile 1018 France Telecom 1019 2 avenue Pierre Marzin 1020 Lannion, F-22307 1021 Email: emile.stephan@orange-ftgroup.com 1023 Full Copyright Statement 1025 Copyright (C) The IETF Trust (2008). 1027 This document is subject to the rights, licenses and restrictions 1028 contained in BCP 78, and except as set forth therein, the authors 1029 retain all their rights. 1031 This document and the information contained herein are provided on an 1032 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 1033 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND 1034 THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS 1035 OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF 1036 THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 1037 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 1039 Intellectual Property 1041 The IETF takes no position regarding the validity or scope of any 1042 Intellectual Property Rights or other rights that might be claimed to 1043 pertain to the implementation or use of the technology described in 1044 this document or the extent to which any license under such rights 1045 might or might not be available; nor does it represent that it has 1046 made any independent effort to identify any such rights. Information 1047 on the procedures with respect to rights in RFC documents can be 1048 found in BCP 78 and BCP 79. 1050 draft-kkoushik-pce-pcep-mib-02 PCE-PCEP-MIB Nov 3, 2008 1052 Copies of IPR disclosures made to the IETF Secretariat and any 1053 assurances of licenses to be made available, or the result of an 1054 attempt made to obtain a general license or permission for the use of 1055 such proprietary rights by implementers or users of this 1056 specification can be obtained from the IETF on-line IPR repository at 1057 http://www.ietf.org/ipr. 1059 The IETF invites any interested party to bring to its attention any 1060 copyrights, patents or patent applications, or other proprietary 1061 rights that may cover technology that may be required to implement 1062 this standard. Please address the information to the IETF at 1063 ietf-ipr@ietf.org. 1065 This document is a product of the MPLS Working Group. 1066 Funding for the RFC Editor function is provided by the IETF 1067 Administrative Support Activity (IASA).