< draft-ietf-pce-pcep-yang-10.txt   draft-ietf-pce-pcep-yang-11.txt >
PCE Working Group D. Dhody, Ed. PCE Working Group D. Dhody, Ed.
Internet-Draft Huawei Technologies Internet-Draft Huawei Technologies
Intended status: Standards Track J. Hardwick Intended status: Standards Track J. Hardwick
Expires: September 25, 2019 Metaswitch Expires: September 27, 2019 Metaswitch
V. Beeram V. Beeram
Juniper Networks Juniper Networks
J. Tantsura J. Tantsura
March 24, 2019 March 26, 2019
A YANG Data Model for Path Computation Element Communications Protocol A YANG Data Model for Path Computation Element Communications Protocol
(PCEP) (PCEP)
draft-ietf-pce-pcep-yang-10 draft-ietf-pce-pcep-yang-11
Abstract Abstract
This document defines a YANG data model for the management of Path This document defines a YANG data model for the management of Path
Computation Element communications Protocol (PCEP) for communications Computation Element communications Protocol (PCEP) for communications
between a Path Computation Client (PCC) and a Path Computation between a Path Computation Client (PCC) and a Path Computation
Element (PCE), or between two PCEs. The data model includes Element (PCE), or between two PCEs. The data model includes
configuration and state data. configuration and state data.
Status of This Memo Status of This Memo
skipping to change at page 1, line 39 skipping to change at page 1, line 39
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on September 25, 2019. This Internet-Draft will expire on September 27, 2019.
Copyright Notice Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the Copyright (c) 2019 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 22 skipping to change at page 2, line 22
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Requirements Language . . . . . . . . . . . . . . . . . . . . 3 2. Requirements Language . . . . . . . . . . . . . . . . . . . . 3
3. Terminology and Notation . . . . . . . . . . . . . . . . . . 3 3. Terminology and Notation . . . . . . . . . . . . . . . . . . 3
3.1. Tree Diagrams . . . . . . . . . . . . . . . . . . . . . . 4 3.1. Tree Diagrams . . . . . . . . . . . . . . . . . . . . . . 4
3.2. Prefixes in Data Node Names . . . . . . . . . . . . . . . 5 3.2. Prefixes in Data Node Names . . . . . . . . . . . . . . . 5
3.3. Refrences in the Model . . . . . . . . . . . . . . . . . 5 3.3. Refrences in the Model . . . . . . . . . . . . . . . . . 5
4. Objectives . . . . . . . . . . . . . . . . . . . . . . . . . 7 4. Objectives . . . . . . . . . . . . . . . . . . . . . . . . . 7
5. The Design of PCEP Data Model . . . . . . . . . . . . . . . . 8 5. The Design of PCEP Data Model . . . . . . . . . . . . . . . . 8
5.1. The Overview of PCEP Data Model . . . . . . . . . . . . . 8 5.1. The Overview of PCEP Data Model . . . . . . . . . . . . . 8
5.2. The Entity . . . . . . . . . . . . . . . . . . . . . . . 9 5.2. The Entity . . . . . . . . . . . . . . . . . . . . . . . 9
5.3. The Peer Lists . . . . . . . . . . . . . . . . . . . . . 9 5.3. The Peer Lists . . . . . . . . . . . . . . . . . . . . . 13
5.4. The Session Lists . . . . . . . . . . . . . . . . . . . . 10 5.4. The Session Lists . . . . . . . . . . . . . . . . . . . . 15
5.5. Notifications . . . . . . . . . . . . . . . . . . . . . . 10 5.5. Notifications . . . . . . . . . . . . . . . . . . . . . . 17
5.6. RPC . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 5.6. RPC . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
5.7. The Full PCEP Data Model . . . . . . . . . . . . . . . . 11 5.7. The Full PCEP Data Model . . . . . . . . . . . . . . . . 18
6. The Design of PCEP Statistics Data Model . . . . . . . . . . 17 6. The Design of PCEP Statistics Data Model . . . . . . . . . . 24
7. Advanced PCE Features . . . . . . . . . . . . . . . . . . . . 20 7. Advanced PCE Features . . . . . . . . . . . . . . . . . . . . 27
7.1. Stateful PCE's LSP-DB . . . . . . . . . . . . . . . . . . 20 7.1. Stateful PCE's LSP-DB . . . . . . . . . . . . . . . . . . 28
8. Open Issues and Next Step . . . . . . . . . . . . . . . . . . 21 8. Open Issues and Next Step . . . . . . . . . . . . . . . . . . 28
8.1. The PCE-Initiated LSP . . . . . . . . . . . . . . . . . . 21 8.1. The PCE-Initiated LSP . . . . . . . . . . . . . . . . . . 28
9. Other Considerations . . . . . . . . . . . . . . . . . . . . 21 9. Other Considerations . . . . . . . . . . . . . . . . . . . . 28
9.1. PCEP over TLS (PCEPS) . . . . . . . . . . . . . . . . . . 21 9.1. PCEP over TLS (PCEPS) . . . . . . . . . . . . . . . . . . 28
10. PCEP YANG Modules . . . . . . . . . . . . . . . . . . . . . . 21 10. PCEP YANG Modules . . . . . . . . . . . . . . . . . . . . . . 28
10.1. ietf-pcep module . . . . . . . . . . . . . . . . . . . . 21 10.1. ietf-pcep module . . . . . . . . . . . . . . . . . . . . 29
10.2. ietf-pcep-stats module . . . . . . . . . . . . . . . . . 78 10.2. ietf-pcep-stats module . . . . . . . . . . . . . . . . . 83
11. Security Considerations . . . . . . . . . . . . . . . . . . . 98 11. Security Considerations . . . . . . . . . . . . . . . . . . . 101
12. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 99 12. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 102
13. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 99 13. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 102
14. References . . . . . . . . . . . . . . . . . . . . . . . . . 99 14. References . . . . . . . . . . . . . . . . . . . . . . . . . 103
14.1. Normative References . . . . . . . . . . . . . . . . . . 99 14.1. Normative References . . . . . . . . . . . . . . . . . . 103
14.2. Informative References . . . . . . . . . . . . . . . . . 103 14.2. Informative References . . . . . . . . . . . . . . . . . 106
Appendix A. Example . . . . . . . . . . . . . . . . . . . . . . 104 Appendix A. Example . . . . . . . . . . . . . . . . . . . . . . 108
Appendix B. Contributor Addresses . . . . . . . . . . . . . . . 107 Appendix B. Contributor Addresses . . . . . . . . . . . . . . . 111
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 108 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 112
1. Introduction 1. Introduction
The Path Computation Element (PCE) defined in [RFC4655] is an entity The Path Computation Element (PCE) defined in [RFC4655] is an entity
that is capable of computing a network path or route based on a that is capable of computing a network path or route based on a
network graph, and applying computational constraints. A Path network graph, and applying computational constraints. A Path
Computation Client (PCC) may make requests to a PCE for paths to be Computation Client (PCC) may make requests to a PCE for paths to be
computed. computed.
PCEP is the communication protocol between a PCC and PCE and is PCEP is the communication protocol between a PCC and PCE and is
skipping to change at page 9, line 40 skipping to change at page 9, line 40
The entity has an IP address (using ietf-inet-types [RFC6991]) and a The entity has an IP address (using ietf-inet-types [RFC6991]) and a
"role" leaf (the local entity PCEP role) as mandatory. "role" leaf (the local entity PCEP role) as mandatory.
Note that, the PCEP MIB module [RFC7420] uses an entity list and a Note that, the PCEP MIB module [RFC7420] uses an entity list and a
system generated entity index as a primary index to the read only system generated entity index as a primary index to the read only
entity table. If the device implements the PCEP MIB, the "index" entity table. If the device implements the PCEP MIB, the "index"
leaf MUST contain the value of the corresponding pcePcepEntityIndex leaf MUST contain the value of the corresponding pcePcepEntityIndex
and only one entity is assumed. and only one entity is assumed.
The various information related to this entity such as its domain,
capcabilities etc. Further incase when the entity is PCE it could
also have path-key and the LSP-DB information.
module: ietf-pcep
+--rw pcep!
+--rw entity
+--rw addr inet:ip-address
+--rw enabled? boolean
+--rw role pcep-role
+--rw description? string
+--rw speaker-entity-id? string {sync-opt}?
+--rw admin-status? boolean
+--ro index? uint32
+--ro oper-status? pcep-oper-status
+--rw domain
| +--rw domain* [domain-type domain]
| +--rw domain-type domain-type
| +--rw domain domain
+--rw capability
| +--rw capability? bits
| +--rw pce-initiated? boolean {pce-initiated}?
| +--rw include-db-ver? boolean
| | {stateful,sync-opt}?
| +--rw trigger-resync? boolean
| | {stateful,sync-opt}?
| +--rw trigger-initial-sync? boolean
| | {stateful,sync-opt}?
| +--rw incremental-sync? boolean
| | {stateful,sync-opt}?
| +--rw sr {sr}?
| +--rw enabled? boolean
| +--rw msd-limit? boolean
| +--rw nai? boolean
+--rw msd? uint8 {sr}?
+--rw pce-info
| +--rw scope
| | +--rw path-scope? bits
| | +--rw intra-area-pref? uint8
| | +--rw inter-area-pref? uint8
| | +--rw inter-as-pref? uint8
| | +--rw inter-layer-pref? uint8
| +--rw neigh-domains
| | +--rw domain* [domain-type domain]
| | +--rw domain-type domain-type
| | +--rw domain domain
| +--rw path-key {path-key}?
| +--rw enabled? boolean
| +--rw discard-timer? uint32
| +--rw reuse-time? uint32
| +--rw pce-id? inet:ip-address
+--rw connect-timer? uint16
+--rw connect-max-retry? uint32
+--rw init-backoff-timer? uint16
+--rw max-backoff-timer? uint32
+--rw open-wait-timer? uint16
+--rw keep-wait-timer? uint16
+--rw keep-alive-timer? uint8
+--rw dead-timer? uint8
+--rw allow-negotiation? boolean
+--rw max-keep-alive-timer? uint8
+--rw max-dead-timer? uint8
+--rw min-keep-alive-timer? uint8
+--rw min-dead-timer? uint8
+--rw sync-timer? uint16 {svec}?
+--rw request-timer? uint16
+--rw max-sessions? uint32
+--rw max-unknown-reqs? uint32
+--rw max-unknown-msgs? uint32
+--rw pcep-notification-max-rate uint32
+--rw stateful-parameter {stateful}?
| +--rw state-timeout? uint32
| +--rw redelegation-timeout? uint32
| +--rw rpt-non-pcep-lsp? boolean
+--rw of-list {objective-function}?
| +--rw objective-function* [of]
| +--rw of identityref
+--ro lsp-db {stateful}?
| +--ro db-ver? uint64 {sync-opt}?
| +--ro association-list*
| | [type id source global-source extended-id]
| | {association}?
| | +--ro type identityref
| | +--ro id uint16
| | +--ro source inet:ip-address
| | +--ro global-source uint32
| | +--ro extended-id string
| | +--ro lsp* [plsp-id pcc-id]
| | +--ro plsp-id -> /pcep/entity/lsp-db/lsp/plsp-id
| | +--ro pcc-id -> /pcep/entity/lsp-db/lsp/pcc-id
| +--ro lsp* [plsp-id pcc-id]
| +--ro plsp-id uint32
| +--ro pcc-id inet:ip-address
| +--ro lsp-ref
| | +--ro source?
| | | -> /te:te/lsps-state/lsp/source
| | +--ro destination?
| | | -> /te:te/lsps-state/lsp/destination
| | +--ro tunnel-id?
| | | -> /te:te/lsps-state/lsp/tunnel-id
| | +--ro lsp-id?
| | | -> /te:te/lsps-state/lsp/lsp-id
| | +--ro extended-tunnel-id?
| | -> /te:te/lsps-state/lsp/extended-tunnel-id
| +--ro admin-state? boolean
| +--ro operational-state? operational-state
| +--ro delegated
| | +--ro enabled? boolean
| | +--ro peer? -> /pcep/entity/peers/peer/addr
| | +--ro srp-id? uint32
| +--ro initiation {pce-initiated}?
| | +--ro enabled? boolean
| | +--ro peer? -> /pcep/entity/peers/peer/addr
| +--ro symbolic-path-name? string
| +--ro last-error? identityref
| +--ro pst? identityref
| +--ro association-list*
| [type id source global-source extended-id]
| {association}?
| +--ro type
| | -> /pcep/entity/lsp-db/association-list/type
| +--ro id
| | -> /pcep/entity/lsp-db/association-list/id
| +--ro source leafref
| +--ro global-source leafref
| +--ro extended-id leafref
+--ro path-keys {path-key}?
| +--ro path-keys* [path-key]
| +--ro path-key uint16
| +--ro cps
| | +--ro explicit-route-objects* [index]
| | +--ro index uint32
| | +--ro (type)?
| | +--:(numbered-node-hop)
| | | +--ro numbered-node-hop
| | | +--ro node-id te-node-id
| | | +--ro hop-type? te-hop-type
| | +--:(numbered-link-hop)
| | | +--ro numbered-link-hop
| | | +--ro link-tp-id te-tp-id
| | | +--ro hop-type? te-hop-type
| | | +--ro direction? te-link-direction
| | +--:(unnumbered-link-hop)
| | | +--ro unnumbered-link-hop
| | | +--ro link-tp-id te-tp-id
| | | +--ro node-id te-node-id
| | | +--ro hop-type? te-hop-type
| | | +--ro direction? te-link-direction
| | +--:(as-number)
| | | +--ro as-number-hop
| | | +--ro as-number inet:as-number
| | | +--ro hop-type? te-hop-type
| | +--:(label)
| | +--ro label-hop
| | +--ro te-label
| | ...
| +--ro pcc-original? -> /pcep/entity/peers/peer/addr
| +--ro req-id? uint32
| +--ro retrieved? boolean
| +--ro pcc-retrieved? -> /pcep/entity/peers/peer/addr
| +--ro creation-time? yang:timestamp
| +--ro discard-time? uint32
| +--ro reuse-time? uint32
+--rw peers
+--rw peer* [addr]
...
5.3. The Peer Lists 5.3. The Peer Lists
The peer list contains peer(s) that the local PCEP entity knows The peer list contains peer(s) that the local PCEP entity knows
about. A PCEP speaker is identified by its IP address. If there is about. A PCEP speaker is identified by its IP address. If there is
a PCEP speaker in the network that uses multiple IP addresses then it a PCEP speaker in the network that uses multiple IP addresses then it
looks like multiple distinct peers to the other PCEP speakers in the looks like multiple distinct peers to the other PCEP speakers in the
network. network.
Since PCEP sessions can be ephemeral, the peer list tracks a peer Since PCEP sessions can be ephemeral, the peer list tracks a peer
even when no PCEP session currently exists to that peer. The even when no PCEP session currently exists to that peer. The
skipping to change at page 10, line 20 skipping to change at page 13, line 44
list of peers. Each peer in the list is identified by its IP address list of peers. Each peer in the list is identified by its IP address
(addr-type, addr). (addr-type, addr).
There is a list for static peer configuration and operational state There is a list for static peer configuration and operational state
of all peers (i.e.static as well as discovered)("/pcep/entity/ of all peers (i.e.static as well as discovered)("/pcep/entity/
peers"). The list is used to enable remote PCE configuration at PCC peers"). The list is used to enable remote PCE configuration at PCC
(or PCE) and has the operational state of these peers as well as the (or PCE) and has the operational state of these peers as well as the
remote PCE peer which were discovered and PCC peers that have remote PCE peer which were discovered and PCC peers that have
initiated session. initiated session.
module: ietf-pcep
+--rw pcep!
+--rw entity
...
+--rw peers
+--rw peer* [addr]
+--rw addr inet:ip-address
+--rw role pcep-role
+--rw description? string
+--rw domain
| +--rw domain* [domain-type domain]
| +--rw domain-type domain-type
| +--rw domain domain
+--rw capability
| +--rw capability? bits
| +--rw pce-initiated? boolean
| | {pce-initiated}?
| +--rw include-db-ver? boolean
| | {stateful,sync-opt}?
| +--rw trigger-resync? boolean
| | {stateful,sync-opt}?
| +--rw trigger-initial-sync? boolean
| | {stateful,sync-opt}?
| +--rw incremental-sync? boolean
| | {stateful,sync-opt}?
| +--rw sr {sr}?
| +--rw enabled? boolean
| +--rw msd-limit? boolean
| +--rw nai? boolean
+--rw msd? uint8 {sr}?
+--rw pce-info
| +--rw scope
| | +--rw path-scope? bits
| | +--rw intra-area-pref? uint8
| | +--rw inter-area-pref? uint8
| | +--rw inter-as-pref? uint8
| | +--rw inter-layer-pref? uint8
| +--rw neigh-domains
| +--rw domain* [domain-type domain]
| +--rw domain-type domain-type
| +--rw domain domain
+--rw delegation-pref? uint8 {stateful}?
+--rw auth
| +--rw (auth-type-selection)?
| +--:(auth-key-chain)
| | +--rw key-chain?
| | key-chain:key-chain-ref
| +--:(auth-key)
| | +--rw crypto-algorithm identityref
| | +--rw (key-string-style)?
| | +--:(keystring)
| | | +--rw keystring? string
| | +--:(hexadecimal)
| | {key-chain:hex-key-string}?
| | +--rw hexadecimal-string?
| | yang:hex-string
| +--:(auth-tls) {tls}?
| +--rw (role)?
| +--:(server)
| | +--rw tls-server
| | ...
| +--:(client)
| +--rw tls-client
| ...
+--ro discontinuity-time? yang:timestamp
+--ro initiate-session? boolean
+--ro session-exists? boolean
+--ro session-up-time? yang:timestamp
+--ro session-fail-time? yang:timestamp
+--ro session-fail-up-time? yang:timestamp
+--ro sessions
+--ro session* [initiator]
...
5.4. The Session Lists 5.4. The Session Lists
The session list contains PCEP session that the PCEP entity (PCE or The session list contains PCEP session that the PCEP entity (PCE or
PCC) is currently participating in. The statistics in session are PCC) is currently participating in. The statistics in session are
semantically different from those in peer since the former applies to semantically different from those in peer since the former applies to
the current session only, whereas the latter is the aggregate for all the current session only, whereas the latter is the aggregate for all
sessions that have existed to that peer. sessions that have existed to that peer.
Although [RFC5440] forbids more than one active PCEP session between Although [RFC5440] forbids more than one active PCEP session between
a given pair of PCEP entities at any given time, there is a window a given pair of PCEP entities at any given time, there is a window
skipping to change at page 10, line 41 skipping to change at page 16, line 5
pair, one representing a session initiated by the local PCEP entity pair, one representing a session initiated by the local PCEP entity
and the other representing a session initiated by the peer. If and the other representing a session initiated by the peer. If
either of these sessions reaches active state first, then the other either of these sessions reaches active state first, then the other
is discarded. is discarded.
The data model for PCEP session presented in this document uses a The data model for PCEP session presented in this document uses a
flat list of sessions. Each session in the list is identified by its flat list of sessions. Each session in the list is identified by its
initiator. This index allows two sessions to exist transiently for a initiator. This index allows two sessions to exist transiently for a
given peer, as discussed above. given peer, as discussed above.
module: ietf-pcep
+--rw pcep!
+--rw entity
...
+--rw peers
+--rw peer* [addr]
...
+--ro sessions
+--ro session* [initiator]
+--ro initiator pcep-initiator
+--ro role?
| -> /pcep/entity/role
+--ro state-last-change? yang:timestamp
+--ro state? pcep-sess-state
+--ro session-creation? yang:timestamp
+--ro connect-retry? yang:counter32
+--ro local-id? uint8
+--ro remote-id? uint8
+--ro keepalive-timer? uint8
+--ro peer-keepalive-timer? uint8
+--ro dead-timer? uint8
+--ro peer-dead-timer? uint8
+--ro ka-hold-time-rem? uint8
+--ro overloaded? boolean
+--ro overload-time? uint32
+--ro peer-overloaded? boolean
+--ro peer-overload-time? uint32
+--ro lspdb-sync? sync-state
| {stateful}?
+--ro recv-db-ver? uint64
| {stateful,sync-opt}?
+--ro of-list {objective-function}?
| +--ro objective-function* [of]
| +--ro of identityref
+--ro pst-list
| +--ro path-setup-type* [pst]
| +--ro pst identityref
+--ro assoc-type-list {association}?
| +--ro assoc-type* [at]
| +--ro at identityref
+--ro speaker-entity-id? string {sync-opt}?
+--ro discontinuity-time? yang:timestamp
5.5. Notifications 5.5. Notifications
This YANG model defines a list of notifications to inform client of This YANG model defines a list of notifications to inform client of
important events detected during the protocol operation. The important events detected during the protocol operation. The
notifications defined cover the PCEP MIB notifications. notifications defined cover the PCEP MIB notifications.
notifications:
+---n pcep-session-up
| +--ro peer-addr? -> /pcep/entity/peers/peer/addr
| +--ro session-initiator?
| | -> /pcep/entity/peers/peer/sessions/session/initiator
| +--ro state-last-change? yang:timestamp
| +--ro state? pcep-sess-state
+---n pcep-session-down
| +--ro peer-addr? -> /pcep/entity/peers/peer/addr
| +--ro session-initiator? pcep-initiator
| +--ro state-last-change? yang:timestamp
| +--ro state? pcep-sess-state
+---n pcep-session-local-overload
| +--ro peer-addr? -> /pcep/entity/peers/peer/addr
| +--ro session-initiator?
| | -> /pcep/entity/peers/peer/sessions/session/initiator
| +--ro overloaded? boolean
| +--ro overload-time? uint32
+---n pcep-session-local-overload-clear
| +--ro peer-addr? -> /pcep/entity/peers/peer/addr
| +--ro overloaded? boolean
+---n pcep-session-peer-overload
| +--ro peer-addr? -> /pcep/entity/peers/peer/addr
| +--ro session-initiator?
| | -> /pcep/entity/peers/peer/sessions/session/initiator
| +--ro peer-overloaded? boolean
| +--ro peer-overload-time? uint32
+---n pcep-session-peer-overload-clear
+--ro peer-addr? -> /pcep/entity/peers/peer/addr
+--ro peer-overloaded? boolean
5.6. RPC 5.6. RPC
This YANG model defines a RPC to trigger state resynchronization to a This YANG model defines a RPC to trigger state resynchronization to a
particular PCEP peer. particular PCEP peer.
rpcs:
+---x trigger-resync {stateful,sync-opt}?
+---w input
+---w pcc? -> /pcep/entity/peers/peer/addr
5.7. The Full PCEP Data Model 5.7. The Full PCEP Data Model
The module, "ietf-pcep", defines the basic components of a PCE The module, "ietf-pcep", defines the basic components of a PCE
speaker. The tree depth in the tree is set to 10. speaker. The tree depth in the tree is set to 10.
module: ietf-pcep module: ietf-pcep
+--rw pcep! +--rw pcep!
+--rw entity +--rw entity
+--rw addr inet:ip-address +--rw addr inet:ip-address
+--rw enabled? boolean +--rw enabled? boolean
+--rw role pcep-role +--rw role pcep-role
+--rw description? string +--rw description? string
+--rw speaker-entity-id? string {sync-opt}? +--rw speaker-entity-id? string {sync-opt}?
+--rw admin-status? boolean +--rw admin-status? boolean
+--ro index? uint32 +--ro index? uint32
+--ro oper-status? pcep-oper-status +--ro oper-status? pcep-oper-status
+--rw domain +--rw domain
| +--rw domain* [domain-type domain] | +--rw domain* [domain-type domain]
| +--rw domain-type domain-type | +--rw domain-type domain-type
| +--rw domain domain | +--rw domain domain
+--rw capability +--rw capability
| +--rw capability? bits | +--rw capability? bits
| +--rw pce-initiated? boolean {pce-initiated}? | +--rw pce-initiated? boolean {pce-initiated}?
| +--rw include-db-ver? boolean | +--rw include-db-ver? boolean
| | {stateful,sync-opt}? | | {stateful,sync-opt}?
| +--rw trigger-resync? boolean | +--rw trigger-resync? boolean
| | {stateful,sync-opt}? | | {stateful,sync-opt}?
| +--rw trigger-initial-sync? boolean | +--rw trigger-initial-sync? boolean
| | {stateful,sync-opt}? | | {stateful,sync-opt}?
| +--rw incremental-sync? boolean | +--rw incremental-sync? boolean
| | {stateful,sync-opt}? | | {stateful,sync-opt}?
| +--rw sr {sr}? | +--rw sr {sr}?
| +--rw enabled? boolean | +--rw enabled? boolean
| +--rw msd-limit? boolean | +--rw msd-limit? boolean
| +--rw nai? boolean | +--rw nai? boolean
+--rw msd? uint8 {sr}? +--rw msd? uint8 {sr}?
+--rw pce-info +--rw pce-info
| +--rw scope | +--rw scope
| | +--rw path-scope? bits | | +--rw path-scope? bits
| | +--rw intra-area-pref? uint8 | | +--rw intra-area-pref? uint8
| | +--rw inter-area-pref? uint8 | | +--rw inter-area-pref? uint8
| | +--rw inter-as-pref? uint8 | | +--rw inter-as-pref? uint8
| | +--rw inter-layer-pref? uint8 | | +--rw inter-layer-pref? uint8
| +--rw neigh-domains | +--rw neigh-domains
| | +--rw domain* [domain-type domain] | | +--rw domain* [domain-type domain]
| | +--rw domain-type domain-type | | +--rw domain-type domain-type
| | +--rw domain domain | | +--rw domain domain
| +--rw path-key {path-key}? | +--rw path-key {path-key}?
| +--rw enabled? boolean | +--rw enabled? boolean
| +--rw discard-timer? uint32 | +--rw discard-timer? uint32
| +--rw reuse-time? uint32 | +--rw reuse-time? uint32
| +--rw pce-id? inet:ip-address | +--rw pce-id? inet:ip-address
+--rw connect-timer? uint16 +--rw connect-timer? uint16
+--rw connect-max-retry? uint32 +--rw connect-max-retry? uint32
+--rw init-backoff-timer? uint16 +--rw init-backoff-timer? uint16
+--rw max-backoff-timer? uint32 +--rw max-backoff-timer? uint32
+--rw open-wait-timer? uint16 +--rw open-wait-timer? uint16
+--rw keep-wait-timer? uint16 +--rw keep-wait-timer? uint16
+--rw keep-alive-timer? uint8 +--rw keep-alive-timer? uint8
+--rw dead-timer? uint8 +--rw dead-timer? uint8
+--rw allow-negotiation? boolean +--rw allow-negotiation? boolean
+--rw max-keep-alive-timer? uint8 +--rw max-keep-alive-timer? uint8
+--rw max-dead-timer? uint8 +--rw max-dead-timer? uint8
+--rw min-keep-alive-timer? uint8 +--rw min-keep-alive-timer? uint8
+--rw min-dead-timer? uint8 +--rw min-dead-timer? uint8
+--rw sync-timer? uint16 {svec}? +--rw sync-timer? uint16 {svec}?
+--rw request-timer? uint16 +--rw request-timer? uint16
+--rw max-sessions? uint32 +--rw max-sessions? uint32
+--rw max-unknown-reqs? uint32 +--rw max-unknown-reqs? uint32
+--rw max-unknown-msgs? uint32 +--rw max-unknown-msgs? uint32
+--rw pcep-notification-max-rate uint32 +--rw pcep-notification-max-rate uint32
+--rw stateful-parameter {stateful}? +--rw stateful-parameter {stateful}?
| +--rw state-timeout? uint32 | +--rw state-timeout? uint32
| +--rw redelegation-timeout? uint32 | +--rw redelegation-timeout? uint32
| +--rw rpt-non-pcep-lsp? boolean | +--rw rpt-non-pcep-lsp? boolean
+--rw of-list {objective-function}? +--rw of-list {objective-function}?
| +--rw objective-function* [of] | +--rw objective-function* [of]
| +--rw of identityref | +--rw of identityref
+--ro lsp-db {stateful}? +--ro lsp-db {stateful}?
| +--ro db-ver? uint64 {sync-opt}? | +--ro db-ver? uint64 {sync-opt}?
| +--ro association-list* | +--ro association-list*
| | [type id source global-source extended-id] | | [type id source global-source extended-id]
| | {association}? | | {association}?
| | +--ro type identityref | | +--ro type identityref
| | +--ro id uint16 | | +--ro id uint16
| | +--ro source inet:ip-address | | +--ro source inet:ip-address
| | +--ro global-source uint32 | | +--ro global-source uint32
| | +--ro extended-id string | | +--ro extended-id string
| | +--ro lsp* [plsp-id pcc-id] | | +--ro lsp* [plsp-id pcc-id]
| | +--ro plsp-id -> /pcep/entity/lsp-db/lsp/plsp-id | | +--ro plsp-id -> /pcep/entity/lsp-db/lsp/plsp-id
| | +--ro pcc-id -> /pcep/entity/lsp-db/lsp/pcc-id | | +--ro pcc-id -> /pcep/entity/lsp-db/lsp/pcc-id
| +--ro lsp* [plsp-id pcc-id] | +--ro lsp* [plsp-id pcc-id]
| +--ro plsp-id uint32 | +--ro plsp-id uint32
| +--ro pcc-id inet:ip-address | +--ro pcc-id inet:ip-address
| +--ro lsp-ref | +--ro lsp-ref
| | +--ro source? | | +--ro source?
| | | -> /te:te/lsps-state/lsp/source | | | -> /te:te/lsps-state/lsp/source
| | +--ro destination? | | +--ro destination?
| | | -> /te:te/lsps-state/lsp/destination | | | -> /te:te/lsps-state/lsp/destination
| | +--ro tunnel-id? | | +--ro tunnel-id?
| | | -> /te:te/lsps-state/lsp/tunnel-id | | | -> /te:te/lsps-state/lsp/tunnel-id
| | +--ro lsp-id? | | +--ro lsp-id?
| | | -> /te:te/lsps-state/lsp/lsp-id | | | -> /te:te/lsps-state/lsp/lsp-id
| | +--ro extended-tunnel-id? leafref | | +--ro extended-tunnel-id?
| +--ro admin-state? boolean | | -> /te:te/lsps-state/lsp/extended-tunnel-id
| +--ro operational-state? operational-state | +--ro admin-state? boolean
| +--ro delegated | +--ro operational-state? operational-state
| | +--ro enabled? boolean | +--ro delegated
| | +--ro peer? -> /pcep/entity/peers/peer/addr | | +--ro enabled? boolean
| | +--ro srp-id? uint32 | | +--ro peer? -> /pcep/entity/peers/peer/addr
| +--ro initiation {pce-initiated}? | | +--ro srp-id? uint32
| | +--ro enabled? boolean | +--ro initiation {pce-initiated}?
| | +--ro peer? -> /pcep/entity/peers/peer/addr | | +--ro enabled? boolean
| +--ro symbolic-path-name? string | | +--ro peer? -> /pcep/entity/peers/peer/addr
| +--ro last-error? identityref | +--ro symbolic-path-name? string
| +--ro pst? identityref | +--ro last-error? identityref
| +--ro association-list* | +--ro pst? identityref
| [type id source global-source extended-id] | +--ro association-list*
| {association}? | [type id source global-source extended-id]
| +--ro type leafref | {association}?
| +--ro id | +--ro type
| | -> /pcep/entity/lsp-db/association-list/id | | -> /pcep/entity/lsp-db/association-list/type
| +--ro source leafref | +--ro id
| +--ro global-source leafref | | -> /pcep/entity/lsp-db/association-list/id
| +--ro extended-id leafref | +--ro source leafref
+--ro path-keys {path-key}? | +--ro global-source leafref
| +--ro path-keys* [path-key] | +--ro extended-id leafref
| +--ro path-key uint16 +--ro path-keys {path-key}?
| +--ro cps | +--ro path-keys* [path-key]
| | +--ro explicit-route-objects* [index] | +--ro path-key uint16
| | +--ro index uint32 | +--ro cps
| | +--ro (type)? | | +--ro explicit-route-objects* [index]
| | +--:(numbered-node-hop) | | +--ro index uint32
| | | +--ro numbered-node-hop | | +--ro (type)?
| | | +--ro node-id te-node-id | | +--:(numbered-node-hop)
| | | +--ro hop-type? te-hop-type | | | +--ro numbered-node-hop
| | +--:(numbered-link-hop) | | | +--ro node-id te-node-id
| | | +--ro numbered-link-hop | | | +--ro hop-type? te-hop-type
| | | +--ro link-tp-id te-tp-id | | +--:(numbered-link-hop)
| | | +--ro hop-type? te-hop-type | | | +--ro numbered-link-hop
| | | +--ro direction? te-link-direction | | | +--ro link-tp-id te-tp-id
| | +--:(unnumbered-link-hop) | | | +--ro hop-type? te-hop-type
| | | +--ro unnumbered-link-hop | | | +--ro direction? te-link-direction
| | | +--ro link-tp-id te-tp-id | | +--:(unnumbered-link-hop)
| | | +--ro node-id te-node-id | | | +--ro unnumbered-link-hop
| | | +--ro hop-type? te-hop-type | | | +--ro link-tp-id te-tp-id
| | | +--ro direction? te-link-direction | | | +--ro node-id te-node-id
| | +--:(as-number) | | | +--ro hop-type? te-hop-type
| | | +--ro as-number-hop | | | +--ro direction? te-link-direction
| | | +--ro as-number inet:as-number | | +--:(as-number)
| | | +--ro hop-type? te-hop-type | | | +--ro as-number-hop
| | +--:(label) | | | +--ro as-number inet:as-number
| | +--ro label-hop | | | +--ro hop-type? te-hop-type
| | +--ro te-label | | +--:(label)
| | ... | | +--ro label-hop
| +--ro pcc-original? -> /pcep/entity/peers/peer/addr | | +--ro te-label
| +--ro req-id? uint32 | | ...
| +--ro retrieved? boolean | +--ro pcc-original? -> /pcep/entity/peers/peer/addr
| +--ro pcc-retrieved? -> /pcep/entity/peers/peer/addr | +--ro req-id? uint32
| +--ro creation-time? yang:timestamp | +--ro retrieved? boolean
| +--ro discard-time? uint32 | +--ro pcc-retrieved? -> /pcep/entity/peers/peer/addr
| +--ro reuse-time? uint32 | +--ro creation-time? yang:timestamp
+--rw peers | +--ro discard-time? uint32
+--rw peer* [addr] | +--ro reuse-time? uint32
+--rw addr inet:ip-address +--rw peers
+--rw role pcep-role +--rw peer* [addr]
+--rw description? string +--rw addr inet:ip-address
+--rw domain +--rw role pcep-role
| +--rw domain* [domain-type domain] +--rw description? string
| +--rw domain-type domain-type +--rw domain
| +--rw domain domain | +--rw domain* [domain-type domain]
+--rw capability | +--rw domain-type domain-type
| +--rw capability? bits | +--rw domain domain
| +--rw pce-initiated? boolean +--rw capability
| | {pce-initiated}? | +--rw capability? bits
| +--rw include-db-ver? boolean | +--rw pce-initiated? boolean
| | {stateful,sync-opt}? | | {pce-initiated}?
| +--rw trigger-resync? boolean | +--rw include-db-ver? boolean
| | {stateful,sync-opt}? | | {stateful,sync-opt}?
| +--rw trigger-initial-sync? boolean | +--rw trigger-resync? boolean
| | {stateful,sync-opt}? | | {stateful,sync-opt}?
| +--rw incremental-sync? boolean | +--rw trigger-initial-sync? boolean
| | {stateful,sync-opt}? | | {stateful,sync-opt}?
| +--rw sr {sr}? | +--rw incremental-sync? boolean
| +--rw enabled? boolean | | {stateful,sync-opt}?
| +--rw msd-limit? boolean | +--rw sr {sr}?
| +--rw nai? boolean | +--rw enabled? boolean
+--rw msd? uint8 {sr}? | +--rw msd-limit? boolean
+--rw pce-info | +--rw nai? boolean
| +--rw scope +--rw msd? uint8 {sr}?
| | +--rw path-scope? bits +--rw pce-info
| | +--rw intra-area-pref? uint8 | +--rw scope
| | +--rw inter-area-pref? uint8 | | +--rw path-scope? bits
| | +--rw inter-as-pref? uint8 | | +--rw intra-area-pref? uint8
| | +--rw inter-layer-pref? uint8 | | +--rw inter-area-pref? uint8
| +--rw neigh-domains | | +--rw inter-as-pref? uint8
| +--rw domain* [domain-type domain] | | +--rw inter-layer-pref? uint8
| +--rw domain-type domain-type | +--rw neigh-domains
| +--rw domain domain | +--rw domain* [domain-type domain]
+--rw delegation-pref? uint8 {stateful}? | +--rw domain-type domain-type
+--rw auth | +--rw domain domain
| +--rw (auth-type-selection)? +--rw delegation-pref? uint8 {stateful}?
| +--:(auth-key-chain) +--rw auth
| | +--rw key-chain? kc:key-chain-ref | +--rw (auth-type-selection)?
| +--:(auth-key) | +--:(auth-key-chain)
| | +--rw crypto-algorithm identityref | | +--rw key-chain?
| | +--rw (key-string-style)? | | key-chain:key-chain-ref
| | +--:(keystring) | +--:(auth-key)
| | | +--rw keystring? string | | +--rw crypto-algorithm identityref
| | +--:(hexadecimal) {kc:hex-key-string}? | | +--rw (key-string-style)?
| | +--rw hexadecimal-string? | | +--:(keystring)
| | yang:hex-string | | | +--rw keystring? string
| +--:(auth-tls) {tls}? | | +--:(hexadecimal)
| +--rw (role)? | | {key-chain:hex-key-string}?
| +--:(server) | | +--rw hexadecimal-string?
| | +--rw tls-server | | yang:hex-string
| | ... | +--:(auth-tls) {tls}?
| +--:(client) | +--rw (role)?
| +--rw tls-client | +--:(server)
| ... | | +--rw tls-server
+--ro discontinuity-time? yang:timestamp | | ...
+--ro initiate-session? boolean | +--:(client)
+--ro session-exists? boolean | +--rw tls-client
+--ro session-up-time? yang:timestamp | ...
+--ro session-fail-time? yang:timestamp +--ro discontinuity-time? yang:timestamp
+--ro session-fail-up-time? yang:timestamp +--ro initiate-session? boolean
+--ro sessions +--ro session-exists? boolean
+--ro session* [initiator] +--ro session-up-time? yang:timestamp
+--ro initiator pcep-initiator +--ro session-fail-time? yang:timestamp
+--ro role? -> /pcep/entity/role +--ro session-fail-up-time? yang:timestamp
+--ro state-last-change? yang:timestamp +--ro sessions
+--ro state? pcep-sess-state +--ro session* [initiator]
+--ro session-creation? yang:timestamp +--ro initiator pcep-initiator
+--ro connect-retry? yang:counter32 +--ro role?
+--ro local-id? uint8 | -> /pcep/entity/role
+--ro remote-id? uint8 +--ro state-last-change? yang:timestamp
+--ro keepalive-timer? uint8 +--ro state? pcep-sess-state
+--ro peer-keepalive-timer? uint8 +--ro session-creation? yang:timestamp
+--ro dead-timer? uint8 +--ro connect-retry? yang:counter32
+--ro peer-dead-timer? uint8 +--ro local-id? uint8
+--ro ka-hold-time-rem? uint8 +--ro remote-id? uint8
+--ro overloaded? boolean +--ro keepalive-timer? uint8
+--ro overload-time? uint32 +--ro peer-keepalive-timer? uint8
+--ro peer-overloaded? boolean +--ro dead-timer? uint8
+--ro peer-overload-time? uint32 +--ro peer-dead-timer? uint8
+--ro lspdb-sync? sync-state +--ro ka-hold-time-rem? uint8
| {stateful}? +--ro overloaded? boolean
+--ro recv-db-ver? uint64 +--ro overload-time? uint32
| {stateful,sync-opt}? +--ro peer-overloaded? boolean
+--ro of-list {objective-function}? +--ro peer-overload-time? uint32
| +--ro objective-function* [of] +--ro lspdb-sync? sync-state
| +--ro of identityref | {stateful}?
+--ro pst-list +--ro recv-db-ver? uint64
| +--ro path-setup-type* [pst] | {stateful,sync-opt}?
| +--ro pst identityref +--ro of-list {objective-function}?
+--ro assoc-type-list {association}? | +--ro objective-function* [of]
| +--ro assoc-type* [at] | +--ro of identityref
| +--ro at identityref +--ro pst-list
+--ro speaker-entity-id? string | +--ro path-setup-type* [pst]
| {sync-opt}? | +--ro pst identityref
+--ro discontinuity-time? yang:timestamp +--ro assoc-type-list {association}?
| +--ro assoc-type* [at]
| +--ro at identityref
+--ro speaker-entity-id? string {sync-opt}?
+--ro discontinuity-time? yang:timestamp
rpcs: rpcs:
+---x trigger-resync {stateful,sync-opt}? +---x trigger-resync {stateful,sync-opt}?
+---w input +---w input
+---w pcc? -> /pcep/entity/peers/peer/addr +---w pcc? -> /pcep/entity/peers/peer/addr
notifications: notifications:
+---n pcep-session-up +---n pcep-session-up
| +--ro peer-addr? -> /pcep/entity/peers/peer/addr | +--ro peer-addr? -> /pcep/entity/peers/peer/addr
| +--ro session-initiator? | +--ro session-initiator?
| | -> /pcep/entity/peers/peer/sessions/session/initiator | | -> /pcep/entity/peers/peer/sessions/session/initiator
| +--ro state-last-change? yang:timestamp | +--ro state-last-change? yang:timestamp
| +--ro state? pcep-sess-state | +--ro state? pcep-sess-state
+---n pcep-session-down +---n pcep-session-down
| +--ro peer-addr? -> /pcep/entity/peers/peer/addr | +--ro peer-addr? -> /pcep/entity/peers/peer/addr
| +--ro session-initiator? pcep-initiator | +--ro session-initiator? pcep-initiator
| +--ro state-last-change? yang:timestamp | +--ro state-last-change? yang:timestamp
| +--ro state? pcep-sess-state | +--ro state? pcep-sess-state
+---n pcep-session-local-overload +---n pcep-session-local-overload
| +--ro peer-addr? -> /pcep/entity/peers/peer/addr | +--ro peer-addr? -> /pcep/entity/peers/peer/addr
| +--ro session-initiator? | +--ro session-initiator?
| | -> /pcep/entity/peers/peer/sessions/session/initiator | | -> /pcep/entity/peers/peer/sessions/session/initiator
| +--ro overloaded? boolean | +--ro overloaded? boolean
| +--ro overload-time? uint32 | +--ro overload-time? uint32
+---n pcep-session-local-overload-clear +---n pcep-session-local-overload-clear
| +--ro peer-addr? -> /pcep/entity/peers/peer/addr | +--ro peer-addr? -> /pcep/entity/peers/peer/addr
| +--ro overloaded? boolean | +--ro overloaded? boolean
+---n pcep-session-peer-overload +---n pcep-session-peer-overload
| +--ro peer-addr? -> /pcep/entity/peers/peer/addr | +--ro peer-addr? -> /pcep/entity/peers/peer/addr
| +--ro session-initiator? | +--ro session-initiator?
| | -> /pcep/entity/peers/peer/sessions/session/initiator | | -> /pcep/entity/peers/peer/sessions/session/initiator
| +--ro peer-overloaded? boolean | +--ro peer-overloaded? boolean
| +--ro peer-overload-time? uint32 | +--ro peer-overload-time? uint32
+---n pcep-session-peer-overload-clear +---n pcep-session-peer-overload-clear
+--ro peer-addr? -> /pcep/entity/peers/peer/addr +--ro peer-addr? -> /pcep/entity/peers/peer/addr
+--ro peer-overloaded? boolean +--ro peer-overloaded? boolean
6. The Design of PCEP Statistics Data Model 6. The Design of PCEP Statistics Data Model
The module, "ietf-pcep-stats", augments the ietf-pcep module to The module, "ietf-pcep-stats", augments the ietf-pcep module to
include statistics at the PCEP peer and session level. include statistics at the PCEP peer and session level.
module: ietf-pcep-stats module: ietf-pcep-stats
augment /p:pcep/p:entity/p:peers/p:peer: augment /pcep:pcep/pcep:entity/pcep:peers/pcep:peer:
+--ro num-sess-setup-ok? yang:counter32 +--ro num-sess-setup-ok? yang:counter32
+--ro num-sess-setup-fail? yang:counter32 +--ro num-sess-setup-fail? yang:counter32
+--ro pcep-stats +--ro pcep-stats
+--ro avg-rsp-time? uint32 +--ro avg-rsp-time? uint32
+--ro lwm-rsp-time? uint32 +--ro lwm-rsp-time? uint32
+--ro hwm-rsp-time? uint32 +--ro hwm-rsp-time? uint32
+--ro num-pcreq-sent? yang:counter32 +--ro num-pcreq-sent? yang:counter32
+--ro num-pcreq-rcvd? yang:counter32 +--ro num-pcreq-rcvd? yang:counter32
+--ro num-pcrep-sent? yang:counter32 +--ro num-pcrep-sent? yang:counter32
+--ro num-pcrep-rcvd? yang:counter32 +--ro num-pcrep-rcvd? yang:counter32
skipping to change at page 18, line 10 skipping to change at page 25, line 16
+--ro num-req-sent-cancel-sent? yang:counter32 +--ro num-req-sent-cancel-sent? yang:counter32
+--ro num-req-rcvd? yang:counter32 +--ro num-req-rcvd? yang:counter32
+--ro num-req-rcvd-pend-rep? yang:counter32 +--ro num-req-rcvd-pend-rep? yang:counter32
+--ro num-req-rcvd-ero-sent? yang:counter32 +--ro num-req-rcvd-ero-sent? yang:counter32
+--ro num-req-rcvd-nopath-sent? yang:counter32 +--ro num-req-rcvd-nopath-sent? yang:counter32
+--ro num-req-rcvd-cancel-sent? yang:counter32 +--ro num-req-rcvd-cancel-sent? yang:counter32
+--ro num-req-rcvd-error-sent? yang:counter32 +--ro num-req-rcvd-error-sent? yang:counter32
+--ro num-req-rcvd-cancel-rcvd? yang:counter32 +--ro num-req-rcvd-cancel-rcvd? yang:counter32
+--ro num-rep-rcvd-unknown? yang:counter32 +--ro num-rep-rcvd-unknown? yang:counter32
+--ro num-req-rcvd-unknown? yang:counter32 +--ro num-req-rcvd-unknown? yang:counter32
+--ro svec {p:svec}? +--ro svec {pcep:svec}?
| +--ro num-svec-sent? yang:counter32 | +--ro num-svec-sent? yang:counter32
| +--ro num-svec-req-sent? yang:counter32 | +--ro num-svec-req-sent? yang:counter32
| +--ro num-svec-rcvd? yang:counter32 | +--ro num-svec-rcvd? yang:counter32
| +--ro num-svec-req-rcvd? yang:counter32 | +--ro num-svec-req-rcvd? yang:counter32
+--ro stateful {p:stateful}? +--ro stateful {pcep:stateful}?
| +--ro num-pcrpt-sent? yang:counter32 | +--ro num-pcrpt-sent? yang:counter32
| +--ro num-pcrpt-rcvd? yang:counter32 | +--ro num-pcrpt-rcvd? yang:counter32
| +--ro num-pcupd-sent? yang:counter32 | +--ro num-pcupd-sent? yang:counter32
| +--ro num-pcupd-rcvd? yang:counter32 | +--ro num-pcupd-rcvd? yang:counter32
| +--ro num-rpt-sent? yang:counter32 | +--ro num-rpt-sent? yang:counter32
| +--ro num-rpt-rcvd? yang:counter32 | +--ro num-rpt-rcvd? yang:counter32
| +--ro num-rpt-rcvd-error-sent? yang:counter32 | +--ro num-rpt-rcvd-error-sent? yang:counter32
| +--ro num-upd-sent? yang:counter32 | +--ro num-upd-sent? yang:counter32
| +--ro num-upd-rcvd? yang:counter32 | +--ro num-upd-rcvd? yang:counter32
| +--ro num-upd-rcvd-unknown? yang:counter32 | +--ro num-upd-rcvd-unknown? yang:counter32
| +--ro num-upd-rcvd-undelegated? yang:counter32 | +--ro num-upd-rcvd-undelegated? yang:counter32
| +--ro num-upd-rcvd-error-sent? yang:counter32 | +--ro num-upd-rcvd-error-sent? yang:counter32
| +--ro initiation {p:pce-initiated}? | +--ro initiation {pcep:pce-initiated}?
| +--ro num-pcinitiate-sent? yang:counter32 | +--ro num-pcinitiate-sent? yang:counter32
| +--ro num-pcinitiate-rcvd? yang:counter32 | +--ro num-pcinitiate-rcvd? yang:counter32
| +--ro num-initiate-sent? yang:counter32 | +--ro num-initiate-sent? yang:counter32
| +--ro num-initiate-rcvd? yang:counter32 | +--ro num-initiate-rcvd? yang:counter32
| +--ro num-initiate-rcvd-error-sent? yang:counter32 | +--ro num-initiate-rcvd-error-sent? yang:counter32
+--ro path-key {p:path-key}? +--ro path-key {pcep:path-key}?
| +--ro num-unknown-path-key? yang:counter32 | +--ro num-unknown-path-key? yang:counter32
| +--ro num-exp-path-key? yang:counter32 | +--ro num-exp-path-key? yang:counter32
| +--ro num-dup-path-key? yang:counter32 | +--ro num-dup-path-key? yang:counter32
| +--ro num-path-key-no-attempt? yang:counter32 | +--ro num-path-key-no-attempt? yang:counter32
+--ro num-req-sent-closed? yang:counter32 +--ro num-req-sent-closed? yang:counter32
+--ro num-req-rcvd-closed? yang:counter32 +--ro num-req-rcvd-closed? yang:counter32
augment /p:pcep/p:entity/p:peers/p:peer/p:sessions/p:session: augment /pcep:pcep/pcep:entity/pcep:peers/pcep:peer/pcep:sessions
/pcep:session:
+--ro pcep-stats +--ro pcep-stats
+--ro avg-rsp-time? uint32 +--ro avg-rsp-time? uint32
+--ro lwm-rsp-time? uint32 +--ro lwm-rsp-time? uint32
+--ro hwm-rsp-time? uint32 +--ro hwm-rsp-time? uint32
+--ro num-pcreq-sent? yang:counter32 +--ro num-pcreq-sent? yang:counter32
+--ro num-pcreq-rcvd? yang:counter32 +--ro num-pcreq-rcvd? yang:counter32
+--ro num-pcrep-sent? yang:counter32 +--ro num-pcrep-sent? yang:counter32
+--ro num-pcrep-rcvd? yang:counter32 +--ro num-pcrep-rcvd? yang:counter32
+--ro num-pcerr-sent? yang:counter32 +--ro num-pcerr-sent? yang:counter32
+--ro num-pcerr-rcvd? yang:counter32 +--ro num-pcerr-rcvd? yang:counter32
skipping to change at page 19, line 27 skipping to change at page 26, line 34
+--ro num-req-sent-cancel-sent? yang:counter32 +--ro num-req-sent-cancel-sent? yang:counter32
+--ro num-req-rcvd? yang:counter32 +--ro num-req-rcvd? yang:counter32
+--ro num-req-rcvd-pend-rep? yang:counter32 +--ro num-req-rcvd-pend-rep? yang:counter32
+--ro num-req-rcvd-ero-sent? yang:counter32 +--ro num-req-rcvd-ero-sent? yang:counter32
+--ro num-req-rcvd-nopath-sent? yang:counter32 +--ro num-req-rcvd-nopath-sent? yang:counter32
+--ro num-req-rcvd-cancel-sent? yang:counter32 +--ro num-req-rcvd-cancel-sent? yang:counter32
+--ro num-req-rcvd-error-sent? yang:counter32 +--ro num-req-rcvd-error-sent? yang:counter32
+--ro num-req-rcvd-cancel-rcvd? yang:counter32 +--ro num-req-rcvd-cancel-rcvd? yang:counter32
+--ro num-rep-rcvd-unknown? yang:counter32 +--ro num-rep-rcvd-unknown? yang:counter32
+--ro num-req-rcvd-unknown? yang:counter32 +--ro num-req-rcvd-unknown? yang:counter32
+--ro svec {p:svec}? +--ro svec {pcep:svec}?
| +--ro num-svec-sent? yang:counter32 | +--ro num-svec-sent? yang:counter32
| +--ro num-svec-req-sent? yang:counter32 | +--ro num-svec-req-sent? yang:counter32
| +--ro num-svec-rcvd? yang:counter32 | +--ro num-svec-rcvd? yang:counter32
| +--ro num-svec-req-rcvd? yang:counter32 | +--ro num-svec-req-rcvd? yang:counter32
+--ro stateful {p:stateful}? +--ro stateful {pcep:stateful}?
| +--ro num-pcrpt-sent? yang:counter32 | +--ro num-pcrpt-sent? yang:counter32
| +--ro num-pcrpt-rcvd? yang:counter32 | +--ro num-pcrpt-rcvd? yang:counter32
| +--ro num-pcupd-sent? yang:counter32 | +--ro num-pcupd-sent? yang:counter32
| +--ro num-pcupd-rcvd? yang:counter32 | +--ro num-pcupd-rcvd? yang:counter32
| +--ro num-rpt-sent? yang:counter32 | +--ro num-rpt-sent? yang:counter32
| +--ro num-rpt-rcvd? yang:counter32 | +--ro num-rpt-rcvd? yang:counter32
| +--ro num-rpt-rcvd-error-sent? yang:counter32 | +--ro num-rpt-rcvd-error-sent? yang:counter32
| +--ro num-upd-sent? yang:counter32 | +--ro num-upd-sent? yang:counter32
| +--ro num-upd-rcvd? yang:counter32 | +--ro num-upd-rcvd? yang:counter32
| +--ro num-upd-rcvd-unknown? yang:counter32 | +--ro num-upd-rcvd-unknown? yang:counter32
| +--ro num-upd-rcvd-undelegated? yang:counter32 | +--ro num-upd-rcvd-undelegated? yang:counter32
| +--ro num-upd-rcvd-error-sent? yang:counter32 | +--ro num-upd-rcvd-error-sent? yang:counter32
| +--ro initiation {p:pce-initiated}? | +--ro initiation {pcep:pce-initiated}?
| +--ro num-pcinitiate-sent? yang:counter32 | +--ro num-pcinitiate-sent? yang:counter32
| +--ro num-pcinitiate-rcvd? yang:counter32 | +--ro num-pcinitiate-rcvd? yang:counter32
| +--ro num-initiate-sent? yang:counter32 | +--ro num-initiate-sent? yang:counter32
| +--ro num-initiate-rcvd? yang:counter32 | +--ro num-initiate-rcvd? yang:counter32
| +--ro num-initiate-rcvd-error-sent? yang:counter32 | +--ro num-initiate-rcvd-error-sent? yang:counter32
+--ro path-key {p:path-key}? +--ro path-key {pcep:path-key}?
+--ro num-unknown-path-key? yang:counter32 +--ro num-unknown-path-key? yang:counter32
+--ro num-exp-path-key? yang:counter32 +--ro num-exp-path-key? yang:counter32
+--ro num-dup-path-key? yang:counter32 +--ro num-dup-path-key? yang:counter32
+--ro num-path-key-no-attempt? yang:counter32 +--ro num-path-key-no-attempt? yang:counter32
7. Advanced PCE Features 7. Advanced PCE Features
This document contains a specification of the base PCEP YANG module, This document contains a specification of the base PCEP YANG module,
"ietf-pcep" which provides the basic PCEP [RFC5440] data model. "ietf-pcep" which provides the basic PCEP [RFC5440] data model.
skipping to change at page 21, line 36 skipping to change at page 29, line 4
PCEP over TLS clients. The TLS client MUST send the TLS ClientHello PCEP over TLS clients. The TLS client MUST send the TLS ClientHello
message to begin the TLS handshake. The TLS server MUST send a message to begin the TLS handshake. The TLS server MUST send a
CertificateRequest in order to request a certificate from the TLS CertificateRequest in order to request a certificate from the TLS
client. Once the TLS handshake has finished, the client and the client. Once the TLS handshake has finished, the client and the
server MAY begin to exchange PCEP messages. Client and server server MAY begin to exchange PCEP messages. Client and server
identity verification is done before the PCEP open message is sent. identity verification is done before the PCEP open message is sent.
This means that the identity verification is completed before the This means that the identity verification is completed before the
PCEP session is started.. PCEP session is started..
10. PCEP YANG Modules 10. PCEP YANG Modules
10.1. ietf-pcep module 10.1. ietf-pcep module
RFC Ed.: In this section, replace all occurrences of 'XXXX' with the RFC Ed.: In this section, replace all occurrences of 'XXXX' with the
actual RFC number and all occurrences of the revision date below with actual RFC number and all occurrences of the revision date below with
the date of RFC publication (and remove this note). the date of RFC publication (and remove this note).
<CODE BEGINS> file "ietf-pcep@2019-03-24.yang" <CODE BEGINS> file "ietf-pcep@2019-03-26.yang"
module ietf-pcep { module ietf-pcep {
yang-version 1.1;
yang-version 1.1; namespace "urn:ietf:params:xml:ns:yang:ietf-pcep";
prefix pcep;
namespace "urn:ietf:params:xml:ns:yang:ietf-pcep";
prefix p;
import ietf-inet-types {
prefix "inet";
reference
"RFC 6991: Common YANG Data Types";
}
import ietf-yang-types {
prefix "yang";
reference
"RFC 6991: Common YANG Data Types";
}
import ietf-te { import ietf-inet-types {
prefix "te"; prefix inet;
reference reference
"I-D.ietf-teas-yang-te: A YANG Data Model for Traffic "RFC 6991: Common YANG Data Types";
}
import ietf-yang-types {
prefix yang;
reference
"RFC 6991: Common YANG Data Types";
}
import ietf-te {
prefix te;
reference
"[I-D.ietf-teas-yang-te]: A YANG Data Model for Traffic
Engineering Tunnels and Interfaces"; Engineering Tunnels and Interfaces";
} }
import ietf-te-types {
import ietf-te-types { prefix te-types;
prefix "te-types"; reference
reference "[I-D.ietf-teas-yang-te-types]: Traffic Engineering Common YANG
"I-D.ietf-teas-yang-te-types: Traffic Engineering Common YANG
Types"; Types";
} }
import ietf-key-chain {
import ietf-key-chain { prefix key-chain;
prefix "kc"; reference
reference "RFC 8177: YANG Data Model for Key Chains";
"RFC 8177: YANG Data Model for Key Chains"; }
} import ietf-netconf-acm {
prefix netconf-acm;
import ietf-netconf-acm { reference
prefix "nacm"; "RFC 8341: Network Configuration Protocol (NETCONF) Access
reference
"RFC 8341: Network Configuration Protocol (NETCONF) Access
Control Model"; Control Model";
} }
import ietf-tls-server {
import ietf-tls-server { prefix tls-server;
prefix "ts"; reference
reference "[I-D.ietf-netconf-tls-client-server]: YANG Groupings for TLS
"I-D.ietf-netconf-tls-client-server: YANG Groupings for TLS
Clients and TLS Servers"; Clients and TLS Servers";
} }
import ietf-tls-client {
import ietf-tls-client { prefix tls-client;
prefix "tc"; reference
reference "[I-D.ietf-netconf-tls-client-server]: YANG Groupings for TLS
"I-D.ietf-netconf-tls-client-server: YANG Groupings for TLS Clients and TLS Servers";
Clients and TLS Servers"; }
} import ietf-ospf {
prefix ospf;
import ietf-ospf { reference
prefix "ospf"; "[I-D.ietf-ospf-yang]: YANG Data Model for OSPF Protocol";
reference }
"I-D.ietf-ospf-yang: YANG Data Model for OSPF Protocol"; import ietf-isis {
} prefix isis;
reference
import ietf-isis { "[I-D.ietf-isis-yang-isis-cfg]: YANG Data Model for IS-IS
prefix "isis";
reference
"I-D.ietf-isis-yang-isis-cfg: YANG Data Model for IS-IS
Protocol"; Protocol";
} }
organization
"IETF PCE (Path Computation Element) Working Group";
contact organization
"WG Web: <http://tools.ietf.org/wg/pce/> "IETF PCE (Path Computation Element) Working Group";
contact
"WG Web: <https://tools.ietf.org/wg/pce/>
WG List: <mailto:pce@ietf.org> WG List: <mailto:pce@ietf.org>
Editor: Dhruv Dhody Editor: Dhruv Dhody
<mailto:dhruv.ietf@gmail.com>"; <mailto:dhruv.ietf@gmail.com>";
description
description "The YANG module defines a generic configuration and
"The YANG module defines a generic configuration and
operational model for PCEP. operational model for PCEP.
Copyright (c) 2019 IETF Trust and the persons identified as Copyright (c) 2019 IETF Trust and the persons identified as
authors of the code. All rights reserved. authors of the code. All rights reserved.
Redistribution and use in source and binary forms, with or Redistribution and use in source and binary forms, with or
without modification, is permitted pursuant to, and subject without modification, is permitted pursuant to, and subject
to the license terms contained in, the Simplified BSD License to the license terms contained in, the Simplified BSD License
set forth in Section 4.c of the IETF Trust's Legal Provisions set forth in Section 4.c of the IETF Trust's Legal Provisions
Relating to IETF Documents Relating to IETF Documents
(http://trustee.ietf.org/license-info). (http://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC XXXX; see the This version of this YANG module is part of RFC XXXX; see the
RFC itself for full legal notices."; RFC itself for full legal notices.";
revision 2019-03-24 { revision 2019-03-26 {
description "Initial revision."; description
reference "Initial revision.";
"RFC XXXX: A YANG Data Model for Path Computation reference
"RFC XXXX: A YANG Data Model for Path Computation
Element Communications Protocol (PCEP)"; Element Communications Protocol (PCEP)";
}
} /*
* Typedefs
*/
/* typedef pcep-role {
* Typedefs type enumeration {
*/ enum unknown {
typedef pcep-role { value 0;
type enumeration { description
enum unknown { "An unknown role";
value "0"; }
description enum pcc {
"An unknown role"; value 1;
} description
enum pcc { "The role of a Path Computation Client";
value "1"; }
description enum pce {
"The role of a Path Computation Client"; value 2;
} description
enum pce { "The role of Path Computation Element";
value "2"; }
description enum pcc-and-pce {
"The role of Path Computation Element"; value 3;
} description
enum pcc-and-pce { "The role of both Path Computation Client and
value "3";
description
"The role of both Path Computation Client and
Path Computation Element"; Path Computation Element";
} }
} }
description description
"The role of a PCEP speaker. "The role of a PCEP speaker.
Takes one of the following values Takes one of the following values
- unknown(0): the role is not known. - unknown(0): the role is not known.
- pcc(1): the role is of a Path Computation - pcc(1): the role is of a Path Computation
Client (PCC). Client (PCC).
- pce(2): the role is of a Path Computation - pce(2): the role is of a Path Computation
Server (PCE). Server (PCE).
- pccAndPce(3): the role is of both a PCC and - pccAndPce(3): the role is of both a PCC and
a PCE."; a PCE.";
} }
typedef pcep-oper-status { typedef pcep-oper-status {
type enumeration { type enumeration {
enum oper-status-up { enum oper-status-up {
value "1"; value 1;
description description
"The PCEP entity is active"; "The PCEP entity is active";
} }
enum oper-status-down { enum oper-status-down {
value "2"; value 2;
description description
"The PCEP entity is inactive"; "The PCEP entity is inactive";
} }
enum oper-status-going-up { enum oper-status-going-up {
value "3"; value 3;
description description
"The PCEP entity is activating"; "The PCEP entity is activating";
} }
enum oper-status-going-down { enum oper-status-going-down {
value "4"; value 4;
description description
"The PCEP entity is deactivating"; "The PCEP entity is deactivating";
} }
enum oper-status-failed { enum oper-status-failed {
value "5"; value 5;
description description
"The PCEP entity has failed and will recover "The PCEP entity has failed and will recover
when possible."; when possible.";
} }
enum oper-status-failed-perm { enum oper-status-failed-perm {
value "6"; value 6;
description description
"The PCEP entity has failed and will not recover "The PCEP entity has failed and will not recover
without operator intervention"; without operator intervention";
} }
} }
description description
"The operational status of the PCEP entity. "The operational status of the PCEP entity.
Takes one of the following values Takes one of the following values
- oper-status-up(1): Active - oper-status-up(1): Active
- oper-status-down(2): Inactive - oper-status-down(2): Inactive
- oper-status-going-up(3): Activating - oper-status-going-up(3): Activating
- oper-status-going-down(4): Deactivating - oper-status-going-down(4): Deactivating
- oper-status-failed(5): Failed - oper-status-failed(5): Failed
- oper-status-failed-perm(6): Failed Permanantly"; - oper-status-failed-perm(6): Failed Permanantly";
reference reference
"RFC 5440: Path Computation Element (PCE) Communication "RFC 5440: Path Computation Element (PCE) Communication
Protocol (PCEP)"; Protocol (PCEP)";
} }
typedef pcep-initiator {
type enumeration {
enum local {
value "1";
description
"The local PCEP entity initiated the session";
} typedef pcep-initiator {
enum remote { type enumeration {
value "2"; enum local {
description value 1;
"The remote PCEP peer initiated the session"; description
} "The local PCEP entity initiated the session";
} }
description enum remote {
"The initiator of the session, that is, whether the TCP value 2;
description
"The remote PCEP peer initiated the session";
}
}
description
"The initiator of the session, that is, whether the TCP
connection was initiated by the local PCEP entity or connection was initiated by the local PCEP entity or
the remote peer. the remote peer.
Takes one of the following values Takes one of the following values
- local(1): Initiated locally - local(1): Initiated locally
- remote(2): Initiated remotely"; - remote(2): Initiated remotely";
} }
typedef pcep-sess-state { typedef pcep-sess-state {
type enumeration { type enumeration {
enum tcp-pending { enum tcp-pending {
value "1"; value 1;
description description
"The tcp-pending state of PCEP session."; "The tcp-pending state of PCEP session.";
} }
enum open-wait { enum open-wait {
value "2"; value 2;
description description
"The open-wait state of PCEP session."; "The open-wait state of PCEP session.";
} }
enum keep-wait { enum keep-wait {
value "3"; value 3;
description description
"The keep-wait state of PCEP session."; "The keep-wait state of PCEP session.";
} }
enum session-up { enum session-up {
value "4"; value 4;
description description
"The session-up state of PCEP session."; "The session-up state of PCEP session.";
} }
} }
description description
"The current state of the session. "The current state of the session.
The set of possible states excludes the idle state The set of possible states excludes the idle state
since entries do not exist in the idle state. since entries do not exist in the idle state.
Takes one of the following values Takes one of the following values
- tcp-pending(1): PCEP TCP Pending state - tcp-pending(1): PCEP TCP Pending state
- open-wait(2): PCEP Open Wait state - open-wait(2): PCEP Open Wait state
- keep-wait(3): PCEP Keep Wait state - keep-wait(3): PCEP Keep Wait state
- session-up(4): PCEP Session Up state"; - session-up(4): PCEP Session Up state";
reference
reference "RFC 5440: Path Computation Element (PCE) Communication
"RFC 5440: Path Computation Element (PCE) Communication
Protocol (PCEP)"; Protocol (PCEP)";
} }
typedef domain-type { typedef domain-type {
type enumeration { type enumeration {
enum ospf-area { enum ospf-area {
value "1"; value 1;
description description
"The OSPF area."; "The OSPF area.";
} }
enum isis-area { enum isis-area {
value "2"; value 2;
description description
"The IS-IS area."; "The IS-IS area.";
} }
enum as { enum as {
value "3"; value 3;
description description
"The Autonomous System (AS)."; "The Autonomous System (AS).";
} }
} }
description description
"The PCE Domain Type"; "The PCE Domain Type";
} }
typedef domain-ospf-area { typedef domain-ospf-area {
type ospf:area-id-type; type ospf:area-id-type;
description description
"OSPF Area ID."; "OSPF Area ID.";
reference reference
"I-D.ietf-ospf-yang: YANG Data Model for OSPF Protocol"; "[I-D.ietf-ospf-yang]: YANG Data Model for OSPF Protocol";
} }
typedef domain-isis-area { typedef domain-isis-area {
type isis:area-address; type isis:area-address;
description description
"IS-IS Area ID."; "IS-IS Area ID.";
reference reference
"I-D.ietf-isis-yang-isis-cfg: YANG Data Model for IS-IS "[I-D.ietf-isis-yang-isis-cfg]: YANG Data Model for IS-IS
Protocol"; Protocol";
} }
typedef domain-as {
typedef domain-as { type inet:as-number;
type inet:as-number; description
description "Autonomous System number.";
"Autonomous System number."; }
}
typedef domain { typedef domain {
type union { type union {
type domain-ospf-area; type domain-ospf-area;
type domain-isis-area; type domain-isis-area;
type domain-as; type domain-as;
} }
description description
"The Domain Information"; "The Domain Information";
} }
typedef operational-state { typedef operational-state {
type enumeration { type enumeration {
enum down { enum down {
value "0"; value 0;
description description
"not active."; "not active.";
} }
enum up { enum up {
value "1"; value 1;
description description
"signalled."; "signalled.";
} }
enum active { enum active {
value "2"; value 2;
description description
"up and carrying traffic."; "up and carrying traffic.";
} }
enum going-down { enum going-down {
value "3"; value 3;
description description
"LSP is being torn down, resources are "LSP is being torn down, resources are
being released."; being released.";
} }
enum going-up { enum going-up {
value "4"; value 4;
description description
"LSP is being signalled."; "LSP is being signalled.";
} }
} }
description description
"The operational status of the LSP"; "The operational status of the LSP";
reference reference
"RFC 8231: Path Computation Element Communication Protocol "RFC 8231: Path Computation Element Communication Protocol
(PCEP) Extensions for Stateful PCE"; (PCEP) Extensions for Stateful PCE";
} }
typedef sync-state {
type enumeration { typedef sync-state {
enum pending { type enumeration {
value "0"; enum pending {
description value 0;
"The state synchronization description
"The state synchronization
has not started."; has not started.";
} }
enum ongoing { enum ongoing {
value "1"; value 1;
description description
"The state synchronization "The state synchronization
is ongoing."; is ongoing.";
} }
enum finished { enum finished {
value "2"; value 2;
description description
"The state synchronization "The state synchronization
is finished."; is finished.";
} }
} }
description description
"The LSP-DB state synchronization operational "The LSP-DB state synchronization operational
status."; status.";
reference reference
"RFC 8231: Path Computation Element Communication Protocol "RFC 8231: Path Computation Element Communication Protocol
(PCEP) Extensions for Stateful PCE"; (PCEP) Extensions for Stateful PCE";
} }
/* /*
* Features * Features
*/ */
feature svec { feature svec {
description description
"Support synchronized path computation."; "Support synchronized path computation.";
reference reference
"RFC 5440: Path Computation Element (PCE) Communication "RFC 5440: Path Computation Element (PCE) Communication
Protocol (PCEP)"; Protocol (PCEP)";
} }
feature gmpls { feature gmpls {
description description
"Support GMPLS."; "Support GMPLS.";
reference
"I-D.ietf-pce-gmpls-pcep-extensions: PCEP extensions for reference
"[I-D.ietf-pce-gmpls-pcep-extensions]: PCEP extensions for
GMPLS"; GMPLS";
} }
feature objective-function {
description feature objective-function {
"Support OF as per RFC 5541."; description
reference "Support OF as per RFC 5541.";
"RFC 5541: Encoding of Objective Functions in the Path reference
"RFC 5541: Encoding of Objective Functions in the Path
Computation Element Communication Protocol (PCEP)"; Computation Element Communication Protocol (PCEP)";
} }
feature global-concurrent { feature global-concurrent {
description description
"Support GCO as per RFC 5557."; "Support GCO as per RFC 5557.";
reference reference
"RFC 5557: Path Computation Element Communication Protocol "RFC 5557: Path Computation Element Communication Protocol
(PCEP) Requirements and Protocol Extensions in Support of (PCEP) Requirements and Protocol Extensions in Support of
Global Concurrent Optimization"; Global Concurrent Optimization";
} }
feature path-key { feature path-key {
description description
"Support path-key as per RFC 5520."; "Support path-key as per RFC 5520.";
reference reference
"RFC 5520: Preserving Topology Confidentiality in Inter- "RFC 5520: Preserving Topology Confidentiality in Inter-
Domain Path Computation Using a Path-Key-Based Mechanism"; Domain Path Computation Using a Path-Key-Based Mechanism";
} }
feature p2mp { feature p2mp {
description description
"Support P2MP as per RFC 8306."; "Support P2MP as per RFC 8306.";
reference reference
"RFC 8306: Extensions to the Path Computation Element "RFC 8306: Extensions to the Path Computation Element
Communication Protocol (PCEP) for Point-to-Multipoint Communication Protocol (PCEP) for Point-to-Multipoint
Traffic Engineering Label Switched Paths"; Traffic Engineering Label Switched Paths";
} }
feature stateful { feature stateful {
description description
"Support stateful PCE as per RFC 8231."; "Support stateful PCE as per RFC 8231.";
reference reference
"RFC 8231: Path Computation Element Communication Protocol "RFC 8231: Path Computation Element Communication Protocol
(PCEP) Extensions for Stateful PCE"; (PCEP) Extensions for Stateful PCE";
} }
feature sync-opt { feature sync-opt {
description description
"Support stateful sync optimization "Support stateful sync optimization
as per RFC 8232"; as per RFC 8232";
reference reference
"RFC 8232: Optimizations of Label Switched Path State "RFC 8232: Optimizations of Label Switched Path State
Synchronization Procedures for a Stateful PCE"; Synchronization Procedures for a Stateful PCE";
} }
feature pce-initiated { feature pce-initiated {
description description
"Support PCE-Initiated LSP as per "Support PCE-Initiated LSP as per
RFC 8281."; RFC 8281.";
reference reference
"RFC 8281: Path Computation Element Communication Protocol "RFC 8281: Path Computation Element Communication Protocol
(PCEP) Extensions for PCE-Initiated LSP Setup in a Stateful (PCEP) Extensions for PCE-Initiated LSP Setup in a Stateful
PCE Model"; PCE Model";
} }
feature tls { feature tls {
description description
"Support PCEP over TLS as per "Support PCEP over TLS as per
RFC 8253."; RFC 8253.";
reference reference
"RFC 8253: PCEPS: Usage of TLS to Provide a Secure Transport "RFC 8253: PCEPS: Usage of TLS to Provide a Secure Transport
for the Path Computation Element Communication Protocol for the Path Computation Element Communication Protocol
(PCEP)"; (PCEP)";
} }
feature sr { feature sr {
description description
"Support Segment Routing for PCE."; "Support Segment Routing for PCE.";
reference reference
"I-D.ietf-pce-segment-routing: PCEP Extensions for Segment "[I-D.ietf-pce-segment-routing]: PCEP Extensions for Segment
Routing"; Routing";
} }
feature association { feature association {
description description
"Support Association in PCEP."; "Support Association in PCEP.";
reference reference
"I-D.ietf-pce-association-group: PCEP Extensions for "[I-D.ietf-pce-association-group]: PCEP Extensions for
Establishing Relationships Between Sets of LSPs"; Establishing Relationships Between Sets of LSPs";
} }
/* /*
* Identities * Identities
*/ */
identity lsp-error { identity lsp-error {
if-feature stateful; if-feature "stateful";
description description
"Base LSP error"; "Base LSP error";
reference reference
"RFC 8231: Path Computation Element Communication Protocol "RFC 8231: Path Computation Element Communication Protocol
(PCEP) Extensions for Stateful PCE"; (PCEP) Extensions for Stateful PCE";
} }
identity no-error-lsp-error { identity no-error-lsp-error {
base lsp-error; base lsp-error;
if-feature stateful; if-feature "stateful";
description description
"No error, LSP is fine."; "No error, LSP is fine.";
reference reference
"RFC 8231: Path Computation Element Communication Protocol "RFC 8231: Path Computation Element Communication Protocol
(PCEP) Extensions for Stateful PCE"; (PCEP) Extensions for Stateful PCE";
} }
identity unknown-lsp-error { identity unknown-lsp-error {
base lsp-error; base lsp-error;
if-feature stateful; if-feature "stateful";
description description
"Unknown reason."; "Unknown reason.";
reference reference
"RFC 8231: Path Computation Element Communication Protocol "RFC 8231: Path Computation Element Communication Protocol
(PCEP) Extensions for Stateful PCE"; (PCEP) Extensions for Stateful PCE";
} }
identity limit-lsp-error { identity limit-lsp-error {
base lsp-error; base lsp-error;
if-feature stateful; if-feature "stateful";
description description
"Limit reached for PCE-controlled LSPs."; "Limit reached for PCE-controlled LSPs.";
reference reference
"RFC 8231: Path Computation Element Communication Protocol "RFC 8231: Path Computation Element Communication Protocol
(PCEP) Extensions for Stateful PCE"; (PCEP) Extensions for Stateful PCE";
} }
identity pending-lsp-error { identity pending-lsp-error {
base lsp-error; base lsp-error;
if-feature stateful; if-feature "stateful";
description description
"Too many pending LSP update requests."; "Too many pending LSP update requests.";
reference reference
"RFC 8231: Path Computation Element Communication Protocol "RFC 8231: Path Computation Element Communication Protocol
(PCEP) Extensions for Stateful PCE"; (PCEP) Extensions for Stateful PCE";
} }
identity unacceptable-lsp-error {
identity unacceptable-lsp-error { base lsp-error;
base lsp-error; if-feature "stateful";
if-feature stateful; description
description "Unacceptable parameters.";
"Unacceptable parameters."; reference
reference "RFC 8231: Path Computation Element Communication Protocol
"RFC 8231: Path Computation Element Communication Protocol
(PCEP) Extensions for Stateful PCE"; (PCEP) Extensions for Stateful PCE";
} }
identity internal-lsp-error { identity internal-lsp-error {
base lsp-error; base lsp-error;
if-feature stateful; if-feature "stateful";
description description
"Internal error."; "Internal error.";
reference reference
"RFC 8231: Path Computation Element Communication Protocol "RFC 8231: Path Computation Element Communication Protocol
(PCEP) Extensions for Stateful PCE"; (PCEP) Extensions for Stateful PCE";
} }
identity admin-lsp-error { identity admin-lsp-error {
base lsp-error; base lsp-error;
if-feature stateful; if-feature "stateful";
description description
"LSP administratively brought down."; "LSP administratively brought down.";
reference reference
"RFC 8231: Path Computation Element Communication Protocol "RFC 8231: Path Computation Element Communication Protocol
(PCEP) Extensions for Stateful PCE"; (PCEP) Extensions for Stateful PCE";
} }
identity preempted-lsp-error { identity preempted-lsp-error {
base lsp-error; base lsp-error;
if-feature stateful; if-feature "stateful";
description description
"LSP preempted."; "LSP preempted.";
reference reference
"RFC 8231: Path Computation Element Communication Protocol "RFC 8231: Path Computation Element Communication Protocol
(PCEP) Extensions for Stateful PCE"; (PCEP) Extensions for Stateful PCE";
} }
identity rsvp-lsp-error { identity rsvp-lsp-error {
base lsp-error; base lsp-error;
if-feature stateful; if-feature "stateful";
description description
"RSVP signaling error."; "RSVP signaling error.";
reference reference
"RFC 8231: Path Computation Element Communication Protocol "RFC 8231: Path Computation Element Communication Protocol
(PCEP) Extensions for Stateful PCE"; (PCEP) Extensions for Stateful PCE";
}
/* }
* Groupings
*/
grouping pce-scope{ /*
description * Groupings
"This grouping defines PCE path computation scope */
grouping pce-scope {
description
"This grouping defines PCE path computation scope
information which maybe relevant to PCE selection. information which maybe relevant to PCE selection.
This information corresponds to PCE auto-discovery This information corresponds to PCE auto-discovery
information."; information.";
reference reference
"RFC 5088: OSPF Protocol Extensions for Path "RFC 5088: OSPF Protocol Extensions for Path
Computation Element (PCE) Discovery Computation Element (PCE) Discovery
RFC 5089: IS-IS Protocol Extensions for Path RFC 5089: IS-IS Protocol Extensions for Path
Computation Element (PCE) Discovery"; Computation Element (PCE) Discovery";
leaf path-scope{ leaf path-scope {
type bits{ type bits {
bit intra-area-scope{ bit intra-area-scope {
description description
"PCE can compute intra-area paths."; "PCE can compute intra-area paths.";
} }
bit inter-area-scope{ bit inter-area-scope {
description description
"PCE can compute inter-area paths."; "PCE can compute inter-area paths.";
} }
bit inter-area-scope-default{ bit inter-area-scope-default {
description description
"PCE can act as a default PCE for inter-area "PCE can act as a default PCE for inter-area
path computation."; path computation.";
} }
bit inter-as-scope{ bit inter-as-scope {
description description
"PCE can compute inter-AS paths."; "PCE can compute inter-AS paths.";
} }
bit inter-as-scope-default{ bit inter-as-scope-default {
description description
"PCE can act as a default PCE for inter-AS "PCE can act as a default PCE for inter-AS
path computation."; path computation.";
} }
bit inter-layer-scope{ bit inter-layer-scope {
description description
"PCE can compute inter-layer paths."; "PCE can compute inter-layer paths.";
} }
} }
description description
"The field corresponding to the path scope bits"; "The field corresponding to the path scope bits";
}
leaf intra-area-pref{ }
type uint8{ leaf intra-area-pref {
range "0..7"; type uint8 {
} range "0..7";
description }
"The PCE's preference for intra-area TE LSP description
"The PCE's preference for intra-area TE LSP
computation."; computation.";
} }
leaf inter-area-pref {
leaf inter-area-pref{ type uint8 {
type uint8{ range "0..7";
range "0..7"; }
} description
description "The PCE's preference for inter-area TE LSP
"The PCE's preference for inter-area TE LSP
computation."; computation.";
} }
leaf inter-as-pref {
leaf inter-as-pref{ type uint8 {
type uint8{ range "0..7";
range "0..7"; }
} description
description "The PCE's preference for inter-AS TE LSP
"The PCE's preference for inter-AS TE LSP
computation."; computation.";
} }
leaf inter-layer-pref {
leaf inter-layer-pref{ type uint8 {
type uint8{ range "0..7";
range "0..7"; }
} description
description "The PCE's preference for inter-layer TE LSP
"The PCE's preference for inter-layer TE LSP
computation."; computation.";
} }
}//pce-scope }
grouping domain{ //pce-scope
description
"This grouping specifies a Domain where the grouping domain {
description
"This grouping specifies a Domain where the
PCEP speaker has topology visibility."; PCEP speaker has topology visibility.";
leaf domain-type{ leaf domain-type {
type domain-type; type domain-type;
description description
"The domain type."; "The domain type.";
} }
leaf domain{ leaf domain {
type domain; type domain;
description description
"The domain Information."; "The domain Information.";
} }
}//domain }
grouping info{ //domain
description
"This grouping specifies all information which grouping info {
description
"This grouping specifies all information which
maybe relevant to both PCC and PCE. maybe relevant to both PCC and PCE.
This information corresponds to PCE auto-discovery This information corresponds to PCE auto-discovery
information."; information.";
container domain{ container domain {
description description
"The local domain for the PCEP entity"; "The local domain for the PCEP entity";
list domain{ list domain {
key "domain-type domain"; key "domain-type domain";
description description
"The local domain."; "The local domain.";
uses domain{ uses domain {
description description
"The local domain for the PCEP entity."; "The local domain for the PCEP entity.";
} }
} }
} }
container capability{ container capability {
description description
"The PCEP entity capability information of local "The PCEP entity capability information of local
PCEP entity. This maybe relevant to PCE selection PCEP entity. This maybe relevant to PCE selection
as well. This information corresponds to PCE auto- as well. This information corresponds to PCE auto-
discovery information."; discovery information.";
reference reference
"RFC 5088: OSPF Protocol Extensions for Path "RFC 5088: OSPF Protocol Extensions for Path
Computation Element (PCE) Discovery Computation Element (PCE) Discovery
RFC 5089: IS-IS Protocol Extensions for Path RFC 5089: IS-IS Protocol Extensions for Path
Computation Element (PCE) Discovery"; Computation Element (PCE) Discovery";
leaf capability{ leaf capability {
type bits{ type bits {
bit gmpls{ bit gmpls {
if-feature gmpls; if-feature "gmpls";
description description
"Path computation with GMPLS link "Path computation with GMPLS link
constraints."; constraints.";
} }
bit bi-dir{ bit bi-dir {
description description
"Bidirectional path computation."; "Bidirectional path computation.";
}
bit diverse{ }
description bit diverse {
"Diverse path computation."; description
} "Diverse path computation.";
bit load-balance{ }
description bit load-balance {
"Load-balanced path computation."; description
} "Load-balanced path computation.";
bit synchronize{ }
if-feature svec; bit synchronize {
description if-feature "svec";
"Synchronized paths computation."; description
} "Synchronized paths computation.";
bit objective-function{ }
if-feature objective-function; bit objective-function {
description if-feature "objective-function";
"Support for multiple objective functions."; description
} "Support for multiple objective functions.";
bit add-path-constraint{ }
description bit add-path-constraint {
"Support for additive path constraints (max description
"Support for additive path constraints (max
hop count, etc.)."; hop count, etc.).";
} }
bit prioritization{ bit prioritization {
description description
"Support for request prioritization."; "Support for request prioritization.";
} }
bit multi-request{ bit multi-request {
description description
"Support for multiple requests per message."; "Support for multiple requests per message.";
} }
bit global-concurrent{ bit global-concurrent {
if-feature global-concurrent; if-feature "global-concurrent";
description description
"Support for Global Concurrent Optimization "Support for Global Concurrent Optimization
(GCO)."; (GCO).";
} }
bit p2mp{ bit p2mp {
if-feature p2mp; if-feature "p2mp";
description description
"Support for P2MP path computation."; "Support for P2MP path computation.";
} }
bit active{ bit active {
if-feature stateful; if-feature "stateful";
description description
"Support for active stateful PCE."; "Support for active stateful PCE.";
} }
bit passive{ bit passive {
if-feature stateful; if-feature "stateful";
description description
"Support for passive stateful PCE."; "Support for passive stateful PCE.";
} }
bit p2mp-active{ bit p2mp-active {
if-feature stateful; if-feature "stateful";
if-feature p2mp; if-feature "p2mp";
description description
"Support for active stateful PCE for P2MP."; "Support for active stateful PCE for P2MP.";
} }
bit p2mp-passive{ bit p2mp-passive {
if-feature stateful; if-feature "stateful";
if-feature p2mp; if-feature "p2mp";
description description
"Support for passive stateful PCE for P2MP."; "Support for passive stateful PCE for P2MP.";
} }
bit p2mp-pce-initiated{ bit p2mp-pce-initiated {
if-feature stateful; if-feature "stateful";
if-feature pce-initiated; if-feature "pce-initiated";
if-feature p2mp; if-feature "p2mp";
description description
"Support for PCE-initiated LSP for P2MP."; "Support for PCE-initiated LSP for P2MP.";
} }
} }
description description
"The bits string indicating the capabiliies"; "The bits string indicating the capabiliies";
reference reference
"RFC 5088: OSPF Protocol Extensions for Path "RFC 5088: OSPF Protocol Extensions for Path
Computation Element (PCE) Discovery Computation Element (PCE) Discovery
RFC 5089: IS-IS Protocol Extensions for Path RFC 5089: IS-IS Protocol Extensions for Path
Computation Element (PCE) Discovery"; Computation Element (PCE) Discovery";
} }
leaf pce-initiated{ leaf pce-initiated {
if-feature pce-initiated; if-feature "pce-initiated";
type boolean; type boolean;
description description
"Set to true if PCE-initiated LSP capability is "Set to true if PCE-initiated LSP capability is
enabled."; enabled.";
reference reference
"RFC 8281: Path Computation Element Communication "RFC 8281: Path Computation Element Communication
Protocol (PCEP) Extensions for PCE-Initiated LSP Protocol (PCEP) Extensions for PCE-Initiated LSP
Setup in a Stateful PCE Model"; Setup in a Stateful PCE Model";
} }
leaf include-db-ver{ leaf include-db-ver {
if-feature stateful; if-feature "stateful";
if-feature sync-opt; if-feature "sync-opt";
type boolean; type boolean;
description description
"Support inclusion of LSP-DB-VERSION "Support inclusion of LSP-DB-VERSION
in LSP object"; in LSP object";
reference reference
"RFC 8232: Optimizations of Label Switched Path State "RFC 8232: Optimizations of Label Switched Path State
Synchronization Procedures for a Stateful PCE"; Synchronization Procedures for a Stateful PCE";
} }
leaf trigger-resync{ leaf trigger-resync {
if-feature stateful; if-feature "stateful";
if-feature sync-opt; if-feature "sync-opt";
type boolean; type boolean;
description description
"Support PCE triggered re-synchronization"; "Support PCE triggered re-synchronization";
reference reference
"RFC 8232: Optimizations of Label Switched Path State "RFC 8232: Optimizations of Label Switched Path State
Synchronization Procedures for a Stateful PCE"; Synchronization Procedures for a Stateful PCE";
} }
leaf trigger-initial-sync{ leaf trigger-initial-sync {
if-feature stateful; if-feature "stateful";
if-feature sync-opt; if-feature "sync-opt";
type boolean; type boolean;
description description
"PCE triggered initial synchronization"; "PCE triggered initial synchronization";
reference reference
"RFC 8232: Optimizations of Label Switched Path State "RFC 8232: Optimizations of Label Switched Path State
Synchronization Procedures for a Stateful PCE"; Synchronization Procedures for a Stateful PCE";
} }
leaf incremental-sync{ leaf incremental-sync {
if-feature stateful; if-feature "stateful";
if-feature sync-opt; if-feature "sync-opt";
type boolean; type boolean;
description description
"Support incremental (delta) sync"; "Support incremental (delta) sync";
reference reference
"RFC 8232: Optimizations of Label Switched Path State "RFC 8232: Optimizations of Label Switched Path State
Synchronization Procedures for a Stateful PCE"; Synchronization Procedures for a Stateful PCE";
} }
container sr{ container sr {
if-feature sr; if-feature "sr";
description description
"If segment routing is supported"; "If segment routing is supported";
reference reference
"I-D.ietf-pce-segment-routing: PCEP Extensions for Segment "[I-D.ietf-pce-segment-routing]: PCEP Extensions for Segment
Routing"; Routing";
leaf enabled{ leaf enabled {
type boolean; type boolean;
description description
"Set to true if SR is enabled"; "Set to true if SR is enabled";
}
leaf msd-limit{ }
type boolean; leaf msd-limit {
default false; type boolean;
description default "false";
"True indicates no limit on MSD, the description
"True indicates no limit on MSD, the
leaf msd is ignored"; leaf msd is ignored";
} }
leaf nai{ leaf nai {
type boolean; type boolean;
default false; default "false";
description description
"True indicates capability to resolve NAI "True indicates capability to resolve NAI
to SID"; to SID";
} }
}//sr }
}//capability //sr
leaf msd{ }
if-feature sr; //capability
type uint8; leaf msd {
description if-feature "sr";
"Maximum SID Depth for SR"; type uint8;
reference description
"I-D.ietf-pce-segment-routing: PCEP Extensions for Segment "Maximum SID Depth for SR";
reference
"[I-D.ietf-pce-segment-routing]: PCEP Extensions for Segment
Routing"; Routing";
} }
}//info }
grouping pce-info{ //info
description
"This grouping specifies all PCE information grouping pce-info {
description
"This grouping specifies all PCE information
which maybe relevant to the PCE selection. which maybe relevant to the PCE selection.
This information corresponds to PCE auto-discovery This information corresponds to PCE auto-discovery
information."; information.";
container scope{ container scope {
description description
"The path computation scope"; "The path computation scope";
uses pce-scope; uses pce-scope;
} }
container neigh-domains {
container neigh-domains{ description
description "The list of neighbour PCE-Domain
"The list of neighbour PCE-Domain
toward which a PCE can compute toward which a PCE can compute
paths"; paths";
list domain{
key "domain-type domain";
description
"The neighbour domain.";
uses domain{ list domain {
description key "domain-type domain";
"The PCE neighbour domain."; description
} "The neighbour domain.";
} uses domain {
} description
}//pce-info "The PCE neighbour domain.";
}
}
}
}
grouping notification-instance-hdr { //pce-info
description
"This group describes common instance specific data grouping notification-instance-hdr {
description
"This group describes common instance specific data
for notifications."; for notifications.";
leaf peer-addr {
type leafref {
path "/pcep/entity/peers/peer/addr";
}
description
"Reference to peer address";
}
}
leaf peer-addr { // notification-instance-hdr
type leafref {
path "/pcep/entity/peers/peer/addr";
}
description
"Reference to peer address";
}
}// notification-instance-hdr
grouping notification-session-hdr { grouping notification-session-hdr {
description description
"This group describes common session instance specific "This group describes common session instance specific
data for notifications."; data for notifications.";
leaf session-initiator {
type leafref {
path "/pcep/entity/peers/peer/sessions/"
+ "session/initiator";
}
description
"Reference to pcep session initiator leaf";
}
}
leaf session-initiator { // notification-session-hdr
type leafref {
path "/pcep/entity/peers/peer/sessions/" +
"session/initiator";
}
description
"Reference to pcep session initiator leaf";
}
}// notification-session-hdr
grouping of-list { grouping of-list {
description description
"List of OF"; "List of OF";
reference
"RFC 5541: Encoding of Objective Functions in the Path
Computation Element Communication Protocol (PCEP)";
list objective-function{
key "of";
description
"The list of authorized OF";
leaf of {
type identityref{
base te-types:objective-function-type;
}
description
"The OF authorized";
}
}
}
/* reference
* Configuration data nodes "RFC 5541: Encoding of Objective Functions in the Path
*/ Computation Element Communication Protocol (PCEP)";
container pcep{ list objective-function {
key "of";
description
"The list of authorized OF";
leaf of {
type identityref {
base te-types:objective-function-type;
}
description
"The OF authorized";
}
}
}
presence /*
"The PCEP is enabled"; * Configuration data nodes
*/
description container pcep {
"Parameters for list of configured PCEP entities presence "The PCEP is enabled";
description
"Parameters for list of configured PCEP entities
on the device."; on the device.";
container entity {
container entity { description
description "The configured PCEP entity on the device.";
"The configured PCEP entity on the device."; leaf addr {
type inet:ip-address;
leaf addr { mandatory true;
type inet:ip-address; description
mandatory true; "The local Internet address of this PCEP entity.
description
"The local Internet address of this PCEP entity.
If operating as a PCE server, the PCEP entity If operating as a PCE server, the PCEP entity
listens on this address. If operating as a PCC, listens on this address. If operating as a PCC,
the PCEP entity binds outgoing TCP connections the PCEP entity binds outgoing TCP connections
to this address. It is possible for the PCEP entity to this address. It is possible for the PCEP entity
to operate both as a PCC and a PCE Server, in which to operate both as a PCC and a PCE Server, in which
case it uses this address both to listen for incoming case it uses this address both to listen for incoming
TCP connections and to bind outgoing TCP connections."; TCP connections and to bind outgoing TCP connections.";
} }
leaf enabled {
leaf enabled { type boolean;
type boolean; default "true";
default true; description
description "The administrative status of this PCEP
"The administrative status of this PCEP
Entity."; Entity.";
}
leaf role { }
type pcep-role; leaf role {
mandatory true; type pcep-role;
description mandatory true;
"The role that this entity can play. description
"The role that this entity can play.
Takes one of the following values. Takes one of the following values.
- unknown(0): this PCEP Entity role is not - unknown(0): this PCEP Entity role is not
known. known.
- pcc(1): this PCEP Entity is a PCC. - pcc(1): this PCEP Entity is a PCC.
- pce(2): this PCEP Entity is a PCE. - pce(2): this PCEP Entity is a PCE.
- pcc-and-pce(3): this PCEP Entity is both - pcc-and-pce(3): this PCEP Entity is both
a PCC and a PCE."; a PCC and a PCE.";
} }
leaf description {
leaf description { type string;
type string; description
description "Description of the PCEP entity configured
"Description of the PCEP entity configured
by the user"; by the user";
} }
leaf speaker-entity-id {
leaf speaker-entity-id{ if-feature "sync-opt";
if-feature sync-opt; type string;
type string; description
description "The Speaker Entity Identifier";
"The Speaker Entity Identifier"; reference
reference "RFC 8232: Optimizations of Label Switched
"RFC 8232: Optimizations of Label Switched
Path State Synchronization Procedures for Path State Synchronization Procedures for
a Stateful PCE"; a Stateful PCE";
} }
leaf admin-status {
leaf admin-status { type boolean;
type boolean; default "true";
default true; description
description "The administrative status of this PCEP Entity.
"The administrative status of this PCEP Entity.
The value true represents admin status as up. The value true represents admin status as up.
This is the desired operational status as This is the desired operational status as
currently set by an operator or by default in currently set by an operator or by default in
the implementation. The value of oper-status the implementation. The value of oper-status
represents the current status of an attempt to represents the current status of an attempt to
reach this desired status."; reach this desired status.";
} }
leaf index {
leaf index{ type uint32;
type uint32; config false;
config "false"; description
description "The index of the operational PECP entity";
"The index of the operational PECP entity"; }
} leaf oper-status {
type pcep-oper-status;
leaf oper-status { config false;
type pcep-oper-status; description
config "false"; "The operational status of the PCEP entity.
description
"The operational status of the PCEP entity.
Takes one of the following values. Takes one of the following values.
- oper-status-up(1): the PCEP entity is active. - oper-status-up(1): the PCEP entity is active.
- oper-status-down(2): the PCEP entity is inactive. - oper-status-down(2): the PCEP entity is inactive.
- oper-status-going-up(3): the PCEP entity is - oper-status-going-up(3): the PCEP entity is
activating. activating.
- oper-status-going-down(4): the PCEP entity is - oper-status-going-down(4): the PCEP entity is
deactivating. deactivating.
- oper-status-failed(5): the PCEP entity has - oper-status-failed(5): the PCEP entity has
failed and will recover when possible. failed and will recover when possible.
- oper-status-failed-perm(6): the PCEP entity - oper-status-failed-perm(6): the PCEP entity
has failed and will not recover without has failed and will not recover without
operator intervention."; operator intervention.";
} }
uses info {
uses info { description
description "Local PCEP entity information";
"Local PCEP entity information"; }
} container pce-info {
when "../role = 'pce'"
container pce-info { + "or "
when "../role = 'pce'" + + "../role = 'pcc-and-pce'" {
"or " + description
"../role = 'pcc-and-pce'" "These fields are applicable when the role is PCE.";
{ }
description description
"These fields are applicable when the role is PCE."; "The Local PCE Entity PCE information";
} uses pce-info {
description description
"The Local PCE Entity PCE information"; "Local PCE information";
uses pce-info { }
description container path-key {
"Local PCE information"; if-feature "path-key";
} description
container path-key { "Path-Key Configuration";
if-feature path-key; reference
description "RFC 5520: Preserving Topology Confidentiality in Inter-
"Path-Key Configuration";
reference
"RFC 5520: Preserving Topology Confidentiality in Inter-
Domain Path Computation Using a Path-Key-Based Mechanism"; Domain Path Computation Using a Path-Key-Based Mechanism";
leaf enabled {
leaf enabled { type boolean;
type boolean; description
description "Enabled or Disabled";
"Enabled or Disabled"; }
} leaf discard-timer {
leaf discard-timer { type uint32;
type uint32; units "minutes";
units "minutes"; default "10";
default 10; description
description "A timer to discard unwanted path-keys";
"A timer to discard unwanted path-keys"; }
} leaf reuse-time {
leaf reuse-time { type uint32;
type uint32; units "minutes";
units "minutes"; default "30";
default 30; description
description "A time after which the path-keys could be reused";
"A time after which the path-keys could be reused"; }
} leaf pce-id {
leaf pce-id { type inet:ip-address;
type inet:ip-address; description
description "PCE Address to be used in each Path-Key Subobject
"PCE Address to be used in each Path-Key Subobject
(PKS)"; (PKS)";
} }
} }
} }
leaf connect-timer { leaf connect-timer {
type uint16 { type uint16 {
range "1..65535"; range "1..65535";
} }
units "seconds"; units "seconds";
default 60; default "60";
description description
"The time in seconds that the PCEP entity will wait "The time in seconds that the PCEP entity will wait
to establish a TCP connection with a peer. If a to establish a TCP connection with a peer. If a
TCP connection is not established within this time TCP connection is not established within this time
then PCEP aborts the session setup attempt."; then PCEP aborts the session setup attempt.";
reference reference
"RFC 5440: Path Computation Element (PCE) Communication "RFC 5440: Path Computation Element (PCE) Communication
Protocol (PCEP)"; Protocol (PCEP)";
} }
leaf connect-max-retry { leaf connect-max-retry {
type uint32; type uint32;
default 5; default "5";
description description
"The maximum number of times the system tries to "The maximum number of times the system tries to
establish a TCP connection to a peer before the establish a TCP connection to a peer before the
session with the peer transitions to the idle session with the peer transitions to the idle
state."; state.";
reference reference
"RFC 5440: Path Computation Element (PCE) Communication "RFC 5440: Path Computation Element (PCE) Communication
Protocol (PCEP)"; Protocol (PCEP)";
} }
leaf init-backoff-timer {
leaf init-backoff-timer { type uint16 {
type uint16 { range "1..65535";
range "1..65535"; }
} units "seconds";
units "seconds"; description
description "The initial back-off time in seconds for retrying
"The initial back-off time in seconds for retrying
a failed session setup attempt to a peer. a failed session setup attempt to a peer.
The back-off time increases for each failed The back-off time increases for each failed
session setup attempt, until a maximum back-off session setup attempt, until a maximum back-off
time is reached. The maximum back-off time is time is reached. The maximum back-off time is
max-backoff-timer."; max-backoff-timer.";
reference reference
"RFC 5440: Path Computation Element (PCE) Communication "RFC 5440: Path Computation Element (PCE) Communication
Protocol (PCEP)"; Protocol (PCEP)";
} }
leaf max-backoff-timer {
leaf max-backoff-timer { type uint32;
type uint32; units "seconds";
units "seconds"; description
description "The maximum back-off time in seconds for retrying
"The maximum back-off time in seconds for retrying
a failed session setup attempt to a peer. a failed session setup attempt to a peer.
The back-off time increases for each failed session The back-off time increases for each failed session
setup attempt, until this maximum value is reached. setup attempt, until this maximum value is reached.
Session setup attempts then repeat periodically Session setup attempts then repeat periodically
without any further increase in back-off time."; without any further increase in back-off time.";
reference reference
"RFC 5440: Path Computation Element (PCE) Communication "RFC 5440: Path Computation Element (PCE) Communication
Protocol (PCEP)"; Protocol (PCEP)";
} }
leaf open-wait-timer {
leaf open-wait-timer { type uint16 {
type uint16 { range "1..65535";
range "1..65535"; }
} units "seconds";
units "seconds"; default "60";
default 60; description
description "The time in seconds that the PCEP entity will wait
"The time in seconds that the PCEP entity will wait
to receive an Open message from a peer after the to receive an Open message from a peer after the
TCP connection has come up. TCP connection has come up.
If no Open message is received within this time then If no Open message is received within this time then
PCEP terminates the TCP connection and deletes the PCEP terminates the TCP connection and deletes the
associated sessions."; associated sessions.";
reference reference
"RFC 5440: Path Computation Element (PCE) Communication "RFC 5440: Path Computation Element (PCE) Communication
Protocol (PCEP)"; Protocol (PCEP)";
} }
leaf keep-wait-timer {
leaf keep-wait-timer { type uint16 {
type uint16 { range "1..65535";
range "1..65535"; }
} units "seconds";
units "seconds"; default "60";
default 60; description
description "The time in seconds that the PCEP entity will wait
"The time in seconds that the PCEP entity will wait
to receive a Keepalive or PCErr message from a peer to receive a Keepalive or PCErr message from a peer
during session initialization after receiving an during session initialization after receiving an
Open message. If no Keepalive or PCErr message is Open message. If no Keepalive or PCErr message is
received within this time then PCEP terminates the received within this time then PCEP terminates the
TCP connection and deletes the associated TCP connection and deletes the associated
sessions."; sessions.";
reference reference
"RFC 5440: Path Computation Element (PCE) Communication "RFC 5440: Path Computation Element (PCE) Communication
Protocol (PCEP)"; Protocol (PCEP)";
} }
leaf keep-alive-timer {
leaf keep-alive-timer { type uint8;
type uint8; units "seconds";
units "seconds"; default "30";
default 30; description
description "The keep alive transmission timer that this PCEP
"The keep alive transmission timer that this PCEP
entity will propose in the initial OPEN message of entity will propose in the initial OPEN message of
each session it is involved in. This is the each session it is involved in. This is the
maximum time between two consecutive messages sent maximum time between two consecutive messages sent
to a peer. Zero means that the PCEP entity prefers to a peer. Zero means that the PCEP entity prefers
not to send Keepalives at all. not to send Keepalives at all.
Note that the actual Keepalive transmission Note that the actual Keepalive transmission
intervals, in either direction of an active PCEP intervals, in either direction of an active PCEP
session, are determined by negotiation between the session, are determined by negotiation between the
peers as specified by RFC 5440, and so may differ peers as specified by RFC 5440, and so may differ
from this configured value."; from this configured value.";
reference reference
"RFC 5440: Path Computation Element (PCE) Communication "RFC 5440: Path Computation Element (PCE) Communication
Protocol (PCEP)"; Protocol (PCEP)";
} }
leaf dead-timer { leaf dead-timer {
type uint8; type uint8;
units "seconds"; units "seconds";
must "(. > ../keep-alive-timer)" { must '(. > ../keep-alive-timer)' {
error-message "The dead timer must be " error-message "The dead timer must be "
+ "larger than the keep alive timer"; + "larger than the keep alive timer";
} }
default 120; default "120";
description description
"The dead timer that this PCEP entity will propose "The dead timer that this PCEP entity will propose
in the initial OPEN message of each session it is in the initial OPEN message of each session it is
involved in. This is the time after which a peer involved in. This is the time after which a peer
should declare a session down if it does not should declare a session down if it does not
receive any PCEP messages. Zero suggests that the receive any PCEP messages. Zero suggests that the
peer does not run a dead timer at all."; peer does not run a dead timer at all.";
reference reference
"RFC 5440: Path Computation Element (PCE) Communication "RFC 5440: Path Computation Element (PCE) Communication
Protocol (PCEP)"; Protocol (PCEP)";
} }
leaf allow-negotiation {
leaf allow-negotiation{ type boolean;
type boolean; description
description "Whether the PCEP entity will permit negotiation of
"Whether the PCEP entity will permit negotiation of
session parameters."; session parameters.";
} }
leaf max-keep-alive-timer {
leaf max-keep-alive-timer{ type uint8;
type uint8; units "seconds";
units "seconds"; description
description "In PCEP session parameter negotiation in seconds,
"In PCEP session parameter negotiation in seconds,
the maximum value that this PCEP entity will the maximum value that this PCEP entity will
accept from a peer for the interval between accept from a peer for the interval between
Keepalive transmissions. Zero means that the PCEP Keepalive transmissions. Zero means that the PCEP
entity will allow no Keepalive transmission at entity will allow no Keepalive transmission at
all."; all.";
} }
leaf max-dead-timer {
leaf max-dead-timer{ type uint8;
type uint8; units "seconds";
units "seconds"; description
description "In PCEP session parameter negotiation in seconds,
"In PCEP session parameter negotiation in seconds,
the maximum value that this PCEP entity will accept the maximum value that this PCEP entity will accept
from a peer for the Dead timer. Zero means that from a peer for the Dead timer. Zero means that
the PCEP entity will allow not running a Dead the PCEP entity will allow not running a Dead
timer."; timer.";
}
} leaf min-keep-alive-timer {
type uint8;
leaf min-keep-alive-timer{ units "seconds";
type uint8; description
units "seconds"; "In PCEP session parameter negotiation in seconds,
description
"In PCEP session parameter negotiation in seconds,
the minimum value that this PCEP entity will the minimum value that this PCEP entity will
accept for the interval between Keepalive accept for the interval between Keepalive
transmissions. Zero means that the PCEP entity transmissions. Zero means that the PCEP entity
insists on no Keepalive transmission at all."; insists on no Keepalive transmission at all.";
} }
leaf min-dead-timer {
leaf min-dead-timer{ type uint8;
type uint8; units "seconds";
units "seconds"; description
description "In PCEP session parameter negotiation in
"In PCEP session parameter negotiation in
seconds, the minimum value that this PCEP entity seconds, the minimum value that this PCEP entity
will accept for the Dead timer. Zero means that will accept for the Dead timer. Zero means that
the PCEP entity insists on not running a Dead the PCEP entity insists on not running a Dead
timer."; timer.";
} }
leaf sync-timer {
leaf sync-timer{ if-feature "svec";
if-feature svec; type uint16;
type uint16; units "seconds";
units "seconds"; default "60";
default 60; description
description "The value of SyncTimer in seconds is used in the
"The value of SyncTimer in seconds is used in the
case of synchronized path computation request case of synchronized path computation request
using the SVEC object. Consider the case where a using the SVEC object. Consider the case where a
PCReq message is received by a PCE that contains PCReq message is received by a PCE that contains
the SVEC object referring to M synchronized path the SVEC object referring to M synchronized path
computation requests. If after the expiration of computation requests. If after the expiration of
the SyncTimer all the M path computation requests the SyncTimer all the M path computation requests
have not been, received a protocol error is have not been, received a protocol error is
triggered and the PCE MUST cancel the whole set triggered and the PCE MUST cancel the whole set
of path computation requests. of path computation requests.
The aim of the SyncTimer is to avoid the storage The aim of the SyncTimer is to avoid the storage
of unused synchronized requests should one of of unused synchronized requests should one of
them get lost for some reasons (for example, a them get lost for some reasons (for example, a
misbehaving PCC). misbehaving PCC).
Zero means that the PCEP entity does not use the Zero means that the PCEP entity does not use the
SyncTimer."; SyncTimer.";
reference reference
"RFC 5440: Path Computation Element (PCE) "RFC 5440: Path Computation Element (PCE)
Communication Protocol (PCEP)"; Communication Protocol (PCEP)";
} }
leaf request-timer {
leaf request-timer{ type uint16 {
type uint16 { range "1..65535";
range "1..65535"; }
} units "seconds";
units "seconds"; description
description "The maximum time that the PCEP entity will wait
"The maximum time that the PCEP entity will wait
for a response to a PCReq message."; for a response to a PCReq message.";
} }
leaf max-sessions {
leaf max-sessions{ type uint32;
type uint32; description
description "Maximum number of sessions involving this PCEP
"Maximum number of sessions involving this PCEP
entity that can exist at any time."; entity that can exist at any time.";
} }
leaf max-unknown-reqs {
leaf max-unknown-reqs{ type uint32;
type uint32; default "5";
default 5; description
description "The maximum number of unrecognized requests and
"The maximum number of unrecognized requests and
replies that any session on this PCEP entity is replies that any session on this PCEP entity is
willing to accept per minute before terminating willing to accept per minute before terminating
the session. the session.
A PCRep message contains an unrecognized reply A PCRep message contains an unrecognized reply
if it contains an RP object whose request ID if it contains an RP object whose request ID
does not correspond to any in-progress request does not correspond to any in-progress request
sent by this PCEP entity. sent by this PCEP entity.
A PCReq message contains an unrecognized request A PCReq message contains an unrecognized request
if it contains an RP object whose request ID is if it contains an RP object whose request ID is
zero."; zero.";
reference reference
"RFC 5440: Path Computation Element (PCE) "RFC 5440: Path Computation Element (PCE)
Communication Protocol (PCEP)"; Communication Protocol (PCEP)";
} }
leaf max-unknown-msgs {
leaf max-unknown-msgs{ type uint32;
type uint32; default "5";
default 5; description
description "The maximum number of unknown messages that any
"The maximum number of unknown messages that any
session on this PCEP entity is willing to accept session on this PCEP entity is willing to accept
per minute before terminating the session."; per minute before terminating the session.";
reference reference
"RFC 5440: Path Computation Element (PCE) "RFC 5440: Path Computation Element (PCE)
Communication Protocol (PCEP)"; Communication Protocol (PCEP)";
} }
leaf pcep-notification-max-rate {
leaf pcep-notification-max-rate { type uint32;
type uint32; mandatory true;
mandatory true; description
description "This variable indicates the maximum number of
"This variable indicates the maximum number of
notifications issued per second. If events notifications issued per second. If events
occur more rapidly, the implementation may occur more rapidly, the implementation may
simply fail to emit these notifications during simply fail to emit these notifications during
that period, or may queue them until an that period, or may queue them until an
appropriate time. A value of 0 means no appropriate time. A value of 0 means no
notifications are emitted and all should be notifications are emitted and all should be
discarded (that is, not queued)."; discarded (that is, not queued).";
} }
container stateful-parameter{ container stateful-parameter {
if-feature stateful; if-feature "stateful";
description description
"The configured stateful PCE parameters"; "The configured stateful PCE parameters";
leaf state-timeout{ leaf state-timeout {
type uint32; type uint32;
units "seconds"; units "seconds";
description description
"When a PCEP session is terminated, a PCC "When a PCEP session is terminated, a PCC
waits for this time period before flushing waits for this time period before flushing
LSP state associated with that PCEP session LSP state associated with that PCEP session
and reverting to operator-defined default and reverting to operator-defined default
parameters or behaviours."; parameters or behaviours.";
} }
leaf redelegation-timeout{ leaf redelegation-timeout {
when "../../role = 'pcc'" + when "../../role = 'pcc'"
"or " + + "or "
"../../role = 'pcc-and-pce'" + "../../role = 'pcc-and-pce'" {
{ description
description "This field is applicable when the role is
"This field is applicable when the role is
PCC"; PCC";
} }
type uint32; type uint32;
units "seconds"; units "seconds";
description description
"When a PCEP session is terminated, a PCC "When a PCEP session is terminated, a PCC
waits for this time period before revoking waits for this time period before revoking
LSP delegation to a PCE and attempting to LSP delegation to a PCE and attempting to
redelegate LSPs associated with the redelegate LSPs associated with the
terminated PCEP session to an alternate terminated PCEP session to an alternate
PCE."; PCE.";
} }
leaf rpt-non-pcep-lsp{ leaf rpt-non-pcep-lsp {
when "../../role = 'pcc'" + when "../../role = 'pcc'"
"or " + + "or "
"../../role = 'pcc-and-pce'" + "../../role = 'pcc-and-pce'" {
{ description
description "This field is applicable when the role is
"This field is applicable when the role is
PCC"; PCC";
} }
type boolean; type boolean;
default true; default "true";
description description
"If set, a PCC reports LSPs that are not "If set, a PCC reports LSPs that are not
controlled by any PCE (for example, LSPs controlled by any PCE (for example, LSPs
that are statically configured at the that are statically configured at the
PCC). "; PCC). ";
} }
reference reference
"RFC 8231: Path Computation Element Communication Protocol "RFC 8231: Path Computation Element Communication Protocol
(PCEP) Extensions for Stateful PCE"; (PCEP) Extensions for Stateful PCE";
} }
container of-list{ container of-list {
when "../role = 'pce'" + when "../role = 'pce'"
"or " + + "or "
"../role = 'pcc-and-pce'" + "../role = 'pcc-and-pce'" {
{ description
description "These field are applicable when the role is
"These field are applicable when the role is PCE";
PCE"; }
} if-feature "objective-function";
if-feature objective-function; uses of-list;
description
uses of-list; "The authorized OF-List at PCE for all peers";
}
container lsp-db {
if-feature "stateful";
config false;
description
"The LSP-DB";
leaf db-ver {
when "../../role = 'pcc'"
+ "or "
+ "../../role = 'pcc-and-pce'" {
description
"This field is applicable when the role is
PCC";
}
if-feature "sync-opt";
type uint64;
description
"The LSP State Database Version Number";
}
list association-list {
if-feature "association";
key "type id source global-source extended-id";
description
"List of all PCEP associations";
reference
"[I-D.ietf-pce-association-group]: PCEP
Extensions for Establishing Relationships
Between Sets of LSPs";
leaf type {
type identityref {
base te-types:association-type;
}
description
"The PCEP association type";
}
leaf id {
type uint16;
description
"PCEP Association ID";
}
leaf source {
type inet:ip-address;
description
"PCEP Association Source.";
}
leaf global-source {
type uint32;
description
"PCEP Association Global Source.";
}
leaf extended-id {
type string;
description
"Additional information to support unique
identification.";
}
list lsp {
key "plsp-id pcc-id";
description
"List of all LSP in this association";
leaf plsp-id {
type leafref {
path "/pcep/entity/lsp-db/"
+ "lsp/plsp-id";
}
description
"Reference to PLSP-ID in LSP-DB";
}
leaf pcc-id {
type leafref {
path "/pcep/entity/lsp-db/"
+ "lsp/pcc-id";
}
description
"Reference to PCC-ID in LSP-DB";
}
}
}
list lsp {
key "plsp-id pcc-id";
description
"List of all LSPs in LSP-DB";
leaf plsp-id {
type uint32 {
range "1..1048575";
description }
"The authorized OF-List at PCE for all peers"; description
} "A PCEP-specific identifier for the LSP. A PCC
container lsp-db{ creates a unique PLSP-ID for each LSP that is
if-feature stateful; constant for the lifetime of a PCEP session.
config false; PLSP-ID is 20 bits with 0 and 0xFFFFF are
description reserved";
"The LSP-DB"; }
leaf db-ver{ leaf pcc-id {
when "../../role = 'pcc'" + type inet:ip-address;
"or " + description
"../../role = 'pcc-and-pce'" "The local internet address of the PCC, that
generated the PLSP-ID.";
}
container lsp-ref {
description
"reference to ietf-te lsp state";
leaf source {
type leafref {
path "/te:te/te:lsps-state/te:lsp/te:source";
}
description
"Tunnel sender address extracted from
SENDER_TEMPLATE object";
reference
"RFC 3209: RSVP-TE: Extensions to RSVP for
LSP Tunnels";
}
leaf destination {
type leafref {
path "/te:te/te:lsps-state/te:lsp/te:"
+ "destination";
}
description
"Tunnel endpoint address extracted from
SESSION object";
reference
"RFC 3209: RSVP-TE: Extensions to RSVP for
LSP Tunnels";
}
leaf tunnel-id {
type leafref {
path "/te:te/te:lsps-state/te:lsp/te:tunnel-id";
}
description
"Tunnel identifier used in the SESSION
that remains constant over the life
of the tunnel.";
{ reference
description "RFC 3209: RSVP-TE: Extensions to RSVP for
"This field is applicable when the role is LSP Tunnels";
PCC"; }
} leaf lsp-id {
if-feature sync-opt; type leafref {
type uint64; path "/te:te/te:lsps-state/te:lsp/te:lsp-id";
description }
"The LSP State Database Version Number"; description
} "Identifier used in the SENDER_TEMPLATE
list association-list { and the FILTER_SPEC that can be changed
if-feature association; to allow a sender to share resources with
key "type id source global-source extended-id"; itself.";
description reference
"List of all PCEP associations"; "RFC 3209: RSVP-TE: Extensions to RSVP for
reference LSP Tunnels";
"I-D.ietf-pce-association-group: PCEP }
leaf extended-tunnel-id {
type leafref {
path "/te:te/te:lsps-state/te:lsp/te:"
+ "extended-tunnel-id";
}
description
"Extended Tunnel ID of the LSP.";
reference
"RFC 3209: RSVP-TE: Extensions to RSVP for
LSP Tunnels";
}
}
leaf admin-state {
type boolean;
description
"The desired operational state";
}
leaf operational-state {
type operational-state;
description
"The operational status of the LSP";
}
container delegated {
description
"The delegation related parameters";
leaf enabled {
type boolean;
description
"LSP is delegated or not";
}
leaf peer {
type leafref {
path "/pcep/entity/peers/peer/addr";
}
must '(../enabled = true())' {
error-message "The LSP must be delegated";
}
description
"At the PCC, the reference to the PCEP peer to
which LSP is delegated; At the PCE, the
reference to the PCEP peer which delegated this
LSP";
}
leaf srp-id {
type uint32;
description
"The last SRP-ID-number associated with this
LSP.";
}
}
container initiation {
if-feature "pce-initiated";
description
"The PCE initiation related parameters";
reference
"RFC 8281: Path Computation Element Communication
Protocol (PCEP) Extensions for PCE-Initiated LSP
Setup in a Stateful PCE Model";
leaf enabled {
type boolean;
description
"Set to true if this LSP is initiated by a PCE";
}
leaf peer {
type leafref {
path "/pcep/entity/peers/peer/addr";
}
must '(../enabled = true())' {
error-message "The LSP must be PCE-Initiated";
}
description
"At the PCC, the reference to the PCEP peer
that initiated this LSP; At the PCE, the
reference to the PCEP peer where the LSP
is initiated";
}
}
leaf symbolic-path-name {
type string;
description
"The symbolic path name associated with the LSP.";
reference
"RFC 8231: Path Computation Element Communication
Protocol (PCEP) Extensions for Stateful PCE";
}
leaf last-error {
type identityref {
base lsp-error;
}
description
"The last error for the LSP.";
}
leaf pst {
type identityref {
base te-types:path-signaling-type;
}
default "te-types:path-setup-rsvp";
description
"The Path Setup Type";
reference
"RFC 8408: Conveying Path Setup Type in PCE
Communication Protocol (PCEP) Messages";
}
list association-list {
if-feature "association";
key "type id source global-source extended-id";
description
"List of all PCEP associations";
leaf type {
type leafref {
path "/pcep/entity/lsp-db/"
+ "association-list/type";
}
description
"PCEP Association Type";
}
leaf id {
type leafref {
path "/pcep/entity/lsp-db/"
+ "association-list/id";
}
description
"PCEP Association ID";
}
leaf source {
type leafref {
path "/pcep/entity/lsp-db/"
+ "association-list/source";
}
description
"PCEP Association Source.";
}
leaf global-source {
type leafref {
path "/pcep/entity/lsp-db/"
+ "association-list/global-source";
}
description
"PCEP Association Global Source.";
}
leaf extended-id {
type leafref {
path "/pcep/entity/lsp-db/"
+ "association-list/extended-id";
}
description
"Additional information to
support unique identification.";
}
reference
"[I-D.ietf-pce-association-group]: PCEP
Extensions for Establishing Relationships Extensions for Establishing Relationships
Between Sets of LSPs"; Between Sets of LSPs";
leaf type { }
type identityref { }
base te-types:association-type; }
} container path-keys {
description when "../role = 'pce' or ../role = 'pcc-and-pce'" {
"The PCEP association type"; description
} "These fields are applicable when the role is
leaf id { PCE";
type uint16; }
description if-feature "path-key";
"PCEP Association ID"; config false;
} description
leaf source { "The path-keys generated by the PCE";
type inet:ip-address; reference
description "RFC 5520: Preserving Topology Confidentiality
"PCEP Association Source."; in Inter-Domain Path Computation Using a Path-
} Key-Based Mechanism";
leaf global-source { list path-keys {
type uint32; key "path-key";
description description
"PCEP Association Global Source."; "The list of path-keys generated by the PCE";
} leaf path-key {
leaf extended-id{ type uint16;
type string; description
description "The identifier, or token used to represent
"Additional information to support unique the Confidential Path Segment (CPS) within
identification."; the context of the PCE";
} }
list lsp { container cps {
key "plsp-id pcc-id"; description
description "The Confidential Path Segment (CPS)";
"List of all LSP in this association"; list explicit-route-objects {
leaf plsp-id { key "index";
type leafref { description
path "/pcep/entity/lsp-db/" "List of explicit route objects";
+ "lsp/plsp-id"; leaf index {
} type uint32;
description description
"Reference to PLSP-ID in LSP-DB"; "ERO subobject index";
} }
leaf pcc-id { uses te-types:explicit-route-hop;
type leafref { }
path "/pcep/entity/lsp-db/" }
+ "lsp/pcc-id"; leaf pcc-original {
} type leafref {
description path "/pcep/entity/peers/peer/addr";
"Reference to PCC-ID in LSP-DB"; }
} description
} "Reference to PCC peer address of
} the original request";
list lsp { }
key "plsp-id pcc-id"; leaf req-id {
description type uint32;
"List of all LSPs in LSP-DB"; description
leaf plsp-id{ "The request ID of the original PCReq.";
type uint32{ }
range "1..1048575"; leaf retrieved {
} type boolean;
description description
"A PCEP-specific identifier for the LSP. A PCC "If path-key has been retrieved yet";
creates a unique PLSP-ID for each LSP that is }
constant for the lifetime of a PCEP session. leaf pcc-retrieved {
PLSP-ID is 20 bits with 0 and 0xFFFFF are type leafref {
reserved"; path "/pcep/entity/peers/peer/addr";
} }
leaf pcc-id{ must '(../retrieved = true())' {
type inet:ip-address; error-message "The Path-key should be retreived";
description }
"The local internet address of the PCC, that description
generated the PLSP-ID."; "Reference to PCC peer address which
} retreived the path-key";
container lsp-ref{ }
description leaf creation-time {
"reference to ietf-te lsp state"; type yang:timestamp;
description
leaf source { "The timestamp value at the time this Path-Key
type leafref { was created.";
path "/te:te/te:lsps-state/te:lsp/te:source"; }
} leaf discard-time {
description type uint32;
"Tunnel sender address extracted from units "minutes";
SENDER_TEMPLATE object"; description
reference "A time after which this path-keys will be
"RFC 3209: RSVP-TE: Extensions to RSVP for discarded";
LSP Tunnels"; }
} leaf reuse-time {
leaf destination { type uint32;
type leafref { units "minutes";
path "/te:te/te:lsps-state/te:lsp/te:" description
+ "destination"; "A time after which this path-keys could be
} reused";
description }
"Tunnel endpoint address extracted from }
SESSION object"; }
reference container peers {
"RFC 3209: RSVP-TE: Extensions to RSVP for description
LSP Tunnels"; "The list of configured peers for the
} entity (remote PCE)";
leaf tunnel-id { list peer {
type leafref { key "addr";
path "/te:te/te:lsps-state/te:lsp/te:tunnel-id"; description
} "The peer configured for the entity.
description (remote PCE)";
"Tunnel identifier used in the SESSION leaf addr {
that remains constant over the life type inet:ip-address;
of the tunnel."; description
reference "The local Internet address of this
"RFC 3209: RSVP-TE: Extensions to RSVP for PCEP peer.";
LSP Tunnels"; }
} leaf role {
leaf lsp-id { type pcep-role;
type leafref { mandatory true;
path "/te:te/te:lsps-state/te:lsp/te:lsp-id"; description
} "The role of the PCEP Peer.
description Takes one of the following values.
"Identifier used in the SENDER_TEMPLATE - unknown(0): this PCEP peer role is not
and the FILTER_SPEC that can be changed known.
to allow a sender to share resources with - pcc(1): this PCEP peer is a PCC.
itself.";
reference
"RFC 3209: RSVP-TE: Extensions to RSVP for
LSP Tunnels";
}
leaf extended-tunnel-id {
type leafref {
path "/te:te/te:lsps-state/te:lsp/te:"
+ "extended-tunnel-id";
}
description
"Extended Tunnel ID of the LSP.";
reference
"RFC 3209: RSVP-TE: Extensions to RSVP for
LSP Tunnels";
}
}
leaf admin-state{
type boolean;
description
"The desired operational state";
}
leaf operational-state{
type operational-state;
description
"The operational status of the LSP";
}
container delegated{
description
"The delegation related parameters";
leaf enabled{
type boolean;
description
"LSP is delegated or not";
}
leaf peer{
type leafref {
path "/pcep/entity/peers/peer/addr";
}
must "(../enabled = true())"
{
error-message
"The LSP must be delegated";
}
description
"At the PCC, the reference to the PCEP peer to
which LSP is delegated; At the PCE, the
reference to the PCEP peer which delegated this
LSP";
}
leaf srp-id{
type uint32;
description
"The last SRP-ID-number associated with this
LSP.";
}
}
container initiation {
if-feature pce-initiated;
description
"The PCE initiation related parameters";
reference
"RFC 8281: Path Computation Element Communication
Protocol (PCEP) Extensions for PCE-Initiated LSP
Setup in a Stateful PCE Model";
leaf enabled{
type boolean;
description
"Set to true if this LSP is initiated by a PCE";
}
leaf peer{
type leafref {
path "/pcep/entity/peers/peer/addr";
}
must "(../enabled = true())"
{
error-message
"The LSP must be PCE-Initiated";
}
description
"At the PCC, the reference to the PCEP peer
that initiated this LSP; At the PCE, the
reference to the PCEP peer where the LSP
is initiated";
}
}
leaf symbolic-path-name{
type string;
description
"The symbolic path name associated with the LSP.";
reference
"RFC 8231: Path Computation Element Communication
Protocol (PCEP) Extensions for Stateful PCE";
}
leaf last-error{
type identityref {
base lsp-error;
}
description
"The last error for the LSP.";
}
leaf pst{
type identityref{
base te-types:path-signaling-type;
}
default "te-types:path-setup-rsvp";
description
"The Path Setup Type";
reference
"RFC 8408: Conveying Path Setup Type in PCE
Communication Protocol (PCEP) Messages";
}
list association-list {
if-feature association;
key "type id source global-source extended-id";
description
"List of all PCEP associations";
leaf type {
type leafref {
path "/pcep/entity/lsp-db/"
+ "association-list/type";
}
description
"PCEP Association Type";
}
leaf id {
type leafref {
path "/pcep/entity/lsp-db/"
+ "association-list/id";
}
description
"PCEP Association ID";
}
leaf source {
type leafref {
path "/pcep/entity/lsp-db/"
+ "association-list/source";
}
description
"PCEP Association Source.";
}
leaf global-source {
type leafref {
path "/pcep/entity/lsp-db/"
+ "association-list/global-source";
}
description
"PCEP Association Global Source.";
}
leaf extended-id{
type leafref {
path "/pcep/entity/lsp-db/"
+ "association-list/extended-id";
}
description
"Additional information to
support unique identification.";
}
reference
"I-D.ietf-pce-association-group: PCEP
Extensions for Establishing Relationships
Between Sets of LSPs";
}
}
}
container path-keys {
when "../role = 'pce' or ../role = 'pcc-and-pce'" {
description
"These fields are applicable when the role is
PCE";
}
if-feature path-key;
config false;
description
"The path-keys generated by the PCE";
reference
"RFC 5520: Preserving Topology Confidentiality
in Inter-Domain Path Computation Using a Path-
Key-Based Mechanism";
list path-keys{
key "path-key";
description
"The list of path-keys generated by the PCE";
leaf path-key {
type uint16;
description
"The identifier, or token used to represent
the Confidential Path Segment (CPS) within
the context of the PCE";
}
container cps {
description
"The Confidential Path Segment (CPS)";
list explicit-route-objects {
key "index";
description
"List of explicit route objects";
leaf index {
type uint32;
description
"ERO subobject index";
}
uses te-types:explicit-route-hop;
}
}
leaf pcc-original {
type leafref {
path "/pcep/entity/peers/peer/addr";
}
description
"Reference to PCC peer address of
the original request";
}
leaf req-id {
type uint32;
description
"The request ID of the original PCReq.";
}
leaf retrieved {
type boolean;
description
"If path-key has been retrieved yet";
}
leaf pcc-retrieved {
type leafref {
path "/pcep/entity/peers/peer/addr";
}
must "(../retrieved = true())"
{
error-message
"The Path-key should be retreived";
}
description
"Reference to PCC peer address which
retreived the path-key";
}
leaf creation-time {
type yang:timestamp;
description
"The timestamp value at the time this Path-Key
was created.";
}
leaf discard-time {
type uint32;
units "minutes";
description
"A time after which this path-keys will be
discarded";
}
leaf reuse-time {
type uint32;
units "minutes";
description
"A time after which this path-keys could be
reused";
}
}
}
container peers{
description
"The list of configured peers for the
entity (remote PCE)";
list peer{
key "addr";
description
"The peer configured for the entity.
(remote PCE)";
leaf addr {
type inet:ip-address;
description
"The local Internet address of this
PCEP peer.";
}
leaf role {
type pcep-role;
mandatory true;
description
"The role of the PCEP Peer.
Takes one of the following values.
- unknown(0): this PCEP peer role is not
known.
- pcc(1): this PCEP peer is a PCC.
- pce(2): this PCEP peer is a PCE.
- pcc-and-pce(3): this PCEP peer
is both a PCC and a PCE.";
}
leaf description {
type string;
description
"Description of the PCEP peer
configured by the user";
}
uses info {
description
"PCE Peer information";
}
container pce-info { - pce(2): this PCEP peer is a PCE.
uses pce-info { - pcc-and-pce(3): this PCEP peer
description is both a PCC and a PCE.";
"PCE Peer information"; }
} leaf description {
description type string;
"The PCE Peer information"; description
} "Description of the PCEP peer
configured by the user";
}
uses info {
description
"PCE Peer information";
}
container pce-info {
uses pce-info {
description
"PCE Peer information";
}
description
"The PCE Peer information";
}
leaf delegation-pref {
if-feature "stateful";
type uint8 {
range "0..7";
}
description
"The PCE peer delegation preference.";
}
container auth {
description
"The Authentication options";
choice auth-type-selection {
description
"Options for expressing authentication
setting.";
case auth-key-chain {
leaf key-chain {
type key-chain:key-chain-ref;
description
"key-chain name.";
}
}
case auth-key {
leaf crypto-algorithm {
type identityref {
base key-chain:crypto-algorithm;
leaf delegation-pref{ }
if-feature stateful; mandatory true;
type uint8{ description
range "0..7"; "Cryptographic algorithm associated
} with key.";
description }
"The PCE peer delegation preference."; choice key-string-style {
} description
container auth { "Key string styles";
description case keystring {
"The Authentication options"; leaf keystring {
choice auth-type-selection { netconf-acm:default-deny-all;
description type string;
"Options for expressing authentication description
setting."; "Key string in ASCII format.";
case auth-key-chain { }
leaf key-chain { }
type kc:key-chain-ref; case hexadecimal {
description if-feature "key-chain:hex-key-string";
"key-chain name."; leaf hexadecimal-string {
} netconf-acm:default-deny-all;
} type yang:hex-string;
case auth-key { description
leaf crypto-algorithm { "Key in hexadecimal string format. When
type identityref { compared to ASCII, specification in
base kc:crypto-algorithm; hexadecimal affords greater key entropy
} with the same number of internal
mandatory true; key-string octets. Additionally, it
description discourages usage of well-known words or
"Cryptographic algorithm associated numbers.";
with key."; }
} }
choice key-string-style { }
description }
"Key string styles"; case auth-tls {
case keystring { if-feature "tls";
leaf keystring { choice role {
nacm:default-deny-all; description
type string; "The role of the local entity";
description case server {
"Key string in ASCII format."; container tls-server {
} uses tls-server:tls-server-grouping {
} description
case hexadecimal { "Server TLS information.";
if-feature "kc:hex-key-string"; }
leaf hexadecimal-string { description
nacm:default-deny-all; "TLS related information";
type yang:hex-string; }
description
"Key in hexadecimal string format. When
compared to ASCII, specification in
hexadecimal affords greater key entropy
with the same number of internal
key-string octets. Additionally, it
discourages usage of well-known words or
numbers.";
}
}
}
}
case auth-tls {
if-feature tls;
choice role{
description
"The role of the local entity";
case server {
container tls-server {
uses ts:tls-server-grouping {
description
"Server TLS information.";
}
description
"TLS related information";
}
}
case client{
container tls-client {
uses tc:tls-client-grouping {
description
"Client TLS information.";
}
description
"TLS related information";
}
}
}
}
}
}
leaf discontinuity-time { }
type yang:timestamp; case client {
config false; container tls-client {
description uses tls-client:tls-client-grouping {
"The timestamp of the time when the information and description
"Client TLS information.";
}
description
"TLS related information";
}
}
}
}
}
}
leaf discontinuity-time {
type yang:timestamp;
config false;
description
"The timestamp of the time when the information and
statistics were last reset."; statistics were last reset.";
} }
leaf initiate-session {
leaf initiate-session { type boolean;
type boolean; config false;
config false; description
description "Indicates whether the local PCEP entity initiates
"Indicates whether the local PCEP entity initiates
sessions to this peer, or waits for the peer to sessions to this peer, or waits for the peer to
initiate a session."; initiate a session.";
} }
leaf session-exists {
leaf session-exists{ type boolean;
type boolean; config false;
config false; description
description "Indicates whether a session with
"Indicates whether a session with
this peer currently exists."; this peer currently exists.";
} }
leaf session-up-time {
leaf session-up-time{ type yang:timestamp;
type yang:timestamp; config false;
config false; description
description "The timestamp value of the last time a
"The timestamp value of the last time a
session with this peer was successfully session with this peer was successfully
established."; established.";
} }
leaf session-fail-time {
leaf session-fail-time{ type yang:timestamp;
type yang:timestamp; config false;
config false; description
description "The timestamp value of the last time a
"The timestamp value of the last time a
session with this peer failed to be session with this peer failed to be
established."; established.";
} }
leaf session-fail-up-time {
leaf session-fail-up-time{ type yang:timestamp;
type yang:timestamp; config false;
config false; description
description "The timestamp value of the last time a
"The timestamp value of the last time a
session with this peer failed from session with this peer failed from
active."; active.";
} }
container sessions {
container sessions { config false;
config false; description
description "This entry represents a single PCEP
"This entry represents a single PCEP
session in which the local PCEP entity participates. session in which the local PCEP entity participates.
This entry exists only if the corresponding PCEP This entry exists only if the corresponding PCEP
session has been initialized by some event, such as session has been initialized by some event, such as
manual user configuration, auto-discovery of a peer, manual user configuration, auto-discovery of a peer,
or an incoming TCP connection."; or an incoming TCP connection.";
list session {
list session { key "initiator";
key "initiator"; description
description "The list of sessions, note that for a time being
"The list of sessions, note that for a time being
two sessions may exist for a peer"; two sessions may exist for a peer";
leaf initiator {
leaf initiator { type pcep-initiator;
type pcep-initiator; description
description "The initiator of the session,that is, whether
"The initiator of the session,that is, whether
the TCP connection was initiated by the local the TCP connection was initiated by the local
PCEP entity or the peer. PCEP entity or the peer.
There is a window during session There is a window during session
initialization where two sessions can exist initialization where two sessions can exist
between a pair of PCEP speakers, each between a pair of PCEP speakers, each
initiated by one of the speakers. One of initiated by one of the speakers. One of
these sessions is always discarded before it these sessions is always discarded before it
leaves OpenWait state. However, before it is leaves OpenWait state. However, before it is
discarded, two sessions to the given peer discarded, two sessions to the given peer
appear transiently in this yang module. The appear transiently in this yang module. The
sessions are distinguished by who initiated sessions are distinguished by who initiated
them, and so this field is the key."; them, and so this field is the key.";
} }
leaf role {
leaf role { type leafref {
type leafref { path "/pcep/entity/role";
path "/pcep/entity/role"; }
} description
description "The reference to peer role .";
"The reference to peer role ."; }
} leaf state-last-change {
type yang:timestamp;
leaf state-last-change { description
type yang:timestamp; "The timestamp value at the time this
description
"The timestamp value at the time this
session entered its current state as session entered its current state as
denoted by the state leaf."; denoted by the state leaf.";
} }
leaf state {
leaf state { type pcep-sess-state;
type pcep-sess-state; description
description "The current state of the session.
"The current state of the session.
The set of possible states excludes the The set of possible states excludes the
idle state since entries do not exist idle state since entries do not exist
in the idle state."; in the idle state.";
} }
leaf session-creation {
leaf session-creation { type yang:timestamp;
type yang:timestamp; description
description "The timestamp value at the time this
"The timestamp value at the time this
session was created."; session was created.";
} }
leaf connect-retry {
leaf connect-retry { type yang:counter32;
type yang:counter32; description
description "The number of times that the local PCEP
"The number of times that the local PCEP
entity has attempted to establish a TCP entity has attempted to establish a TCP
connection for this session without connection for this session without
success. The PCEP entity gives up when success. The PCEP entity gives up when
this reaches connect-max-retry."; this reaches connect-max-retry.";
} }
leaf local-id {
leaf local-id { type uint8;
type uint8; description
description "The value of the PCEP session ID used by
"The value of the PCEP session ID used by
the local PCEP entity in the Open message the local PCEP entity in the Open message
for this session. If state is tcp-pending for this session. If state is tcp-pending
then this is the session ID that will be then this is the session ID that will be
used in the Open message. Otherwise, this used in the Open message. Otherwise, this
is the session ID that was sent in the is the session ID that was sent in the
Open message."; Open message.";
reference reference
"RFC 5440: Path Computation Element (PCE) "RFC 5440: Path Computation Element (PCE)
Communication Protocol (PCEP)"; Communication Protocol (PCEP)";
} }
leaf remote-id {
leaf remote-id { type uint8;
type uint8; must "((../state != 'tcp-pending'"
must "((../state != 'tcp-pending'" + + "and "
"and " + + "../state != 'open-wait' )"
"../state != 'open-wait' )" + + "or "
"or " + + "((../state = 'tcp-pending'"
"((../state = 'tcp-pending'" + + " or "
" or " + + "../state = 'open-wait' )"
"../state = 'open-wait' )" + + "and (. = 0)))" {
"and (. = 0)))" { error-message "Invalid remote-id";
error-message description
"Invalid remote-id"; "If state is tcp-pending or open-wait then
description
"If state is tcp-pending or open-wait then
this leaf is not used and MUST be set to this leaf is not used and MUST be set to
zero."; zero.";
} }
description description
"The value of the PCEP session ID used by the "The value of the PCEP session ID used by the
peer in its Open message for this session."; peer in its Open message for this session.";
reference reference
"RFC 5440: Path Computation Element (PCE) "RFC 5440: Path Computation Element (PCE)
Communication Protocol (PCEP)"; Communication Protocol (PCEP)";
} }
leaf keepalive-timer {
leaf keepalive-timer { type uint8;
type uint8; units "seconds";
units "seconds"; must "(../state = 'session-up'"
must "(../state = 'session-up'" + + "or "
"or " + + "(../state != 'session-up'"
"(../state != 'session-up'" + + "and (. = 0)))" {
"and (. = 0)))" { error-message "Invalid keepalive timer";
error-message description
"Invalid keepalive timer"; "This field is used if and only if state is
description session-up. Otherwise, it is not used and
"This field is used if and only if state is MUST be set to zero.";
session-up. Otherwise, it is not used and }
MUST be set to zero."; description
} "The agreed maximum interval at which the local
description
"The agreed maximum interval at which the local
PCEP entity transmits PCEP messages on this PCEP PCEP entity transmits PCEP messages on this PCEP
session. Zero means that the local PCEP entity session. Zero means that the local PCEP entity
never sends Keepalives on this session."; never sends Keepalives on this session.";
reference reference
"RFC 5440: Path Computation Element (PCE) "RFC 5440: Path Computation Element (PCE)
Communication Protocol (PCEP)"; Communication Protocol (PCEP)";
} }
leaf peer-keepalive-timer {
leaf peer-keepalive-timer { type uint8;
type uint8; units "seconds";
units "seconds"; must "(../state = 'session-up'"
must "(../state = 'session-up'" + + "or "
"or " + + "(../state != 'session-up'"
"(../state != 'session-up'" + + "and "
"and " + + "(. = 0)))" {
"(. = 0)))" { error-message "Invalid Peer keepalive timer";
error-message description
"Invalid Peer keepalive timer"; "This field is used if and only if state is
description
"This field is used if and only if state is
session-up. Otherwise, it is not used and MUST session-up. Otherwise, it is not used and MUST
be set to zero."; be set to zero.";
} }
description description
"The agreed maximum interval at which the peer "The agreed maximum interval at which the peer
transmits PCEP messages on this PCEP session. transmits PCEP messages on this PCEP session.
Zero means that the peer never sends Keepalives Zero means that the peer never sends Keepalives
on this session."; on this session.";
reference reference
"RFC 5440: Path Computation Element (PCE) "RFC 5440: Path Computation Element (PCE)
Communication Protocol (PCEP)"; Communication Protocol (PCEP)";
} }
leaf dead-timer {
leaf dead-timer { type uint8;
type uint8; units "seconds";
units "seconds"; description
description "The dead timer interval for this PCEP session.";
"The dead timer interval for this PCEP session."; reference
reference "RFC 5440: Path Computation Element (PCE)
"RFC 5440: Path Computation Element (PCE)
Communication Protocol (PCEP)"; Communication Protocol (PCEP)";
} }
leaf peer-dead-timer {
leaf peer-dead-timer { type uint8;
type uint8; units "seconds";
units "seconds"; must "((../state != 'tcp-pending'"
must "((../state != 'tcp-pending'" + + "and "
"and " + + "../state != 'open-wait' )"
"../state != 'open-wait' )" + + "or "
"or " + + "((../state = 'tcp-pending'"
"((../state = 'tcp-pending'" + + " or "
" or " + + "../state = 'open-wait' )"
"../state = 'open-wait' )" + + "and "
"and " + + "(. = 0)))" {
"(. = 0)))" { error-message "Invalid Peer Dead timer";
error-message description
"Invalid Peer Dead timer"; "If state is tcp-pending or open-wait then this
description leaf is not used and MUST be set to zero.";
"If state is tcp-pending or open-wait then this }
leaf is not used and MUST be set to zero."; description
} "The peer's dead-timer interval
description
"The peer's dead-timer interval
for this PCEP session."; for this PCEP session.";
reference
"RFC 5440: Path Computation Element (PCE)
Communication Protocol (PCEP)";
}
leaf ka-hold-time-rem { reference
type uint8; "RFC 5440: Path Computation Element (PCE)
units "seconds"; Communication Protocol (PCEP)";
must "((../state != 'tcp-pending'" + }
"and " + leaf ka-hold-time-rem {
"../state != 'open-wait' ) " + type uint8;
"or " + units "seconds";
"((../state = 'tcp-pending'" + must "((../state != 'tcp-pending'"
"or " + + "and "
"../state = 'open-wait' )" + + "../state != 'open-wait' ) "
"and " + + "or "
"(. = 0)))" { + "((../state = 'tcp-pending'"
error-message + "or "
"Invalid Keepalive hold time remaining"; + "../state = 'open-wait' )"
description + "and "
"If state is tcp-pending or open-wait then this + "(. = 0)))" {
error-message
"Invalid Keepalive hold time remaining";
description
"If state is tcp-pending or open-wait then this
field is not used and MUST be set to zero."; field is not used and MUST be set to zero.";
} }
description description
"The keep alive hold time remaining for this "The keep alive hold time remaining for this
session."; session.";
} }
leaf overloaded { leaf overloaded {
type boolean; type boolean;
description description
"If the local PCEP entity has informed the peer that "If the local PCEP entity has informed the peer that
it is currently overloaded, then this is set to true. it is currently overloaded, then this is set to true.
Otherwise, it is set to false."; Otherwise, it is set to false.";
reference reference
"RFC 5440: Path Computation Element (PCE) "RFC 5440: Path Computation Element (PCE)
Communication Protocol (PCEP)"; Communication Protocol (PCEP)";
} }
leaf overload-time { leaf overload-time {
type uint32; type uint32;
units "seconds"; units "seconds";
must "((../overloaded = true()) " + must '((../overloaded = true()) '
"or ((../overloaded != true()) " + + 'or ((../overloaded != true()) '
"and (. = 0)))" { + 'and (. = 0)))' {
error-message error-message "Invalid overload-time";
"Invalid overload-time"; description
description "This field is only used if overloaded is set to
"This field is only used if overloaded is set to
true. Otherwise, it is not used and MUST be set true. Otherwise, it is not used and MUST be set
to zero."; to zero.";
} }
description description
"The interval of time that is remaining until the "The interval of time that is remaining until the
local PCEP entity will cease to be overloaded on local PCEP entity will cease to be overloaded on
this session."; this session.";
reference reference
"RFC 5440: Path Computation Element (PCE) "RFC 5440: Path Computation Element (PCE)
Communication Protocol (PCEP)"; Communication Protocol (PCEP)";
} }
leaf peer-overloaded { leaf peer-overloaded {
type boolean; type boolean;
description description
"If the peer has informed the local PCEP entity "If the peer has informed the local PCEP entity
that it is currently overloaded, then this is that it is currently overloaded, then this is
set to true. Otherwise, it is set to false."; set to true. Otherwise, it is set to false.";
reference reference
"RFC 5440: Path Computation Element (PCE) "RFC 5440: Path Computation Element (PCE)
Communication Protocol (PCEP)"; Communication Protocol (PCEP)";
} }
leaf peer-overload-time {
leaf peer-overload-time { type uint32;
type uint32; units "seconds";
units "seconds"; must '((../peer-overloaded = '
must "((../peer-overloaded = " + + 'true()) or '
"true()) or " + + '((../peer-overloaded !='
"((../peer-overloaded !=" + + 'true())'
"true())" + + ' and '
" and " + + '(. = 0)))' {
"(. = 0)))" { error-message "Invalid peer overload time";
error-message description
"Invalid peer overload time"; "This field is only used if peer-overloaded
description is set to true. Otherwise, it is not used
"This field is only used if peer-overloaded and MUST be set to zero.";
is set to true. Otherwise, it is not used }
and MUST be set to zero."; description
} "The interval of time that is remaining until
description
"The interval of time that is remaining until
the peer will cease to be overloaded. If it the peer will cease to be overloaded. If it
is not known how long the peer will stay in is not known how long the peer will stay in
overloaded state, this leaf is set to zero."; overloaded state, this leaf is set to zero.";
reference reference
"RFC 5440: Path Computation Element (PCE) "RFC 5440: Path Computation Element (PCE)
Communication Protocol (PCEP)"; Communication Protocol (PCEP)";
} }
leaf lspdb-sync { leaf lspdb-sync {
if-feature stateful; if-feature "stateful";
type sync-state; type sync-state;
description description
"The LSP-DB state synchronization status."; "The LSP-DB state synchronization status.";
reference reference
"RFC 8231: Path Computation Element Communication "RFC 8231: Path Computation Element Communication
Protocol (PCEP) Extensions for Stateful PCE"; Protocol (PCEP) Extensions for Stateful PCE";
} }
leaf recv-db-ver {
leaf recv-db-ver{ when "../role = 'pcc'"
when "../role = 'pcc'" + + "or "
"or " + + "../role = 'pcc-and-pce'" {
"../role = 'pcc-and-pce'" description
{ "This field is applicable when the role is
description
"This field is applicable when the role is
PCC"; PCC";
} }
if-feature "stateful";
if-feature stateful; if-feature "sync-opt";
if-feature sync-opt; type uint64;
description
type uint64; "The last received LSP State Database Version
description
"The last received LSP State Database Version
Number"; Number";
reference reference
"RFC 8231: Path Computation Element Communication "RFC 8231: Path Computation Element Communication
Protocol (PCEP) Extensions for Stateful PCE"; Protocol (PCEP) Extensions for Stateful PCE";
} }
container of-list{ container of-list {
when "../role = 'pce'" + when "../role = 'pce'"
"or " + + "or "
"../role = 'pcc-and-pce'" + "../role = 'pcc-and-pce'" {
{ description
description "These fields are applicable when the role is
"These fields are applicable when the role is
PCE"; PCE";
} }
if-feature objective-function; if-feature "objective-function";
uses of-list;
uses of-list; description
"Indicate the list of supported OF on this
description
"Indicate the list of supported OF on this
session"; session";
reference reference
"RFC 5541: Encoding of Objective Functions in "RFC 5541: Encoding of Objective Functions in
the Path Computation Element Communication the Path Computation Element Communication
Protocol (PCEP)"; Protocol (PCEP)";
}
} container pst-list {
when "../role = 'pce'"
container pst-list{ + "or "
when "../role = 'pce'" + + "../role = 'pcc-and-pce'" {
"or " + description
"../role = 'pcc-and-pce'" "These fields are applicable when the role is
{
description
"These fields are applicable when the role is
PCE"; PCE";
} }
description description
"Indicate the list of supported "Indicate the list of supported
PST on this session"; PST on this session";
reference reference
"RFC 8408: Conveying Path Setup Type in PCE "RFC 8408: Conveying Path Setup Type in PCE
Communication Protocol (PCEP) Messages"; Communication Protocol (PCEP) Messages";
list path-setup-type {
list path-setup-type{ key "pst";
key "pst"; description
"The list of authorized PST";
description leaf pst {
"The list of authorized PST"; type identityref {
base te-types:path-signaling-type;
leaf pst { }
type identityref{ description
base te-types:path-signaling-type; "The PST authorized";
} }
description }
"The PST authorized"; }
} container assoc-type-list {
} if-feature "association";
} description
container assoc-type-list{ "Indicate the list of supported association types
if-feature association;
description
"Indicate the list of supported association types
on this session"; on this session";
reference reference
"I-D.ietf-pce-association-group: PCEP "[I-D.ietf-pce-association-group]: PCEP
Extensions for Establishing Relationships Extensions for Establishing Relationships
Between Sets of LSPs"; Between Sets of LSPs";
list assoc-type {
list assoc-type{ key "at";
key "at"; description
"The list of authorized association types";
description leaf at {
"The list of authorized association types"; type identityref {
base te-types:association-type;
leaf at { }
type identityref { description
base te-types:association-type; "The association type authorized";
} }
description }
"The association type authorized"; }
} leaf speaker-entity-id {
} if-feature "sync-opt";
} type string;
leaf speaker-entity-id{ description
if-feature sync-opt; "The Speaker Entity Identifier";
type string; reference
description "RFC 8232: Optimizations of Label Switched
"The Speaker Entity Identifier";
reference
"RFC 8232: Optimizations of Label Switched
Path State Synchronization Procedures for Path State Synchronization Procedures for
a Stateful PCE"; a Stateful PCE";
} }
leaf discontinuity-time {
leaf discontinuity-time { type yang:timestamp;
type yang:timestamp; description
description "The timestamp value of the time when the
"The timestamp value of the time when the
statistics were last reset."; statistics were last reset.";
} }
} // session }
} // sessions // session
}
}//peer // sessions
}//peers }
}//entity //peer
}//pcep }
//peers
}
//entity
}
/* //pcep
/*
* Notifications * Notifications
*/ */
notification pcep-session-up {
description notification pcep-session-up {
"This notification is sent when the value of description
"This notification is sent when the value of
'/pcep/peers/peer/sessions/session/state' '/pcep/peers/peer/sessions/session/state'
enters the 'session-up' state."; enters the 'session-up' state.";
uses notification-instance-hdr;
uses notification-instance-hdr; uses notification-session-hdr;
leaf state-last-change {
uses notification-session-hdr; type yang:timestamp;
description
leaf state-last-change { "The timestamp value at the time this session
type yang:timestamp;
description
"The timestamp value at the time this session
entered its current state as denoted by the state entered its current state as denoted by the state
leaf."; leaf.";
} }
leaf state {
leaf state { type pcep-sess-state;
type pcep-sess-state; description
description "The current state of the session.
"The current state of the session.
The set of possible states excludes the idle state The set of possible states excludes the idle state
since entries do not exist in the idle state."; since entries do not exist in the idle state.";
} }
reference reference
"RFC 5440: Path Computation Element (PCE) Communication "RFC 5440: Path Computation Element (PCE) Communication
Protocol (PCEP)"; Protocol (PCEP)";
} //notification }
notification pcep-session-down { //notification
description
"This notification is sent when the value of notification pcep-session-down {
description
"This notification is sent when the value of
'/pcep/peers/peer/sessions/session/state' '/pcep/peers/peer/sessions/session/state'
leaves the 'session-up' state."; leaves the 'session-up' state.";
uses notification-instance-hdr;
uses notification-instance-hdr; leaf session-initiator {
type pcep-initiator;
leaf session-initiator { description
type pcep-initiator; "The initiator of the session.";
description }
"The initiator of the session."; leaf state-last-change {
} type yang:timestamp;
description
leaf state-last-change { "The timestamp value at the time this session
type yang:timestamp;
description
"The timestamp value at the time this session
entered its current state as denoted by the state entered its current state as denoted by the state
leaf."; leaf.";
} }
leaf state {
leaf state { type pcep-sess-state;
type pcep-sess-state; description
description "The current state of the session.
"The current state of the session. The set of possible states excludes the idle state
The set of possible states excludes the idle state since entries do not exist in the idle state.";
since entries do not exist in the idle state."; }
} reference
reference "RFC 5440: Path Computation Element (PCE) Communication
"RFC 5440: Path Computation Element (PCE) Communication
Protocol (PCEP)"; Protocol (PCEP)";
} //notification }
notification pcep-session-local-overload {
description
"This notification is sent when the local PCEP entity
enters overload state for a peer.";
uses notification-instance-hdr;
uses notification-session-hdr; //notification
leaf overloaded { notification pcep-session-local-overload {
type boolean; description
description "This notification is sent when the local PCEP entity
"If the local PCEP entity has informed the peer enters overload state for a peer.";
uses notification-instance-hdr;
uses notification-session-hdr;
leaf overloaded {
type boolean;
description
"If the local PCEP entity has informed the peer
that it is currently overloaded, then this is set that it is currently overloaded, then this is set
to true. Otherwise, it is set to false."; to true. Otherwise, it is set to false.";
} }
leaf overload-time {
leaf overload-time { type uint32;
type uint32; units "seconds";
units "seconds"; description
description "The interval of time that is remaining until the
"The interval of time that is remaining until the local PCEP entity will cease to be overloaded on
local PCEP entity will cease to be overloaded on this session.";
this session."; }
reference
} "RFC 5440: Path Computation Element (PCE) Communication
reference
"RFC 5440: Path Computation Element (PCE) Communication
Protocol (PCEP)"; Protocol (PCEP)";
} //notification }
notification pcep-session-local-overload-clear {
description
"This notification is sent when the local PCEP entity
leaves overload state for a peer.";
uses notification-instance-hdr; //notification
leaf overloaded { notification pcep-session-local-overload-clear {
type boolean; description
description "This notification is sent when the local PCEP entity
"If the local PCEP entity has informed the peer leaves overload state for a peer.";
uses notification-instance-hdr;
leaf overloaded {
type boolean;
description
"If the local PCEP entity has informed the peer
that it is currently overloaded, then this is set that it is currently overloaded, then this is set
to true. Otherwise, it is set to false."; to true. Otherwise, it is set to false.";
} }
reference reference
"RFC 5440: Path Computation Element (PCE) Communication "RFC 5440: Path Computation Element (PCE) Communication
Protocol (PCEP)"; Protocol (PCEP)";
} //notification }
notification pcep-session-peer-overload {
description
"This notification is sent when a peer enters overload
state.";
uses notification-instance-hdr;
uses notification-session-hdr; //notification
leaf peer-overloaded { notification pcep-session-peer-overload {
type boolean; description
description "This notification is sent when a peer enters overload
"If the peer has informed the local PCEP entity that state.";
uses notification-instance-hdr;
uses notification-session-hdr;
leaf peer-overloaded {
type boolean;
description
"If the peer has informed the local PCEP entity that
it is currently overloaded, then this is set to it is currently overloaded, then this is set to
true. Otherwise, it is set to false."; true. Otherwise, it is set to false.";
}
leaf peer-overload-time { }
type uint32; leaf peer-overload-time {
units "seconds"; type uint32;
description units "seconds";
"The interval of time that is remaining until the description
"The interval of time that is remaining until the
peer will cease to be overloaded. If it is not peer will cease to be overloaded. If it is not
known how long the peer will stay in overloaded known how long the peer will stay in overloaded
state, this leaf is set to zero."; state, this leaf is set to zero.";
} }
reference reference
"RFC 5440: Path Computation Element (PCE) Communication "RFC 5440: Path Computation Element (PCE) Communication
Protocol (PCEP)"; Protocol (PCEP)";
} //notification }
notification pcep-session-peer-overload-clear {
description
"This notification is sent when a peer leaves overload
state.";
uses notification-instance-hdr; //notification
leaf peer-overloaded { notification pcep-session-peer-overload-clear {
type boolean; description
description "This notification is sent when a peer leaves overload
"If the peer has informed the local PCEP entity that state.";
uses notification-instance-hdr;
leaf peer-overloaded {
type boolean;
description
"If the peer has informed the local PCEP entity that
it is currently overloaded, then this is set to it is currently overloaded, then this is set to
true. Otherwise, it is set to false."; true. Otherwise, it is set to false.";
} }
reference reference
"RFC 5440: Path Computation Element (PCE) Communication "RFC 5440: Path Computation Element (PCE) Communication
Protocol (PCEP)"; Protocol (PCEP)";
} //notification }
/* //notification
* RPC /*
*/ * RPC
*/
rpc trigger-resync { rpc trigger-resync {
if-feature stateful; if-feature "stateful";
if-feature sync-opt; if-feature "sync-opt";
description description
"Trigger the resyncrinization at the PCE"; "Trigger the resyncrinization at the PCE";
reference reference
"RFC 8232: Optimizations of Label Switched Path State "RFC 8232: Optimizations of Label Switched Path State
Synchronization Procedures for a Stateful PCE"; Synchronization Procedures for a Stateful PCE";
input { input {
leaf pcc { leaf pcc {
type leafref { type leafref {
path "/pcep/entity/peers/peer/addr"; path "/pcep/entity/peers/peer/addr";
} }
description description
"The IP address to identify the PCC. The state "The IP address to identify the PCC. The state
syncronization is re-triggered for all LSPs from syncronization is re-triggered for all LSPs from
the PCC. The rpc on the PCC will be ignored."; the PCC. The rpc on the PCC will be ignored.";
}
}
//input
}
} //rpc
}//input }
}//rpc
}//module <CODE ENDS>
<CODE ENDS>
10.2. ietf-pcep-stats module 10.2. ietf-pcep-stats module
<CODE BEGINS> file "ietf-pcep-stats@2019-03-24.yang" <CODE BEGINS> file "ietf-pcep-stats@2019-03-26.yang"
module ietf-pcep-stats { module ietf-pcep-stats {
yang-version 1.1; yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-pcep-stats"; namespace "urn:ietf:params:xml:ns:yang:ietf-pcep-stats";
prefix pcep-stats;
prefix ps;
import ietf-pcep { import ietf-pcep {
prefix p; prefix pcep;
reference reference
"RFC XXXX: A YANG Data Model for Path Computation "RFC XXXX: A YANG Data Model for Path Computation
Element Communications Protocol (PCEP)"; Element Communications Protocol (PCEP)";
} }
import ietf-yang-types { import ietf-yang-types {
prefix "yang"; prefix yang;
reference reference
"RFC 6991: Common YANG Data Types"; "RFC 6991: Common YANG Data Types";
} }
organization organization
"IETF PCE (Path Computation Element) Working Group"; "IETF PCE (Path Computation Element) Working Group";
contact contact
"WG Web: <http://tools.ietf.org/wg/pce/> "WG Web: <https://tools.ietf.org/wg/pce/>
WG List: <mailto:pce@ietf.org> WG List: <mailto:pce@ietf.org>
Editor: Dhruv Dhody Editor: Dhruv Dhody
<mailto:dhruv.ietf@gmail.com>"; <mailto:dhruv.ietf@gmail.com>";
description description
"The YANG module augments the PCEP yang operational "The YANG module augments the PCEP yang operational
model with statistics, counters and telemetry data. model with statistics, counters and telemetry data.
Copyright (c) 2019 IETF Trust and the persons identified as Copyright (c) 2019 IETF Trust and the persons identified as
authors of the code. All rights reserved. authors of the code. All rights reserved.
Redistribution and use in source and binary forms, with or Redistribution and use in source and binary forms, with or
without modification, is permitted pursuant to, and subject without modification, is permitted pursuant to, and subject
to the license terms contained in, the Simplified BSD License to the license terms contained in, the Simplified BSD License
set forth in Section 4.c of the IETF Trust's Legal Provisions set forth in Section 4.c of the IETF Trust's Legal Provisions
Relating to IETF Documents Relating to IETF Documents
(http://trustee.ietf.org/license-info). (httpcep://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC XXXX; see the This version of this YANG module is part of RFC XXXX; see the
RFC itself for full legal notices."; RFC itself for full legal notices.";
revision 2019-03-24 { revision 2019-03-26 {
description "Initial revision."; description
"Initial revision.";
reference reference
"RFC XXXX: A YANG Data Model for Path Computation "RFC XXXX: A YANG Data Model for Path Computation
Element Communications Protocol (PCEP)"; Element Communications Protocol (PCEP)";
} }
/* /*
* Groupings * Groupings
*/ */
grouping pcep-stats{ grouping pcep-stats {
description description
"This grouping defines statistics for PCEP. It is used "This grouping defines statistics for PCEP. It is used
for both peer and current session."; for both peer and current session.";
leaf avg-rsp-time{ leaf avg-rsp-time {
when "../../p:role = 'pce'" + when "../../pcep:role = 'pce'"
"or " + + "or "
"../../p:role = 'pcc-and-pce'" + "../../pcep:role = 'pcc-and-pce'" {
{
description description
"Valid for PCEP Peer as PCE"; "Valid for PCEP Peer as PCE";
} }
type uint32; type uint32;
units "milliseconds"; units "milliseconds";
description description
"The average response time. If an average response time "The average response time. If an average response time
has not been calculated then this leaf has the value has not been calculated then this leaf has the value
zero."; zero.";
} }
leaf lwm-rsp-time {
leaf lwm-rsp-time{ when "../../pcep:role = 'pce'"
when "../../p:role = 'pce'" + + "or "
"or " + + "../../pcep:role = 'pcc-and-pce'" {
"../../p:role = 'pcc-and-pce'"
{
description description
"Valid for PCEP Peer as PCE"; "Valid for PCEP Peer as PCE";
} }
type uint32; type uint32;
units "milliseconds"; units "milliseconds";
description description
"The smallest (low-water mark) response time seen. "The smallest (low-water mark) response time seen.
If no responses have been received then this leaf has If no responses have been received then this leaf has
the value zero."; the value zero.";
} }
leaf hwm-rsp-time {
leaf hwm-rsp-time{ when "../../pcep:role = 'pce'"
when "../../p:role = 'pce'" + + "or "
"or " + + "../../pcep:role = 'pcc-and-pce'" {
"../../p:role = 'pcc-and-pce'"
{
description description
"Valid for PCEP Peer as PCE"; "Valid for PCEP Peer as PCE";
} }
type uint32; type uint32;
units "milliseconds"; units "milliseconds";
description description
"The greatest (high-water mark) response time seen. "The greatest (high-water mark) response time seen.
If no responses have been received then this object If no responses have been received then this object
has the value zero."; has the value zero.";
} }
leaf num-pcreq-sent {
leaf num-pcreq-sent{ when "../../pcep:role = 'pce'"
when "../../p:role = 'pce'" + + "or "
"or " + + "../../pcep:role = 'pcc-and-pce'" {
"../../p:role = 'pcc-and-pce'"
{
description
"Valid for PCEP Peer as PCE";
}
type yang:counter32;
description description
"The number of PCReq messages sent."; "Valid for PCEP Peer as PCE";
}
type yang:counter32;
description
"The number of PCReq messages sent.";
} }
leaf num-pcreq-rcvd {
leaf num-pcreq-rcvd{ when "../../pcep:role = 'pcc'"
when "../../p:role = 'pcc'" + + "or "
"or " + + "../../pcep:role = 'pcc-and-pce'" {
"../../p:role = 'pcc-and-pce'"
{
description description
"Valid for PCEP Peer as PCC"; "Valid for PCEP Peer as PCC";
} }
type yang:counter32; type yang:counter32;
description description
"The number of PCReq messages received."; "The number of PCReq messages received.";
} }
leaf num-pcrep-sent {
leaf num-pcrep-sent{ when "../../pcep:role = 'pcc'"
when "../../p:role = 'pcc'" + + "or "
"or " + + "../../pcep:role = 'pcc-and-pce'" {
"../../p:role = 'pcc-and-pce'"
{
description description
"Valid for PCEP Peer as PCC"; "Valid for PCEP Peer as PCC";
} }
type yang:counter32; type yang:counter32;
description description
"The number of PCRep messages sent."; "The number of PCRep messages sent.";
}
leaf num-pcrep-rcvd {
when "../../pcep:role = 'pce'"
+ "or "
+ "../../pcep:role = 'pcc-and-pce'" {
description
"Valid for PCEP Peer as PCE";
} }
type yang:counter32;
leaf num-pcrep-rcvd{ description
when "../../p:role = 'pce'" + "The number of PCRep messages received.";
"or " + }
"../../p:role = 'pcc-and-pce'" leaf num-pcerr-sent {
{ type yang:counter32;
description description
"Valid for PCEP Peer as PCE"; "The number of PCErr messages sent.";
} }
leaf num-pcerr-rcvd {
type yang:counter32; type yang:counter32;
description
"The number of PCErr messages received.";
}
leaf num-pcntf-sent {
type yang:counter32;
description
"The number of PCNtf messages sent.";
}
leaf num-pcntf-rcvd {
type yang:counter32;
description
"The number of PCNtf messages received.";
}
leaf num-keepalive-sent {
type yang:counter32;
description
"The number of Keepalive messages sent.";
}
leaf num-keepalive-rcvd {
type yang:counter32;
description
"The number of Keepalive messages received.";
}
leaf num-unknown-rcvd {
type yang:counter32;
description
"The number of unknown messages received.";
}
leaf num-corrupt-rcvd {
type yang:counter32;
description
"The number of corrupted PCEP message received.";
}
leaf num-req-sent {
when "../../pcep:role = 'pce'"
+ "or "
+ "../../pcep:role = 'pcc-and-pce'" {
description description
"The number of PCRep messages received."; "Valid for PCEP Peer as PCE";
} }
type yang:counter32;
leaf num-pcerr-sent{ description
type yang:counter32; "The number of requests sent. A request corresponds
1:1 with an RP object in a PCReq message. This might
be greater than num-pcreq-sent because multiple
requests can be batched into a single PCReq
message.";
}
leaf num-req-sent-pend-rep {
when "../../pcep:role = 'pce'"
+ "or "
+ "../../pcep:role = 'pcc-and-pce'" {
description description
"The number of PCErr messages sent."; "Valid for PCEP Peer as PCE";
} }
type yang:counter32;
leaf num-pcerr-rcvd{ description
type yang:counter32; "The number of requests that have been sent for
which a response is still pending.";
}
leaf num-req-sent-ero-rcvd {
when "../../pcep:role = 'pce'"
+ "or "
+ "../../pcep:role = 'pcc-and-pce'" {
description description
"The number of PCErr messages received."; "Valid for PCEP Peer as PCE";
} }
type yang:counter32;
leaf num-pcntf-sent{ description
type yang:counter32; "The number of requests that have been sent for
which a response with an ERO object was received.
Such responses indicate that a path was
successfully computed by the peer.";
}
leaf num-req-sent-nopath-rcvd {
when "../../pcep:role = 'pce'"
+ "or "
+ "../../pcep:role = 'pcc-and-pce'" {
description description
"The number of PCNtf messages sent."; "Valid for PCEP Peer as PCE";
} }
type yang:counter32;
leaf num-pcntf-rcvd{ description
type yang:counter32; "The number of requests that have been sent for
which a response with a NO-PATH object was
received. Such responses indicate that the peer
could not find a path to satisfy the
request.";
}
leaf num-req-sent-cancel-rcvd {
when "../../pcep:role = 'pce'"
+ "or "
+ "../../pcep:role = 'pcc-and-pce'" {
description description
"The number of PCNtf messages received."; "Valid for PCEP Peer as PCE";
} }
type yang:counter32;
leaf num-keepalive-sent{ description
type yang:counter32; "The number of requests that were cancelled with
a PCNtf message. This might be different than
num-pcntf-rcvd because not all PCNtf messages are
used to cancel requests, and a single PCNtf message
can cancel multiple requests.";
}
leaf num-req-sent-error-rcvd {
when "../../pcep:role = 'pce'"
+ "or "
+ "../../pcep:role = 'pcc-and-pce'" {
description description
"The number of Keepalive messages sent."; "Valid for PCEP Peer as PCE";
} }
type yang:counter32;
leaf num-keepalive-rcvd{ description
type yang:counter32; "The number of requests that were rejected with a
PCErr message. This might be different than
num-pcerr-rcvd because not all PCErr messages are
used to reject requests, and a single PCErr message
can reject multiple requests.";
}
leaf num-req-sent-timeout {
when "../../pcep:role = 'pce'"
+ "or "
+ "../../pcep:role = 'pcc-and-pce'" {
description description
"The number of Keepalive messages received."; "Valid for PCEP Peer as PCE";
} }
type yang:counter32;
leaf num-unknown-rcvd{ description
type yang:counter32; "The number of requests that have been sent to a peer
and have been abandoned because the peer has taken too
long to respond to them.";
}
leaf num-req-sent-cancel-sent {
when "../../pcep:role = 'pce'"
+ "or "
+ "../../pcep:role = 'pcc-and-pce'" {
description description
"The number of unknown messages received."; "Valid for PCEP Peer as PCE";
} }
type yang:counter32;
leaf num-corrupt-rcvd{ description
type yang:counter32; "The number of requests that were sent to the peer and
explicitly cancelled by the local PCEP entity sending
a PCNtf.";
}
leaf num-req-rcvd {
when "../../pcep:role = 'pcc'"
+ "or "
+ "../../pcep:role = 'pcc-and-pce'" {
description description
"The number of corrupted PCEP message received."; "Valid for PCEP Peer as PCC";
} }
type yang:counter32;
leaf num-req-sent{ description
when "../../p:role = 'pce'" + "The number of requests received. A request
"or " + corresponds 1:1 with an RP object in a PCReq
"../../p:role = 'pcc-and-pce'" message.
{ This might be greater than num-pcreq-rcvd because
description multiple requests can be batched into a single
"Valid for PCEP Peer as PCE"; PCReq message.";
} }
type yang:counter32; leaf num-req-rcvd-pend-rep {
when "../../pcep:role = 'pcc'"
+ "or "
+ "../../pcep:role = 'pcc-and-pce'" {
description description
"The number of requests sent. A request corresponds "Valid for PCEP Peer as PCC";
1:1 with an RP object in a PCReq message. This might
be greater than num-pcreq-sent because multiple
requests can be batched into a single PCReq
message.";
} }
type yang:counter32;
leaf num-req-sent-pend-rep{ description
when "../../p:role = 'pce'" + "The number of requests that have been received for
"or " + which a response is still pending.";
"../../p:role = 'pcc-and-pce'" }
{ leaf num-req-rcvd-ero-sent {
description when "../../pcep:role = 'pcc'"
"Valid for PCEP Peer as PCE"; + "or "
} + "../../pcep:role = 'pcc-and-pce'" {
type yang:counter32;
description description
"The number of requests that have been sent for "Valid for PCEP Peer as PCC";
which a response is still pending."; }
type yang:counter32;
description
"The number of requests that have been received for
which a response with an ERO object was sent. Such
responses indicate that a path was successfully
computed by the local PCEP entity.";
}
leaf num-req-rcvd-nopath-sent {
when "../../pcep:role = 'pcc'"
+ "or "
+ "../../pcep:role = 'pcc-and-pce'" {
description
"Valid for PCEP Peer as PCC";
}
type yang:counter32;
description
"The number of requests that have been received for
which a response with a NO-PATH object was sent. Such
responses indicate that the local PCEP entity could
not find a path to satisfy the request.";
}
leaf num-req-rcvd-cancel-sent {
when "../../pcep:role = 'pcc'"
+ "or "
+ "../../pcep:role = 'pcc-and-pce'" {
description
"Valid for PCEP Peer as PCC";
} }
type yang:counter32;
description
"The number of requests received that were cancelled
by the local PCEP entity sending a PCNtf message.
leaf num-req-sent-ero-rcvd{ This might be different than num-pcntf-sent because
when "../../p:role = 'pce'" + not all PCNtf messages are used to cancel requests,
"or " + and a single PCNtf message can cancel multiple
"../../p:role = 'pcc-and-pce'" requests.";
{ }
description leaf num-req-rcvd-error-sent {
"Valid for PCEP Peer as PCE"; when "../../pcep:role = 'pcc'"
} + "or "
type yang:counter32; + "../../pcep:role = 'pcc-and-pce'" {
description description
"The number of requests that have been sent for "Valid for PCEP Peer as PCC";
which a response with an ERO object was received.
Such responses indicate that a path was
successfully computed by the peer.";
} }
type yang:counter32;
description
"The number of requests received that were cancelled
by the local PCEP entity sending a PCErr message.
This might be different than num-pcerr-sent because
not all PCErr messages are used to cancel requests,
and a single PCErr message can cancel multiple
requests.";
}
leaf num-req-rcvd-cancel-rcvd {
when "../../pcep:role = 'pcc'"
+ "or "
+ "../../pcep:role = 'pcc-and-pce'" {
description
"Valid for PCEP Peer as PCC";
}
type yang:counter32;
description
"The number of requests that were received from the
peer and explicitly cancelled by the peer sending
a PCNtf.";
}
leaf num-rep-rcvd-unknown {
when "../../pcep:role = 'pce'"
+ "or "
+ "../../pcep:role = 'pcc-and-pce'" {
description
"Valid for PCEP Peer as PCE";
}
type yang:counter32;
description
"The number of responses to unknown requests
received. A response to an unknown request is a
response whose RP object does not contain the
request ID of any request that is currently
outstanding on the session.";
leaf num-req-sent-nopath-rcvd{ }
when "../../p:role = 'pce'" + leaf num-req-rcvd-unknown {
"or " + when "../../pcep:role = 'pcc'"
"../../p:role = 'pcc-and-pce'" + "or "
{ + "../../pcep:role = 'pcc-and-pce'" {
description
"Valid for PCEP Peer as PCC";
}
type yang:counter32;
description
"The number of unknown requests that have been
received. An unknown request is a request
whose RP object contains a request ID of zero.";
}
container svec {
if-feature "pcep:svec";
description
"If synchronized path computation is supported";
leaf num-svec-sent {
when "../../../pcep:role = 'pce'"
+ "or "
+ "../../../pcep:role = 'pcc-and-pce'" {
description description
"Valid for PCEP Peer as PCE"; "Valid for PCEP Peer as PCE";
} }
type yang:counter32; type yang:counter32;
description description
"The number of requests that have been sent for "The number of SVEC objects sent in PCReq messages.
which a response with a NO-PATH object was An SVEC object represents a set of synchronized
received. Such responses indicate that the peer requests.";
could not find a path to satisfy the
request.";
} }
leaf num-svec-req-sent {
leaf num-req-sent-cancel-rcvd{ when "../../../pcep:role = 'pce'"
when "../../p:role = 'pce'" + + "or "
"or " + + "../../../pcep:role = 'pcc-and-pce'" {
"../../p:role = 'pcc-and-pce'"
{
description description
"Valid for PCEP Peer as PCE"; "Valid for PCEP Peer as PCE";
} }
type yang:counter32; type yang:counter32;
description description
"The number of requests that were cancelled with "The number of requests sent that appeared in one
a PCNtf message. This might be different than or more SVEC objects.";
num-pcntf-rcvd because not all PCNtf messages are
used to cancel requests, and a single PCNtf message
can cancel multiple requests.";
} }
leaf num-svec-rcvd {
leaf num-req-sent-error-rcvd{ when "../../../pcep:role = 'pcc'"
when "../../p:role = 'pce'" + + "or "
"or " + + "../../../pcep:role = 'pcc-and-pce'" {
"../../p:role = 'pcc-and-pce'"
{
description description
"Valid for PCEP Peer as PCE"; "Valid for PCEP Peer as PCC";
} }
type yang:counter32; type yang:counter32;
description description
"The number of requests that were rejected with a "The number of SVEC objects received in PCReq
PCErr message. This might be different than messages. An SVEC object represents a set of
num-pcerr-rcvd because not all PCErr messages are synchronized requests.";
used to reject requests, and a single PCErr message
can reject multiple requests.";
} }
leaf num-svec-req-rcvd {
leaf num-req-sent-timeout{ when "../../../pcep:role = 'pcc'"
when "../../p:role = 'pce'" + + "or "
"or " + + "../../../pcep:role = 'pcc-and-pce'" {
"../../p:role = 'pcc-and-pce'"
{
description description
"Valid for PCEP Peer as PCE"; "Valid for PCEP Peer as PCC";
} }
type yang:counter32; type yang:counter32;
description description
"The number of requests that have been sent to a peer "The number of requests received that appeared
and have been abandoned because the peer has taken too in one or more SVEC objects.";
long to respond to them.";
} }
}
leaf num-req-sent-cancel-sent{ //svec
when "../../p:role = 'pce'" + container stateful {
"or " + if-feature "pcep:stateful";
"../../p:role = 'pcc-and-pce'" description
{ "Stateful PCE related statistics";
leaf num-pcrpt-sent {
when "../../../pcep:role = 'pce'"
+ "or "
+ "../../../pcep:role = 'pcc-and-pce'" {
description description
"Valid for PCEP Peer as PCE"; "Valid for PCEP Peer as PCE";
} }
type yang:counter32; type yang:counter32;
description description
"The number of requests that were sent to the peer and "The number of PCRpt messages sent.";
explicitly cancelled by the local PCEP entity sending
a PCNtf.";
} }
leaf num-pcrpt-rcvd {
leaf num-req-rcvd{ when "../../../pcep:role = 'pcc'"
when "../../p:role = 'pcc'" + + "or "
"or " + + "../../../pcep:role = 'pcc-and-pce'" {
"../../p:role = 'pcc-and-pce'"
{
description description
"Valid for PCEP Peer as PCC"; "Valid for PCEP Peer as PCC";
} }
type yang:counter32; type yang:counter32;
description description
"The number of requests received. A request "The number of PCRpt messages received.";
corresponds 1:1 with an RP object in a PCReq
message.
This might be greater than num-pcreq-rcvd because
multiple requests can be batched into a single
PCReq message.";
} }
leaf num-pcupd-sent {
leaf num-req-rcvd-pend-rep{ when "../../../pcep:role = 'pcc'"
when "../../p:role = 'pcc'" + + "or "
"or " + + "../../../pcep:role = 'pcc-and-pce'" {
"../../p:role = 'pcc-and-pce'"
{
description description
"Valid for PCEP Peer as PCC"; "Valid for PCEP Peer as PCC";
} }
type yang:counter32; type yang:counter32;
description description
"The number of requests that have been received for "The number of PCUpd messages sent.";
which a response is still pending.";
} }
leaf num-pcupd-rcvd {
leaf num-req-rcvd-ero-sent{ when "../../../pcep:role = 'pce'"
when "../../p:role = 'pcc'" + + "or "
"or " + + "../../../pcep:role = 'pcc-and-pce'" {
"../../p:role = 'pcc-and-pce'"
{
description description
"Valid for PCEP Peer as PCC"; "Valid for PCEP Peer as PCE";
} }
type yang:counter32; type yang:counter32;
description description
"The number of requests that have been received for "The number of PCUpd messages received.";
which a response with an ERO object was sent. Such
responses indicate that a path was successfully
computed by the local PCEP entity.";
} }
leaf num-rpt-sent {
leaf num-req-rcvd-nopath-sent{ when "../../../pcep:role = 'pce'"
when "../../p:role = 'pcc'" + + "or "
"or " + + "../../../pcep:role = 'pcc-and-pce'" {
"../../p:role = 'pcc-and-pce'"
{
description description
"Valid for PCEP Peer as PCC"; "Valid for PCEP Peer as PCE";
} }
type yang:counter32; type yang:counter32;
description description
"The number of requests that have been received for "The number of LSP Reports sent. A LSP report
which a response with a NO-PATH object was sent. Such corresponds 1:1 with an LSP object in a PCRpt
responses indicate that the local PCEP entity could message. This might be greater than
not find a path to satisfy the request."; num-pcrpt-sent because multiple reports can
be batched into a single PCRpt message.";
} }
leaf num-rpt-rcvd {
leaf num-req-rcvd-cancel-sent{ when "../../../pcep:role = 'pcc'"
when "../../p:role = 'pcc'" + + "or "
"or " + + "../../../pcep:role = 'pcc-and-pce'" {
"../../p:role = 'pcc-and-pce'"
{
description description
"Valid for PCEP Peer as PCC"; "Valid for PCEP Peer as PCC";
} }
type yang:counter32; type yang:counter32;
description description
"The number of requests received that were cancelled "The number of LSP Reports received. A LSP report
by the local PCEP entity sending a PCNtf message. corresponds 1:1 with an LSP object in a PCRpt
This might be different than num-pcntf-sent because message.
not all PCNtf messages are used to cancel requests, This might be greater than num-pcrpt-rcvd because
and a single PCNtf message can cancel multiple multiple reports can be batched into a single
requests."; PCRpt message.";
} }
leaf num-rpt-rcvd-error-sent {
leaf num-req-rcvd-error-sent{ when "../../../pcep:role = 'pcc'"
when "../../p:role = 'pcc'" + + "or "
"or " + + "../../../pcep:role = 'pcc-and-pce'" {
"../../p:role = 'pcc-and-pce'"
{
description description
"Valid for PCEP Peer as PCC"; "Valid for PCEP Peer as PCC";
} }
type yang:counter32; type yang:counter32;
description description
"The number of requests received that were cancelled "The number of reports of LSPs received that were
by the local PCEP entity sending a PCErr message. responded by the local PCEP entity by sending a
This might be different than num-pcerr-sent because PCErr message.";
not all PCErr messages are used to cancel requests,
and a single PCErr message can cancel multiple
requests.";
} }
leaf num-upd-sent {
leaf num-req-rcvd-cancel-rcvd{ when "../../../pcep:role = 'pcc'"
when "../../p:role = 'pcc'" + + "or "
"or " + + "../../../pcep:role = 'pcc-and-pce'" {
"../../p:role = 'pcc-and-pce'"
{
description description
"Valid for PCEP Peer as PCC"; "Valid for PCEP Peer as PCC";
} }
type yang:counter32; type yang:counter32;
description description
"The number of requests that were received from the "The number of LSP updates sent. A LSP update
peer and explicitly cancelled by the peer sending corresponds 1:1 with an LSP object in a PCUpd
a PCNtf."; message. This might be greater than
num-pcupd-sent because multiple updates can
be batched into a single PCUpd message.";
} }
leaf num-rep-rcvd-unknown{ leaf num-upd-rcvd {
when "../../p:role = 'pce'" + when "../../../pcep:role = 'pce'"
"or " + + "or "
"../../p:role = 'pcc-and-pce'" + "../../../pcep:role = 'pcc-and-pce'" {
{
description description
"Valid for PCEP Peer as PCE"; "Valid for PCEP Peer as PCE";
} }
type yang:counter32; type yang:counter32;
description description
"The number of responses to unknown requests "The number of LSP Updates received. A LSP update
received. A response to an unknown request is a corresponds 1:1 with an LSP object in a PCUpd
response whose RP object does not contain the message.
request ID of any request that is currently This might be greater than num-pcupd-rcvd because
outstanding on the session."; multiple updates can be batched into a single
} PCUpd message.";
leaf num-req-rcvd-unknown{ }
when "../../p:role = 'pcc'" + leaf num-upd-rcvd-unknown {
"or " + when "../../../pcep:role = 'pce'"
"../../p:role = 'pcc-and-pce'" + "or "
{ + "../../../pcep:role = 'pcc-and-pce'" {
description description
"Valid for PCEP Peer as PCC"; "Valid for PCEP Peer as PCE";
} }
type yang:counter32; type yang:counter32;
description description
"The number of unknown requests that have been "The number of updates to unknown LSPs
received. An unknown request is a request received. An update to an unknown LSP is a
whose RP object contains a request ID of zero."; update whose LSP object does not contain the
PLSP-ID of any LSP that is currently
present.";
} }
leaf num-upd-rcvd-undelegated {
container svec{ when "../../../pcep:role = 'pce'"
if-feature p:svec; + "or "
description + "../../../pcep:role = 'pcc-and-pce'" {
"If synchronized path computation is supported";
leaf num-svec-sent{
when "../../../p:role = 'pce'" +
"or " +
"../../../p:role = 'pcc-and-pce'"
{
description
"Valid for PCEP Peer as PCE";
}
type yang:counter32;
description
"The number of SVEC objects sent in PCReq messages.
An SVEC object represents a set of synchronized
requests.";
}
leaf num-svec-req-sent{
when "../../../p:role = 'pce'" +
"or " +
"../../../p:role = 'pcc-and-pce'"
{
description
"Valid for PCEP Peer as PCE";
}
type yang:counter32;
description
"The number of requests sent that appeared in one
or more SVEC objects.";
}
leaf num-svec-rcvd{
when "../../../p:role = 'pcc'" +
"or " +
"../../../p:role = 'pcc-and-pce'"
{
description
"Valid for PCEP Peer as PCC";
}
type yang:counter32;
description
"The number of SVEC objects received in PCReq
messages. An SVEC object represents a set of
synchronized requests.";
}
leaf num-svec-req-rcvd{
when "../../../p:role = 'pcc'" +
"or " +
"../../../p:role = 'pcc-and-pce'"
{
description
"Valid for PCEP Peer as PCC";
}
type yang:counter32;
description description
"The number of requests received that appeared "Valid for PCEP Peer as PCE";
in one or more SVEC objects.";
} }
}//svec type yang:counter32;
container stateful{
if-feature p:stateful;
description description
"Stateful PCE related statistics"; "The number of updates to not delegated LSPs
leaf num-pcrpt-sent{ received. An update to an undelegated LSP is a
when "../../../p:role = 'pce'" + update whose LSP object does not contain the
"or " + PLSP-ID of any LSP that is currently
"../../../p:role = 'pcc-and-pce'" delegated to current PCEP session.";
{ }
description leaf num-upd-rcvd-error-sent {
"Valid for PCEP Peer as PCE"; when "../../../pcep:role = 'pce'"
} + "or "
type yang:counter32; + "../../../pcep:role = 'pcc-and-pce'" {
description
"The number of PCRpt messages sent.";
}
leaf num-pcrpt-rcvd{
when "../../../p:role = 'pcc'" +
"or " +
"../../../p:role = 'pcc-and-pce'"
{
description
"Valid for PCEP Peer as PCC";
}
type yang:counter32;
description
"The number of PCRpt messages received.";
}
leaf num-pcupd-sent{
when "../../../p:role = 'pcc'" +
"or " +
"../../../p:role = 'pcc-and-pce'"
{
description
"Valid for PCEP Peer as PCC";
}
type yang:counter32;
description
"The number of PCUpd messages sent.";
}
leaf num-pcupd-rcvd{
when "../../../p:role = 'pce'" +
"or " +
"../../../p:role = 'pcc-and-pce'"
{
description
"Valid for PCEP Peer as PCE";
}
type yang:counter32;
description
"The number of PCUpd messages received.";
}
leaf num-rpt-sent{
when "../../../p:role = 'pce'" +
"or " +
"../../../p:role = 'pcc-and-pce'"
{
description
"Valid for PCEP Peer as PCE";
}
type yang:counter32;
description
"The number of LSP Reports sent. A LSP report
corresponds 1:1 with an LSP object in a PCRpt
message. This might be greater than
num-pcrpt-sent because multiple reports can
be batched into a single PCRpt message.";
}
leaf num-rpt-rcvd{
when "../../../p:role = 'pcc'" +
"or " +
"../../../p:role = 'pcc-and-pce'"
{
description
"Valid for PCEP Peer as PCC";
}
type yang:counter32;
description
"The number of LSP Reports received. A LSP report
corresponds 1:1 with an LSP object in a PCRpt
message.
This might be greater than num-pcrpt-rcvd because
multiple reports can be batched into a single
PCRpt message.";
}
leaf num-rpt-rcvd-error-sent{
when "../../../p:role = 'pcc'" +
"or " +
"../../../p:role = 'pcc-and-pce'"
{
description
"Valid for PCEP Peer as PCC";
}
type yang:counter32;
description
"The number of reports of LSPs received that were
responded by the local PCEP entity by sending a
PCErr message.";
}
leaf num-upd-sent{
when "../../../p:role = 'pcc'" +
"or " +
"../../../p:role = 'pcc-and-pce'"
{
description
"Valid for PCEP Peer as PCC";
}
type yang:counter32;
description
"The number of LSP updates sent. A LSP update
corresponds 1:1 with an LSP object in a PCUpd
message. This might be greater than
num-pcupd-sent because multiple updates can
be batched into a single PCUpd message.";
}
leaf num-upd-rcvd{
when "../../../p:role = 'pce'" +
"or " +
"../../../p:role = 'pcc-and-pce'"
{
description
"Valid for PCEP Peer as PCE";
}
type yang:counter32;
description
"The number of LSP Updates received. A LSP update
corresponds 1:1 with an LSP object in a PCUpd
message.
This might be greater than num-pcupd-rcvd because
multiple updates can be batched into a single
PCUpd message.";
}
leaf num-upd-rcvd-unknown{
when "../../../p:role = 'pce'" +
"or " +
"../../../p:role = 'pcc-and-pce'"
{
description
"Valid for PCEP Peer as PCE";
}
type yang:counter32;
description
"The number of updates to unknown LSPs
received. An update to an unknown LSP is a
update whose LSP object does not contain the
PLSP-ID of any LSP that is currently
present.";
}
leaf num-upd-rcvd-undelegated{
when "../../../p:role = 'pce'" +
"or " +
"../../../p:role = 'pcc-and-pce'"
{
description
"Valid for PCEP Peer as PCE";
}
type yang:counter32;
description description
"The number of updates to not delegated LSPs "Valid for PCEP Peer as PCE";
received. An update to an undelegated LSP is a
update whose LSP object does not contain the
PLSP-ID of any LSP that is currently
delegated to current PCEP session.";
} }
type yang:counter32;
leaf num-upd-rcvd-error-sent{ description
when "../../../p:role = 'pce'" + "The number of updates to LSPs received that were
"or " + responded by the local PCEP entity by sending a
"../../../p:role = 'pcc-and-pce'" PCErr message.";
{ }
description
"Valid for PCEP Peer as PCE";
}
type yang:counter32;
description
"The number of updates to LSPs received that were
responded by the local PCEP entity by sending a
PCErr message.";
}
container initiation { container initiation {
if-feature p:pce-initiated; if-feature "pcep:pce-initiated";
description description
"PCE-Initiated related statistics"; "PCE-Initiated related statistics";
leaf num-pcinitiate-sent{
when "../../../../p:role = 'pcc'" + leaf num-pcinitiate-sent {
"or " + when "../../../../pcep:role = 'pcc'"
"../../../../p:role = 'pcc-and-pce'" + "or "
{ + "../../../../pcep:role = 'pcc-and-pce'" {
description description
"Valid for PCEP Peer as PCC"; "Valid for PCEP Peer as PCC";
} }
type yang:counter32; type yang:counter32;
description description
"The number of PCInitiate messages sent."; "The number of PCInitiate messages sent.";
} }
leaf num-pcinitiate-rcvd{ leaf num-pcinitiate-rcvd {
when "../../../../p:role = 'pce'" + when "../../../../pcep:role = 'pce'"
"or " + + "or "
"../../../../p:role = 'pcc-and-pce'" + "../../../../pcep:role = 'pcc-and-pce'" {
{
description description
"Valid for PCEP Peer as PCE"; "Valid for PCEP Peer as PCE";
} }
type yang:counter32; type yang:counter32;
description description
"The number of PCInitiate messages received."; "The number of PCInitiate messages received.";
} }
leaf num-initiate-sent {
leaf num-initiate-sent{ when "../../../../pcep:role = 'pcc'"
when "../../../../p:role = 'pcc'" + + "or "
"or " + + "../../../../pcep:role = 'pcc-and-pce'" {
"../../../../p:role = 'pcc-and-pce'"
{
description description
"Valid for PCEP Peer as PCC"; "Valid for PCEP Peer as PCC";
} }
type yang:counter32; type yang:counter32;
description description
"The number of LSP Initiation sent via PCE. "The number of LSP Initiation sent via PCE.
A LSP initiation corresponds 1:1 with an LSP A LSP initiation corresponds 1:1 with an LSP
object in a PCInitiate message. This might be object in a PCInitiate message. This might be
greater than num-pcinitiate-sent because greater than num-pcinitiate-sent because
multiple initiations can be batched into a multiple initiations can be batched into a
single PCInitiate message."; single PCInitiate message.";
} }
leaf num-initiate-rcvd {
leaf num-initiate-rcvd{ when "../../../../pcep:role = 'pce'"
when "../../../../p:role = 'pce'" + + "or "
"or " + + "../../../../pcep:role = 'pcc-and-pce'" {
"../../../../p:role = 'pcc-and-pce'"
{
description description
"Valid for PCEP Peer as PCE"; "Valid for PCEP Peer as PCE";
} }
type yang:counter32; type yang:counter32;
description description
"The number of LSP Initiation received from "The number of LSP Initiation received from
PCE. A LSP initiation corresponds 1:1 with PCE. A LSP initiation corresponds 1:1 with
an LSP object in a PCInitiate message. This an LSP object in a PCInitiate message. This
might be greater than num-pcinitiate-rcvd might be greater than num-pcinitiate-rcvd
because multiple initiations can be batched because multiple initiations can be batched
into a single PCInitiate message."; into a single PCInitiate message.";
} }
leaf num-initiate-rcvd-error-sent{ leaf num-initiate-rcvd-error-sent {
when "../../../../p:role = 'pce'" + when "../../../../pcep:role = 'pce'"
"or " + + "or "
"../../../../p:role = 'pcc-and-pce'" + "../../../../pcep:role = 'pcc-and-pce'" {
{
description description
"Valid for PCEP Peer as PCE"; "Valid for PCEP Peer as PCE";
} }
type yang:counter32; type yang:counter32;
description description
"The number of initiations of LSPs received "The number of initiations of LSPs received
that were responded by the local PCEP entity that were responded by the local PCEP entity
by sending a PCErr message."; by sending a PCErr message.";
} }
}//initiation }
}//stateful //initiation
}
//stateful
container path-key { container path-key {
when "../../p:role = 'pcc'" + when "../../pcep:role = 'pcc'"
"or " + + "or "
"../../p:role = 'pcc-and-pce'" + "../../pcep:role = 'pcc-and-pce'" {
{
description description
"Valid for PCEP Peer as PCC"; "Valid for PCEP Peer as PCC";
} }
if-feature p:path-key; if-feature "pcep:path-key";
description description
"If Path-Key is supported"; "If Path-Key is supported";
leaf num-unknown-path-key{ leaf num-unknown-path-key {
type yang:counter32; type yang:counter32;
description description
"The number of attempts to expand an unknown "The number of attempts to expand an unknown
path-key."; path-key.";
} }
leaf num-exp-path-key{ leaf num-exp-path-key {
type yang:counter32; type yang:counter32;
description description
"The number of attempts to expand an expired "The number of attempts to expand an expired
path-key."; path-key.";
} }
leaf num-dup-path-key{ leaf num-dup-path-key {
type yang:counter32; type yang:counter32;
description description
"The number of duplicate attempts to expand same "The number of duplicate attempts to expand same
path-key."; path-key.";
} }
leaf num-path-key-no-attempt{ leaf num-path-key-no-attempt {
type yang:counter32; type yang:counter32;
description description
"The number of expired path-keys with no attempt to "The number of expired path-keys with no attempt to
expand it."; expand it.";
} }
}//path-key }
}//pcep-stats //path-key
}
//pcep-stats
/* /*
* Augment modules to add statistics * Augment modules to add statistics
*/ */
augment "/p:pcep/p:entity/p:peers/p:peer" { augment "/pcep:pcep/pcep:entity/pcep:peers/pcep:peer" {
description description
"Augmenting the statistics"; "Augmenting the statistics";
leaf num-sess-setup-ok {
leaf num-sess-setup-ok{ type yang:counter32;
type yang:counter32; config false;
config false; description
"The number of PCEP sessions successfully established with
the peer, including any current session. This counter is
incremented each time a session with this peer is
successfully established.";
}
leaf num-sess-setup-fail {
type yang:counter32;
config false;
description
"The number of PCEP sessions with the peer
that have been attempted but failed
before being fully established. This
counter is incremented each time a
session retry to this peer fails.";
}
container pcep-stats {
config false;
description
"The container for all statistics at peer level.";
uses pcep-stats {
description description
"The number of PCEP sessions successfully established with "Since PCEP sessions can be ephemeral, the peer statistics
the peer, including any current session. This counter is tracks a peer even when no PCEP session currently exists
incremented each time a session with this peer is to that peer. The statistics contained are an aggregate of
successfully established."; the statistics for all successive sessions to that peer.";
}
leaf num-sess-setup-fail{
type yang:counter32;
config false;
description
"The number of PCEP sessions with the peer
that have been attempted but failed
before being fully established. This
counter is incremented each time a
session retry to this peer fails.";
} }
leaf num-req-sent-closed {
container pcep-stats { when "../../pcep:role = 'pce'"
config false; + "or "
description + "../../pcep:role = 'pcc-and-pce'" {
"The container for all statistics at peer level.";
uses pcep-stats{
description description
"Since PCEP sessions can be ephemeral, the peer statistics "Valid for PCEP Peer as PCE";
tracks a peer even when no PCEP session currently exists
to that peer. The statistics contained are an aggregate of
the statistics for all successive sessions to that peer.";
} }
leaf num-req-sent-closed{ type yang:counter32;
when "../../p:role = 'pce'" + description
"or " + "The number of requests that were sent to the peer and
"../../p:role = 'pcc-and-pce'" implicitly cancelled when the session they were sent
{ over was closed.";
description }
"Valid for PCEP Peer as PCE"; leaf num-req-rcvd-closed {
} when "../../pcep:role = 'pcc'"
type yang:counter32; + "or "
+ "../../pcep:role = 'pcc-and-pce'" {
description description
"The number of requests that were sent to the peer and "Valid for PCEP Peer as PCC";
implicitly cancelled when the session they were sent
over was closed.";
} }
type yang:counter32;
description
"The number of requests that were received from the peer
and implicitly cancelled when the session they were
received over was closed.";
}
}
//pcep-stats
}
leaf num-req-rcvd-closed{ //augment
when "../../p:role = 'pcc'" +
"or " +
"../../p:role = 'pcc-and-pce'"
{
description
"Valid for PCEP Peer as PCC";
}
type yang:counter32;
description
"The number of requests that were received from the peer
and implicitly cancelled when the session they were
received over was closed.";
}
}//pcep-stats
}//augment
augment "/p:pcep/p:entity/p:peers/p:peer/" + augment "/pcep:pcep/pcep:entity/pcep:peers/pcep:peer/"
"p:sessions/p:session" { + "pcep:sessions/pcep:session" {
description description
"Augmenting the statistics"; "Augmenting the statistics";
container pcep-stats { container pcep-stats {
description description
"The container for all statistics at session level."; "The container for all statistics at session level.";
uses pcep-stats{ uses pcep-stats {
description description
"The statistics contained are for the current sessions to "The statistics contained are for the current sessions to
that peer. These are lost when the session goes down."; that peer. These are lost when the session goes down.";
} }
}//pcep-stats }
}//augment //pcep-stats
}//module }
//augment
}
<CODE ENDS> <CODE ENDS>
11. Security Considerations 11. Security Considerations
The YANG module defined in this document is designed to be accessed The YANG module defined in this document is designed to be accessed
via network management protocol such as NETCONF [RFC6241] or RESTCONF via network management protocol such as NETCONF [RFC6241] or RESTCONF
[RFC8040]. The lowest NETCONF layer is the secure transport layer [RFC8040]. The lowest NETCONF layer is the secure transport layer
and the mandatory-to-implement secure transport is SSH [RFC6242]. and the mandatory-to-implement secure transport is SSH [RFC6242].
The lowest RESTCONF layer is HTTPS, and the mandatory-to-implement The lowest RESTCONF layer is HTTPS, and the mandatory-to-implement
secure transport is TLS [RFC8446] secure transport is TLS [RFC8446]
skipping to change at page 99, line 29 skipping to change at page 102, line 36
Registrant Contact: The PCE WG of the IETF. Registrant Contact: The PCE WG of the IETF.
XML: N/A; the requested URI is an XML namespace. XML: N/A; the requested URI is an XML namespace.
This document registers a YANG module in the "YANG Module Names" This document registers a YANG module in the "YANG Module Names"
registry [RFC6020]. registry [RFC6020].
Name: ietf-pcep Name: ietf-pcep
Namespace: urn:ietf:params:xml:ns:yang:ietf-pcep Namespace: urn:ietf:params:xml:ns:yang:ietf-pcep
Prefix: pcep Prefix: pcep
Reference: This I-D Reference: [This.I-D]
Name: ietf-pcep-stats
Namespace: urn:ietf:params:xml:ns:yang:ietf-pcep-stats
Prefix: pcep-stats
Reference: [This.I-D]
13. Acknowledgements 13. Acknowledgements
The initial document is based on the PCEP MIB [RFC7420]. We would The initial document is based on the PCEP MIB [RFC7420]. We would
like to thank the authors of aforementioned documents. like to thank the authors of aforementioned documents.
Thanks to Mahesh Jethmalani for the Yang Doctor review.
Thanks to Martin Bjorklund and Tom Petch for providing guidance
regarding the Yang guidelines.
14. References 14. References
14.1. Normative References 14.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>. <https://www.rfc-editor.org/info/rfc2119>.
[RFC3209] Awduche, D., Berger, L., Gan, D., Li, T., Srinivasan, V., [RFC3209] Awduche, D., Berger, L., Gan, D., Li, T., Srinivasan, V.,
skipping to change at page 102, line 33 skipping to change at page 105, line 51
Protocol (PCEP) Messages", RFC 8408, DOI 10.17487/RFC8408, Protocol (PCEP) Messages", RFC 8408, DOI 10.17487/RFC8408,
July 2018, <https://www.rfc-editor.org/info/rfc8408>. July 2018, <https://www.rfc-editor.org/info/rfc8408>.
[RFC8446] Rescorla, E., "The Transport Layer Security (TLS) Protocol [RFC8446] Rescorla, E., "The Transport Layer Security (TLS) Protocol
Version 1.3", RFC 8446, DOI 10.17487/RFC8446, August 2018, Version 1.3", RFC 8446, DOI 10.17487/RFC8446, August 2018,
<https://www.rfc-editor.org/info/rfc8446>. <https://www.rfc-editor.org/info/rfc8446>.
[I-D.ietf-teas-yang-te] [I-D.ietf-teas-yang-te]
Saad, T., Gandhi, R., Liu, X., Beeram, V., and I. Bryskin, Saad, T., Gandhi, R., Liu, X., Beeram, V., and I. Bryskin,
"A YANG Data Model for Traffic Engineering Tunnels and "A YANG Data Model for Traffic Engineering Tunnels and
Interfaces", draft-ietf-teas-yang-te-19 (work in Interfaces", draft-ietf-teas-yang-te-20 (work in
progress), February 2019. progress), March 2019.
[I-D.ietf-teas-yang-te-types] [I-D.ietf-teas-yang-te-types]
Saad, T., Gandhi, R., Liu, X., Beeram, V., and I. Bryskin, Saad, T., Gandhi, R., Liu, X., Beeram, V., and I. Bryskin,
"Traffic Engineering Common YANG Types", draft-ietf-teas- "Traffic Engineering Common YANG Types", draft-ietf-teas-
yang-te-types-06 (work in progress), February 2019. yang-te-types-06 (work in progress), February 2019.
[I-D.ietf-netconf-tls-client-server] [I-D.ietf-netconf-tls-client-server]
Watsen, K., Wu, G., and L. Xia, "YANG Groupings for TLS Watsen, K., Wu, G., and L. Xia, "YANG Groupings for TLS
Clients and TLS Servers", draft-ietf-netconf-tls-client- Clients and TLS Servers", draft-ietf-netconf-tls-client-
server-10 (work in progress), March 2019. server-10 (work in progress), March 2019.
 End of changes. 431 change blocks. 
3236 lines changed or deleted 3378 lines changed or added

This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/