draft-ietf-pce-pcep-yang-06.txt   draft-ietf-pce-pcep-yang-07.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: July 9, 2018 Metaswitch Expires: September 6, 2018 Metaswitch
V. Beeram V. Beeram
Juniper Networks Juniper Networks
J. Tantsura J. Tantsura
January 5, 2018 March 5, 2018
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-06 draft-ietf-pce-pcep-yang-07
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 data and state data (status information and counters configuration data and state data (status information and counters
for the collection of statistics). for the collection of statistics).
skipping to change at page 1, line 40 skipping to change at page 1, line 40
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 July 9, 2018. This Internet-Draft will expire on September 6, 2018.
Copyright Notice Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the Copyright (c) 2018 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 19 skipping to change at page 2, line 19
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
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 . . . . . . . . . . . . . . . 4 3.2. Prefixes in Data Node Names . . . . . . . . . . . . . . . 4
4. Objectives . . . . . . . . . . . . . . . . . . . . . . . . . 5 4. Objectives . . . . . . . . . . . . . . . . . . . . . . . . . 5
5. The Design of PCEP Data Model . . . . . . . . . . . . . . . . 5 5. The Design of PCEP Data Model . . . . . . . . . . . . . . . . 6
5.1. The Overview of PCEP Data Model . . . . . . . . . . . . . 6 5.1. The Overview of PCEP Data Model . . . . . . . . . . . . . 6
5.2. The Full PCEP Data Model . . . . . . . . . . . . . . . . 7 5.2. The Full PCEP Data Model . . . . . . . . . . . . . . . . 7
5.3. The Entity . . . . . . . . . . . . . . . . . . . . . . . 17 5.3. The Entity . . . . . . . . . . . . . . . . . . . . . . . 15
5.4. The Peer Lists . . . . . . . . . . . . . . . . . . . . . 18 5.4. The Peer Lists . . . . . . . . . . . . . . . . . . . . . 16
5.5. The Session Lists . . . . . . . . . . . . . . . . . . . . 18 5.5. The Session Lists . . . . . . . . . . . . . . . . . . . . 16
5.6. Notifications . . . . . . . . . . . . . . . . . . . . . . 19 5.6. Notifications . . . . . . . . . . . . . . . . . . . . . . 17
5.7. RPC . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 5.7. RPC . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
6. The Design of PCEP Statistics Data Model . . . . . . . . . . 19 6. The Design of PCEP Statistics Data Model . . . . . . . . . . 17
7. Advanced PCE Features . . . . . . . . . . . . . . . . . . . . 22 7. Advanced PCE Features . . . . . . . . . . . . . . . . . . . . 20
7.1. Stateful PCE's LSP-DB . . . . . . . . . . . . . . . . . . 22 7.1. Stateful PCE's LSP-DB . . . . . . . . . . . . . . . . . . 20
8. Open Issues and Next Step . . . . . . . . . . . . . . . . . . 23 8. Open Issues and Next Step . . . . . . . . . . . . . . . . . . 21
8.1. The PCE-Initiated LSP . . . . . . . . . . . . . . . . . . 23 8.1. The PCE-Initiated LSP . . . . . . . . . . . . . . . . . . 21
9. Other Considerations . . . . . . . . . . . . . . . . . . . . 23 9. Other Considerations . . . . . . . . . . . . . . . . . . . . 21
9.1. PCEP over TLS (PCEPS) . . . . . . . . . . . . . . . . . . 23 9.1. PCEP over TLS (PCEPS) . . . . . . . . . . . . . . . . . . 21
10. PCEP YANG Modules . . . . . . . . . . . . . . . . . . . . . . 23 10. PCEP YANG Modules . . . . . . . . . . . . . . . . . . . . . . 21
10.1. ietf-pcep module . . . . . . . . . . . . . . . . . . . . 23 10.1. ietf-pcep module . . . . . . . . . . . . . . . . . . . . 21
10.2. ietf-pcep-stats module . . . . . . . . . . . . . . . . . 79 10.2. ietf-pcep-stats module . . . . . . . . . . . . . . . . . 77
11. Security Considerations . . . . . . . . . . . . . . . . . . . 99 11. Security Considerations . . . . . . . . . . . . . . . . . . . 97
12. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 100 12. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 98
13. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 101 13. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 98
14. References . . . . . . . . . . . . . . . . . . . . . . . . . 101 14. References . . . . . . . . . . . . . . . . . . . . . . . . . 98
14.1. Normative References . . . . . . . . . . . . . . . . . . 101 14.1. Normative References . . . . . . . . . . . . . . . . . . 98
14.2. Informative References . . . . . . . . . . . . . . . . . 103 14.2. Informative References . . . . . . . . . . . . . . . . . 100
Appendix A. Example . . . . . . . . . . . . . . . . . . . . . . 104 Appendix A. Example . . . . . . . . . . . . . . . . . . . . . . 102
Appendix B. Contributor Addresses . . . . . . . . . . . . . . . 106 Appendix B. Contributor Addresses . . . . . . . . . . . . . . . 104
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 107 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 105
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 3, line 32 skipping to change at page 3, line 32
"ietf-pcep" which provides the PCEP [RFC5440] data model. "ietf-pcep" which provides the PCEP [RFC5440] data model.
The PCEP operational state is included in the same tree as the PCEP The PCEP operational state is included in the same tree as the PCEP
configuration consistent with Network Management Datastore configuration consistent with Network Management Datastore
Architecture [I-D.ietf-netmod-revised-datastores]. The origin of the Architecture [I-D.ietf-netmod-revised-datastores]. The origin of the
data is indicated as per the origin metadata annotation. data is indicated as per the origin metadata annotation.
2. Requirements Language 2. Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
document are to be interpreted as described in [RFC2119]. "OPTIONAL" in this document are to be interpreted as described in BCP
14 [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here.
3. Terminology and Notation 3. Terminology and Notation
This document uses the terminology defined in [RFC4655] and This document uses the terminology defined in [RFC4655] and
[RFC5440]. In particular, it uses the following acronyms. [RFC5440]. In particular, it uses the following acronyms.
o Path Computation Request message (PCReq). o Path Computation Request message (PCReq).
o Path Computation Reply message (PCRep). o Path Computation Reply message (PCRep).
skipping to change at page 7, line 32 skipping to change at page 7, line 34
... ...
5.2. The Full PCEP Data Model 5.2. 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. speaker.
module: ietf-pcep module: ietf-pcep
+--rw pcep! +--rw pcep!
+--rw entity +--rw entity
+--rw addr +--rw addr inet:ip-address
| inet:ip-address
+--rw enabled? boolean +--rw enabled? boolean
+--rw role +--rw role pcep-role
| pcep-role
+--rw description? string +--rw description? string
+--rw speaker-entity-id? string +--rw speaker-entity-id? string
| {stateful-sync-opt}? | {stateful-sync-opt}?
+--rw admin-status? +--rw admin-status? pcep-admin-status
| pcep-admin-status
+--ro index? uint32 +--ro index? uint32
+--ro oper-status? +--ro oper-status? pcep-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 gmpls? boolean | +--rw gmpls? boolean {gmpls}?
| | {gmpls}?
| +--rw bi-dir? boolean | +--rw bi-dir? boolean
| +--rw diverse? boolean | +--rw diverse? boolean
| +--rw load-balance? boolean | +--rw load-balance? boolean
| +--rw synchronize? boolean | +--rw synchronize? boolean {svec}?
| | {svec}?
| +--rw objective-function? boolean | +--rw objective-function? boolean
| | {objective-function}? | | {objective-function}?
| +--rw add-path-constraint? boolean | +--rw add-path-constraint? boolean
| +--rw prioritization? boolean | +--rw prioritization? boolean
| +--rw multi-request? boolean | +--rw multi-request? boolean
| +--rw gco? boolean | +--rw gco? boolean {gco}?
| | {gco}? | +--rw p2mp? boolean {p2mp}?
| +--rw p2mp? boolean
| | {p2mp}?
| +--rw stateful {stateful}? | +--rw stateful {stateful}?
| | +--rw enabled? boolean | | +--rw enabled? boolean
| | +--rw active? boolean | | +--rw active? boolean
| | +--rw pce-initiated? boolean | | +--rw pce-initiated? boolean
| | | {pce-initiated}? | | | {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 pce-info +--rw pce-info
| +--rw scope | +--rw scope
| | +--rw intra-area-scope? | | +--rw intra-area-scope? boolean
| | | boolean | | +--rw intra-area-pref? uint8
| | +--rw intra-area-pref? | | +--rw inter-area-scope? boolean
| | | uint8 | | +--rw inter-area-scope-default? boolean
| | +--rw inter-area-scope? | | +--rw inter-area-pref? uint8
| | | boolean | | +--rw inter-as-scope? boolean
| | +--rw inter-area-scope-default? | | +--rw inter-as-scope-default? boolean
| | | boolean | | +--rw inter-as-pref? uint8
| | +--rw inter-area-pref? | | +--rw inter-layer-scope? boolean
| | | uint8 | | +--rw inter-layer-pref? uint8
| | +--rw inter-as-scope?
| | | boolean
| | +--rw inter-as-scope-default?
| | | boolean
| | +--rw inter-as-pref?
| | | uint8
| | +--rw inter-layer-scope?
| | | boolean
| | +--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? uint32 +--rw connect-timer? uint32
skipping to change at page 9, line 28 skipping to change at page 9, line 13
+--rw max-backoff-timer? uint32 +--rw max-backoff-timer? uint32
+--rw open-wait-timer? uint32 +--rw open-wait-timer? uint32
+--rw keep-wait-timer? uint32 +--rw keep-wait-timer? uint32
+--rw keep-alive-timer? uint32 +--rw keep-alive-timer? uint32
+--rw dead-timer? uint32 +--rw dead-timer? uint32
+--rw allow-negotiation? boolean +--rw allow-negotiation? boolean
+--rw max-keep-alive-timer? uint32 +--rw max-keep-alive-timer? uint32
+--rw max-dead-timer? uint32 +--rw max-dead-timer? uint32
+--rw min-keep-alive-timer? uint32 +--rw min-keep-alive-timer? uint32
+--rw min-dead-timer? uint32 +--rw min-dead-timer? uint32
+--rw sync-timer? uint32 +--rw sync-timer? uint32 {svec}?
| {svec}?
+--rw request-timer? uint32 +--rw request-timer? uint32
+--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 objective-function | +--rw of objective-function
+--ro lsp-db {stateful}? +--ro lsp-db {stateful}?
| +--ro db-ver? uint64 | +--ro db-ver? uint64 {stateful-sync-opt}?
| | {stateful-sync-opt}?
| +--ro association-list* | +--ro association-list*
| | [id source global-source extended-id] | | [id source global-source extended-id]
| | +--ro type? assoc-type | | +--ro type? assoc-type
| | +--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 leafref | | +--ro plsp-id -> /pcep/entity/lsp-db/lsp/plsp-id
| | +--ro pcc-id leafref | | +--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 | +--ro pcc-id inet:ip-address
| | inet:ip-address
| +--ro lsp-ref | +--ro lsp-ref
| | +--ro source? leafref | | +--ro source?
| | +--ro destination? leafref | | | -> /te:te/lsps-state/lsp/source
| | +--ro tunnel-id? leafref | | +--ro destination?
| | +--ro lsp-id? leafref | | | -> /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? leafref | | +--ro extended-tunnel-id? leafref
| +--ro admin-state? boolean | +--ro admin-state? boolean
| +--ro operational-state? | +--ro operational-state? operational-state
| | operational-state
| +--ro delegated | +--ro delegated
| | +--ro enabled? boolean | | +--ro enabled? boolean
| | +--ro peer? leafref | | +--ro peer? -> /pcep/entity/peers/peer/addr
| | +--ro srp-id? uint32 | | +--ro srp-id? uint32
| +--ro initiation {pce-initiated}? | +--ro initiation {pce-initiated}?
| | +--ro enabled? boolean | | +--ro enabled? boolean
| | +--ro peer? leafref | | +--ro peer? -> /pcep/entity/peers/peer/addr
| +--ro symbolic-path-name? string | +--ro symbolic-path-name? string
| +--ro last-error? lsp-error | +--ro last-error? lsp-error
| +--ro pst? pst | +--ro pst? pst
| +--ro association-list* | +--ro association-list*
| [id source global-source extended-id] | [id source global-source extended-id]
| +--ro id leafref | +--ro id
| | -> /pcep/entity/lsp-db/association-list/id
| +--ro source leafref | +--ro source leafref
| +--ro global-source leafref | +--ro global-source leafref
| +--ro extended-id leafref | +--ro extended-id leafref
+--ro path-keys {path-key}? +--ro path-keys {path-key}?
| +--ro path-keys* [path-key] | +--ro path-keys* [path-key]
| +--ro path-key uint16 | +--ro path-key uint16
| +--ro cps | +--ro cps
| | +--ro explicit-route-objects* | | +--ro explicit-route-objects* [index]
| | [index] | | +--ro explicit-route-usage? identityref
| | +--ro explicit-route-usage? | | +--ro index uint32
| | | identityref
| | +--ro index
| | | uint32
| | +--ro (type)? | | +--ro (type)?
| | +--:(numbered) | | +--:(numbered)
| | | +--ro numbered-hop | | | +--ro numbered-hop
| | | +--ro address? | | | +--ro address? te-types:te-tp-id
| | | | te-types:te-tp-id | | | +--ro hop-type? te-hop-type
| | | +--ro hop-type? | | | +--ro direction? te-link-direction
| | | te-hop-type
| | +--:(as-number) | | +--:(as-number)
| | | +--ro as-number-hop | | | +--ro as-number-hop
| | | +--ro as-number? | | | +--ro as-number? binary
| | | | binary | | | +--ro hop-type? te-hop-type
| | | +--ro hop-type?
| | | te-hop-type
| | +--:(unnumbered) | | +--:(unnumbered)
| | | +--ro unnumbered-hop | | | +--ro unnumbered-hop
| | | +--ro node-id? | | | +--ro node-id? te-types:te-node-id
| | | | te-types:te-node-id | | | +--ro link-tp-id? te-types:te-tp-id
| | | +--ro link-tp-id? | | | +--ro hop-type? te-hop-type
| | | | te-types:te-tp-id | | | +--ro direction? te-link-direction
| | | +--ro hop-type?
| | | te-hop-type
| | +--:(label) | | +--:(label)
| | | +--ro label-hop | | +--ro label-hop
| | | +--ro value? | | +--ro te-label
| | | rt-types:generalized-label | | +--ro (technology)?
| | +--:(sid) | | | +--:(generic)
| | +--ro sid-hop | | | +--ro generic?
| | +--ro sid? | | | rt-types:generalized-label
| | rt-types:generalized-label | | +--ro direction? te-label-direction
| +--ro pcc-original? leafref | +--ro pcc-original? -> /pcep/entity/peers/peer/addr
| +--ro req-id? uint32 | +--ro req-id? uint32
| +--ro retrieved? boolean | +--ro retrieved? boolean
| +--ro pcc-retrieved? leafref | +--ro pcc-retrieved? -> /pcep/entity/peers/peer/addr
| +--ro creation-time? yang:timestamp | +--ro creation-time? yang:timestamp
| +--ro discard-time? uint32 | +--ro discard-time? uint32
| +--ro reuse-time? uint32 | +--ro reuse-time? uint32
+--rw peers +--rw peers
+--rw peer* [addr] +--rw peer* [addr]
+--rw addr +--rw addr inet:ip-address
| inet:ip-address +--rw role pcep-role
+--rw role
| pcep-role
+--rw description? string +--rw description? string
+--rw domain +--rw domain
| +--rw domain* | +--rw domain* [domain-type 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 gmpls? | +--rw gmpls? boolean {gmpls}?
| | boolean {gmpls}? | +--rw bi-dir? boolean
| +--rw bi-dir? | +--rw diverse? boolean
| | boolean | +--rw load-balance? boolean
| +--rw diverse? | +--rw synchronize? boolean {svec}?
| | boolean | +--rw objective-function? boolean
| +--rw load-balance?
| | boolean
| +--rw synchronize?
| | boolean {svec}?
| +--rw objective-function?
| | boolean
| | {objective-function}? | | {objective-function}?
| +--rw add-path-constraint? | +--rw add-path-constraint? boolean
| | boolean | +--rw prioritization? boolean
| +--rw prioritization? | +--rw multi-request? boolean
| | boolean | +--rw gco? boolean {gco}?
| +--rw multi-request? | +--rw p2mp? boolean {p2mp}?
| | boolean
| +--rw gco?
| | boolean {gco}?
| +--rw p2mp?
| | boolean {p2mp}?
| +--rw stateful {stateful}? | +--rw stateful {stateful}?
| | +--rw enabled? | | +--rw enabled? boolean
| | | boolean | | +--rw active? boolean
| | +--rw active? | | +--rw pce-initiated? boolean
| | | boolean
| | +--rw pce-initiated?
| | | boolean
| | | {pce-initiated}? | | | {pce-initiated}?
| | +--rw include-db-ver? | | +--rw include-db-ver? boolean
| | | boolean
| | | {stateful-sync-opt}? | | | {stateful-sync-opt}?
| | +--rw trigger-resync? | | +--rw trigger-resync? boolean
| | | boolean
| | | {stateful-sync-opt}? | | | {stateful-sync-opt}?
| | +--rw trigger-initial-sync? | | +--rw trigger-initial-sync? boolean
| | | boolean
| | | {stateful-sync-opt}? | | | {stateful-sync-opt}?
| | +--rw incremental-sync? | | +--rw incremental-sync? boolean
| | boolean
| | {stateful-sync-opt}? | | {stateful-sync-opt}?
| +--rw sr {sr}? | +--rw sr {sr}?
| +--rw enabled? boolean | +--rw enabled? boolean
+--rw pce-info +--rw pce-info
| +--rw scope | +--rw scope
| | +--rw intra-area-scope? | | +--rw intra-area-scope? boolean
| | | boolean | | +--rw intra-area-pref? uint8
| | +--rw intra-area-pref? | | +--rw inter-area-scope? boolean
| | | uint8 | | +--rw inter-area-scope-default? boolean
| | +--rw inter-area-scope? | | +--rw inter-area-pref? uint8
| | | boolean | | +--rw inter-as-scope? boolean
| | +--rw inter-area-scope-default? | | +--rw inter-as-scope-default? boolean
| | | boolean | | +--rw inter-as-pref? uint8
| | +--rw inter-area-pref? | | +--rw inter-layer-scope? boolean
| | | uint8 | | +--rw inter-layer-pref? uint8
| | +--rw inter-as-scope?
| | | boolean
| | +--rw inter-as-scope-default?
| | | boolean
| | +--rw inter-as-pref?
| | | uint8
| | +--rw inter-layer-scope?
| | | boolean
| | +--rw inter-layer-pref?
| | uint8
| +--rw neigh-domains | +--rw neigh-domains
| +--rw domain* | +--rw domain* [domain-type domain]
| [domain-type domain] | +--rw domain-type domain-type
| +--rw domain-type
| | domain-type
| +--rw domain domain | +--rw domain domain
+--rw delegation-pref? uint8 +--rw delegation-pref? uint8 {stateful}?
| {stateful}?
+--rw auth +--rw auth
| +--rw (auth-type-selection)? | +--rw (auth-type-selection)?
| +--:(auth-key-chain) | +--:(auth-key-chain)
| | +--rw key-chain? | | +--rw key-chain?
| | key-chain:key-chain-ref | | key-chain:key-chain-ref
| +--:(auth-key) | +--:(auth-key)
| | +--rw crypto-algorithm | | +--rw crypto-algorithm identityref
| | | identityref
| | +--rw key-string | | +--rw key-string
| | +--rw (key-string-style)? | | +--rw (key-string-style)?
| | +--:(keystring) | | +--:(keystring)
| | | +--rw keystring? | | | +--rw keystring? string
| | | string
| | +--:(hexadecimal) | | +--:(hexadecimal)
| | {key-chain:hex-key-string}? | | {key-chain:hex-key-string}?
| | +--rw hexadecimal-string? | | +--rw hexadecimal-string?
| | yang:hex-string | | yang:hex-string
| +--:(auth-tls) {tls}? | +--:(auth-tls) {tls}?
| +--rw (role)? | +--rw (role)?
| +--:(server) | +--:(server)
| | +--rw tls-server | | +--rw tls-server
| | +--rw server-identity | | +--rw server-identity
| | | +--rw algorithm? | | | +--rw algorithm?
| | | | identityref | | | | identityref
| | | +--rw private-key? | | | +--rw private-key?
| | | | union | | | | union
| | | +--rw public-key? | | | +--rw public-key?
| | | | binary | | | | binary
| | | +---x generate-private-key | | | +---x generate-private-key
| | | | +---w input | | | | +---w input
| | | | +---w algorithm | | | | +---w algorithm
| | | | identityref | | | | identityref
| | | +--rw certificates | | | +--rw certificates
| | | | +--rw certificate* | | | | +--rw certificate* [name]
| | | | [name] | | | | +--rw name string
| | | | +--rw name | | | | +--rw value? binary
| | | | | string
| | | | +--rw value?
| | | | binary
| | | +---x generate-certificate-signing-request | | | +---x generate-certificate-signing-request
| | | +---w input | | | +---w input
| | | | +---w subject | | | | +---w subject binary
| | | | | binary | | | | +---w attributes? binary
| | | | +---w attributes?
| | | | binary
| | | +--ro output | | | +--ro output
| | | +--ro certificate-signing-request | | | +--ro certificate-signing-request
| | | binary | | | binary
| | +--rw client-auth | | +--rw client-auth
| | | +--rw pinned-ca-certs? | | | +--rw pinned-ca-certs?
| | | | ks:pinned-certificates | | | | ks:pinned-certificates
| | | +--rw pinned-client-certs? | | | +--rw pinned-client-certs?
| | | ks:pinned-certificates | | | ks:pinned-certificates
| | +--rw hello-params | | +--rw hello-params
| | {tls-server-hello-params-config}? | | {tls-server-hello-params-config}?
| | +--rw tls-versions | | +--rw tls-versions
| | | +--rw tls-version* | | | +--rw tls-version* identityref
| | | identityref
| | +--rw cipher-suites | | +--rw cipher-suites
| | +--rw cipher-suite* | | +--rw cipher-suite*
| | identityref | | identityref
| +--:(client) | +--:(client)
| +--rw tls-client | +--rw tls-client
| +--rw client-identity | +--rw client-identity
| | +--rw (auth-type)? | | +--rw (auth-type)?
| | +--:(certificate) | | +--:(certificate)
| | +--rw certificate | | +--rw certificate
| | +--rw algorithm? | | +--rw algorithm?
skipping to change at page 15, line 31 skipping to change at page 14, line 15
| | +--ro certificate-signing-request | | +--ro certificate-signing-request
| | binary | | binary
| +--rw server-auth | +--rw server-auth
| | +--rw pinned-ca-certs? | | +--rw pinned-ca-certs?
| | | ks:pinned-certificates | | | ks:pinned-certificates
| | +--rw pinned-server-certs? | | +--rw pinned-server-certs?
| | ks:pinned-certificates | | ks:pinned-certificates
| +--rw hello-params | +--rw hello-params
| {tls-client-hello-params-config}? | {tls-client-hello-params-config}?
| +--rw tls-versions | +--rw tls-versions
| | +--rw tls-version* | | +--rw tls-version* identityref
| | identityref
| +--rw cipher-suites | +--rw cipher-suites
| +--rw cipher-suite* | +--rw cipher-suite*
| identityref | identityref
+--ro discontinuity-time? +--ro discontinuity-time? yang:timestamp
| yang:timestamp
+--ro initiate-session? boolean +--ro initiate-session? boolean
+--ro session-exists? boolean +--ro session-exists? boolean
+--ro session-up-time? +--ro session-up-time? yang:timestamp
| yang:timestamp +--ro session-fail-time? yang:timestamp
+--ro session-fail-time? +--ro session-fail-up-time? yang:timestamp
| yang:timestamp
+--ro session-fail-up-time?
| yang:timestamp
+--ro sessions +--ro sessions
+--ro session* [initiator] +--ro session* [initiator]
+--ro initiator +--ro initiator pcep-initiator
| pcep-initiator +--ro role? -> /pcep/entity/role
+--ro role? +--ro state-last-change? yang:timestamp
| -> /pcep/entity/role +--ro state? pcep-sess-state
+--ro state-last-change? +--ro session-creation? yang:timestamp
| yang:timestamp +--ro connect-retry? yang:counter32
+--ro state? +--ro local-id? uint32
| pcep-sess-state +--ro remote-id? uint32
+--ro session-creation? +--ro keepalive-timer? uint32
| yang:timestamp +--ro peer-keepalive-timer? uint32
+--ro connect-retry? +--ro dead-timer? uint32
| yang:counter32 +--ro peer-dead-timer? uint32
+--ro local-id? +--ro ka-hold-time-rem? uint32
| uint32 +--ro overloaded? boolean
+--ro remote-id? +--ro overload-time? uint32
| uint32 +--ro peer-overloaded? boolean
+--ro keepalive-timer? +--ro peer-overload-time? uint32
| uint32 +--ro lspdb-sync? sync-state
+--ro peer-keepalive-timer?
| uint32
+--ro dead-timer?
| uint32
+--ro peer-dead-timer?
| uint32
+--ro ka-hold-time-rem?
| uint32
+--ro overloaded?
| boolean
+--ro overload-time?
| uint32
+--ro peer-overloaded?
| boolean
+--ro peer-overload-time?
| uint32
+--ro lspdb-sync?
| sync-state
| {stateful}? | {stateful}?
+--ro recv-db-ver? +--ro recv-db-ver? uint64
| uint64
| {stateful,stateful-sync-opt}? | {stateful,stateful-sync-opt}?
+--ro of-list +--ro of-list {objective-function}?
| {objective-function}? | +--ro objective-function* [of]
| +--ro objective-function* | +--ro of objective-function
| [of] +--ro speaker-entity-id? string
| +--ro of
| objective-function
+--ro speaker-entity-id?
| string
| {stateful-sync-opt}? | {stateful-sync-opt}?
+--ro discontinuity-time? +--ro discontinuity-time? yang:timestamp
yang:timestamp
rpcs: rpcs:
+---x trigger-resync +---x trigger-resync {stateful,stateful-sync-opt}?
{stateful,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? | +--ro peer-addr? -> /pcep/entity/peers/peer/addr
| | -> /pcep/entity/peers/peer/addr | +--ro session-initiator?
| +--ro session-initiator? leafref | | -> /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? | +--ro peer-addr? -> /pcep/entity/peers/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? | +--ro peer-addr? -> /pcep/entity/peers/peer/addr
| | -> /pcep/entity/peers/peer/addr | +--ro session-initiator?
| +--ro session-initiator? leafref | | -> /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? | +--ro peer-addr? -> /pcep/entity/peers/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? | +--ro peer-addr? -> /pcep/entity/peers/peer/addr
| | -> /pcep/entity/peers/peer/addr | +--ro session-initiator?
| +--ro session-initiator? leafref | | -> /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? +--ro peer-addr? -> /pcep/entity/peers/peer/addr
| -> /pcep/entity/peers/peer/addr
+--ro peer-overloaded? boolean +--ro peer-overloaded? boolean
5.3. The Entity 5.3. The Entity
The PCEP yang module may contain status information for the local The PCEP yang module may contain status information for the local
PCEP entity. PCEP entity.
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.
skipping to change at page 23, line 49 skipping to change at page 21, line 49
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@2018-01-05.yang" <CODE BEGINS> file "ietf-pcep@2018-03-05.yang"
module ietf-pcep { module ietf-pcep {
yang-version 1.1; yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-pcep"; namespace "urn:ietf:params:xml:ns:yang:ietf-pcep";
prefix pcep; prefix pcep;
import ietf-inet-types { import ietf-inet-types {
prefix "inet"; prefix "inet";
} }
skipping to change at page 24, line 47 skipping to change at page 22, line 47
import ietf-tls-client { import ietf-tls-client {
prefix "tls-client"; prefix "tls-client";
} }
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: <http://tools.ietf.org/wg/pce/>
WG List: <mailto:pce@ietf.org> WG List: <mailto:pce@ietf.org>
WG Chair: JP Vasseur
<mailto:jpv@cisco.com>
WG Chair: Julien Meuric
<mailto:julien.meuric@orange.com>
WG Chair: Jonathan Hardwick
<mailto:Jonathan.Hardwick@metaswitch.com>
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 common across all of the operational model for PCEP common across all of the
vendor implementations."; vendor implementations.";
revision 2018-01-05 { revision 2018-03-05 {
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 Element Communications Protocol
(PCEP)"; (PCEP)";
} }
/* /*
* Identities * Identities
*/ */
skipping to change at page 56, line 23 skipping to change at page 54, line 14
"List of explicit route objects"; "List of explicit route objects";
leaf explicit-route-usage { leaf explicit-route-usage {
type identityref { type identityref {
base te-types:route-usage-type; base te-types:route-usage-type;
} }
description description
"An explicit-route hop action."; "An explicit-route hop action.";
} }
uses te-types:explicit-route-hop_config; uses te-types:explicit-route-hop;
} }
} }
leaf pcc-original { leaf pcc-original {
type leafref { type leafref {
path "/pcep/entity/peers/peer/addr"; path "/pcep/entity/peers/peer/addr";
} }
description description
"Reference to PCC peer address of "Reference to PCC peer address of
the original request"; the original request";
} }
skipping to change at page 79, line 32 skipping to change at page 77, line 20
} }
} }
}//rpc }//rpc
}//module }//module
<CODE ENDS> <CODE ENDS>
10.2. ietf-pcep-stats module 10.2. ietf-pcep-stats module
<CODE BEGINS> file "ietf-pcep-stats@2018-01-05.yang" <CODE BEGINS> file "ietf-pcep-stats@2018-03-05.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 ps; prefix ps;
import ietf-pcep { import ietf-pcep {
prefix p; prefix p;
skipping to change at page 80, line 9 skipping to change at page 77, line 43
import ietf-yang-types { import ietf-yang-types {
prefix "yang"; prefix "yang";
} }
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: <http://tools.ietf.org/wg/pce/>
WG List: <mailto:pce@ietf.org> WG List: <mailto:pce@ietf.org>
WG Chair: JP Vasseur
<mailto:jpv@cisco.com>
WG Chair: Julien Meuric
<mailto:julien.meuric@orange.com>
WG Chair: Jonathan Hardwick
<mailto:Jonathan.Hardwick@metaswitch.com>
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";
revision 2018-01-05 { revision 2018-03-05 {
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 Element Communications Protocol
(PCEP)"; (PCEP)";
} }
/* /*
* Groupings * Groupings
*/ */
skipping to change at page 102, line 23 skipping to change at page 100, line 5
[RFC8177] Lindem, A., Ed., Qu, Y., Yeung, D., Chen, I., and J. [RFC8177] Lindem, A., Ed., Qu, Y., Yeung, D., Chen, I., and J.
Zhang, "YANG Data Model for Key Chains", RFC 8177, Zhang, "YANG Data Model for Key Chains", RFC 8177,
DOI 10.17487/RFC8177, June 2017, DOI 10.17487/RFC8177, June 2017,
<https://www.rfc-editor.org/info/rfc8177>. <https://www.rfc-editor.org/info/rfc8177>.
[RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF [RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF
Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017, Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017,
<https://www.rfc-editor.org/info/rfc8040>. <https://www.rfc-editor.org/info/rfc8040>.
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/info/rfc8174>.
[RFC8231] Crabbe, E., Minei, I., Medved, J., and R. Varga, "Path [RFC8231] Crabbe, E., Minei, I., Medved, J., and R. Varga, "Path
Computation Element Communication Protocol (PCEP) Computation Element Communication Protocol (PCEP)
Extensions for Stateful PCE", RFC 8231, Extensions for Stateful PCE", RFC 8231,
DOI 10.17487/RFC8231, September 2017, DOI 10.17487/RFC8231, September 2017,
<https://www.rfc-editor.org/info/rfc8231>. <https://www.rfc-editor.org/info/rfc8231>.
[RFC8281] Crabbe, E., Minei, I., Sivabalan, S., and R. Varga, "Path [RFC8281] Crabbe, E., Minei, I., Sivabalan, S., and R. Varga, "Path
Computation Element Communication Protocol (PCEP) Computation Element Communication Protocol (PCEP)
Extensions for PCE-Initiated LSP Setup in a Stateful PCE Extensions for PCE-Initiated LSP Setup in a Stateful PCE
Model", RFC 8281, DOI 10.17487/RFC8281, December 2017, Model", RFC 8281, DOI 10.17487/RFC8281, December 2017,
<https://www.rfc-editor.org/info/rfc8281>. <https://www.rfc-editor.org/info/rfc8281>.
[I-D.ietf-pce-lsp-setup-type] [I-D.ietf-pce-lsp-setup-type]
Sivabalan, S., Tantsura, J., Minei, I., Varga, R., and J. Sivabalan, S., Tantsura, J., Minei, I., Varga, R., and J.
Hardwick, "Conveying path setup type in PCEP messages", Hardwick, "Conveying path setup type in PCEP messages",
draft-ietf-pce-lsp-setup-type-07 (work in progress), draft-ietf-pce-lsp-setup-type-08 (work in progress),
December 2017. January 2018.
[I-D.ietf-pce-segment-routing] [I-D.ietf-pce-segment-routing]
Sivabalan, S., Filsfils, C., Tantsura, J., Henderickx, W., Sivabalan, S., Filsfils, C., Tantsura, J., Henderickx, W.,
and J. Hardwick, "PCEP Extensions for Segment Routing", and J. Hardwick, "PCEP Extensions for Segment Routing",
draft-ietf-pce-segment-routing-11 (work in progress), draft-ietf-pce-segment-routing-11 (work in progress),
November 2017. November 2017.
[I-D.ietf-teas-yang-te] [I-D.ietf-teas-yang-te]
Saad, T., Gandhi, R., Liu, X., Beeram, V., Shah, H., and Saad, T., Gandhi, R., Liu, X., Beeram, V., Shah, H., and
I. Bryskin, "A YANG Data Model for Traffic Engineering I. Bryskin, "A YANG Data Model for Traffic Engineering
Tunnels and Interfaces", draft-ietf-teas-yang-te-10 (work Tunnels and Interfaces", draft-ietf-teas-yang-te-13 (work
in progress), December 2017. in progress), March 2018.
[I-D.ietf-netconf-tls-client-server] [I-D.ietf-netconf-tls-client-server]
Watsen, K. and G. Wu, "YANG Groupings for TLS Clients and Watsen, K. and G. Wu, "YANG Groupings for TLS Clients and
TLS Servers", draft-ietf-netconf-tls-client-server-05 TLS Servers", draft-ietf-netconf-tls-client-server-05
(work in progress), October 2017. (work in progress), October 2017.
14.2. Informative References 14.2. Informative References
[RFC4655] Farrel, A., Vasseur, J., and J. Ash, "A Path Computation [RFC4655] Farrel, A., Vasseur, J., and J. Ash, "A Path Computation
Element (PCE)-Based Architecture", RFC 4655, Element (PCE)-Based Architecture", RFC 4655,
skipping to change at page 103, line 31 skipping to change at page 101, line 19
<https://www.rfc-editor.org/info/rfc7420>. <https://www.rfc-editor.org/info/rfc7420>.
[RFC8253] Lopez, D., Gonzalez de Dios, O., Wu, Q., and D. Dhody, [RFC8253] Lopez, D., Gonzalez de Dios, O., Wu, Q., and D. Dhody,
"PCEPS: Usage of TLS to Provide a Secure Transport for the "PCEPS: Usage of TLS to Provide a Secure Transport for the
Path Computation Element Communication Protocol (PCEP)", Path Computation Element Communication Protocol (PCEP)",
RFC 8253, DOI 10.17487/RFC8253, October 2017, RFC 8253, DOI 10.17487/RFC8253, October 2017,
<https://www.rfc-editor.org/info/rfc8253>. <https://www.rfc-editor.org/info/rfc8253>.
[I-D.ietf-netmod-yang-tree-diagrams] [I-D.ietf-netmod-yang-tree-diagrams]
Bjorklund, M. and L. Berger, "YANG Tree Diagrams", draft- Bjorklund, M. and L. Berger, "YANG Tree Diagrams", draft-
ietf-netmod-yang-tree-diagrams-04 (work in progress), ietf-netmod-yang-tree-diagrams-06 (work in progress),
December 2017. February 2018.
[I-D.ietf-netmod-revised-datastores] [I-D.ietf-netmod-revised-datastores]
Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K., Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K.,
and R. Wilton, "Network Management Datastore and R. Wilton, "Network Management Datastore
Architecture", draft-ietf-netmod-revised-datastores-09 Architecture", draft-ietf-netmod-revised-datastores-10
(work in progress), December 2017. (work in progress), January 2018.
Appendix A. Example Appendix A. Example
The example below provide an overview of PCEP peer session The example below provide an overview of PCEP peer session
informations and LSP-DB in the Yang Module. informations and LSP-DB in the Yang Module.
+-------+ +-------+ +-------+ +-------+
| | | | | | | |
| PCC1 |<---------------->| | | PCC1 |<---------------->| |
| | | | | | | |
 End of changes. 73 change blocks. 
297 lines changed or deleted 191 lines changed or added

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