draft-ietf-netconf-restconf-client-server-10.txt   draft-ietf-netconf-restconf-client-server-11.txt 
NETCONF Working Group K. Watsen NETCONF Working Group K. Watsen
Internet-Draft Watsen Networks Internet-Draft Watsen Networks
Intended status: Standards Track March 9, 2019 Intended status: Standards Track April 7, 2019
Expires: September 10, 2019 Expires: October 9, 2019
RESTCONF Client and Server Models RESTCONF Client and Server Models
draft-ietf-netconf-restconf-client-server-10 draft-ietf-netconf-restconf-client-server-11
Abstract Abstract
This document defines two YANG modules, one module to configure a This document defines two YANG modules, one module to configure a
RESTCONF client and the other module to configure a RESTCONF server. RESTCONF client and the other module to configure a RESTCONF server.
Both modules support the TLS transport protocol with both standard Both modules support the TLS transport protocol with both standard
RESTCONF and RESTCONF Call Home connections. RESTCONF and RESTCONF Call Home connections.
Editorial Note (To be removed by RFC Editor) Editorial Note (To be removed by RFC Editor)
skipping to change at page 1, line 46 skipping to change at page 1, line 46
o I-D.ietf-netconf-http-client-server o I-D.ietf-netconf-http-client-server
Artwork in this document contains shorthand references to drafts in Artwork in this document contains shorthand references to drafts in
progress. Please apply the following replacements: progress. Please apply the following replacements:
o "XXXX" --> the assigned RFC value for this draft o "XXXX" --> the assigned RFC value for this draft
o "AAAA" --> the assigned RFC value for I-D.ietf-netconf-tcp-client- o "AAAA" --> the assigned RFC value for I-D.ietf-netconf-tcp-client-
server server
o "CCCC" --> the assigned RFC value for I-D.ietf-netconf-tls-client- o "BBBB" --> the assigned RFC value for I-D.ietf-netconf-tls-client-
server server
o "BBBB" --> the assigned RFC value for I-D.ietf-netconf-http- o "CCCC" --> the assigned RFC value for I-D.ietf-netconf-http-
client-server client-server
Artwork in this document contains placeholder values for the date of Artwork in this document contains placeholder values for the date of
publication of this draft. Please apply the following replacement: publication of this draft. Please apply the following replacement:
o "2019-03-09" --> the publication date of this draft o "2019-04-07" --> the publication date of this draft
The following Appendix section is to be removed prior to publication: The following Appendix section is to be removed prior to publication:
o Appendix A. Change Log o Appendix B. Change Log
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
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 10, 2019. This Internet-Draft will expire on October 9, 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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3 1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 4
2. The RESTCONF Client Model . . . . . . . . . . . . . . . . . . 4 2. The RESTCONF Client Model . . . . . . . . . . . . . . . . . . 4
2.1. Tree Diagram . . . . . . . . . . . . . . . . . . . . . . 4 2.1. Tree Diagram . . . . . . . . . . . . . . . . . . . . . . 4
2.2. Example Usage . . . . . . . . . . . . . . . . . . . . . . 9 2.2. Example Usage . . . . . . . . . . . . . . . . . . . . . . 5
2.3. YANG Module . . . . . . . . . . . . . . . . . . . . . . . 12 2.3. YANG Module . . . . . . . . . . . . . . . . . . . . . . . 9
3. The RESTCONF Server Model . . . . . . . . . . . . . . . . . . 20 3. The RESTCONF Server Model . . . . . . . . . . . . . . . . . . 17
3.1. Tree Diagram . . . . . . . . . . . . . . . . . . . . . . 21 3.1. Tree Diagram . . . . . . . . . . . . . . . . . . . . . . 17
3.2. Example Usage . . . . . . . . . . . . . . . . . . . . . . 24 3.2. Example Usage . . . . . . . . . . . . . . . . . . . . . . 18
3.3. YANG Module . . . . . . . . . . . . . . . . . . . . . . . 27 3.3. YANG Module . . . . . . . . . . . . . . . . . . . . . . . 22
4. Security Considerations . . . . . . . . . . . . . . . . . . . 36 4. Security Considerations . . . . . . . . . . . . . . . . . . . 31
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 37 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 32
5.1. The IETF XML Registry . . . . . . . . . . . . . . . . . . 37 5.1. The IETF XML Registry . . . . . . . . . . . . . . . . . . 32
5.2. The YANG Module Names Registry . . . . . . . . . . . . . 38 5.2. The YANG Module Names Registry . . . . . . . . . . . . . 33
6. References . . . . . . . . . . . . . . . . . . . . . . . . . 38 6. References . . . . . . . . . . . . . . . . . . . . . . . . . 33
6.1. Normative References . . . . . . . . . . . . . . . . . . 38 6.1. Normative References . . . . . . . . . . . . . . . . . . 33
6.2. Informative References . . . . . . . . . . . . . . . . . 39 6.2. Informative References . . . . . . . . . . . . . . . . . 34
Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 41 Appendix A. Expanded Tree Diagrams . . . . . . . . . . . . . . . 36
A.1. 00 to 01 . . . . . . . . . . . . . . . . . . . . . . . . 41 A.1. Expanded Tree Diagram for 'ietf-restconf-client' . . . . 36
A.2. 01 to 02 . . . . . . . . . . . . . . . . . . . . . . . . 41 A.2. Expanded Tree Diagram for 'ietf-restconf-server' . . . . 45
A.3. 02 to 03 . . . . . . . . . . . . . . . . . . . . . . . . 41 Appendix B. Change Log . . . . . . . . . . . . . . . . . . . . . 49
A.4. 03 to 04 . . . . . . . . . . . . . . . . . . . . . . . . 41 B.1. 00 to 01 . . . . . . . . . . . . . . . . . . . . . . . . 49
A.5. 04 to 05 . . . . . . . . . . . . . . . . . . . . . . . . 41 B.2. 01 to 02 . . . . . . . . . . . . . . . . . . . . . . . . 49
A.6. 05 to 06 . . . . . . . . . . . . . . . . . . . . . . . . 42 B.3. 02 to 03 . . . . . . . . . . . . . . . . . . . . . . . . 49
A.7. 06 to 07 . . . . . . . . . . . . . . . . . . . . . . . . 42 B.4. 03 to 04 . . . . . . . . . . . . . . . . . . . . . . . . 49
A.8. 07 to 08 . . . . . . . . . . . . . . . . . . . . . . . . 42 B.5. 04 to 05 . . . . . . . . . . . . . . . . . . . . . . . . 50
A.9. 08 to 09 . . . . . . . . . . . . . . . . . . . . . . . . 42 B.6. 05 to 06 . . . . . . . . . . . . . . . . . . . . . . . . 50
A.10. 09 to 10 . . . . . . . . . . . . . . . . . . . . . . . . 42 B.7. 06 to 07 . . . . . . . . . . . . . . . . . . . . . . . . 50
Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 43 B.8. 07 to 08 . . . . . . . . . . . . . . . . . . . . . . . . 50
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 43 B.9. 08 to 09 . . . . . . . . . . . . . . . . . . . . . . . . 50
B.10. 09 to 10 . . . . . . . . . . . . . . . . . . . . . . . . 51
B.11. 10 to 11 . . . . . . . . . . . . . . . . . . . . . . . . 51
Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 51
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 51
1. Introduction 1. Introduction
This document defines two YANG [RFC7950] modules, one module to This document defines two YANG [RFC7950] modules, one module to
configure a RESTCONF client and the other module to configure a configure a RESTCONF client and the other module to configure a
RESTCONF server [RFC8040]. Both modules support the TLS [RFC8446] RESTCONF server [RFC8040]. Both modules support the TLS [RFC8446]
transport protocol with both standard RESTCONF and RESTCONF Call Home transport protocol with both standard RESTCONF and RESTCONF Call Home
connections [RFC8071]. connections [RFC8071].
1.1. Terminology 1.1. Terminology
skipping to change at page 4, line 11 skipping to change at page 4, line 19
"OPTIONAL" in this document are to be interpreted as described in BCP "OPTIONAL" in this document are to be interpreted as described in BCP
14 [RFC2119] [RFC8174] when, and only when, they appear in all 14 [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here. capitals, as shown here.
2. The RESTCONF Client Model 2. The RESTCONF Client Model
The RESTCONF client model presented in this section supports both The RESTCONF client model presented in this section supports both
clients initiating connections to servers, as well as clients clients initiating connections to servers, as well as clients
listening for connections from servers calling home. listening for connections from servers calling home.
This model, like that presented in
[I-D.ietf-netconf-netconf-client-server], is designed to support any
number of possible transports. RESTCONF only supports the TLS
transport currently, thus this model only supports the TLS transport.
All private keys and trusted certificates are held in the keystore
model defined in [I-D.ietf-netconf-keystore].
YANG feature statements are used to enable implementations to YANG feature statements are used to enable implementations to
advertise which parts of the model the RESTCONF client supports. advertise which potentially uncommon parts of the model the RESTCONF
client supports.
2.1. Tree Diagram 2.1. Tree Diagram
The following tree diagram [RFC8340] provides an overview of the data The following tree diagram [RFC8340] provides an overview of the data
model for the "ietf-restconf-client" module. Just the container is model for the "ietf-restconf-client" module.
displayed below, but there is also a reusable grouping called
"restconf-client-grouping" that the container is using.
========== NOTE: '\\' line wrapping per BCP XX (RFC XXXX) =========== This tree diagram only shows the nodes defined in this module; it
does show the nodes defined by "grouping" statements used by this
module.
Please see Appendix A.1 for a tree diagram that illustrates what the
module looks like with all the "grouping" statements expanded.
module: ietf-restconf-client module: ietf-restconf-client
+--rw restconf-client +--rw restconf-client
+--rw initiate! {initiate}? +---u restconf-client-grouping
| +--rw restconf-server* [name]
| +--rw name string
| +--rw endpoints
| +--rw endpoint* [name]
| +--rw name string
| +--rw (transport)
| | +--:(https) {https-initiate}?
| | +--rw https
| | +--rw remote-address inet:host
| | +--rw remote-port?
| | | inet:port-number
| | +--rw local-address? inet:ip-addr\
\ess
| | +--rw local-port?
| | | inet:port-number
| | +--rw tcp-keepalives {tcp-client-keepalive\
\s}?
| | | +--rw idle-time? uint16
| | | +--rw max-probes? uint16
| | | +--rw probe-interval? uint16
| | +--rw tls-client-identity
| | | +--rw (auth-type)
| | | +--:(certificate)
| | | +--rw certificate
| | | +--rw (local-or-keystore)
| | | +--:(local)
| | | | {local-keys-suppor\
\ted}?
| | | | +--rw local-definition
| | | | +--rw algorithm?
| | | | | asymmetric-ke\
\y-algorithm-ref
| | | | +--rw public-key?
| | | | | binary
| | | | +--rw private-key?
| | | | | union
| | | | +---x generate-hidden\
\-key
| | | | | +---w input
| | | | | +---w algorithm
| | | | | asymmet\
\ric-key-algorithm-ref
| | | | +---x install-hidden-\
\key
| | | | | +---w input
| | | | | +---w algorithm
| | | | | | asymmet\
\ric-key-algorithm-ref
| | | | | +---w public-ke\
\y?
| | | | | | binary
| | | | | +---w private-k\
\ey?
| | | | | binary
| | | | +--rw cert?
| | | | | end-entity-ce\
\rt-cms
| | | | +---n certificate-exp\
\iration
| | | | +-- expiration-date
| | | | yang:date-\
\and-time
| | | +--:(keystore)
| | | {keystore-supporte\
\d}?
| | | +--rw keystore-reference?
| | | ks:asymmetric-ke\
\y-certificate-ref grouping restconf-client-grouping
| | +--rw tls-server-auth +-- initiate! {initiate}?
| | | +--rw pinned-ca-certs? | +-- restconf-server* [name]
| | | | ta:pinned-certificates-ref | +-- name? string
| | | | {ta:x509-certificates}? | +-- endpoints
| | | +--rw pinned-server-certs? | | +-- endpoint* [name]
| | | ta:pinned-certificates-ref | | +-- name? string
| | | {ta:x509-certificates}? | | +-- (transport)
| | +--rw tls-hello-params | | +--:(https) {https-initiate}?
| | | {tls-client-hello-params-config}? | | +-- https
| | | +--rw tls-versions | | +---u restconf-client-grouping
| | | | +--rw tls-version* identityref | +-- connection-type
| | | +--rw cipher-suites | | +-- (connection-type)
| | | +--rw cipher-suite* identityref | | +--:(persistent-connection)
| | +--rw tls-keepalives {tls-client-keepalive\ | | | +-- persistent!
\s}? | | +--:(periodic-connection)
| | | +--rw max-wait? uint16 | | +-- periodic!
| | | +--rw max-attempts? uint8 | | +-- period? uint16
| | +--rw http-client-identity | | +-- anchor-time? yang:date-and-time
| | | +--rw (auth-type)? | | +-- idle-timeout? uint16
| | | +--:(basic) | +-- reconnect-strategy
| | | | +--rw basic | +-- start-with? enumeration
| | | | +--rw user-id? string | +-- max-attempts? uint8
| | | | +--rw password? string +-- listen! {listen}?
| | | +--:(bearer) +-- idle-timeout? uint16
| | | | +--rw bearer +-- endpoint* [name]
| | | | +--rw token? string +-- name? string
| | | +--:(digest) +-- (transport)
| | | | +--rw digest +--:(https) {https-listen}?
| | | | +--rw username? string +-- https
| | | | +--rw password? string +---u restconf-client-grouping
| | | +--:(hoba)
| | | | +--rw hoba
| | | +--:(mutual)
| | | | +--rw mutual
| | | +--:(negotiate)
| | | | +--rw negotiate
| | | +--:(oauth)
| | | | +--rw oauth
| | | +--:(scram-sha-1)
| | | | +--rw scram-sha-1
| | | +--:(scram-sha-256)
| | | | +--rw scram-sha-256
| | | +--:(vapid)
| | | +--rw vapid
| | +--rw http-keepalives
| | {http-client-keepalives}?
| | +--rw max-wait? uint16
| | +--rw max-attempts? uint8
| +--rw connection-type
| | +--rw (connection-type)
| | +--:(persistent-connection)
| | | +--rw persistent!
| | +--:(periodic-connection)
| | +--rw periodic!
| | +--rw period? uint16
| | +--rw anchor-time? yang:date-and-time
| | +--rw idle-timeout? uint16
| +--rw reconnect-strategy
| +--rw start-with? enumeration
| +--rw max-attempts? uint8
+--rw listen! {listen}?
+--rw idle-timeout? uint16
+--rw endpoint* [name]
+--rw name string
+--rw (transport)
+--:(https) {https-listen}?
+--rw https
+--rw local-address inet:ip-address
+--rw local-port? inet:port-number
+--rw tcp-keepalives {tcp-server-keepalives}?
| +--rw idle-time? uint16
| +--rw max-probes? uint16
| +--rw probe-interval? uint16
+--rw tls-client-identity
| +--rw (auth-type)
| +--:(certificate)
| +--rw certificate
| +--rw (local-or-keystore)
| +--:(local) {local-keys-supported\
\}?
| | +--rw local-definition
| | +--rw algorithm?
| | | asymmetric-key-algo\
\rithm-ref
| | +--rw public-key?
| | | binary
| | +--rw private-key?
| | | union
| | +---x generate-hidden-key
| | | +---w input
| | | +---w algorithm
| | | asymmetric-ke\
\y-algorithm-ref
| | +---x install-hidden-key
| | | +---w input
| | | +---w algorithm
| | | | asymmetric-ke\
\y-algorithm-ref
| | | +---w public-key?
| | | | binary
| | | +---w private-key?
| | | binary
| | +--rw cert?
| | | end-entity-cert-cms
| | +---n certificate-expiration
| | +-- expiration-date
| | yang:date-and-ti\
\me
| +--:(keystore) {keystore-supporte\
\d}?
| +--rw keystore-reference?
| ks:asymmetric-key-cert\
\ificate-ref
+--rw tls-server-auth
| +--rw pinned-ca-certs?
| | ta:pinned-certificates-ref
| | {ta:x509-certificates}?
| +--rw pinned-server-certs?
| ta:pinned-certificates-ref
| {ta:x509-certificates}?
+--rw tls-hello-params
| {tls-client-hello-params-config}?
| +--rw tls-versions
| | +--rw tls-version* identityref
| +--rw cipher-suites
| +--rw cipher-suite* identityref
+--rw tls-keepalives {tls-client-keepalives}?
| +--rw max-wait? uint16
| +--rw max-attempts? uint8
+--rw http-client-identity
| +--rw (auth-type)?
| +--:(basic)
| | +--rw basic
| | +--rw user-id? string
| | +--rw password? string
| +--:(bearer)
| | +--rw bearer
| | +--rw token? string
| +--:(digest)
| | +--rw digest
| | +--rw username? string
| | +--rw password? string
| +--:(hoba)
| | +--rw hoba
| +--:(mutual)
| | +--rw mutual
| +--:(negotiate)
| | +--rw negotiate
| +--:(oauth)
| | +--rw oauth
| +--:(scram-sha-1)
| | +--rw scram-sha-1
| +--:(scram-sha-256)
| | +--rw scram-sha-256
| +--:(vapid)
| +--rw vapid
+--rw http-keepalives {http-client-keepalives}?
+--rw max-wait? uint16
+--rw max-attempts? uint8
2.2. Example Usage 2.2. Example Usage
The following example illustrates configuring a RESTCONF client to The following example illustrates configuring a RESTCONF client to
initiate connections, as well as listening for call-home connections. initiate connections, as well as listening for call-home connections.
This example is consistent with the examples presented in Section 3.2 This example is consistent with the examples presented in Section 2
of [I-D.ietf-netconf-keystore]. of [I-D.ietf-netconf-trust-anchors] and Section 3.2 of
[I-D.ietf-netconf-keystore].
========== NOTE: '\\' line wrapping per BCP XX (RFC XXXX) =========== =========== NOTE: '\' line wrapping per BCP XX (RFC XXXX) ===========
<restconf-client <restconf-client
xmlns="urn:ietf:params:xml:ns:yang:ietf-restconf-client"> xmlns="urn:ietf:params:xml:ns:yang:ietf-restconf-client">
<!-- RESTCONF servers to initiate connections to --> <!-- RESTCONF servers to initiate connections to -->
<initiate> <initiate>
<restconf-server> <restconf-server>
<name>corp-fw1</name> <name>corp-fw1</name>
<endpoints> <endpoints>
<endpoint> <endpoint>
<name>corp-fw1.example.com</name> <name>corp-fw1.example.com</name>
<https> <https>
<remote-address>corp-fw1.example.com</remote-address> <tcp-client-parameters>
<tcp-keepalives> <remote-address>corp-fw1.example.com</remote-address>
<idle-time>15</idle-time> <keepalives>
<max-probes>3</max-probes> <idle-time>15</idle-time>
<probe-interval>30</probe-interval> <max-probes>3</max-probes>
</tcp-keepalives> <probe-interval>30</probe-interval>
<tls-client-identity> </keepalives>
<certificate> </tcp-client-parameters>
<local-definition> <tls-client-parameters>
<algorithm xmlns:ct="urn:ietf:params:xml:ns:yang:i\ <client-identity>
<certificate>
<local-definition>
<algorithm xmlns:ct="urn:ietf:params:xml:ns:yang\
:ietf-crypto-types">ct:rsa2048</algorithm>
<private-key>base64encodedvalue==</private-key>
<public-key>base64encodedvalue==</public-key>
<cert>base64encodedvalue==</cert>
</local-definition>
</certificate>
</client-identity>
<server-authentication>
<pinned-ca-certs>explicitly-trusted-server-ca-certs<\
/pinned-ca-certs>
<pinned-server-certs>explicitly-trusted-server-certs\
</pinned-server-certs>
</server-authentication>
<keepalives>
<max-wait>30</max-wait>
<max-attempts>3</max-attempts>
</keepalives>
</tls-client-parameters>
<http-client-parameters>
<protocol-version>HTTP/1.1</protocol-version>
<client-identity>
<basic>
<user-id>bob</user-id>
<password>secret</password>
</basic>
\etf-crypto-types">ct:rsa2048</algorithm> </client-identity>
<private-key>base64encodedvalue==</private-key> </http-client-parameters>
<public-key>base64encodedvalue==</public-key>
<cert>base64encodedvalue==</cert>
</local-definition>
</certificate>
</tls-client-identity>
<tls-server-auth>
<pinned-ca-certs>explicitly-trusted-server-ca-certs</p\
\inned-ca-certs>
<pinned-server-certs>explicitly-trusted-server-certs</\
\pinned-server-certs>
</tls-server-auth>
<tls-keepalives>
<max-wait>30</max-wait>
<max-attempts>3</max-attempts>
</tls-keepalives>
<http-client-identity>
<basic>
<user-id>bob</user-id>
<password>secret</password>
</basic>
</http-client-identity>
<http-keepalives>
<max-wait>30</max-wait>
<max-attempts>3</max-attempts>
</http-keepalives>
</https> </https>
<connection-type>
<persistent/>
</connection-type>
</endpoint> </endpoint>
<endpoint> <endpoint>
<name>corp-fw2.example.com</name> <name>corp-fw2.example.com</name>
<https> <https>
<remote-address>corp-fw2.example.com</remote-address> <tcp-client-parameters>
<tcp-keepalives> <remote-address>corp-fw2.example.com</remote-address>
<idle-time>15</idle-time> <keepalives>
<max-probes>3</max-probes> <idle-time>15</idle-time>
<probe-interval>30</probe-interval> <max-probes>3</max-probes>
</tcp-keepalives> <probe-interval>30</probe-interval>
<tls-client-identity> </keepalives>
<certificate> </tcp-client-parameters>
<local-definition> <tls-client-parameters>
<algorithm xmlns:ct="urn:ietf:params:xml:ns:yang:i\ <client-identity>
\etf-crypto-types">ct:rsa2048</algorithm> <certificate>
<private-key>base64encodedvalue==</private-key> <local-definition>
<public-key>base64encodedvalue==</public-key> <algorithm xmlns:ct="urn:ietf:params:xml:ns:yang\
<cert>base64encodedvalue==</cert> :ietf-crypto-types">ct:rsa2048</algorithm>
</local-definition> <private-key>base64encodedvalue==</private-key>
</certificate> <public-key>base64encodedvalue==</public-key>
</tls-client-identity> <cert>base64encodedvalue==</cert>
<tls-server-auth> </local-definition>
<pinned-ca-certs>explicitly-trusted-server-ca-certs</p\ </certificate>
\inned-ca-certs> </client-identity>
<pinned-server-certs>explicitly-trusted-server-certs</\ <server-authentication>
\pinned-server-certs> <pinned-ca-certs>explicitly-trusted-server-ca-certs<\
</tls-server-auth> /pinned-ca-certs>
<tls-keepalives> <pinned-server-certs>explicitly-trusted-server-certs\
<max-wait>30</max-wait> </pinned-server-certs>
<max-attempts>3</max-attempts> </server-authentication>
</tls-keepalives> <keepalives>
<http-client-identity> <max-wait>30</max-wait>
<basic> <max-attempts>3</max-attempts>
<user-id>bob</user-id> </keepalives>
<password>secret</password> </tls-client-parameters>
</basic> <http-client-parameters>
</http-client-identity> <protocol-version>HTTP/1.1</protocol-version>
<http-keepalives> <client-identity>
<max-wait>30</max-wait> <basic>
<max-attempts>3</max-attempts> <user-id>bob</user-id>
</http-keepalives> <password>secret</password>
</basic>
</client-identity>
</http-client-parameters>
</https> </https>
<connection-type>
<persistent/>
</connection-type>
</endpoint> </endpoint>
</endpoints> </endpoints>
<connection-type>
<persistent/>
</connection-type>
</restconf-server> </restconf-server>
</initiate> </initiate>
<!-- endpoints to listen for RESTCONF Call Home connections on --> <!-- endpoints to listen for RESTCONF Call Home connections on -->
<listen> <listen>
<endpoint> <endpoint>
<name>Intranet-facing listener</name> <name>Intranet-facing listener</name>
<https> <https>
<local-address>11.22.33.44</local-address> <tcp-server-parameters>
<tls-client-identity> <local-address>11.22.33.44</local-address>
<certificate> </tcp-server-parameters>
<local-definition> <tls-client-parameters>
<algorithm xmlns:ct="urn:ietf:params:xml:ns:yang:ietf-\ <client-identity>
\crypto-types">ct:rsa2048</algorithm> <certificate>
<private-key>base64encodedvalue==</private-key> <local-definition>
<public-key>base64encodedvalue==</public-key> <algorithm xmlns:ct="urn:ietf:params:xml:ns:yang:iet\
<cert>base64encodedvalue==</cert> f-crypto-types">ct:rsa2048</algorithm>
</local-definition> <private-key>base64encodedvalue==</private-key>
<public-key>base64encodedvalue==</public-key>
</certificate> <cert>base64encodedvalue==</cert>
</tls-client-identity> </local-definition>
<tls-server-auth> </certificate>
<pinned-ca-certs>explicitly-trusted-server-ca-certs</pinne\ </client-identity>
\d-ca-certs> <server-authentication>
<pinned-server-certs>explicitly-trusted-server-certs</pinn\ <pinned-ca-certs>explicitly-trusted-server-ca-certs</pin\
\ed-server-certs> ned-ca-certs>
</tls-server-auth> <pinned-server-certs>explicitly-trusted-server-certs</pi\
nned-server-certs>
</server-authentication>
</tls-client-parameters>
<http-client-parameters>
<protocol-version>HTTP/1.1</protocol-version>
<client-identity>
<basic>
<user-id>bob</user-id>
<password>secret</password>
</basic>
</client-identity>
</http-client-parameters>
</https> </https>
</endpoint> </endpoint>
</listen> </listen>
</restconf-client> </restconf-client>
2.3. YANG Module 2.3. YANG Module
This YANG module has normative references to [RFC6991], [RFC8040], This YANG module has normative references to [RFC6991], [RFC8040],
and [RFC8071], [I-D.kwatsen-netconf-tcp-client-server], and [RFC8071], [I-D.kwatsen-netconf-tcp-client-server],
[I-D.ietf-netconf-tls-client-server], and [I-D.ietf-netconf-tls-client-server], and
[I-D.kwatsen-netconf-http-client-server]. [I-D.kwatsen-netconf-http-client-server].
<CODE BEGINS> file "ietf-restconf-client@2019-03-09.yang" <CODE BEGINS> file "ietf-restconf-client@2019-04-07.yang"
module ietf-restconf-client { module ietf-restconf-client {
yang-version 1.1; yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-restconf-client"; namespace "urn:ietf:params:xml:ns:yang:ietf-restconf-client";
prefix rcc; prefix rcc;
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";
} }
skipping to change at page 13, line 17 skipping to change at page 9, line 52
import ietf-http-client { import ietf-http-client {
prefix httpc; prefix httpc;
reference reference
"RFC CCCC: YANG Groupings for HTTP Clients and HTTP Servers"; "RFC CCCC: YANG Groupings for HTTP Clients and HTTP Servers";
} }
organization organization
"IETF NETCONF (Network Configuration) Working Group"; "IETF NETCONF (Network Configuration) Working Group";
contact contact
"WG Web: <http://datatracker.ietf.org/wg/restconf/> "WG Web: <http://datatracker.ietf.org/wg/netconf/>
WG List: <mailto:netconf@ietf.org> WG List: <mailto:netconf@ietf.org>
Author: Kent Watsen <mailto:kent+ietf@watsen.net> Author: Kent Watsen <mailto:kent+ietf@watsen.net>
Author: Gary Wu <mailto:garywu@cisco.com>"; Author: Gary Wu <mailto:garywu@cisco.com>";
description description
"This module contains a collection of YANG definitions for "This module contains a collection of YANG definitions
configuring RESTCONF clients. for configuring RESTCONF clients.
The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL',
'SHALL NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED',
'NOT RECOMMENDED', 'MAY', and '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.
Copyright (c) 2019 IETF Trust and the persons identified as Copyright (c) 2019 IETF Trust and the persons identified
authors of the code. All rights reserved. as 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
without modification, is permitted pursuant to, and subject or without modification, is permitted pursuant to, and
to the license terms contained in, the Simplified BSD subject to the license terms contained in, the Simplified
License set forth in Section 4.c of the IETF Trust's BSD License set forth in Section 4.c of the IETF Trust's
Legal Provisions Relating to IETF Documents Legal Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info). (https://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC XXXX; see This version of this YANG module is part of RFC XXXX
the RFC itself for full legal notices."; (https://www.rfc-editor.org/info/rfcXXXX); see the RFC
itself for full legal notices.;
revision 2019-03-09 { The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL',
'SHALL NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED',
'NOT RECOMMENDED', 'MAY', and 'OPTIONAL' in this document
are to be interpreted as described in BCP 14 (RFC 2119)
(RFC 8174) when, and only when, they appear in all
capitals, as shown here.";
revision 2019-04-07 {
description description
"Initial version"; "Initial version";
reference reference
"RFC XXXX: RESTCONF Client and Server Models"; "RFC XXXX: RESTCONF Client and Server Models";
} }
// Features // Features
feature initiate { feature initiate {
description description
"The 'initiate' feature indicates that the RESTCONF client "The 'initiate' feature indicates that the RESTCONF client
supports initiating RESTCONF connections to RESTCONF servers supports initiating RESTCONF connections to RESTCONF servers
using at least one transport (e.g., HTTPS, etc.)."; using at least one transport (e.g., HTTPS, etc.).";
} }
feature https-initiate { feature https-initiate {
skipping to change at page 15, line 45 skipping to change at page 12, line 33
"Selects between available transports. This is a "Selects between available transports. This is a
'choice' statement so as to support additional 'choice' statement so as to support additional
transport options to be augmented in."; transport options to be augmented in.";
case https { case https {
if-feature "https-initiate"; if-feature "https-initiate";
container https { container https {
description description
"Specifies HTTPS-specific transport "Specifies HTTPS-specific transport
configuration."; configuration.";
uses tcpc:tcp-client-grouping { uses tcpc:tcp-client-grouping {
refine "remote-port" { refine "tcp-client-parameters/remote-port" {
default "443"; default "443";
description description
"The RESTCONF client will attempt to "The RESTCONF client will attempt to
connect to the IANA-assigned well-known connect to the IANA-assigned well-known
port value for 'https' (443) if no value port value for 'https' (443) if no value
is specified."; is specified.";
} }
} }
uses tlsc:tls-client-grouping { uses tlsc:tls-client-grouping {
refine "tls-client-identity/auth-type" { refine "tls-client-parameters/client-identity"
+ "/auth-type" {
mandatory true; mandatory true;
description description
"RESTCONF clients MUST pass some "RESTCONF clients MUST pass some
authentication credentials."; authentication credentials.";
} }
} }
uses httpc:http-client-grouping; uses httpc:http-client-grouping;
} }
} // https } // https
} // transport } // transport
container connection-type { } // endpoint
description } // endpoints
"Indicates the RESTCONF client's preference for how container connection-type {
the RESTCONF connection is maintained."; description
choice connection-type { "Indicates the RESTCONF client's preference for how
mandatory true; the RESTCONF connection is maintained.";
choice connection-type {
mandatory true;
description
"Selects between available connection types.";
case persistent-connection {
container persistent {
presence "Indicates that a persistent connection
is to be maintained.";
description description
"Selects between available connection types."; "Maintain a persistent connection to the
case persistent-connection { RESTCONF server. If the connection goes down,
container persistent { immediately start trying to reconnect to it,
presence "Indicates that a persistent connection using the reconnection strategy. This
is to be maintained."; connection type minimizes any RESTCONF server
description to RESTCONF client data-transfer delay, albeit
"Maintain a persistent connection to the at the expense of holding resources longer.";
RESTCONF server. If the connection goes down, }
immediately start trying to reconnect to it, }
using the reconnection strategy. This case periodic-connection {
connection type minimizes any RESTCONF server container periodic {
to RESTCONF client data-transfer delay, albeit must 'not (../../endpoints/endpoint/https/'
at the expense of holding resources longer."; + 'tcp-client-parameters/keepalives '
} + 'or ../../endpoints/endpoint/https/'
} + 'tls-client-parameters/keepalives)';
case periodic-connection { presence "Indicates that a periodic connection is
container periodic { to be maintained.";
presence "Indicates that a periodic connection is description
to be maintained."; "Periodically connect to the RESTCONF server.
description The RESTCONF server should close the
"Periodically connect to the RESTCONF server. underlying TCP connection upon completing
The RESTCONF server should close the planned activities.
underlying TCP connection upon completing
planned activities.
This connection type increases resource This connection type increases resource
utilization, albeit with increased delay in utilization, albeit with increased delay in
RESTCONF server to RESTCONF client RESTCONF server to RESTCONF client
interactions."; interactions.";
leaf period { leaf period {
type uint16; type uint16;
units "minutes"; units "minutes";
default "60"; default "60";
description description
"Duration of time between periodic "Duration of time between periodic
connections."; connections.";
} }
leaf anchor-time { leaf anchor-time {
type yang:date-and-time { type yang:date-and-time {
// constrained to minute-level granularity // constrained to minute-level granularity
pattern '\d{4}-\d{2}-\d{2}T\d{2}:\d{2}' pattern '\d{4}-\d{2}-\d{2}T\d{2}:\d{2}'
+ '(Z|[\+\-]\d{2}:\d{2})'; + '(Z|[\+\-]\d{2}:\d{2})';
}
description
"Designates a timestamp before or after which
a series of periodic connections are
determined. The periodic connections occur
at a whole multiple interval from the anchor
time. For example, for an anchor time is 15
minutes past midnight and a period interval
of 24 hours, then a periodic connection will
occur 15 minutes past midnight everyday.";
}
leaf idle-timeout {
type uint16;
units "seconds";
default 120; // two minutes
description
"Specifies the maximum number of seconds
that the underlying TCP session may remain
idle. A TCP session will be dropped if it
is idle for an interval longer than this
number of seconds If set to zero, then the
RESTCONF client will never drop a session
because it is idle.";
}
}
} // periodic-connection
} // connection-type
} // connection-type
container reconnect-strategy {
description
"The reconnection strategy directs how a RESTCONF
client reconnects to a RESTCONF server, after
discovering its connection to the server has
dropped, even if due to a reboot. The RESTCONF
client starts with the specified endpoint and
tries to connect to it max-attempts times before
trying the next endpoint in the list (round
robin).";
leaf start-with {
type enumeration {
enum first-listed {
description
"Indicates that reconnections should start
with the first endpoint listed.";
}
enum last-connected {
description
"Indicates that reconnections should start
with the endpoint last connected to. If
no previous connection has ever been
established, then the first endpoint
configured is used. RESTCONF clients
SHOULD be able to remember the last
endpoint connected to across reboots.";
}
enum random-selection {
description
"Indicates that reconnections should start with
a random endpoint.";
} }
description
"Designates a timestamp before or after which
a series of periodic connections are
determined. The periodic connections occur
at a whole multiple interval from the anchor
time. For example, for an anchor time is 15
minutes past midnight and a period interval
of 24 hours, then a periodic connection will
occur 15 minutes past midnight everyday.";
} }
default "first-listed"; leaf idle-timeout {
type uint16;
units "seconds";
default 120; // two minutes
description
"Specifies the maximum number of seconds
that the underlying TCP session may remain
idle. A TCP session will be dropped if it
is idle for an interval longer than this
number of seconds If set to zero, then the
RESTCONF client will never drop a session
because it is idle.";
}
}
} // periodic-connection
} // connection-type
} // connection-type
container reconnect-strategy {
description
"The reconnection strategy directs how a RESTCONF
client reconnects to a RESTCONF server, after
discovering its connection to the server has
dropped, even if due to a reboot. The RESTCONF
client starts with the specified endpoint and
tries to connect to it max-attempts times before
trying the next endpoint in the list (round
robin).";
leaf start-with {
type enumeration {
enum first-listed {
description description
"Specifies which of the RESTCONF server's "Indicates that reconnections should start
endpoints the RESTCONF client should start with the first endpoint listed.";
with when trying to connect to the RESTCONF
server.";
} }
leaf max-attempts { enum last-connected {
type uint8 {
range "1..max";
}
default "3";
description description
"Specifies the number times the RESTCONF client "Indicates that reconnections should start
tries to connect to a specific endpoint before with the endpoint last connected to. If
moving on to the next endpoint in the list no previous connection has ever been
(round robin)."; established, then the first endpoint
configured is used. RESTCONF clients
SHOULD be able to remember the last
endpoint connected to across reboots.";
} }
} // reconnect-strategy enum random-selection {
} // endpoint description
"Indicates that reconnections should start with
} // endpoints a random endpoint.";
}
}
default "first-listed";
description
"Specifies which of the RESTCONF server's
endpoints the RESTCONF client should start
with when trying to connect to the RESTCONF
server.";
}
leaf max-attempts {
type uint8 {
range "1..max";
}
default "3";
description
"Specifies the number times the RESTCONF client
tries to connect to a specific endpoint before
moving on to the next endpoint in the list
(round robin).";
}
} // reconnect-strategy
} // restconf-server } // restconf-server
} // initiate } // initiate
container listen { container listen {
if-feature "listen"; if-feature "listen";
presence "Enables client to accept call-home connections"; presence "Enables client to accept call-home connections";
description description
"Configures client accepting call-home TCP connections."; "Configures client accepting call-home TCP connections.";
leaf idle-timeout { leaf idle-timeout {
type uint16; type uint16;
units "seconds"; units "seconds";
default 3600; // one hour default 3600; // one hour
description description
"Specifies the maximum number of seconds that an "Specifies the maximum number of seconds that an
underlying TCP session may remain idle. A TCP session underlying TCP session may remain idle. A TCP session
will be dropped if it is idle for an interval longer will be dropped if it is idle for an interval longer
than this number of seconds. If set to zero, then then this number of seconds. If set to zero, then
the server will never drop a session because it is the server will never drop a session because it is
idle. Sessions that have a notification subscription idle. Sessions that have a notification subscription
active are never dropped."; active are never dropped.";
} }
list endpoint { list endpoint {
key "name"; key "name";
min-elements 1; min-elements 1;
description description
"List of endpoints to listen for RESTCONF connections."; "List of endpoints to listen for RESTCONF connections.";
leaf name { leaf name {
skipping to change at page 19, line 50 skipping to change at page 16, line 42
"Selects between available transports. This is a "Selects between available transports. This is a
'choice' statement so as to support additional 'choice' statement so as to support additional
transport options to be augmented in."; transport options to be augmented in.";
case https { case https {
if-feature "https-listen"; if-feature "https-listen";
container https { container https {
description description
"HTTPS-specific listening configuration for inbound "HTTPS-specific listening configuration for inbound
connections."; connections.";
uses tcps:tcp-server-grouping { uses tcps:tcp-server-grouping {
refine "local-port" { refine "tcp-server-parameters/local-port" {
default "4336"; default "4336";
description description
"The RESTCONF client will listen on the IANA- "The RESTCONF client will listen on the IANA-
assigned well-known port for 'restconf-ch-tls' assigned well-known port for 'restconf-ch-tls'
(4336) if no value is specified."; (4336) if no value is specified.";
} }
} }
uses tlsc:tls-client-grouping { uses tlsc:tls-client-grouping {
refine "tls-client-identity/auth-type" { refine
"tls-client-parameters/client-identity/auth-type" {
mandatory true; mandatory true;
description description
"RESTCONF clients MUST pass some authentication "RESTCONF clients MUST pass some authentication
credentials."; credentials.";
} }
} }
uses httpc:http-client-grouping; uses httpc:http-client-grouping;
} }
} // case https } // case https
} // transport } // transport
skipping to change at page 20, line 38 skipping to change at page 17, line 32
container restconf-client { container restconf-client {
uses restconf-client-grouping; uses restconf-client-grouping;
description description
"Top-level container for RESTCONF client configuration."; "Top-level container for RESTCONF client configuration.";
} }
} }
<CODE ENDS> <CODE ENDS>
3. The RESTCONF Server Model 3. The RESTCONF Server Model
The RESTCONF server model presented in this section supports servers The RESTCONF server model presented in this section supports both
both listening for connections as well as initiating call-home listening for connections as well as initiating call-home
connections. connections.
All private keys and trusted certificates are held in the keystore
model defined in [I-D.ietf-netconf-keystore].
YANG feature statements are used to enable implementations to YANG feature statements are used to enable implementations to
advertise which parts of the model the RESTCONF server supports. advertise which potentially uncommon parts of the model the RESTCONF
server supports.
3.1. Tree Diagram 3.1. Tree Diagram
The following tree diagram [RFC8340] provides an overview of the data The following tree diagram [RFC8340] provides an overview of the data
model for the "ietf-restconf-server" module. Just the container is model for the "ietf-restconf-server" module.
displayed below, but there is also a reusable grouping called
"restconf-server-grouping" that the container is using.
========== NOTE: '\\' line wrapping per BCP XX (RFC XXXX) =========== This tree diagram only shows the nodes defined in this module; it
does show the nodes defined by "grouping" statements used by this
module.
Please see Appendix A.2 for a tree diagram that illustrates what the
module looks like with all the "grouping" statements expanded.
module: ietf-restconf-server module: ietf-restconf-server
+--rw restconf-server +--rw restconf-server
+--rw listen! {listen}? +---u restconf-server-grouping
| +--rw endpoint* [name]
| +--rw name string
| +--rw (transport)
| +--:(https) {https-listen}?
| +--rw https
| +--rw local-address inet:ip-address
| +--rw local-port? inet:port-number
| +--rw tcp-keepalives {tcp-server-keepalives}?
| | +--rw idle-time? uint16
| | +--rw max-probes? uint16
| | +--rw probe-interval? uint16
| +--rw tls-server-identity
| | +--rw (local-or-keystore)
| | +--:(local) {local-keys-supported}?
| | | +--rw local-definition
| | | +--rw algorithm?
| | | | asymmetric-key-algorithm-ref
| | | +--rw public-key? bina\
\ry
| | | +--rw private-key? union
| | | +---x generate-hidden-key
| | | | +---w input
| | | | +---w algorithm
| | | | asymmetric-key-algorit\
\hm-ref
| | | +---x install-hidden-key
| | | | +---w input
| | | | +---w algorithm
| | | | | asymmetric-key-algorit\
\hm-ref
| | | | +---w public-key? binary
| | | | +---w private-key? binary
| | | +--rw cert?
| | | | end-entity-cert-cms
| | | +---n certificate-expiration
| | | +-- expiration-date
| | | yang:date-and-time
| | +--:(keystore) {keystore-supported}?
| | +--rw keystore-reference?
| | ks:asymmetric-key-certificate-r\
\ef
| +--rw tls-client-auth
| | +--rw pinned-ca-certs?
| | | ta:pinned-certificates-ref
| | | {ta:x509-certificates}?
| | +--rw pinned-client-certs?
| | | ta:pinned-certificates-ref
| | | {ta:x509-certificates}?
| | +--rw cert-maps
| | +--rw cert-to-name* [id]
| | +--rw id uint32
| | +--rw fingerprint
| | | x509c2n:tls-fingerprint
| | +--rw map-type identityref
| | +--rw name string
| +--rw tls-hello-params
| | {tls-server-hello-params-config}?
| | +--rw tls-versions
| | | +--rw tls-version* identityref
| | +--rw cipher-suites
| | +--rw cipher-suite* identityref
| +--rw tls-keepalives {tls-server-keepalives}?
| | +--rw max-wait? uint16
| | +--rw max-attempts? uint8
| +--rw http-keepalives {http-server-keepalives}?
| +--rw max-wait? uint16
| +--rw max-attempts? uint8
+--rw call-home! {call-home}?
+--rw restconf-client* [name]
+--rw name string
+--rw endpoints
| +--rw endpoint* [name]
| +--rw name string
| +--rw (transport)
| +--:(https) {https-call-home}?
| +--rw https
| +--rw remote-address inet:host
| +--rw remote-port? inet:port-num\
\ber
| +--rw local-address? inet:ip-addre\
\ss
| +--rw local-port? inet:port-num\
\ber
| +--rw tcp-keepalives {tcp-client-keepalive\
\s}? grouping restconf-server-grouping
| | +--rw idle-time? uint16 +-- listen! {listen}?
| | +--rw max-probes? uint16 | +-- endpoint* [name]
| | +--rw probe-interval? uint16 | +-- name? string
| +--rw tls-server-identity | +-- (transport)
| | +--rw (local-or-keystore) | +--:(https) {https-listen}?
| | +--:(local) {local-keys-supported}? | +-- https
| | | +--rw local-definition | +---u restconf-server-grouping
| | | +--rw algorithm? +-- call-home! {call-home}?
| | | | asymmetric-key-algorit\ +-- restconf-client* [name]
\hm-ref +-- name? string
| | | +--rw public-key? +-- endpoints
| | | | binary | +-- endpoint* [name]
| | | +--rw private-key? | +-- name? string
| | | | union | +-- (transport)
| | | +---x generate-hidden-key | +--:(https) {https-call-home}?
| | | | +---w input | +-- https
| | | | +---w algorithm | +---u restconf-server-grouping
| | | | asymmetric-key-a\ +-- connection-type
\lgorithm-ref | +-- (connection-type)
| | | +---x install-hidden-key | +--:(persistent-connection)
| | | | +---w input | | +-- persistent!
| | | | +---w algorithm | +--:(periodic-connection)
| | | | | asymmetric-key-a\ | +-- periodic!
\lgorithm-ref | +-- period? uint16
| | | | +---w public-key? bin\ | +-- anchor-time? yang:date-and-time
\ary | +-- idle-timeout? uint16
| | | | +---w private-key? bin\ +-- reconnect-strategy
\ary +-- start-with? enumeration
| | | +--rw cert? +-- max-attempts? uint8
| | | | end-entity-cert-cms
| | | +---n certificate-expiration
| | | +-- expiration-date
| | | yang:date-and-time
| | +--:(keystore) {keystore-supported}?
| | +--rw keystore-reference?
| | ks:asymmetric-key-certifi\
\cate-ref
| +--rw tls-client-auth
| | +--rw pinned-ca-certs?
| | | ta:pinned-certificates-ref
| | | {ta:x509-certificates}?
| | +--rw pinned-client-certs?
| | | ta:pinned-certificates-ref
| | | {ta:x509-certificates}?
| | +--rw cert-maps
| | +--rw cert-to-name* [id]
| | +--rw id uint32
| | +--rw fingerprint
| | | x509c2n:tls-fingerprint
| | +--rw map-type identityref
| | +--rw name string
| +--rw tls-hello-params
| | {tls-server-hello-params-config}?
| | +--rw tls-versions
| | | +--rw tls-version* identityref
| | +--rw cipher-suites
| | +--rw cipher-suite* identityref
| +--rw tls-keepalives {tls-server-keepalive\
\s}?
| | +--rw max-wait? uint16
| | +--rw max-attempts? uint8
| +--rw http-keepalives
| {http-server-keepalives}?
| +--rw max-wait? uint16
| +--rw max-attempts? uint8
+--rw connection-type
| +--rw (connection-type)
| +--:(persistent-connection)
| | +--rw persistent!
| +--:(periodic-connection)
| +--rw periodic!
| +--rw period? uint16
| +--rw anchor-time? yang:date-and-time
| +--rw idle-timeout? uint16
+--rw reconnect-strategy
+--rw start-with? enumeration
+--rw max-attempts? uint8
3.2. Example Usage 3.2. Example Usage
The following example illustrates configuring a RESTCONF server to The following example illustrates configuring a RESTCONF server to
listen for RESTCONF client connections, as well as configuring call- listen for RESTCONF client connections, as well as configuring call-
home to one RESTCONF client. home to one RESTCONF client.
This example is consistent with the examples presented in Section 3.2 This example is consistent with the examples presented in Section 2
of [I-D.ietf-netconf-keystore]. of [I-D.ietf-netconf-trust-anchors] and Section 3.2 of
[I-D.ietf-netconf-keystore].
========== NOTE: '\\' line wrapping per BCP XX (RFC XXXX) =========== =========== NOTE: '\' line wrapping per BCP XX (RFC XXXX) ===========
<restconf-server <restconf-server
xmlns="urn:ietf:params:xml:ns:yang:ietf-restconf-server" xmlns="urn:ietf:params:xml:ns:yang:ietf-restconf-server"
xmlns:x509c2n="urn:ietf:params:xml:ns:yang:ietf-x509-cert-to-name"> xmlns:x509c2n="urn:ietf:params:xml:ns:yang:ietf-x509-cert-to-name">
<!-- endpoints to listen for RESTCONF connections on --> <!-- endpoints to listen for RESTCONF connections on -->
<listen> <listen>
<endpoint> <endpoint>
<name>netconf/tls</name> <name>netconf/tls</name>
<https> <https>
<local-address>11.22.33.44</local-address> <tcp-server-parameters>
<tls-server-identity> <local-address>11.22.33.44</local-address>
<local-definition> </tcp-server-parameters>
<algorithm xmlns:ct="urn:ietf:params:xml:ns:yang:ietf-cr\ <tls-server-parameters>
\ypto-types">ct:rsa2048</algorithm> <server-identity>
<private-key>base64encodedvalue==</private-key> <local-definition>
<public-key>base64encodedvalue==</public-key> <algorithm xmlns:ct="urn:ietf:params:xml:ns:yang:ietf-\
<cert>base64encodedvalue==</cert> crypto-types">ct:rsa2048</algorithm>
</local-definition> <private-key>base64encodedvalue==</private-key>
</tls-server-identity> <public-key>base64encodedvalue==</public-key>
<tls-client-auth> <cert>base64encodedvalue==</cert>
<pinned-ca-certs>explicitly-trusted-client-ca-certs</pinne\ </local-definition>
\d-ca-certs> </server-identity>
<pinned-client-certs>explicitly-trusted-client-certs</pinn\ <client-authentication>
\ed-client-certs> <pinned-ca-certs>explicitly-trusted-client-ca-certs</pin\
<cert-maps> ned-ca-certs>
<cert-to-name> <pinned-client-certs>explicitly-trusted-client-certs</pi\
<id>1</id> nned-client-certs>
<fingerprint>11:0A:05:11:00</fingerprint> <cert-maps>
<map-type>x509c2n:san-any</map-type> <cert-to-name>
</cert-to-name> <id>1</id>
<cert-to-name> <fingerprint>11:0A:05:11:00</fingerprint>
<id>2</id> <map-type>x509c2n:san-any</map-type>
<fingerprint>B3:4F:A1:8C:54</fingerprint> </cert-to-name>
<map-type>x509c2n:specified</map-type> <cert-to-name>
<name>scooby-doo</name> <id>2</id>
</cert-to-name> <fingerprint>B3:4F:A1:8C:54</fingerprint>
</cert-maps> <map-type>x509c2n:specified</map-type>
</tls-client-auth> <name>scooby-doo</name>
</cert-to-name>
</cert-maps>
</client-authentication>
</tls-server-parameters>
<http-server-parameters>
<server-name>foo.example.com</server-name>
<protocol-versions>
<protocol-version>HTTP/1.1</protocol-version>
<protocol-version>HTTP/2.0</protocol-version>
</protocol-versions>
</http-server-parameters>
</https> </https>
</endpoint> </endpoint>
</listen> </listen>
<!-- call home to a RESTCONF client with two endpoints --> <!-- call home to a RESTCONF client with two endpoints -->
<call-home> <call-home>
<restconf-client> <restconf-client>
<name>config-manager</name> <name>config-manager</name>
<endpoints> <endpoints>
<endpoint> <endpoint>
<name>east-data-center</name> <name>east-data-center</name>
<https> <https>
<remote-address>east.example.com</remote-address> <tcp-client-parameters>
<tls-server-identity> <remote-address>east.example.com</remote-address>
<local-definition> </tcp-client-parameters>
<algorithm xmlns:ct="urn:ietf:params:xml:ns:yang:iet\ <tls-server-parameters>
<server-identity>
\f-crypto-types">ct:rsa2048</algorithm> <local-definition>
<private-key>base64encodedvalue==</private-key> <algorithm xmlns:ct="urn:ietf:params:xml:ns:yang:i\
<public-key>base64encodedvalue==</public-key> etf-crypto-types">ct:rsa2048</algorithm>
<cert>base64encodedvalue==</cert> <private-key>base64encodedvalue==</private-key>
</local-definition> <public-key>base64encodedvalue==</public-key>
</tls-server-identity> <cert>base64encodedvalue==</cert>
<tls-client-auth> </local-definition>
<pinned-ca-certs>explicitly-trusted-client-ca-certs</p\ </server-identity>
\inned-ca-certs> <client-authentication>
<pinned-client-certs>explicitly-trusted-client-certs</\ <pinned-ca-certs>explicitly-trusted-client-ca-certs<\
\pinned-client-certs> /pinned-ca-certs>
<cert-maps> <pinned-client-certs>explicitly-trusted-client-certs\
<cert-to-name> </pinned-client-certs>
<id>1</id> <cert-maps>
<fingerprint>11:0A:05:11:00</fingerprint> <cert-to-name>
<map-type>x509c2n:san-any</map-type> <id>1</id>
</cert-to-name> <fingerprint>11:0A:05:11:00</fingerprint>
<cert-to-name> <map-type>x509c2n:san-any</map-type>
<id>2</id> </cert-to-name>
<fingerprint>B3:4F:A1:8C:54</fingerprint> <cert-to-name>
<map-type>x509c2n:specified</map-type> <id>2</id>
<name>scooby-doo</name> <fingerprint>B3:4F:A1:8C:54</fingerprint>
</cert-to-name> <map-type>x509c2n:specified</map-type>
</cert-maps> <name>scooby-doo</name>
</tls-client-auth> </cert-to-name>
</cert-maps>
</client-authentication>
</tls-server-parameters>
<http-server-parameters>
<server-name>foo.example.com</server-name>
<protocol-versions>
<protocol-version>HTTP/1.1</protocol-version>
<protocol-version>HTTP/2.0</protocol-version>
</protocol-versions>
</http-server-parameters>
</https> </https>
</endpoint> </endpoint>
<endpoint> <endpoint>
<name>west-data-center</name> <name>west-data-center</name>
<https> <https>
<remote-address>west.example.com</remote-address> <tcp-client-parameters>
<tcp-keepalives> <remote-address>west.example.com</remote-address>
<idle-time>15</idle-time> </tcp-client-parameters>
<max-probes>3</max-probes> <tls-server-parameters>
<probe-interval>30</probe-interval> <server-identity>
</tcp-keepalives> <local-definition>
<tls-server-identity> <algorithm xmlns:ct="urn:ietf:params:xml:ns:yang:i\
<local-definition> etf-crypto-types">ct:rsa2048</algorithm>
<algorithm xmlns:ct="urn:ietf:params:xml:ns:yang:iet\ <private-key>base64encodedvalue==</private-key>
\f-crypto-types">ct:rsa2048</algorithm> <public-key>base64encodedvalue==</public-key>
<private-key>base64encodedvalue==</private-key> <cert>base64encodedvalue==</cert>
<public-key>base64encodedvalue==</public-key> </local-definition>
<cert>base64encodedvalue==</cert> </server-identity>
</local-definition> <client-authentication>
</tls-server-identity> <pinned-ca-certs>explicitly-trusted-client-ca-certs<\
<tls-client-auth> /pinned-ca-certs>
<pinned-ca-certs>explicitly-trusted-client-ca-certs</p\ <pinned-client-certs>explicitly-trusted-client-certs\
\inned-ca-certs> </pinned-client-certs>
<pinned-client-certs>explicitly-trusted-client-certs</\ <cert-maps>
\pinned-client-certs> <cert-to-name>
<cert-maps> <id>1</id>
<cert-to-name> <fingerprint>11:0A:05:11:00</fingerprint>
<id>1</id> <map-type>x509c2n:san-any</map-type>
<fingerprint>11:0A:05:11:00</fingerprint> </cert-to-name>
<map-type>x509c2n:san-any</map-type> <cert-to-name>
</cert-to-name> <id>2</id>
<cert-to-name> <fingerprint>B3:4F:A1:8C:54</fingerprint>
<id>2</id> <map-type>x509c2n:specified</map-type>
<fingerprint>B3:4F:A1:8C:54</fingerprint> <name>scooby-doo</name>
<map-type>x509c2n:specified</map-type> </cert-to-name>
<name>scooby-doo</name> </cert-maps>
</cert-to-name> </client-authentication>
</cert-maps> </tls-server-parameters>
</tls-client-auth> <http-server-parameters>
<http-keepalives> <server-name>foo.example.com</server-name>
<max-wait>30</max-wait> <protocol-versions>
<max-attempts>3</max-attempts> <protocol-version>HTTP/1.1</protocol-version>
</http-keepalives> <protocol-version>HTTP/2.0</protocol-version>
</protocol-versions>
</http-server-parameters>
</https> </https>
</endpoint> </endpoint>
</endpoints> </endpoints>
<connection-type> <connection-type>
<periodic> <periodic>
<idle-timeout>300</idle-timeout> <idle-timeout>300</idle-timeout>
<period>60</period> <period>60</period>
</periodic> </periodic>
</connection-type> </connection-type>
<reconnect-strategy> <reconnect-strategy>
skipping to change at page 27, line 48 skipping to change at page 22, line 30
</call-home> </call-home>
</restconf-server> </restconf-server>
3.3. YANG Module 3.3. YANG Module
This YANG module has normative references to [RFC6991], [RFC7407], This YANG module has normative references to [RFC6991], [RFC7407],
[RFC8040], [RFC8071], [I-D.kwatsen-netconf-tcp-client-server], [RFC8040], [RFC8071], [I-D.kwatsen-netconf-tcp-client-server],
[I-D.ietf-netconf-tls-client-server], and [I-D.ietf-netconf-tls-client-server], and
[I-D.kwatsen-netconf-http-client-server]. [I-D.kwatsen-netconf-http-client-server].
<CODE BEGINS> file "ietf-restconf-server@2019-03-09.yang" <CODE BEGINS> file "ietf-restconf-server@2019-04-07.yang"
module ietf-restconf-server { module ietf-restconf-server {
yang-version 1.1; yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-restconf-server"; namespace "urn:ietf:params:xml:ns:yang:ietf-restconf-server";
prefix rcs; prefix rcs;
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";
} }
skipping to change at page 29, line 7 skipping to change at page 23, line 34
contact contact
"WG Web: <http://datatracker.ietf.org/wg/netconf/> "WG Web: <http://datatracker.ietf.org/wg/netconf/>
WG List: <mailto:netconf@ietf.org> WG List: <mailto:netconf@ietf.org>
Author: Kent Watsen <mailto:kent+ietf@watsen.net> Author: Kent Watsen <mailto:kent+ietf@watsen.net>
Author: Gary Wu <mailto:garywu@cisco.com> Author: Gary Wu <mailto:garywu@cisco.com>
Author: Juergen Schoenwaelder Author: Juergen Schoenwaelder
<mailto:j.schoenwaelder@jacobs-university.de>"; <mailto:j.schoenwaelder@jacobs-university.de>";
description description
"This module contains a collection of YANG definitions for "This module contains a collection of YANG definitions
configuring RESTCONF servers. for configuring RESTCONF servers.
The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL',
'SHALL NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED',
'NOT RECOMMENDED', 'MAY', and '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.
Copyright (c) 2019 IETF Trust and the persons identified as Copyright (c) 2019 IETF Trust and the persons identified
authors of the code. All rights reserved. as 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
without modification, is permitted pursuant to, and subject or without modification, is permitted pursuant to, and
to the license terms contained in, the Simplified BSD subject to the license terms contained in, the Simplified
License set forth in Section 4.c of the IETF Trust's BSD License set forth in Section 4.c of the IETF Trust's
Legal Provisions Relating to IETF Documents Legal Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info). (https://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC XXXX; see This version of this YANG module is part of RFC XXXX
the RFC itself for full legal notices."; (https://www.rfc-editor.org/info/rfcXXXX); see the RFC
itself for full legal notices.;
revision 2019-03-09 { The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL',
'SHALL NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED',
'NOT RECOMMENDED', 'MAY', and 'OPTIONAL' in this document
are to be interpreted as described in BCP 14 (RFC 2119)
(RFC 8174) when, and only when, they appear in all
capitals, as shown here.";
revision 2019-04-07 {
description description
"Initial version"; "Initial version";
reference reference
"RFC XXXX: RESTCONF Client and Server Models"; "RFC XXXX: RESTCONF Client and Server Models";
} }
// Features // Features
feature listen { feature listen {
description description
skipping to change at page 31, line 14 skipping to change at page 25, line 43
"Selects between available transports. This is a "Selects between available transports. This is a
'choice' statement so as to support additional 'choice' statement so as to support additional
transport options to be augmented in."; transport options to be augmented in.";
case https { case https {
if-feature "https-listen"; if-feature "https-listen";
container https { container https {
description description
"HTTPS-specific listening configuration for inbound "HTTPS-specific listening configuration for inbound
connections."; connections.";
uses tcps:tcp-server-grouping { uses tcps:tcp-server-grouping {
refine "local-port" { refine "tcp-server-parameters/local-port" {
default "443"; default "443";
description description
"The RESTCONF server will listen on the IANA- "The RESTCONF server will listen on the IANA-
assigned well-known port value for 'https' assigned well-known port value for 'https'
(443) if no value is specified."; (443) if no value is specified.";
} }
} }
uses tlss:tls-server-grouping { uses tlss:tls-server-grouping {
refine "tls-client-auth" { refine
"tls-server-parameters/client-authentication" {
must 'pinned-ca-certs or pinned-client-certs'; must 'pinned-ca-certs or pinned-client-certs';
description description
"RESTCONF servers MUST be able to validate "RESTCONF servers MUST be able to validate
clients."; clients.";
} }
augment "tls-client-auth" { augment
"tls-server-parameters/client-authentication" {
description description
"Augments in the cert-to-name structure, "Augments in the cert-to-name structure,
so the RESTCONF server can map TLS-layer so the RESTCONF server can map TLS-layer
client certificates to RESTCONF usernames."; client certificates to RESTCONF usernames.";
container cert-maps { container cert-maps {
uses x509c2n:cert-to-name; uses x509c2n:cert-to-name;
description description
"The cert-maps container is used by a TLS- "The cert-maps container is used by a TLS-
based RESTCONF server to map the RESTCONF based RESTCONF server to map the RESTCONF
client's presented X.509 certificate to client's presented X.509 certificate to
skipping to change at page 33, line 6 skipping to change at page 27, line 36
"Selects between available transports. This is a "Selects between available transports. This is a
'choice' statement so as to support additional 'choice' statement so as to support additional
transport options to be augmented in."; transport options to be augmented in.";
case https { case https {
if-feature "https-call-home"; if-feature "https-call-home";
container https { container https {
description description
"Specifies HTTPS-specific call-home transport "Specifies HTTPS-specific call-home transport
configuration."; configuration.";
uses tcpc:tcp-client-grouping { uses tcpc:tcp-client-grouping {
refine "remote-port" { refine "tcp-client-parameters/remote-port" {
default "4336"; default "4336";
description description
"The RESTCONF server will attempt to connect "The RESTCONF server will attempt to connect
to the IANA-assigned well-known port for to the IANA-assigned well-known port for
'restconf-ch-tls' (4336) if no value is 'restconf-ch-tls' (4336) if no value is
specified."; specified.";
} }
} }
uses tlss:tls-server-grouping { uses tlss:tls-server-grouping {
refine "tls-client-auth" { refine
"tls-server-parameters/client-authentication" {
must 'pinned-ca-certs or pinned-client-certs'; must 'pinned-ca-certs or pinned-client-certs';
description description
"RESTCONF servers MUST be able to validate "RESTCONF servers MUST be able to validate
clients."; clients.";
} }
augment "tls-client-auth" { augment
"tls-server-parameters/client-authentication" {
description description
"Augments in the cert-to-name structure, "Augments in the cert-to-name structure,
so the RESTCONF server can map TLS-layer so the RESTCONF server can map TLS-layer
client certificates to RESTCONF usernames."; client certificates to RESTCONF usernames.";
container cert-maps { container cert-maps {
uses x509c2n:cert-to-name; uses x509c2n:cert-to-name;
description description
"The cert-maps container is used by a "The cert-maps container is used by a
TLS-based RESTCONF server to map the TLS-based RESTCONF server to map the
RESTCONF client's presented X.509 RESTCONF client's presented X.509
skipping to change at page 34, line 29 skipping to change at page 29, line 13
reconnection strategy. reconnection strategy.
This connection type minimizes any RESTCONF This connection type minimizes any RESTCONF
client to RESTCONF server data-transfer delay, client to RESTCONF server data-transfer delay,
albeit at the expense of holding resources albeit at the expense of holding resources
longer."; longer.";
} }
} }
case periodic-connection { case periodic-connection {
container periodic { container periodic {
must 'not (../../endpoints/endpoint/https/'
+ 'tcp-client-parameters/keepalives '
+ 'or ../../endpoints/endpoint/https/'
+ 'tls-server-parameters/keepalives)';
presence "Indicates that a periodic connection is presence "Indicates that a periodic connection is
to be maintained."; to be maintained.";
description description
"Periodically connect to the RESTCONF client. The "Periodically connect to the RESTCONF client. The
RESTCONF client should close the underlying TCP RESTCONF client should close the underlying TCP
connection upon completing planned activities. connection upon completing planned activities.
This connection type increases resource This connection type increases resource
utilization, albeit with increased delay in utilization, albeit with increased delay in
RESTCONF client to RESTCONF client interactions."; RESTCONF client to RESTCONF client interactions.";
skipping to change at page 36, line 47 skipping to change at page 31, line 34
container restconf-server { container restconf-server {
uses restconf-server-grouping; uses restconf-server-grouping;
description description
"Top-level container for RESTCONF server configuration."; "Top-level container for RESTCONF server configuration.";
} }
} }
<CODE ENDS> <CODE ENDS>
4. Security Considerations 4. Security Considerations
The YANG module defined in this document uses a grouping defined in The YANG module defined in this document uses groupings defined in
[I-D.ietf-netconf-tls-client-server]. Please see the Security [I-D.kwatsen-netconf-tcp-client-server],
Considerations section in that document for concerns related that [I-D.ietf-netconf-tls-client-server], and
grouping. [I-D.kwatsen-netconf-http-client-server]. Please see the Security
Considerations section in those documents for concerns related those
groupings.
The YANG module defined in this document is designed to be accessed The YANG modules defined in this document are designed to be accessed
via YANG based management protocols, such as NETCONF [RFC6241] and via YANG based management protocols, such as NETCONF [RFC6241] and
RESTCONF [RFC8040]. Both of these protocols have mandatory-to- RESTCONF [RFC8040]. Both of these protocols have mandatory-to-
implement secure transport layers (e.g., SSH, TLS) with mutual implement secure transport layers (e.g., SSH, TLS) with mutual
authentication. authentication.
The NETCONF access control model (NACM) [RFC8341] provides the means The NETCONF access control model (NACM) [RFC8341] provides the means
to restrict access for particular users to a pre-configured subset of to restrict access for particular users to a pre-configured subset of
all available protocol operations and content. all available protocol operations and content.
There are a number of data nodes defined in this YANG module that are There are a number of data nodes defined in the YANG modules that are
writable/creatable/deletable (i.e., config true, which is the writable/creatable/deletable (i.e., config true, which is the
default). These data nodes may be considered sensitive or vulnerable default). Some of these data nodes may be considered sensitive or
in some network environments. Write operations (e.g., edit-config) vulnerable in some network environments. Write operations (e.g.,
to these data nodes without proper protection can have a negative edit-config) to these data nodes without proper protection can have a
effect on network operations. These are the subtrees and data nodes negative effect on network operations. These are the subtrees and
and their sensitivity/vulnerability: data nodes and their sensitivity/vulnerability:
/: The entire data trees defined by the modules defined in this None of the subtrees or data nodes in the modules defined in this
draft are sensitive to write operations. For instance, the document need to be protected from write operations.
addition or removal of references to keys, certificates,
trusted anchors, etc., can dramatically alter the implemented
security policy. However, no NACM annotations are applied as
the data SHOULD be editable by users other than a designated
'recovery session'.
Some of the readable data nodes in this YANG module may be considered Some of the readable data nodes in the YANG modules may be considered
sensitive or vulnerable in some network environments. It is thus sensitive or vulnerable in some network environments. It is thus
important to control read access (e.g., via get, get-config, or important to control read access (e.g., via get, get-config, or
notification) to these data nodes. These are the subtrees and data notification) to these data nodes. These are the subtrees and data
nodes and their sensitivity/vulnerability: nodes and their sensitivity/vulnerability:
NONE None of the subtrees or data nodes in the modules defined in this
document need to be protected from read operations.
Some of the RPC operations in this YANG module may be considered Some of the RPC operations in the YANG modules may be considered
sensitive or vulnerable in some network environments. It is thus sensitive or vulnerable in some network environments. It is thus
important to control access to these operations. These are the important to control access to these operations. These are the
operations and their sensitivity/vulnerability: operations and their sensitivity/vulnerability:
NONE The modules defined in this document do not define any 'RPC' or
'action' statements.
5. IANA Considerations 5. IANA Considerations
5.1. The IETF XML Registry 5.1. The IETF XML Registry
This document registers two URIs in the "ns" subregistry of the IETF This document registers two URIs in the "ns" subregistry of the IETF
XML Registry [RFC3688]. Following the format in [RFC3688], the XML Registry [RFC3688]. Following the format in [RFC3688], the
following registrations are requested: following registrations are requested:
URI: urn:ietf:params:xml:ns:yang:ietf-restconf-client URI: urn:ietf:params:xml:ns:yang:ietf-restconf-client
skipping to change at page 38, line 41 skipping to change at page 33, line 33
6.1. Normative References 6.1. Normative References
[I-D.ietf-netconf-keystore] [I-D.ietf-netconf-keystore]
Watsen, K., "YANG Data Model for a Centralized Keystore Watsen, K., "YANG Data Model for a Centralized Keystore
Mechanism", draft-ietf-netconf-keystore-08 (work in Mechanism", draft-ietf-netconf-keystore-08 (work in
progress), March 2019. progress), March 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-08 (work in progress), October 2018. server-10 (work in progress), March 2019.
[I-D.kwatsen-netconf-http-client-server] [I-D.kwatsen-netconf-http-client-server]
Watsen, K., "YANG Groupings for HTTP Clients and HTTP Watsen, K., "YANG Groupings for HTTP Clients and HTTP
Servers", draft-kwatsen-netconf-http-client-server-00 Servers", draft-kwatsen-netconf-http-client-server-00
(work in progress), March 2019. (work in progress), March 2019.
[I-D.kwatsen-netconf-tcp-client-server] [I-D.kwatsen-netconf-tcp-client-server]
Watsen, K., "YANG Groupings for TCP Clients and TCP Watsen, K., "YANG Groupings for TCP Clients and TCP
Servers", draft-kwatsen-netconf-tcp-client-server-00 (work Servers", draft-kwatsen-netconf-tcp-client-server-00 (work
in progress), March 2019. in progress), March 2019.
skipping to change at page 39, line 41 skipping to change at page 34, line 36
[RFC8071] Watsen, K., "NETCONF Call Home and RESTCONF Call Home", [RFC8071] Watsen, K., "NETCONF Call Home and RESTCONF Call Home",
RFC 8071, DOI 10.17487/RFC8071, February 2017, RFC 8071, DOI 10.17487/RFC8071, February 2017,
<https://www.rfc-editor.org/info/rfc8071>. <https://www.rfc-editor.org/info/rfc8071>.
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/info/rfc8174>. May 2017, <https://www.rfc-editor.org/info/rfc8174>.
6.2. Informative References 6.2. Informative References
[I-D.ietf-netconf-netconf-client-server] [I-D.ietf-netconf-trust-anchors]
Watsen, K., "NETCONF Client and Server Models", draft- Watsen, K., "YANG Data Model for Global Trust Anchors",
ietf-netconf-netconf-client-server-08 (work in progress), draft-ietf-netconf-trust-anchors-03 (work in progress),
October 2018. March 2019.
[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
DOI 10.17487/RFC3688, January 2004, DOI 10.17487/RFC3688, January 2004,
<https://www.rfc-editor.org/info/rfc3688>. <https://www.rfc-editor.org/info/rfc3688>.
[RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed.,
and A. Bierman, Ed., "Network Configuration Protocol and A. Bierman, Ed., "Network Configuration Protocol
(NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011, (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011,
<https://www.rfc-editor.org/info/rfc6241>. <https://www.rfc-editor.org/info/rfc6241>.
skipping to change at page 41, line 5 skipping to change at page 36, line 5
[RFC8341] Bierman, A. and M. Bjorklund, "Network Configuration [RFC8341] Bierman, A. and M. Bjorklund, "Network Configuration
Access Control Model", STD 91, RFC 8341, Access Control Model", STD 91, RFC 8341,
DOI 10.17487/RFC8341, March 2018, DOI 10.17487/RFC8341, March 2018,
<https://www.rfc-editor.org/info/rfc8341>. <https://www.rfc-editor.org/info/rfc8341>.
[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>.
Appendix A. Change Log Appendix A. Expanded Tree Diagrams
A.1. 00 to 01 A.1. Expanded Tree Diagram for 'ietf-restconf-client'
The following tree diagram [RFC8340] provides an overview of the data
model for the "ietf-restconf-client" module.
This tree diagram shows all the nodes defined in this module,
including those defined by "grouping" statements used by this module.
Please see Section 2.1 for a tree diagram that illustrates what the
module looks like without all the "grouping" statements expanded.
========== NOTE: '\\' line wrapping per BCP XX (RFC XXXX) ===========
module: ietf-restconf-client
+--rw restconf-client
+--rw initiate! {initiate}?
| +--rw restconf-server* [name]
| +--rw name string
| +--rw endpoints
| | +--rw endpoint* [name]
| | +--rw name string
| | +--rw (transport)
| | +--:(https) {https-initiate}?
| | +--rw https
| | +--rw tcp-client-parameters
| | | +--rw remote-address inet:host
| | | +--rw remote-port? inet:port-number
| | | +--rw local-address? inet:ip-address
| | | +--rw local-port? inet:port-number
| | | +--rw keepalives!
| | | {tcp-client-keepalives}?
| | | +--rw idle-time uint16
| | | +--rw max-probes? uint16
| | | +--rw probe-interval? uint16
| | +--rw tls-client-parameters
| | | +--rw client-identity
| | | | +--rw (auth-type)
| | | | +--:(certificate)
| | | | +--rw certificate
| | | | +--rw (local-or-keystore)
| | | | +--:(local)
| | | | | {local-keys-sup\
\ported}?
| | | | | +--rw local-definition
| | | | | +--rw algorithm?
| | | | | | asymmetric\
\-key-algorithm-ref
| | | | | +--rw public-key?
| | | | | | binary
| | | | | +--rw private-key?
| | | | | | union
| | | | | +---x generate-hid\
\den-key
| | | | | | +---w input
| | | | | | +---w algori\
\thm
| | | | | | asym\
\metric-key-algorithm-ref
| | | | | +---x install-hidd\
\en-key
| | | | | | +---w input
| | | | | | +---w algori\
\thm
| | | | | | | asym\
\metric-key-algorithm-ref
| | | | | | +---w public\
\-key?
| | | | | | | bina\
\ry
| | | | | | +---w privat\
\e-key?
| | | | | | bina\
\ry
| | | | | +--rw cert?
| | | | | | end-entity\
\-cert-cms
| | | | | +---n certificate-\
\expiration
| | | | | +-- expiration-\
\date
| | | | | yang:da\
\te-and-time
| | | | +--:(keystore)
| | | | {keystore-suppo\
\rted}?
| | | | +--rw keystore-refere\
\nce?
| | | | ks:asymmetric\
\-key-certificate-ref
| | | +--rw server-authentication
| | | | +--rw pinned-ca-certs?
| | | | | ta:pinned-certificates-ref
| | | | | {ta:x509-certificates}?
| | | | +--rw pinned-server-certs?
| | | | ta:pinned-certificates-ref
| | | | {ta:x509-certificates}?
| | | +--rw hello-params
| | | | {tls-client-hello-params-config\
\}?
| | | | +--rw tls-versions
| | | | | +--rw tls-version* identityref
| | | | +--rw cipher-suites
| | | | +--rw cipher-suite* identityref
| | | +--rw keepalives!
| | | {tls-client-keepalives}?
| | | +--rw max-wait? uint16
| | | +--rw max-attempts? uint8
| | +--rw http-client-parameters
| | +--rw protocol-version? enumeration
| | +--rw client-identity
| | | +--rw (auth-type)?
| | | +--:(basic)
| | | | +--rw basic {basic-auth}?
| | | | +--rw user-id? string
| | | | +--rw password? string
| | | +--:(bearer)
| | | | +--rw bearer {bearer-auth}?
| | | | +--rw token? string
| | | +--:(digest)
| | | | +--rw digest {digest-auth}?
| | | | +--rw username? string
| | | | +--rw password? string
| | | +--:(hoba)
| | | | +--rw hoba {hoba-auth}?
| | | +--:(mutual)
| | | | +--rw mutual {mutual-auth}?
| | | +--:(negotiate)
| | | | +--rw negotiate
| | | | {negotiate-auth}?
| | | +--:(oauth)
| | | | +--rw oauth {oauth-auth}?
| | | +--:(scram-sha-1)
| | | | +--rw scram-sha-1
| | | | {scram-sha-1-auth}?
| | | +--:(scram-sha-256)
| | | | +--rw scram-sha-256
| | | | {scram-sha-256-auth}?
| | | +--:(vapid)
| | | +--rw vapid {vapid-auth}?
| | +--rw proxy-server! {proxy-connect}?
| | +--rw tcp-client-parameters
| | | +--rw remote-address inet:host
| | | +--rw remote-port?
| | | | inet:port-number
| | | +--rw local-address?
| | | | inet:ip-address
| | | +--rw local-port?
| | | | inet:port-number
| | | +--rw keepalives!
| | | {tcp-client-keepalives}?
| | | +--rw idle-time uint16
| | | +--rw max-probes? uint16
| | | +--rw probe-interval? uint16
| | +--rw tls-client-parameters
| | | +--rw client-identity
| | | | +--rw (auth-type)?
| | | | +--:(certificate)
| | | | +--rw certificate
| | | | +--rw (local-or-keyst\
\ore)
| | | | +--:(local)
| | | | | {local-ke\
\ys-supported}?
| | | | | +--rw local-def\
\inition
| | | | | +--rw algori\
\thm?
| | | | | | asym\
\metric-key-algorithm-ref
| | | | | +--rw public\
\-key?
| | | | | | bina\
\ry
| | | | | +--rw privat\
\e-key?
| | | | | | union
| | | | | +---x genera\
\te-hidden-key
| | | | | | +---w inp\
\ut
| | | | | | +---w \
\algorithm
| | | | | | \
\ asymmetric-key-algorithm-ref
| | | | | +---x instal\
\l-hidden-key
| | | | | | +---w inp\
\ut
| | | | | | +---w \
\algorithm
| | | | | | | \
\ asymmetric-key-algorithm-ref
| | | | | | +---w \
\public-key?
| | | | | | | \
\ binary
| | | | | | +---w \
\private-key?
| | | | | | \
\ binary
| | | | | +--rw cert?
| | | | | | end-\
\entity-cert-cms
| | | | | +---n certif\
\icate-expiration
| | | | | +-- expir\
\ation-date
| | | | | y\
\ang:date-and-time
| | | | +--:(keystore)
| | | | {keystore\
\-supported}?
| | | | +--rw keystore-\
\reference?
| | | | ks:asym\
\metric-key-certificate-ref
| | | +--rw server-authentication
| | | | +--rw pinned-ca-certs?
| | | | | ta:pinned-certificates\
\-ref
| | | | | {ta:x509-certificates}?
| | | | +--rw pinned-server-certs?
| | | | ta:pinned-certificates\
\-ref
| | | | {ta:x509-certificates}?
| | | +--rw hello-params
| | | | {tls-client-hello-params-\
\config}?
| | | | +--rw tls-versions
| | | | | +--rw tls-version*
| | | | | identityref
| | | | +--rw cipher-suites
| | | | +--rw cipher-suite*
| | | | identityref
| | | +--rw keepalives!
| | | {tls-client-keepalives}?
| | | +--rw max-wait? uint16
| | | +--rw max-attempts? uint8
| | +--rw proxy-client-identity
| | +--rw user-id? string
| | +--rw password? string
| +--rw connection-type
| | +--rw (connection-type)
| | +--:(persistent-connection)
| | | +--rw persistent!
| | +--:(periodic-connection)
| | +--rw periodic!
| | +--rw period? uint16
| | +--rw anchor-time? yang:date-and-time
| | +--rw idle-timeout? uint16
| +--rw reconnect-strategy
| +--rw start-with? enumeration
| +--rw max-attempts? uint8
+--rw listen! {listen}?
+--rw idle-timeout? uint16
+--rw endpoint* [name]
+--rw name string
+--rw (transport)
+--:(https) {https-listen}?
+--rw https
+--rw tcp-server-parameters
| +--rw local-address inet:ip-address
| +--rw local-port? inet:port-number
| +--rw keepalives! {tcp-server-keepalives}?
| +--rw idle-time uint16
| +--rw max-probes? uint16
| +--rw probe-interval? uint16
+--rw tls-client-parameters
| +--rw client-identity
| | +--rw (auth-type)
| | +--:(certificate)
| | +--rw certificate
| | +--rw (local-or-keystore)
| | +--:(local)
| | | {local-keys-supported\
\}?
| | | +--rw local-definition
| | | +--rw algorithm?
| | | | asymmetric-key-a\
\lgorithm-ref
| | | +--rw public-key?
| | | | binary
| | | +--rw private-key?
| | | | union
| | | +---x generate-hidden-key
| | | | +---w input
| | | | +---w algorithm
| | | | asymmetric\
\-key-algorithm-ref
| | | +---x install-hidden-key
| | | | +---w input
| | | | +---w algorithm
| | | | | asymmetric\
\-key-algorithm-ref
| | | | +---w public-key?
| | | | | binary
| | | | +---w private-key?
| | | | binary
| | | +--rw cert?
| | | | end-entity-cert-\
\cms
| | | +---n certificate-expira\
\tion
| | | +-- expiration-date
| | | yang:date-and\
\-time
| | +--:(keystore)
| | {keystore-supported}?
| | +--rw keystore-reference?
| | ks:asymmetric-key-c\
\ertificate-ref
| +--rw server-authentication
| | +--rw pinned-ca-certs?
| | | ta:pinned-certificates-ref
| | | {ta:x509-certificates}?
| | +--rw pinned-server-certs?
| | ta:pinned-certificates-ref
| | {ta:x509-certificates}?
| +--rw hello-params
| | {tls-client-hello-params-config}?
| | +--rw tls-versions
| | | +--rw tls-version* identityref
| | +--rw cipher-suites
| | +--rw cipher-suite* identityref
| +--rw keepalives! {tls-client-keepalives}?
| +--rw max-wait? uint16
| +--rw max-attempts? uint8
+--rw http-client-parameters
+--rw protocol-version? enumeration
+--rw client-identity
| +--rw (auth-type)?
| +--:(basic)
| | +--rw basic {basic-auth}?
| | +--rw user-id? string
| | +--rw password? string
| +--:(bearer)
| | +--rw bearer {bearer-auth}?
| | +--rw token? string
| +--:(digest)
| | +--rw digest {digest-auth}?
| | +--rw username? string
| | +--rw password? string
| +--:(hoba)
| | +--rw hoba {hoba-auth}?
| +--:(mutual)
| | +--rw mutual {mutual-auth}?
| +--:(negotiate)
| | +--rw negotiate {negotiate-auth}?
| +--:(oauth)
| | +--rw oauth {oauth-auth}?
| +--:(scram-sha-1)
| | +--rw scram-sha-1 {scram-sha-1-auth}?
| +--:(scram-sha-256)
| | +--rw scram-sha-256
| | {scram-sha-256-auth}?
| +--:(vapid)
| +--rw vapid {vapid-auth}?
+--rw proxy-server! {proxy-connect}?
+--rw tcp-client-parameters
| +--rw remote-address inet:host
| +--rw remote-port? inet:port-number
| +--rw local-address? inet:ip-address
| +--rw local-port? inet:port-number
| +--rw keepalives!
| {tcp-client-keepalives}?
| +--rw idle-time uint16
| +--rw max-probes? uint16
| +--rw probe-interval? uint16
+--rw tls-client-parameters
| +--rw client-identity
| | +--rw (auth-type)?
| | +--:(certificate)
| | +--rw certificate
| | +--rw (local-or-keystore)
| | +--:(local)
| | | {local-keys-sup\
\ported}?
| | | +--rw local-definition
| | | +--rw algorithm?
| | | | asymmetric\
\-key-algorithm-ref
| | | +--rw public-key?
| | | | binary
| | | +--rw private-key?
| | | | union
| | | +---x generate-hid\
\den-key
| | | | +---w input
| | | | +---w algori\
\thm
| | | | asym\
\metric-key-algorithm-ref
| | | +---x install-hidd\
\en-key
| | | | +---w input
| | | | +---w algori\
\thm
| | | | | asym\
\metric-key-algorithm-ref
| | | | +---w public\
\-key?
| | | | | bina\
\ry
| | | | +---w privat\
\e-key?
| | | | bina\
\ry
| | | +--rw cert?
| | | | end-entity\
\-cert-cms
| | | +---n certificate-\
\expiration
| | | +-- expiration-\
\date
| | | yang:da\
\te-and-time
| | +--:(keystore)
| | {keystore-suppo\
\rted}?
| | +--rw keystore-refere\
\nce?
| | ks:asymmetric\
\-key-certificate-ref
| +--rw server-authentication
| | +--rw pinned-ca-certs?
| | | ta:pinned-certificates-ref
| | | {ta:x509-certificates}?
| | +--rw pinned-server-certs?
| | ta:pinned-certificates-ref
| | {ta:x509-certificates}?
| +--rw hello-params
| | {tls-client-hello-params-config\
\}?
| | +--rw tls-versions
| | | +--rw tls-version* identityref
| | +--rw cipher-suites
| | +--rw cipher-suite* identityref
| +--rw keepalives!
| {tls-client-keepalives}?
| +--rw max-wait? uint16
| +--rw max-attempts? uint8
+--rw proxy-client-identity
+--rw user-id? string
+--rw password? string
A.2. Expanded Tree Diagram for 'ietf-restconf-server'
The following tree diagram [RFC8340] provides an overview of the data
model for the "ietf-restconf-server" module.
This tree diagram shows all the nodes defined in this module,
including those defined by "grouping" statements used by this module.
Please see Section 3.1 for a tree diagram that illustrates what the
module looks like without all the "grouping" statements expanded.
=========== NOTE: '\' line wrapping per BCP XX (RFC XXXX) ===========
module: ietf-restconf-server
+--rw restconf-server
+--rw listen! {listen}?
| +--rw endpoint* [name]
| +--rw name string
| +--rw (transport)
| +--:(https) {https-listen}?
| +--rw https
| +--rw tcp-server-parameters
| | +--rw local-address inet:ip-address
| | +--rw local-port? inet:port-number
| | +--rw keepalives! {tcp-server-keepalives}?
| | +--rw idle-time uint16
| | +--rw max-probes? uint16
| | +--rw probe-interval? uint16
| +--rw tls-server-parameters
| | +--rw server-identity
| | | +--rw (local-or-keystore)
| | | +--:(local) {local-keys-supported}?
| | | | +--rw local-definition
| | | | +--rw algorithm?
| | | | | asymmetric-key-algorithm-\
ref
| | | | +--rw public-key?
| | | | | binary
| | | | +--rw private-key?
| | | | | union
| | | | +---x generate-hidden-key
| | | | | +---w input
| | | | | +---w algorithm
| | | | | asymmetric-key-algo\
rithm-ref
| | | | +---x install-hidden-key
| | | | | +---w input
| | | | | +---w algorithm
| | | | | | asymmetric-key-algo\
rithm-ref
| | | | | +---w public-key? binary
| | | | | +---w private-key? binary
| | | | +--rw cert?
| | | | | end-entity-cert-cms
| | | | +---n certificate-expiration
| | | | +-- expiration-date
| | | | yang:date-and-time
| | | +--:(keystore) {keystore-supported}?
| | | +--rw keystore-reference?
| | | ks:asymmetric-key-certificat\
e-ref
| | +--rw client-authentication
| | | +--rw pinned-ca-certs?
| | | | ta:pinned-certificates-ref
| | | | {ta:x509-certificates}?
| | | +--rw pinned-client-certs?
| | | | ta:pinned-certificates-ref
| | | | {ta:x509-certificates}?
| | | +--rw cert-maps
| | | +--rw cert-to-name* [id]
| | | +--rw id uint32
| | | +--rw fingerprint
| | | | x509c2n:tls-fingerprint
| | | +--rw map-type identityref
| | | +--rw name string
| | +--rw hello-params
| | | {tls-server-hello-params-config}?
| | | +--rw tls-versions
| | | | +--rw tls-version* identityref
| | | +--rw cipher-suites
| | | +--rw cipher-suite* identityref
| | +--rw keepalives! {tls-server-keepalives}?
| | +--rw max-wait? uint16
| | +--rw max-attempts? uint8
| +--rw http-server-parameters
| +--rw server-name? string
| +--rw protocol-versions
| +--rw protocol-version* enumeration
+--rw call-home! {call-home}?
+--rw restconf-client* [name]
+--rw name string
+--rw endpoints
| +--rw endpoint* [name]
| +--rw name string
| +--rw (transport)
| +--:(https) {https-call-home}?
| +--rw https
| +--rw tcp-client-parameters
| | +--rw remote-address inet:host
| | +--rw remote-port? inet:port-number
| | +--rw local-address? inet:ip-address
| | +--rw local-port? inet:port-number
| | +--rw keepalives!
| | {tcp-client-keepalives}?
| | +--rw idle-time uint16
| | +--rw max-probes? uint16
| | +--rw probe-interval? uint16
| +--rw tls-server-parameters
| | +--rw server-identity
| | | +--rw (local-or-keystore)
| | | +--:(local)
| | | | {local-keys-supported}?
| | | | +--rw local-definition
| | | | +--rw algorithm?
| | | | | asymmetric-key-algo\
rithm-ref
| | | | +--rw public-key?
| | | | | binary
| | | | +--rw private-key?
| | | | | union
| | | | +---x generate-hidden-key
| | | | | +---w input
| | | | | +---w algorithm
| | | | | asymmetric-ke\
y-algorithm-ref
| | | | +---x install-hidden-key
| | | | | +---w input
| | | | | +---w algorithm
| | | | | | asymmetric-ke\
y-algorithm-ref
| | | | | +---w public-key?
| | | | | | binary
| | | | | +---w private-key?
| | | | | binary
| | | | +--rw cert?
| | | | | end-entity-cert-cms
| | | | +---n certificate-expiration
| | | | +-- expiration-date
| | | | yang:date-and-ti\
me
| | | +--:(keystore)
| | | {keystore-supported}?
| | | +--rw keystore-reference?
| | | ks:asymmetric-key-cert\
ificate-ref
| | +--rw client-authentication
| | | +--rw pinned-ca-certs?
| | | | ta:pinned-certificates-ref
| | | | {ta:x509-certificates}?
| | | +--rw pinned-client-certs?
| | | | ta:pinned-certificates-ref
| | | | {ta:x509-certificates}?
| | | +--rw cert-maps
| | | +--rw cert-to-name* [id]
| | | +--rw id uint32
| | | +--rw fingerprint
| | | | x509c2n:tls-fingerprint
| | | +--rw map-type
| | | | identityref
| | | +--rw name string
| | +--rw hello-params
| | | {tls-server-hello-params-config\
}?
| | | +--rw tls-versions
| | | | +--rw tls-version* identityref
| | | +--rw cipher-suites
| | | +--rw cipher-suite* identityref
| | +--rw keepalives!
| | {tls-server-keepalives}?
| | +--rw max-wait? uint16
| | +--rw max-attempts? uint8
| +--rw http-server-parameters
| +--rw server-name? string
| +--rw protocol-versions
| +--rw protocol-version* enumeration
+--rw connection-type
| +--rw (connection-type)
| +--:(persistent-connection)
| | +--rw persistent!
| +--:(periodic-connection)
| +--rw periodic!
| +--rw period? uint16
| +--rw anchor-time? yang:date-and-time
| +--rw idle-timeout? uint16
+--rw reconnect-strategy
+--rw start-with? enumeration
+--rw max-attempts? uint8
Appendix B. Change Log
B.1. 00 to 01
o Renamed "keychain" to "keystore". o Renamed "keychain" to "keystore".
A.2. 01 to 02 B.2. 01 to 02
o Filled in previously missing 'ietf-restconf-client' module. o Filled in previously missing 'ietf-restconf-client' module.
o Updated the ietf-restconf-server module to accomodate new grouping o Updated the ietf-restconf-server module to accommodate new
'ietf-tls-server-grouping'. grouping 'ietf-tls-server-grouping'.
A.3. 02 to 03 B.3. 02 to 03
o Refined use of tls-client-grouping to add a must statement o Refined use of tls-client-grouping to add a must statement
indicating that the TLS client must specify a client-certificate. indicating that the TLS client must specify a client-certificate.
o Changed restconf-client??? to be a grouping (not a container). o Changed restconf-client??? to be a grouping (not a container).
A.4. 03 to 04 B.4. 03 to 04
o Added RFC 8174 to Requirements Language Section. o Added RFC 8174 to Requirements Language Section.
o Replaced refine statement in ietf-restconf-client to add a o Replaced refine statement in ietf-restconf-client to add a
mandatory true. mandatory true.
o Added refine statement in ietf-restconf-server to add a must o Added refine statement in ietf-restconf-server to add a must
statement. statement.
o Now there are containers and groupings, for both the client and o Now there are containers and groupings, for both the client and
server models. server models.
o Now tree diagrams reference ietf-netmod-yang-tree-diagrams o Now tree diagrams reference ietf-netmod-yang-tree-diagrams
o Updated examples to inline key and certificates (no longer a o Updated examples to inline key and certificates (no longer a
leafref to keystore) leafref to keystore)
A.5. 04 to 05 B.5. 04 to 05
o Now tree diagrams reference ietf-netmod-yang-tree-diagrams o Now tree diagrams reference ietf-netmod-yang-tree-diagrams
o Updated examples to inline key and certificates (no longer a o Updated examples to inline key and certificates (no longer a
leafref to keystore) leafref to keystore)
A.6. 05 to 06 B.6. 05 to 06
o Fixed change log missing section issue. o Fixed change log missing section issue.
o Updated examples to match latest updates to the crypto-types, o Updated examples to match latest updates to the crypto-types,
trust-anchors, and keystore drafts. trust-anchors, and keystore drafts.
o Reduced line length of the YANG modules to fit within 69 columns. o Reduced line length of the YANG modules to fit within 69 columns.
A.7. 06 to 07 B.7. 06 to 07
o removed "idle-timeout" from "persistent" connection config. o removed "idle-timeout" from "persistent" connection config.
o Added "random-selection" for reconnection-strategy's "starts-with" o Added "random-selection" for reconnection-strategy's "starts-with"
enum. enum.
o Replaced "connection-type" choice default (persistent) with o Replaced "connection-type" choice default (persistent) with
"mandatory true". "mandatory true".
o Reduced the periodic-connection's "idle-timeout" from 5 to 2 o Reduced the periodic-connection's "idle-timeout" from 5 to 2
minutes. minutes.
o Replaced reconnect-timeout with period/anchor-time combo. o Replaced reconnect-timeout with period/anchor-time combo.
A.8. 07 to 08 B.8. 07 to 08
o Modified examples to be compatible with new crypto-types algs o Modified examples to be compatible with new crypto-types algs
A.9. 08 to 09 B.9. 08 to 09
o Corrected use of "mandatory true" for "address" leafs. o Corrected use of "mandatory true" for "address" leafs.
o Updated examples to reflect update to groupings defined in the o Updated examples to reflect update to groupings defined in the
keystore draft. keystore draft.
o Updated to use groupings defined in new TCP and HTTP drafts. o Updated to use groupings defined in new TCP and HTTP drafts.
o Updated copyright date, boilerplate template, affiliation, and o Updated copyright date, boilerplate template, affiliation, and
folding algorithm. folding algorithm.
A.10. 09 to 10 B.10. 09 to 10
o Reformatted YANG modules. o Reformatted YANG modules.
B.11. 10 to 11
o Adjusted for the top-level "demux container" added to groupings
imported from other modules.
o Added "must" expressions to ensure that keepalives are not
configured for "periodic" connections.
o Updated the boilerplate text in module-level "description"
statement to match copyeditor convention.
o Moved "expanded" tree diagrams to the Appendix.
Acknowledgements Acknowledgements
The authors would like to thank for following for lively discussions The authors would like to thank for following for lively discussions
on list and in the halls (ordered by last name): Andy Bierman, Martin on list and in the halls (ordered by last name): Andy Bierman, Martin
Bjorklund, Benoit Claise, Ramkumar Dhanapal, Mehmet Ersue, Balazs Bjorklund, Benoit Claise, Ramkumar Dhanapal, Mehmet Ersue, Balazs
Kovacs, David Lamparter, Alan Luchuk, Ladislav Lhotka, Radek Krejci, Kovacs, David Lamparter, Alan Luchuk, Ladislav Lhotka, Radek Krejci,
Tom Petch, Juergen Schoenwaelder, Phil Shafer, Sean Turner, and Bert Tom Petch, Juergen Schoenwaelder, Phil Shafer, Sean Turner, and Bert
Wijnen. Wijnen.
Author's Address Author's Address
 End of changes. 100 change blocks. 
868 lines changed or deleted 1251 lines changed or added

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