idnits 2.17.1 draft-pce-mib-extensions-01.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == The document seems to lack the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords -- however, there's a paragraph with a matching beginning. Boilerplate error? (The document does seem to have the reference to RFC 2119 which the ID-Checklist requires). -- The document date (October 7, 2016) is 2758 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) == Outdated reference: A later version (-21) exists of draft-ietf-pce-stateful-pce-16 == Outdated reference: A later version (-11) exists of draft-ietf-pce-pce-initiated-lsp-07 == Outdated reference: A later version (-10) exists of draft-ietf-pce-stateful-sync-optimizations-05 Summary: 0 errors (**), 0 flaws (~~), 5 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet Engineering Task Force V. Ramany 3 Internet-Draft D. Parchuru 4 Intended status: Standards Track D. Kumar 5 Expires: April 10, 2017 Brocade Communications, Inc. 6 October 7, 2016 8 Extensions to the Path Computation Element Protocol(PCEP) Management 9 Information Base(MIB) Module 10 draft-pce-mib-extensions-01 12 Abstract 14 This memo defines a portion of the Management Information Base (MIB) 15 for use with network management protocols in the Internet community. 16 In particular, it describes extensions to the managed objects for 17 modeling of the Path Computation Element Communication Protocol 18 (PCEP) for communications between a Path Computation Client (PCC) and 19 a Path Computation Element (PCE), or between two PCEs, that support 20 stateful capabilities. 22 Status of This Memo 24 This Internet-Draft is submitted in full conformance with the 25 provisions of BCP 78 and BCP 79. 27 Internet-Drafts are working documents of the Internet Engineering 28 Task Force (IETF). Note that other groups may also distribute 29 working documents as Internet-Drafts. The list of current Internet- 30 Drafts is at http://datatracker.ietf.org/drafts/current/. 32 Internet-Drafts are draft documents valid for a maximum of six months 33 and may be updated, replaced, or obsoleted by other documents at any 34 time. It is inappropriate to use Internet-Drafts as reference 35 material or to cite them other than as "work in progress." 37 This Internet-Draft will expire on April 10, 2017. 39 Copyright Notice 41 Copyright (c) 2016 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 46 (http://trustee.ietf.org/license-info) in effect on the date of 47 publication of this document. Please review these documents 48 carefully, as they describe your rights and restrictions with respect 49 to this document. Code Components extracted from this document must 50 include Simplified BSD License text as described in Section 4.e of 51 the Trust Legal Provisions and are provided without warranty as 52 described in the Simplified BSD License. 54 Table of Contents 56 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 57 1.1. Requirements Language . . . . . . . . . . . . . . . . . . 3 58 1.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3 59 2. The Internet-Standard Management Framework . . . . . . . . . 3 60 3. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 4 61 3.1. pcePcepXEntityTable . . . . . . . . . . . . . . . . . . . 4 62 3.2. pcePcepXPeerTable . . . . . . . . . . . . . . . . . . . . 5 63 3.3. pcePcepXSessTable . . . . . . . . . . . . . . . . . . . . 5 64 4. Object Definitions . . . . . . . . . . . . . . . . . . . . . 6 65 4.1. PCE-PCEP-MIB . . . . . . . . . . . . . . . . . . . . . . 6 66 5. Security Considerations . . . . . . . . . . . . . . . . . . . 20 67 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 20 68 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 20 69 7.1. Normative References . . . . . . . . . . . . . . . . . . 20 70 7.2. Informative References . . . . . . . . . . . . . . . . . 22 71 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 22 73 1. Introduction 75 The PCE defined in [RFC4655] is an entity that is capable of 76 computing a network path or route based on a network graph and 77 applying computational constraints. A PCC may make requests to a PCE 78 for paths to be computed. 80 PCEP is the communication protocol between a PCC and PCE and is 81 defined in [RFC5440]. PCEP interactions include path computation 82 requests and path computation replies as well as notifications of 83 specific states related to the use of a PCE in the context of 84 Multiprotocol Label Switching (MPLS) and Generalized MPLS (GMPLS) 85 Traffic Engineering (TE). 87 [RFC7420] defined a MIB module that can be used to monitor PCEP 88 interactions between a PCC and a PCE, or between two PCEs. This memo 89 proposes extensions to the MIB module that can help monitor 90 interactions between PCEP peers that have stateful capabilities as 91 defined in [I-D.ietf-pce-stateful-pce], 92 [I-D.ietf-pce-pce-initiated-lsp] and 93 [I-D.ietf-pce-stateful-sync-optimizations]. 95 The scope of this document is to extend the MIB module for the PCEP 96 base protocol as defined in [RFC7420]. 98 1.1. Requirements Language 100 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 101 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY" and "OPTIONAL" in this 102 document are to be interpreted as described in BCP 14 [RFC2119]. 104 1.2. Terminology 106 This document uses the terminology defined in [RFC4655] and 107 [RFC5440], [draft-ietf-pce-stateful-pce-10], [draft-ietf-pce-pce- 108 initiated-lsp-03] and [draft-ietf-pce-stateful-sync-optimizations- 109 02]. In particular, it uses the following acronyms. 111 o Path Computation Request (PCReq) message. 113 o Path Computation Reply (PCRep) message. 115 o Notification (PCNtf) message. 117 o Error (PCErr) message. 119 o LSP State Report (PCRpt) message. 121 o LSP State Update (PCUpd) message. 123 o LSP Initiate (PCInitiate) message. 125 This document uses the term "PCEP entity" to refer to a local PCEP 126 speaker, "peer" to refer to a remote PCEP speaker, and "PCEP speaker" 127 where it is not necessary to distinguish between local and remote. 129 2. The Internet-Standard Management Framework 131 For a detailed overview of the documents that describe the current 132 Internet-Standard Management Framework, please refer to section 7 of 133 [RFC3410]. 135 Managed objects are accessed via a virtual information store, termed 136 the Management Information Base or MIB. MIB objects are generally 137 accessed through the Simple Network Management Protocol (SNMP). 138 Objects in the MIB are defined using the mechanisms defined in the 139 Structure of Management Information (SMI). This memo specifies a MIB 140 module that is compliant to the SMIv2, which is described in STD 58, 141 [RFC2578], STD 58, [RFC2579] and STD 58, [RFC2580]. 143 3. Overview 145 The PCEP MIB module contains the following information: 147 a. PCE and PCC local entity status (see 148 pcePcepEntityTable [RFC7420]) 150 b. PCEP peer information (see pcePcepPeerTable [RFC7420]) 152 c. PCEP session information (see pcePcepSessTable [RFC7420]) 154 d. Notifications to indicate PCEP session changes ([RFC7420]) 156 This document proposes additional "read-only" access fields for the 157 tables pcePcepEntityTable, pcePcepPeerTable and pcePcepSessTable. 158 These new fields will be defined in new tables pcePcepXEntityTable, 159 pcePcepXPeerTable and pcePcepXSessTable that augment 160 pcePcepEntityTable, pcePcepPeerTable and 161 pcePcepSessTable respectively. No changes to, or additional, 162 Notifications are proposed. 164 These new objects help a user to get information on stateful timers 165 configured, stateful capabilities negotiated by the peers, as well as 166 statistics about different kinds of messages exchanged between PCEP 167 speakers. 169 3.1. pcePcepXEntityTable 171 The PCEP MIB module may contain status information for multiple 172 logical local PCEP entities. The pcePcepXEntityTable contains one 173 row for each local PCEP entity. It augments the table 174 pcePcepEntityTable, and is indexed by the object pcePcepEntityIndex 175 defined in pcePcepEntityTable. 177 This table includes the following information: 179 a. State timeout interval value configured. 181 b. Redelegation timeout interval value configured. 183 The state timeout and redelegation timeout intervals are defined in 184 [draft-ietf-pce-stateful-pce-10], and extended in [draft-ietf-pce- 185 pce-initiated-lsp-03]. 187 3.2. pcePcepXPeerTable 189 The pcePcepXPeerTable augments the pcePcepPeerTable which contains 190 one row for each peer that the local PCEP entity knows about. Each 191 row is read-only and contains information to identify the peer. 193 This table includes the following information for each peer: 195 a. Number of PCRpts sent/received. 197 b. Number of PCRpts sent/received with different flags on: 199 * Sync 201 * Delegate 203 * Create 205 * Remove 207 c. Number of PCUpds sent/received. 209 d. Number of PCupds sent/received with different flags on. 211 * Sync 213 * Delegate 215 e. Number of PCInitiates sent/received 217 f. Number of PCInitiates sent/received with different flags on. 219 * Create 221 * Remove 223 For PCUpds, the sync flag is used only in the case of PCE triggered 224 initial sync and PCE triggered resync as defined in [draft-ietf-pce- 225 stateful-sync-optimizations-02]. 227 3.3. pcePcepXSessTable 229 The pcePcepXSessTable augments the pcePcepSessTable. The 230 pcePcepSessTable contains one row for each PCEP session that the PCEP 231 entity (PCE or PCC) is currently participating in. 233 The statistics in pcePcepSessTable are semantically different from 234 those in pcePcepPeerTable since the former applies to the current 235 session only, whereas the latter is the aggregate for all sessions 236 that have existed to that peer. 238 The pcePcepXSessTable will include the same information as in 239 pcePcepXPeerTable, but for each session. Apart from those fields 240 described in 3.2, it has the following additional information. 242 a. Stateful capabilities negotiated on the session. This is the 243 intersection of the capabilities advertised by the local entity 244 and the remote peer. 246 4. Object Definitions 248 4.1. PCE-PCEP-MIB 250 PCE-PCEP-MIB DEFINITIONS ::= BEGIN 252 IMPORTS 253 MODULE-IDENTITY, 254 OBJECT-TYPE, 255 mib-2, 256 NOTIFICATION-TYPE, 257 Unsigned32, 258 Counter32 259 FROM SNMPv2-SMI -- RFC 2578 260 TruthValue, 261 TimeStamp 262 FROM SNMPv2-TC -- RFC 2579 263 MODULE-COMPLIANCE, 264 OBJECT-GROUP, 265 NOTIFICATION-GROUP 266 FROM SNMPv2-CONF -- RFC 2580 267 InetAddressType, 268 InetAddress 269 FROM INET-ADDRESS-MIB; -- RFC 4001 271 pcePcepMIB MODULE-IDENTITY 272 LAST-UPDATED 273 "201412171200Z" -- 17 December 2014 274 ORGANIZATION 275 "IETF Path Computation Element (PCE) Working Group" 276 CONTACT-INFO 277 "Email: pce@ietf.org 278 WG charter: 279 http://datatracker.ietf.org/wg/pce/charter/" 281 DESCRIPTION 282 "This MIB module defines a collection of objects for managing 283 the Path Computation Element Communication Protocol (PCEP). 285 Copyright (c) 2014 IETF Trust and the persons identified as 286 authors of the code. All rights reserved. 288 Redistribution and use in source and binary forms, with or 289 without modification, is permitted pursuant to, and subject 290 to the license terms contained in, the Simplified BSD License 291 set forth in Section 4.c of the IETF Trust's Legal Provisions 292 Relating to IETF Documents 293 (http://trustee.ietf.org/license-info)." 295 REVISION 296 "201412171200Z" -- 17 December 2014 297 DESCRIPTION 298 "Initial version, published as RFC 7420." 299 ::= { mib-2 227 } 301 pcePcepNotifications OBJECT IDENTIFIER ::= { pcePcepMIB 0 } 302 pcePcepObjects OBJECT IDENTIFIER ::= { pcePcepMIB 1 } 303 pcePcepConformance OBJECT IDENTIFIER ::= { pcePcepMIB 2 } 305 -- 306 -- PCEP Entity Objects 307 -- 309 pcePcepXEntityTable OBJECT-TYPE 310 SYNTAX SEQUENCE OF PcePcepXEntityEntry 311 MAX-ACCESS not-accessible 312 STATUS current 313 DESCRIPTION 314 "This table contains stateful information about local PCEP 315 entities. 316 The entries in this table are read-only." 317 ::= { pcePcepObjects 5 } 319 pcePcepXEntityEntry OBJECT-TYPE 320 SYNTAX PcePcepXEntityEntry 321 MAX-ACCESS not-accessible 322 STATUS current 323 DESCRIPTION 324 "This entry represents a local PCEP entity." 325 AUGMENTS { pcePcepEntityEntry } 326 ::= { pcePcepXEntityTable 1 } 328 PcePcepXEntityEntry ::= SEQUENCE { 329 pcePcepEntityRedelegationTimer Unsigned32, 330 pcePcepEntityStateTimeoutTimer Unsigned32 332 } 334 pcePcepEntityRedelegationTimer OBJECT-TYPE 335 SYNTAX Unsigned32 (0..65535) 336 UNITS "seconds" 337 MAX-ACCESS read-only 338 STATUS current 339 DESCRIPTION 340 "On session down with a stateful PCE, this is the time the 341 PCC will wait before attempting to redelegate LSPs that were 342 delegated to this PCE, to other PCEs. 344 In the case of initiated LSPs this is the time the PCC will 345 wait for the PCE to come back and resume ownership of the 346 LSPs." 347 ::= { pcePcepXEntityEntry 1 } 349 pcePcepEntityStateTimeoutTimer OBJECT-TYPE 350 SYNTAX Unsigned32 (1..65535) 351 UNITS "seconds" 352 MAX-ACCESS read-only 353 STATUS current 354 DESCRIPTION 355 "On session down with a stateful PCE, this is the time the 356 PCC will wait before taking local ownership of LSPs that were 357 delegated to that PCE. 359 In the case of initiated LSPs, this is time the PCC waits for 360 any other backup PCEs to stake claim to the initiated LSPs. 361 After expiration of this timer, any orphan LSPs will be 362 flushed. 364 The state timeout interval MUST be greater than or equal to 365 the redelegation timeout interval and can be set to 366 INIFINITY." 367 ::= { pcePcepXEntityEntry 2 } 369 -- 370 -- The PCEP Peer Table 371 -- 373 pcePcepXPeerTable OBJECT-TYPE 374 SYNTAX SEQUENCE OF PcePcepXPeerEntry 375 MAX-ACCESS not-accessible 376 STATUS current 377 DESCRIPTION 378 "This table augments the pcePcepPeerTable. It includes 379 information about stateful messages exchanged between the 380 peers. All fields in the table are read-only." 381 ::= { pcePcepObjects 6 } 383 pcePcepXPeerEntry OBJECT-TYPE 384 SYNTAX PcePcepXPeerEntry 385 MAX-ACCESS not-accessible 386 STATUS current 387 DESCRIPTION 388 "Information about a single peer that spans all PCEP 389 sessions to that peer. Each row is for a single peer. 391 This table augments the pcePcepPeerTable. It includes 392 additional information about stateful messages exchanged 393 between the peers." 394 AUGMENTS { pcePcepPeerEntry } 395 ::= { pcePcepXPeerTable 1 } 397 PcePcepXPeerEntry ::= SEQUENCE { 398 pcePcepPeerNumPCRptSent Counter32, 399 pcePcepPeerNumPCRptRcvd Counter32, 400 pcePcepPeerNumPCUpdSent Counter32, 401 pcePcepPeerNumPCUpdRcvd Counter32, 402 pcePcepPeerNumPCInitiateSent Counter32, 403 pcePcepPeerNumPCInitiateRcvd Counter32, 404 pcePcepPeerNumPCRptSentDFlag Counter32, 405 pcePcepPeerNumPCRptRcvdDFlag Counter32, 406 pcePcepPeerNumPCRptSentSFlag Counter32, 407 pcePcepPeerNumPCRptRcvdSFlag Counter32, 408 pcePcepPeerNumPCRptSentRFlag Counter32, 409 pcePcepPeerNumPCRptRcvdRFlag Counter32, 410 pcePcepPeerNumPCRptSentCFlag Counter32, 411 pcePcepPeerNumPCRptRcvdCFlag Counter32, 412 pcePcepPeerNumPCUpdSentDFlag Counter32, 413 pcePcepPeerNumPCUpdRcvdDFlag Counter32, 414 pcePcepPeerNumPCUpdSentSFlag Counter32, 415 pcePcepPeerNumPCUpdRcvdSFlag Counter32, 416 pcePcepPeerNumPCInitiateSentCFlag Counter32, 417 pcePcepPeerNumPCInitiateRcvdCFlag Counter32 418 pcePcepPeerNumPCInitiateSentRFlag Counter32, 419 pcePcepPeerNumPCInitiateRcvdRFlag Counter32 420 } 422 pcePcepPeerNumPCRptSent OBJECT-TYPE 423 SYNTAX Counter32 424 MAX-ACCESS read-only 425 STATUS current 426 DESCRIPTION 427 "The number of PCRpt messages sent to this peer." 429 ::= { pcePcepXPeerEntry 1 } 431 pcePcepPeerNumPCRptRcvd OBJECT-TYPE 432 SYNTAX Counter32 433 MAX-ACCESS read-only 434 STATUS current 435 DESCRIPTION 436 "The number of PCRpt messages received from this peer." 437 ::= { pcePcepXPeerEntry 2 } 439 pcePcepPeerNumPCUpdSent OBJECT-TYPE 440 SYNTAX Counter32 441 MAX-ACCESS read-only 442 STATUS current 443 DESCRIPTION 444 "The number of PCUpd messages sent to this peer." 445 ::= { pcePcepXPeerEntry 3 } 447 pcePcepPeerNumPCUpdRcvd OBJECT-TYPE 448 SYNTAX Counter32 449 MAX-ACCESS read-only 450 STATUS current 451 DESCRIPTION 452 "The number of PCUpd messages received from this peer." 453 ::= { pcePcepXPeerEntry 4 } 455 pcePcepPeerNumPCInitiateSent OBJECT-TYPE 456 SYNTAX Counter32 457 MAX-ACCESS read-only 458 STATUS current 459 DESCRIPTION 460 "The number of PCInitiate messages sent to this peer." 461 ::= { pcePcepXPeerEntry 5 } 463 pcePcepPeerNumPCInitiateRcvd OBJECT-TYPE 464 SYNTAX Counter32 465 MAX-ACCESS read-only 466 STATUS current 467 DESCRIPTION 468 "The number of PCInitiate messages received from this peer." 469 ::= { pcePcepXPeerEntry 6 } 471 pcePcepPeerNumPCRptSentDFlag OBJECT-TYPE 472 SYNTAX Counter32 473 MAX-ACCESS read-only 474 STATUS current 475 DESCRIPTION 476 "The number of PCRpt messages with 'D'(Delegate) flag sent to 477 this peer." 478 ::= { pcePcepXPeerEntry 7 } 480 pcePcepPeerNumPCRptRcvdDFlag OBJECT-TYPE 481 SYNTAX Counter32 482 MAX-ACCESS read-only 483 STATUS current 484 DESCRIPTION 485 "The number of PCRpt messages with 'D'(Delegate) flag 486 received from this peer." 487 ::= { pcePcepXPeerEntry 8 } 489 pcePcepPeerNumPCRptSentSFlag OBJECT-TYPE 490 SYNTAX Counter32 491 MAX-ACCESS read-only 492 STATUS current 493 DESCRIPTION 494 "The number of PCRpt messages with 'S'(Sync) flag sent to 495 this peer." 496 ::= { pcePcepXPeerEntry 9 } 498 pcePcepPeerNumPCRptRcvdSFlag OBJECT-TYPE 499 SYNTAX Counter32 500 MAX-ACCESS read-only 501 STATUS current 502 DESCRIPTION 503 "The number of PCRpt messages with 'S'(Sync) flag received 504 from this peer." 505 ::= { pcePcepXPeerEntry 10 } 507 pcePcepPeerNumPCRptSentRFlag OBJECT-TYPE 508 SYNTAX Counter32 509 MAX-ACCESS read-only 510 STATUS current 511 DESCRIPTION 512 "The number of PCRpt messages with 'R'(Remove) flag sent to 513 this peer." 514 ::= { pcePcepXPeerEntry 11 } 516 pcePcepPeerNumPCRptRcvdRFlag OBJECT-TYPE 517 SYNTAX Counter32 518 MAX-ACCESS read-only 519 STATUS current 520 DESCRIPTION 521 "The number of PCRpt messages with 'R'(Remove) flag received 522 from this peer." 523 ::= { pcePcepXPeerEntry 12 } 525 pcePcepPeerNumPCRptSentCFlag OBJECT-TYPE 526 SYNTAX Counter32 527 MAX-ACCESS read-only 528 STATUS current 529 DESCRIPTION 530 "The number of PCRpt messages with 'C'(Create) flag sent to 531 this peer." 532 ::= { pcePcepXPeerEntry 13 } 534 pcePcepPeerNumPCRptRcvdCFlag OBJECT-TYPE 535 SYNTAX Counter32 536 MAX-ACCESS read-only 537 STATUS current 538 DESCRIPTION 539 "The number of PCRpt messages with 'C'(Create) flag received 540 from this peer." 541 ::= { pcePcepXPeerEntry 14 } 543 pcePcepPeerNumPCUpdSentDFlag OBJECT-TYPE 544 SYNTAX Counter32 545 MAX-ACCESS read-only 546 STATUS current 547 DESCRIPTION 548 "The number of PCUpd messages with 'D'(Delegate) flag sent to 549 this peer." 550 ::= { pcePcepXPeerEntry 15 } 552 pcePcepPeerNumPCUpdRcvdDFlag OBJECT-TYPE 553 SYNTAX Counter32 554 MAX-ACCESS read-only 555 STATUS current 556 DESCRIPTION 557 "The number of PCUpd messages with 'D'(Delegate) flag 558 received from this peer." 559 ::= { pcePcepXPeerEntry 16 } 561 pcePcepPeerNumPCUpdSentSFlag OBJECT-TYPE 562 SYNTAX Counter32 563 MAX-ACCESS read-only 564 STATUS current 565 DESCRIPTION 566 "The number of PCUpd messages with 'S'(Sync) flag sent to 567 this peer." 568 ::= { pcePcepXPeerEntry 17 } 570 pcePcepPeerNumPCUpdRcvdSFlag OBJECT-TYPE 571 SYNTAX Counter32 572 MAX-ACCESS read-only 573 STATUS current 574 DESCRIPTION 575 "The number of PCUpd messages with 'S'(Sync) flag received 576 from this peer." 577 ::= { pcePcepXPeerEntry 18 } 579 pcePcepPeerNumPCInitiateSentCFlag OBJECT-TYPE 580 SYNTAX Counter32 581 MAX-ACCESS read-only 582 STATUS current 583 DESCRIPTION 584 "The number of PCInitiate messages with 'C'(Create) flag sent 585 to this peer." 586 ::= { pcePcepXPeerEntry 19 } 588 pcePcepPeerNumPCInitiateRcvdCFlag OBJECT-TYPE 589 SYNTAX Counter32 590 MAX-ACCESS read-only 591 STATUS current 592 DESCRIPTION 593 "The number of PCInitiate messages with 'C'(Create) flag 594 received from this peer." 595 ::= { pcePcepXPeerEntry 20 } 597 pcePcepPeerNumPCInitiateSentRFlag OBJECT-TYPE 598 SYNTAX Counter32 599 MAX-ACCESS read-only 600 STATUS current 601 DESCRIPTION 602 "The number of PCInitiate messages with 'R'(Remove) flag sent 603 to this peer." 604 ::= { pcePcepXPeerEntry 21 } 606 pcePcepPeerNumPCInitiateRcvdRFlag OBJECT-TYPE 607 SYNTAX Counter32 608 MAX-ACCESS read-only 609 STATUS current 610 DESCRIPTION 611 "The number of PCInitiate messages with 'R'(Remove) flag 612 received from this peer." 613 ::= { pcePcepXPeerEntry 22 } 615 -- 616 -- The PCEP Sessions Table 617 -- 619 pcePcepXSessTable OBJECT-TYPE 620 SYNTAX SEQUENCE OF PcePcepXSessEntry 621 MAX-ACCESS not-accessible 622 STATUS current 623 DESCRIPTION 624 "A table of PCEP sessions that involve the local PCEP 625 entity. Each entry in this table represents a single 626 session. The entries in this table are read-only. 627 An entry appears in this table when the corresponding PCEP 628 session transitions out of idle state. If the PCEP session 629 transitions back into an idle state, then the corresponding 630 entry in this table is removed. 632 This table contains additional information to 633 pcePcepSessTable." 634 ::= { pcePcepObjects 7 } 636 pcePcepXSessEntry OBJECT-TYPE 637 SYNTAX PcePcepXSessEntry 638 MAX-ACCESS not-accessible 639 STATUS current 640 DESCRIPTION 641 "This entry represents a single PCEP session in which the 642 local PCEP entity participates. This contains stateful 643 information about the sessions. 645 This entry exists only if the corresponding PCEP session has 646 been initialized by some event, such as manual user 647 configuration, auto-discovery of a peer, or an incoming TCP 648 connection." 649 AUGMENTS { pcePcepSessEntry } 650 ::= { pcePcepXSessTable 1 } 652 PcePcepXSessEntry ::= SEQUENCE { 653 pcePcepSessStateful TruthValue, 654 pcePcepSessStatefulActive TruthValue, 655 pcePcepSessStatefulInitiate TruthValue, 656 pcePcepSessStatefulSyncAvoidance TruthValue, 657 pcePcepSessStatefulSyncIncremental TruthValue, 658 pcePcepSessStatefulTrigInitialSync TruthValue, 659 pcePcepSessStatefulTrigResync TruthValue, 660 pcePcepSessNumPCRptSent Counter32, 661 pcePcepSessNumPCRptRcvd Counter32, 662 pcePcepSessNumPCUpdSent Counter32, 663 pcePcepSessNumPCUpdRcvd Counter32, 664 pcePcepSessNumPCInitiateSent Counter32, 665 pcePcepSessNumPCInitiateRcvd Counter32, 666 pcePcepSessNumPCRptSentDFlag Counter32, 667 pcePcepSessNumPCRptRcvdDFlag Counter32, 668 pcePcepSessNumPCRptSentSFlag Counter32, 669 pcePcepSessNumPCRptRcvdSFlag Counter32, 670 pcePcepSessNumPCRptSentRFlag Counter32, 671 pcePcepSessNumPCRptRcvdRFlag Counter32, 672 pcePcepSessNumPCRptSentCFlag Counter32, 673 pcePcepSessNumPCRptRcvdCFlag Counter32, 674 pcePcepSessNumPCUpdSentDFlag Counter32, 675 pcePcepSessNumPCUpdRcvdDFlag Counter32, 676 pcePcepSessNumPCUpdSentSFlag Counter32, 677 pcePcepSessNumPCUpdRcvdSFlag Counter32, 678 pcePcepSessNumPCInitiateSentCFlag Counter32, 679 pcePcepSessNumPCInitiateRcvdCFlag Counter32 680 pcePcepSessNumPCInitiateSentRFlag Counter32, 681 pcePcepSessNumPCInitiateRcvdRFlag Counter32 682 } 684 pcePcepSessStateful OBJECT-TYPE 685 SYNTAX TruthValue 686 MAX-ACCESS read-only 687 STATUS current 688 DESCRIPTION 689 "Whether the session has Stateful capability negotiated with 690 peer." 691 ::= { pcePcepXSessEntry 1 } 693 pcePcepSessStatefulActive OBJECT-TYPE 694 SYNTAX TruthValue 695 MAX-ACCESS read-only 696 STATUS current 697 DESCRIPTION 698 "Whether the session has Stateful Active capability 699 negotiated with peer." 700 ::= { pcePcepXSessEntry 2 } 702 pcePcepSessStatefulInitiate OBJECT-TYPE 703 SYNTAX TruthValue 704 MAX-ACCESS read-only 705 STATUS current 706 DESCRIPTION 707 "Whether the session has LSP Initiate capability 708 negotiated with peer." 709 ::= { pcePcepXSessEntry 3 } 711 pcePcepSessStatefulSyncAvoidance OBJECT-TYPE 712 SYNTAX TruthValue 713 MAX-ACCESS read-only 714 STATUS current 715 DESCRIPTION 716 "Whether the session has Sync Avoidance capability 717 negotiated with peer." 718 ::= { pcePcepXSessEntry 4 } 720 pcePcepSessStatefulSyncIncremental OBJECT-TYPE 721 SYNTAX TruthValue 722 MAX-ACCESS read-only 723 STATUS current 724 DESCRIPTION 725 "Whether the session has Incremental Sync capability 726 negotiated with peer." 727 ::= { pcePcepXSessEntry 5 } 729 pcePcepSessStatefulTrigInitialSync OBJECT-TYPE 730 SYNTAX TruthValue 731 MAX-ACCESS read-only 732 STATUS current 733 DESCRIPTION 734 "Whether the session has PCE triggered Initial Sync 735 capability negotiated with peer." 736 ::= { pcePcepXSessEntry 6 } 738 pcePcepSessStatefulTrigResync OBJECT-TYPE 739 SYNTAX TruthValue 740 MAX-ACCESS read-only 741 STATUS current 742 DESCRIPTION 743 "Whether the session has PCE triggered Resync capability 744 negotiated with peer." 745 ::= { pcePcepXSessEntry 7 } 747 pcePcepSessNumPCRptSent OBJECT-TYPE 748 SYNTAX Counter32 749 MAX-ACCESS read-only 750 STATUS current 751 DESCRIPTION 752 "The number of PCRpt messages sent on this session." 753 ::= { pcePcepXSessEntry 8 } 755 pcePcepSessNumPCRptRcvd OBJECT-TYPE 756 SYNTAX Counter32 757 MAX-ACCESS read-only 758 STATUS current 759 DESCRIPTION 760 "The number of PCRpt messages received on this session." 761 ::= { pcePcepXSessEntry 9 } 763 pcePcepSessNumPCUpdSent OBJECT-TYPE 764 SYNTAX Counter32 765 MAX-ACCESS read-only 766 STATUS current 767 DESCRIPTION 768 "The number of PCUpd messages sent on this session." 769 ::= { pcePcepXSessEntry 10 } 771 pcePcepSessNumPCUpdRcvd OBJECT-TYPE 772 SYNTAX Counter32 773 MAX-ACCESS read-only 774 STATUS current 775 DESCRIPTION 776 "The number of PCUpd messages received on this session." 777 ::= { pcePcepXSessEntry 11 } 779 pcePcepSessNumPCInitiateSent OBJECT-TYPE 780 SYNTAX Counter32 781 MAX-ACCESS read-only 782 STATUS current 783 DESCRIPTION 784 "The number of PCInitiate messages sent on this session." 785 ::= { pcePcepXSessEntry 12 } 787 pcePcepSessNumPCInitiateRcvd OBJECT-TYPE 788 SYNTAX Counter32 789 MAX-ACCESS read-only 790 STATUS current 791 DESCRIPTION 792 "The number of PCInitiate messages received on this session." 793 ::= { pcePcepXSessEntry 13 } 795 pcePcepSessNumPCRptSentDFlag OBJECT-TYPE 796 SYNTAX Counter32 797 MAX-ACCESS read-only 798 STATUS current 799 DESCRIPTION 800 "The number of PCRpt messages with 'D'(Delegate) flag sent on 801 this session." 802 ::= { pcePcepXSessEntry 14 } 804 pcePcepSessNumPCRptRcvdDFlag OBJECT-TYPE 805 SYNTAX Counter32 806 MAX-ACCESS read-only 807 STATUS current 808 DESCRIPTION 809 "The number of PCRpt messages with 'D'(Delegate) flag 810 received on this session." 811 ::= { pcePcepXSessEntry 15 } 813 pcePcepSessNumPCRptSentSFlag OBJECT-TYPE 814 SYNTAX Counter32 815 MAX-ACCESS read-only 816 STATUS current 817 DESCRIPTION 818 "The number of PCRpt messages with 'S'(Sync) flag sent on 819 this session." 820 ::= { pcePcepXSessEntry 16 } 822 pcePcepSessNumPCRptRcvdSFlag OBJECT-TYPE 823 SYNTAX Counter32 824 MAX-ACCESS read-only 825 STATUS current 826 DESCRIPTION 827 "The number of PCRpt messages with 'S'(Sync) flag received 828 on this session." 829 ::= { pcePcepXSessEntry 17 } 831 pcePcepSessNumPCRptSentRFlag OBJECT-TYPE 832 SYNTAX Counter32 833 MAX-ACCESS read-only 834 STATUS current 835 DESCRIPTION 836 "The number of PCRpt messages with 'R'(Remove) flag sent on 837 this session." 838 ::= { pcePcepXSessEntry 18 } 840 pcePcepSessNumPCRptRcvdRFlag OBJECT-TYPE 841 SYNTAX Counter32 842 MAX-ACCESS read-only 843 STATUS current 844 DESCRIPTION 845 "The number of PCRpt messages with 'R'(Remove) flag received 846 on this session." 847 ::= { pcePcepXSessEntry 19 } 849 pcePcepSessNumPCRptSentCFlag OBJECT-TYPE 850 SYNTAX Counter32 851 MAX-ACCESS read-only 852 STATUS current 853 DESCRIPTION 854 "The number of PCRpt messages with 'C'(Create) flag sent on 855 this session." 856 ::= { pcePcepXSessEntry 20 } 858 pcePcepSessNumPCRptRcvdCFlag OBJECT-TYPE 859 SYNTAX Counter32 860 MAX-ACCESS read-only 861 STATUS current 862 DESCRIPTION 863 "The number of PCRpt messages with 'C'(Create) flag received 864 on this session." 865 ::= { pcePcepXSessEntry 21 } 867 pcePcepSessNumPCUpdSentDFlag OBJECT-TYPE 868 SYNTAX Counter32 869 MAX-ACCESS read-only 870 STATUS current 871 DESCRIPTION 872 "The number of PCUpd messages with 'D'(Delegate) flag sent on 873 this session." 874 ::= { pcePcepXSessEntry 22 } 876 pcePcepSessNumPCUpdRcvdDFlag OBJECT-TYPE 877 SYNTAX Counter32 878 MAX-ACCESS read-only 879 STATUS current 880 DESCRIPTION 881 "The number of PCUpd messages with 'D'(Delegate) flag 882 received on this session." 883 ::= { pcePcepXSessEntry 23 } 885 pcePcepSessNumPCUpdSentSFlag OBJECT-TYPE 886 SYNTAX Counter32 887 MAX-ACCESS read-only 888 STATUS current 889 DESCRIPTION 890 "The number of PCUpd messages with 'S'(Sync) flag sent on 891 this session." 892 ::= { pcePcepXSessEntry 24 } 894 pcePcepSessNumPCUpdRcvdSFlag OBJECT-TYPE 895 SYNTAX Counter32 896 MAX-ACCESS read-only 897 STATUS current 898 DESCRIPTION 899 "The number of PCUpd messages with 'S'(Sync) flag received 900 on this session." 901 ::= { pcePcepXSessEntry 25 } 903 pcePcepSessNumPCInitiateSentCFlag OBJECT-TYPE 904 SYNTAX Counter32 905 MAX-ACCESS read-only 906 STATUS current 907 DESCRIPTION 908 "The number of PCInitiate messages with 'C'(Create) flag sent 909 on this session." 910 ::= { pcePcepXSessEntry 26 } 912 pcePcepSessNumPCInitiateRcvdCFlag OBJECT-TYPE 913 SYNTAX Counter32 914 MAX-ACCESS read-only 915 STATUS current 916 DESCRIPTION 917 "The number of PCInitiate messages with 'C'(Create) flag 918 received on this session." 919 ::= { pcePcepXSessEntry 27 } 921 pcePcepSessNumPCInitiateSentRFlag OBJECT-TYPE 922 SYNTAX Counter32 923 MAX-ACCESS read-only 924 STATUS current 925 DESCRIPTION 926 "The number of PCInitiate messages with 'R'(Remove) flag sent 927 on this session." 928 ::= { pcePcepXSessEntry 28 } 930 pcePcepSessNumPCInitiateRcvdRFlag OBJECT-TYPE 931 SYNTAX Counter32 932 MAX-ACCESS read-only 933 STATUS current 934 DESCRIPTION 935 "The number of PCInitiate messages with 'R'(Remove) flag 936 received on this session." 937 ::= { pcePcepXSessEntry 29 } 939 5. Security Considerations 941 All new objects defined in this document are "read-only". Security 942 considerations from [RFC7420] apply to these objects. 944 6. IANA Considerations 946 IANA is requested to make the OID assignment for the MIB module under 947 the appropriate subtree. 949 7. References 951 7.1. Normative References 953 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 954 Requirement Levels", BCP 14, RFC 2119, 955 DOI 10.17487/RFC2119, March 1997, 956 . 958 [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. 959 Schoenwaelder, Ed., "Structure of Management Information 960 Version 2 (SMIv2)", STD 58, RFC 2578, 961 DOI 10.17487/RFC2578, April 1999, 962 . 964 [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. 965 Schoenwaelder, Ed., "Textual Conventions for SMIv2", 966 STD 58, RFC 2579, DOI 10.17487/RFC2579, April 1999, 967 . 969 [RFC2580] McCloghrie, K., Ed., Perkins, D., Ed., and J. 970 Schoenwaelder, Ed., "Conformance Statements for SMIv2", 971 STD 58, RFC 2580, DOI 10.17487/RFC2580, April 1999, 972 . 974 [RFC5440] Vasseur, JP., Ed. and JL. Le Roux, Ed., "Path Computation 975 Element (PCE) Communication Protocol (PCEP)", RFC 5440, 976 DOI 10.17487/RFC5440, March 2009, 977 . 979 [RFC7420] Koushik, A., Stephan, E., Zhao, Q., King, D., and J. 980 Hardwick, "Path Computation Element Communication Protocol 981 (PCEP) Management Information Base (MIB) Module", 982 RFC 7420, DOI 10.17487/RFC7420, December 2014, 983 . 985 [I-D.ietf-pce-stateful-pce] 986 Crabbe, E., Minei, I., Medved, J., and R. Varga, "PCEP 987 Extensions for Stateful PCE", draft-ietf-pce-stateful- 988 pce-16 (work in progress), September 2016. 990 [I-D.ietf-pce-pce-initiated-lsp] 991 Crabbe, E., Minei, I., Sivabalan, S., and R. Varga, "PCEP 992 Extensions for PCE-initiated LSP Setup in a Stateful PCE 993 Model", draft-ietf-pce-pce-initiated-lsp-07 (work in 994 progress), July 2016. 996 [I-D.ietf-pce-stateful-sync-optimizations] 997 Crabbe, E., Minei, I., Medved, J., Varga, R., Zhang, X., 998 and D. Dhody, "Optimizations of Label Switched Path State 999 Synchronization Procedures for a Stateful PCE", draft- 1000 ietf-pce-stateful-sync-optimizations-05 (work in 1001 progress), April 2016. 1003 7.2. Informative References 1005 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, 1006 "Introduction and Applicability Statements for Internet- 1007 Standard Management Framework", RFC 3410, 1008 DOI 10.17487/RFC3410, December 2002, 1009 . 1011 [RFC4655] Farrel, A., Vasseur, J., and J. Ash, "A Path Computation 1012 Element (PCE)-Based Architecture", RFC 4655, 1013 DOI 10.17487/RFC4655, August 2006, 1014 . 1016 Authors' Addresses 1018 Vaidyanathan Ramany 1019 Brocade Communications, Inc. 1020 Bagmane WTC 1021 Bangalore 560037 1022 India 1024 EMail: vramany@brocade.com 1026 Dheeraj Parchuru 1027 Brocade Communications, Inc. 1028 130 Holger Way 1029 San Jose CA 95134 1030 United States 1032 EMail: dparchur@brocade.com 1034 Dilip Kumar 1035 Brocade Communications, Inc. 1036 130 Holger Way 1037 San Jose CA 95134 1038 United States 1040 EMail: kumard@brocade.com