draft-ietf-netconf-restconf-client-server-19.txt   draft-ietf-netconf-restconf-client-server-20.txt 
NETCONF Working Group K. Watsen NETCONF Working Group K. Watsen
Internet-Draft Watsen Networks Internet-Draft Watsen Networks
Intended status: Standards Track May 20, 2020 Intended status: Standards Track 8 July 2020
Expires: November 21, 2020 Expires: 9 January 2021
RESTCONF Client and Server Models RESTCONF Client and Server Models
draft-ietf-netconf-restconf-client-server-19 draft-ietf-netconf-restconf-client-server-20
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)
This draft contains placeholder values that need to be replaced with This draft contains placeholder values that need to be replaced with
finalized values at the time of publication. This note summarizes finalized values at the time of publication. This note summarizes
all of the substitutions that are needed. No other RFC Editor all of the substitutions that are needed. No other RFC Editor
instructions are specified elsewhere in this document. instructions are specified elsewhere in this document.
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 (note: not all may progress. Please apply the following replacements (note: not all may
be present): be present):
o "AAAA" --> the assigned RFC value for draft-ietf-netconf-crypto- * "AAAA" --> the assigned RFC value for draft-ietf-netconf-crypto-
types types
o "BBBB" --> the assigned RFC value for draft-ietf-netconf-trust- * "BBBB" --> the assigned RFC value for draft-ietf-netconf-trust-
anchors anchors
o "CCCC" --> the assigned RFC value for draft-ietf-netconf-keystore * "CCCC" --> the assigned RFC value for draft-ietf-netconf-keystore
o "DDDD" --> the assigned RFC value for draft-ietf-netconf-tcp- * "DDDD" --> the assigned RFC value for draft-ietf-netconf-tcp-
client-server client-server
o "EEEE" --> the assigned RFC value for draft-ietf-netconf-ssh- * "EEEE" --> the assigned RFC value for draft-ietf-netconf-ssh-
client-server client-server
o "FFFF" --> the assigned RFC value for draft-ietf-netconf-tls- * "FFFF" --> the assigned RFC value for draft-ietf-netconf-tls-
client-server client-server
o "GGGG" --> the assigned RFC value for draft-ietf-netconf-http- * "GGGG" --> the assigned RFC value for draft-ietf-netconf-http-
client-server client-server
o "HHHH" --> the assigned RFC value for draft-ietf-netconf-netconf- * "HHHH" --> the assigned RFC value for draft-ietf-netconf-netconf-
client-server client-server
o "IIII" --> the assigned RFC value for this draft * "IIII" --> the assigned RFC value for this draft
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 "2020-05-20" --> the publication date of this draft * "2020-07-08" --> 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 B. Change Log * Appendix B. Change Log
Note to Reviewers (To be removed by RFC Editor)
This document presents a YANG module or modules that is/are part of a
collection of drafts that work together to produce the ultimate goal
of the NETCONF WG: to define configuration modules for NETCONF client
and servers, and RESTCONF client and servers.
The relationship between the various drafts in the collection is
presented in the below diagram.
crypto-types
^ ^
/ \
/ \
trust-anchors keystore
^ ^ ^ ^
| +---------+ | |
| | | |
| +------------+ |
tcp-client-server | / | |
^ ^ ssh-client-server | |
| | ^ tls-client-server
| | | ^ ^ http-client-server
| | | | | ^
| | | +-----+ +---------+ |
| | | | | |
| +-----------|--------|--------------+ | |
| | | | | |
+-----------+ | | | | |
| | | | | |
| | | | | |
netconf-client-server restconf-client-server
Full draft names and link to drafts:
o draft-ietf-netconf-crypto-types (html [1])
o draft-ietf-netconf-trust-anchors (html [2])
o draft-ietf-netconf-keystore (html [3])
o draft-ietf-netconf-tcp-client-server (html [4])
o draft-ietf-netconf-ssh-client-server (html [5])
o draft-ietf-netconf-tls-client-server (html [6])
o draft-ietf-netconf-http-client-server (html [7])
o draft-ietf-netconf-netconf-client-server (html [8])
o draft-ietf-netconf-restconf-client-server (html [9])
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 November 21, 2020. This Internet-Draft will expire on 9 January 2021.
Copyright Notice Copyright Notice
Copyright (c) 2020 IETF Trust and the persons identified as the Copyright (c) 2020 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/
(https://trustee.ietf.org/license-info) in effect on the date of license-info) in effect on the date of publication of this document.
publication of this document. Please review these documents Please review these documents carefully, as they describe your rights
carefully, as they describe your rights and restrictions with respect and restrictions with respect to this document. Code Components
to this document. Code Components extracted from this document must extracted from this document must include Simplified BSD License text
include Simplified BSD License text as described in Section 4.e of as described in Section 4.e of the Trust Legal Provisions and are
the Trust Legal Provisions and are provided without warranty as provided without warranty as described in the Simplified BSD License.
described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 5 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 4
1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 5 1.1. Relation to other RFCs . . . . . . . . . . . . . . . . . 4
2. The RESTCONF Client Model . . . . . . . . . . . . . . . . . . 5 1.2. Specification Language . . . . . . . . . . . . . . . . . 5
2.1. Tree Diagram . . . . . . . . . . . . . . . . . . . . . . 5 1.3. Adherence to the NMDA . . . . . . . . . . . . . . . . . . 5
2.2. Example Usage . . . . . . . . . . . . . . . . . . . . . . 7 2. The "ietf-restconf-client" Module . . . . . . . . . . . . . . 5
2.3. YANG Module . . . . . . . . . . . . . . . . . . . . . . . 10 2.1. Data Model Overview . . . . . . . . . . . . . . . . . . . 6
3. The RESTCONF Server Model . . . . . . . . . . . . . . . . . . 21 2.2. Example Usage . . . . . . . . . . . . . . . . . . . . . . 10
3.1. Tree Diagram . . . . . . . . . . . . . . . . . . . . . . 21 2.3. YANG Module . . . . . . . . . . . . . . . . . . . . . . . 14
3.2. Example Usage . . . . . . . . . . . . . . . . . . . . . . 23 3. The "ietf-restconf-server" Module . . . . . . . . . . . . . . 24
3.3. YANG Module . . . . . . . . . . . . . . . . . . . . . . . 27 3.1. Data Model Overview . . . . . . . . . . . . . . . . . . . 24
4. Security Considerations . . . . . . . . . . . . . . . . . . . 39 3.2. Example Usage . . . . . . . . . . . . . . . . . . . . . . 29
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 40 3.3. YANG Module . . . . . . . . . . . . . . . . . . . . . . . 33
5.1. The IETF XML Registry . . . . . . . . . . . . . . . . . . 40 4. Security Considerations . . . . . . . . . . . . . . . . . . . 45
5.2. The YANG Module Names Registry . . . . . . . . . . . . . 40 4.1. The "ietf-restconf-client" YANG Module . . . . . . . . . 45
6. References . . . . . . . . . . . . . . . . . . . . . . . . . 41 4.2. The "ietf-restconf-server" YANG Module . . . . . . . . . 45
6.1. Normative References . . . . . . . . . . . . . . . . . . 41 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 46
6.2. Informative References . . . . . . . . . . . . . . . . . 42 5.1. The IETF XML Registry . . . . . . . . . . . . . . . . . . 46
6.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 42 5.2. The YANG Module Names Registry . . . . . . . . . . . . . 46
Appendix A. Expanded Tree Diagrams . . . . . . . . . . . . . . . 44 6. References . . . . . . . . . . . . . . . . . . . . . . . . . 47
A.1. Expanded Tree Diagram for 'ietf-restconf-client' . . . . 44 6.1. Normative References . . . . . . . . . . . . . . . . . . 47
A.2. Expanded Tree Diagram for 'ietf-restconf-server' . . . . 76 6.2. Informative References . . . . . . . . . . . . . . . . . 48
Appendix B. Change Log . . . . . . . . . . . . . . . . . . . . . 89 Appendix A. Expanded Tree Diagrams . . . . . . . . . . . . . . . 49
B.1. 00 to 01 . . . . . . . . . . . . . . . . . . . . . . . . 89 A.1. Expanded Tree Diagram for 'ietf-restconf-client' . . . . 50
B.2. 01 to 02 . . . . . . . . . . . . . . . . . . . . . . . . 89 A.2. Expanded Tree Diagram for 'ietf-restconf-server' . . . . 50
B.3. 02 to 03 . . . . . . . . . . . . . . . . . . . . . . . . 89 Appendix B. Change Log . . . . . . . . . . . . . . . . . . . . . 50
B.4. 03 to 04 . . . . . . . . . . . . . . . . . . . . . . . . 90 B.1. 00 to 01 . . . . . . . . . . . . . . . . . . . . . . . . 50
B.5. 04 to 05 . . . . . . . . . . . . . . . . . . . . . . . . 90 B.2. 01 to 02 . . . . . . . . . . . . . . . . . . . . . . . . 50
B.6. 05 to 06 . . . . . . . . . . . . . . . . . . . . . . . . 90 B.3. 02 to 03 . . . . . . . . . . . . . . . . . . . . . . . . 50
B.7. 06 to 07 . . . . . . . . . . . . . . . . . . . . . . . . 90 B.4. 03 to 04 . . . . . . . . . . . . . . . . . . . . . . . . 51
B.8. 07 to 08 . . . . . . . . . . . . . . . . . . . . . . . . 91 B.5. 04 to 05 . . . . . . . . . . . . . . . . . . . . . . . . 51
B.9. 08 to 09 . . . . . . . . . . . . . . . . . . . . . . . . 91 B.6. 05 to 06 . . . . . . . . . . . . . . . . . . . . . . . . 51
B.10. 09 to 10 . . . . . . . . . . . . . . . . . . . . . . . . 91 B.7. 06 to 07 . . . . . . . . . . . . . . . . . . . . . . . . 51
B.11. 10 to 11 . . . . . . . . . . . . . . . . . . . . . . . . 91 B.8. 07 to 08 . . . . . . . . . . . . . . . . . . . . . . . . 52
B.12. 11 to 12 . . . . . . . . . . . . . . . . . . . . . . . . 91 B.9. 08 to 09 . . . . . . . . . . . . . . . . . . . . . . . . 52
B.13. 12 to 13 . . . . . . . . . . . . . . . . . . . . . . . . 92 B.10. 09 to 10 . . . . . . . . . . . . . . . . . . . . . . . . 52
B.14. 13 to 14 . . . . . . . . . . . . . . . . . . . . . . . . 92 B.11. 10 to 11 . . . . . . . . . . . . . . . . . . . . . . . . 52
B.15. 14 to 15 . . . . . . . . . . . . . . . . . . . . . . . . 92 B.12. 11 to 12 . . . . . . . . . . . . . . . . . . . . . . . . 52
B.16. 15 to 16 . . . . . . . . . . . . . . . . . . . . . . . . 93 B.13. 12 to 13 . . . . . . . . . . . . . . . . . . . . . . . . 53
B.17. 16 to 17 . . . . . . . . . . . . . . . . . . . . . . . . 93 B.14. 13 to 14 . . . . . . . . . . . . . . . . . . . . . . . . 53
B.18. 17 to 18 . . . . . . . . . . . . . . . . . . . . . . . . 93 B.15. 14 to 15 . . . . . . . . . . . . . . . . . . . . . . . . 53
B.19. 18 to 19 . . . . . . . . . . . . . . . . . . . . . . . . 93 B.16. 15 to 16 . . . . . . . . . . . . . . . . . . . . . . . . 54
Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 93 B.17. 16 to 17 . . . . . . . . . . . . . . . . . . . . . . . . 54
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 93 B.18. 17 to 18 . . . . . . . . . . . . . . . . . . . . . . . . 54
B.19. 18 to 19 . . . . . . . . . . . . . . . . . . . . . . . . 54
B.20. 19 to 20 . . . . . . . . . . . . . . . . . . . . . . . . 54
Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 55
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 55
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. Relation to other RFCs
This document presents one or more YANG modules [RFC7950] that are
part of a collection of RFCs that work together to define
configuration modules for clients and servers of both the NETCONF
[RFC6241] and RESTCONF [RFC8040] protocols.
The modules have been defined in a modular fashion to enable their
use by other efforts, some of which are known to be in progress at
the time of this writing, with many more expected to be defined in
time.
The relationship between the various RFCs in the collection is
presented in the below diagram. The labels in the diagram represent
the primary purpose provided by each RFC. Links the each RFC are
provided below the diagram.
crypto-types
^ ^
/ \
/ \
truststore keystore
^ ^ ^ ^
| +---------+ | |
| | | |
| +------------+ |
tcp-client-server | / | |
^ ^ ssh-client-server | |
| | ^ tls-client-server
| | | ^ ^ http-client-server
| | | | | ^
| | | +-----+ +---------+ |
| | | | | |
| +-----------|--------|--------------+ | |
| | | | | |
+-----------+ | | | | |
| | | | | |
| | | | | |
netconf-client-server restconf-client-server
+=======================+===========================================+
| Label in Diagram | Originating RFC |
+=======================+===========================================+
| crypto-types | [I-D.ietf-netconf-crypto-types] |
+-----------------------+-------------------------------------------+
| truststore | [I-D.ietf-netconf-trust-anchors] |
+-----------------------+-------------------------------------------+
| keystore | [I-D.ietf-netconf-keystore] |
+-----------------------+-------------------------------------------+
| tcp-client-server | [I-D.ietf-netconf-tcp-client-server] |
+-----------------------+-------------------------------------------+
| ssh-client-server | [I-D.ietf-netconf-ssh-client-server] |
+-----------------------+-------------------------------------------+
| tls-client-server | [I-D.ietf-netconf-tls-client-server] |
+-----------------------+-------------------------------------------+
| http-client-server | [I-D.ietf-netconf-http-client-server] |
+-----------------------+-------------------------------------------+
| netconf-client-server | [I-D.ietf-netconf-netconf-client-server] |
+-----------------------+-------------------------------------------+
|restconf-client-server | [I-D.ietf-netconf-restconf-client-server] |
+-----------------------+-------------------------------------------+
Table 1: Label to RFC Mapping
1.2. Specification Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"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 1.3. Adherence to the NMDA
This document in compliant with the Network Management Datastore
Architecture (NMDA) [RFC8342]. For instance, as described in
[I-D.ietf-netconf-trust-anchors] and [I-D.ietf-netconf-keystore],
trust anchors and keys installed during manufacturing are expected to
appear in <operational>.
2. The "ietf-restconf-client" Module
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.
YANG feature statements are used to enable implementations to YANG feature statements are used to enable implementations to
advertise which potentially uncommon parts of the model the RESTCONF advertise which potentially uncommon parts of the model the RESTCONF
client supports. client supports.
2.1. Tree Diagram 2.1. Data Model Overview
The following tree diagram [RFC8340] provides an overview of the data 2.1.1. Features
model for the "ietf-restconf-client" module.
This tree diagram only shows the nodes defined in this module; it The following diagram lists all the "feature" statements defined in
does show the nodes defined by "grouping" statements used by this the "ietf-restconf-client" module:
module.
Please see Appendix A.1 for a tree diagram that illustrates what the Features:
module looks like with all the "grouping" statements expanded. +-- https-initiate
+-- http-listen
+-- https-listen
module: ietf-restconf-client 2.1.2. Groupings
+--rw restconf-client
+---u restconf-client-app-grouping The following diagram lists all the "grouping" statements defined in
the "ietf-restconf-client" module:
Groupings:
+-- restconf-client-grouping
+-- restconf-client-initiate-stack-grouping
+-- restconf-client-listen-stack-grouping
+-- restconf-client-app-grouping
Each of these groupings are presented in the following subsections.
2.1.2.1. The "restconf-client-grouping" Grouping
The following tree diagram [RFC8340] illustrates the "restconf-
client-grouping" grouping:
grouping restconf-client-grouping ---> <empty>
Comments:
* This grouping does not define any nodes, but is maintained so that
downstream modules can augment nodes into it if needed.
* The "restconf-client-grouping" defines, if it can be called that,
the configuration for just "RESTCONF" part of a protocol stack.
It does not, for instance, define any configuration for the "TCP",
"TLS", or "HTTP" protocol layers (for that, see Section 2.1.2.2
and Section 2.1.2.3).
2.1.2.2. The "restconf-client-initiate-stack-grouping" Grouping
The following tree diagram [RFC8340] illustrates the "restconf-
client-initiate-stack-grouping" grouping:
grouping restconf-client-grouping
grouping restconf-client-initiate-stack-grouping grouping restconf-client-initiate-stack-grouping
+-- (transport) +-- (transport)
+--:(https) {https-initiate}? +--:(https) {https-initiate}?
+-- https +-- https
+-- tcp-client-parameters +-- tcp-client-parameters
| +---u tcpc:tcp-client-grouping | +---u tcpc:tcp-client-grouping
+-- tls-client-parameters +-- tls-client-parameters
| +---u tlsc:tls-client-grouping | +---u tlsc:tls-client-grouping
+-- http-client-parameters +-- http-client-parameters
| +---u httpc:http-client-grouping | +---u httpc:http-client-grouping
+-- restconf-client-parameters +-- restconf-client-parameters
+---u rcc:restconf-client-grouping
Comments:
* The "restconf-client-initiate-stack-grouping" defines the
configuration for a full RESTCONF protocol stack, for RESTCONF
clients that initiate connections to RESTCONF servers, as opposed
to receiving call-home [RFC8071] connections.
* The "transport" choice node enables transport options to be
configured. This document only defines an "https" option, but
other options MAY be augmented in.
* For the referenced grouping statement(s):
- The "tcp-client-grouping" grouping is discussed in
Section 3.1.2.1 of [I-D.ietf-netconf-tcp-client-server].
- The "tls-client-grouping" grouping is discussed in
Section 3.1.2.1 of [I-D.ietf-netconf-tls-client-server].
- The "http-client-grouping" grouping is discussed in
Section 2.1.2.2 of [I-D.ietf-netconf-http-client-server].
- The "restconf-client-grouping" grouping is discussed in
Section 2.1.2.1 in this document.
2.1.2.3. The "restconf-client-listen-stack-grouping" Grouping
The following tree diagram [RFC8340] illustrates the "restconf-
client-listen-stack-grouping" grouping:
grouping restconf-client-listen-stack-grouping grouping restconf-client-listen-stack-grouping
+-- (transport) +-- (transport)
+--:(http) {http-listen}? +--:(http) {http-listen}?
| +-- http | +-- http
| +-- tcp-server-parameters | +-- tcp-server-parameters
| | +---u tcps:tcp-server-grouping | | +---u tcps:tcp-server-grouping
| +-- http-client-parameters | +-- http-client-parameters
| | +---u httpc:http-client-grouping | | +---u httpc:http-client-grouping
| +-- restconf-client-parameters | +-- restconf-client-parameters
| +---u rcc:restconf-client-grouping
+--:(https) {https-listen}? +--:(https) {https-listen}?
+-- https +-- https
+-- tcp-server-parameters +-- tcp-server-parameters
| +---u tcps:tcp-server-grouping | +---u tcps:tcp-server-grouping
+-- tls-client-parameters +-- tls-client-parameters
| +---u tlsc:tls-client-grouping | +---u tlsc:tls-client-grouping
+-- http-client-parameters +-- http-client-parameters
| +---u httpc:http-client-grouping | +---u httpc:http-client-grouping
+-- restconf-client-parameters +-- restconf-client-parameters
+---u rcc:restconf-client-grouping
Comments:
* The "restconf-client-listen-stack-grouping" defines the
configuration for a full RESTCONF protocol stack, for RESTCONF
clients that receive call-home [RFC8071] connections from RESTCONF
servers.
* The "transport" choice node enables both the HTTP and HTTPS
transports to be configured, with each option enabled by a
"feature" statement. Note that RESTCONF requires HTTPS, the HTTP
option is provided to support cases where a TLS-terminator is
deployed in front of the RESTCONF-client.
* For the referenced grouping statement(s):
- The "tcp-server-grouping" grouping is discussed in
Section 4.1.2.1 of [I-D.ietf-netconf-tcp-client-server].
- The "tls-client-grouping" grouping is discussed in
Section 3.1.2.1 of [I-D.ietf-netconf-tls-client-server].
- The "http-client-grouping" grouping is discussed in
Section 2.1.2.2 of [I-D.ietf-netconf-http-client-server].
- The "restconf-client-grouping" grouping is discussed in
Section 2.1.2.1 in this document.
2.1.2.4. The "restconf-client-app-grouping" Grouping
The following tree diagram [RFC8340] illustrates the "restconf-
client-app-grouping" grouping:
grouping restconf-client-app-grouping grouping restconf-client-app-grouping
+-- initiate! {https-initiate}? +-- initiate! {https-initiate}?
| +-- restconf-server* [name] | +-- restconf-server* [name]
| +-- name? string | +-- name? string
| +-- endpoints | +-- endpoints
| | +-- endpoint* [name] | | +-- endpoint* [name]
| | +-- name? string | | +-- name? string
| | +---u restconf-client-initiate-stack-grouping | | +---u restconf-client-initiate-stack-grouping
| +-- connection-type | +-- connection-type
| | +-- (connection-type) | | +-- (connection-type)
skipping to change at page 7, line 8 skipping to change at page 9, line 36
| | +-- idle-timeout? uint16 | | +-- idle-timeout? uint16
| +-- reconnect-strategy | +-- reconnect-strategy
| +-- start-with? enumeration | +-- start-with? enumeration
| +-- max-attempts? uint8 | +-- max-attempts? uint8
+-- listen! {http-listen or https-listen}? +-- listen! {http-listen or https-listen}?
+-- idle-timeout? uint16 +-- idle-timeout? uint16
+-- endpoint* [name] +-- endpoint* [name]
+-- name? string +-- name? string
+---u restconf-client-listen-stack-grouping +---u restconf-client-listen-stack-grouping
Comments:
* The "restconf-client-app-grouping" defines the configuration for a
RESTCONF client that supports both initiating connections to
RESTCONF servers as well as receiving call-home connections from
RESTCONF servers.
* Both the "initiate" and "listen" subtrees must be enabled by
"feature" statements.
* For the referenced grouping statement(s):
- The "restconf-client-initiate-stack-grouping" grouping is
discussed in Section 2.1.2.2 in this document.
- The "restconf-client-listen-stack-grouping" grouping is
discussed in Section 2.1.2.3 in this document.
2.1.3. Protocol-accessible Nodes
The following diagram lists all the protocol-accessible nodes defined
in the "ietf-restconf-client" module:
module: ietf-restconf-client
+--rw restconf-client
+---u restconf-client-app-grouping
Comments:
* Protocol-accessible nodes are those nodes that are accessible when
the module is "implemented", as described in Section 5.6.5 of
[RFC7950].
* For the "ietf-restconf-client" module, the protocol-accessible
nodes are an instance of the "restconf-client-app-grouping"
discussed in Section 2.1.2.4 grouping.
* The reason for why "restconf-client-app-grouping" exists separate
from the protocol-accessible nodes definition is so as to enable
instances of restconf-client-app-grouping to be instantiated in
other locations, as may be needed or desired by some modules.
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 to listen for call-home connections.
This example is consistent with the examples presented in Section 2 This example is consistent with the examples presented in Section 2.2
of [I-D.ietf-netconf-trust-anchors] and Section 3.2 of of [I-D.ietf-netconf-trust-anchors] and Section 2.2 of
[I-D.ietf-netconf-keystore]. [I-D.ietf-netconf-keystore].
========== NOTE: '\' line wrapping per BCP XXX (RFC XXXX) =========== =============== NOTE: '\' line wrapping per RFC 8792 ================
<restconf-client <restconf-client
xmlns="urn:ietf:params:xml:ns:yang:ietf-restconf-client" xmlns="urn:ietf:params:xml:ns:yang:ietf-restconf-client"
xmlns:ct="urn:ietf:params:xml:ns:yang:ietf-crypto-types"> xmlns:ct="urn:ietf:params:xml:ns:yang:ietf-crypto-types">
<!-- 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>
skipping to change at page 7, line 42 skipping to change at page 11, line 14
<remote-address>corp-fw1.example.com</remote-address> <remote-address>corp-fw1.example.com</remote-address>
<keepalives> <keepalives>
<idle-time>15</idle-time> <idle-time>15</idle-time>
<max-probes>3</max-probes> <max-probes>3</max-probes>
<probe-interval>30</probe-interval> <probe-interval>30</probe-interval>
</keepalives> </keepalives>
</tcp-client-parameters> </tcp-client-parameters>
<tls-client-parameters> <tls-client-parameters>
<client-identity> <client-identity>
<certificate> <certificate>
<local-definition> <keystore-reference>
<public-key-format>ct:subject-public-key-info-fo\ <asymmetric-key>rsa-asymmetric-key</asymmetric-k\
rmat</public-key-format> ey>
<public-key>base64encodedvalue==</public-key> <certificate>ex-rsa-cert</certificate>
<private-key-format>ct:rsa-private-key-format</p\ </keystore-reference>
rivate-key-format>
<private-key>base64encodedvalue==</private-key>
<cert>base64encodedvalue==</cert>
</local-definition>
</certificate> </certificate>
</client-identity> </client-identity>
<server-authentication> <server-authentication>
<ca-certs> <ca-certs>
<truststore-reference>trusted-server-ca-certs</tru\ <truststore-reference>trusted-server-ca-certs</tru\
ststore-reference> ststore-reference>
</ca-certs> </ca-certs>
<ee-certs> <ee-certs>
<truststore-reference>trusted-server-ee-certs</tru\ <truststore-reference>trusted-server-ee-certs</tru\
ststore-reference> ststore-reference>
</ee-certs> </ee-certs>
skipping to change at page 8, line 47 skipping to change at page 12, line 14
<remote-address>corp-fw2.example.com</remote-address> <remote-address>corp-fw2.example.com</remote-address>
<keepalives> <keepalives>
<idle-time>15</idle-time> <idle-time>15</idle-time>
<max-probes>3</max-probes> <max-probes>3</max-probes>
<probe-interval>30</probe-interval> <probe-interval>30</probe-interval>
</keepalives> </keepalives>
</tcp-client-parameters> </tcp-client-parameters>
<tls-client-parameters> <tls-client-parameters>
<client-identity> <client-identity>
<certificate> <certificate>
<local-definition> <keystore-reference>
<public-key-format>ct:subject-public-key-info-fo\ <asymmetric-key>rsa-asymmetric-key</asymmetric-k\
rmat</public-key-format> ey>
<public-key>base64encodedvalue==</public-key> <certificate>ex-rsa-cert</certificate>
<private-key-format>ct:rsa-private-key-format</p\ </keystore-reference>
rivate-key-format>
<private-key>base64encodedvalue==</private-key>
<cert>base64encodedvalue==</cert>
</local-definition>
</certificate> </certificate>
</client-identity> </client-identity>
<server-authentication> <server-authentication>
<ca-certs> <ca-certs>
<truststore-reference>trusted-server-ca-certs</tru\ <truststore-reference>trusted-server-ca-certs</tru\
ststore-reference> ststore-reference>
</ca-certs> </ca-certs>
<ee-certs> <ee-certs>
<truststore-reference>trusted-server-ee-certs</tru\ <truststore-reference>trusted-server-ee-certs</tru\
ststore-reference> ststore-reference>
skipping to change at page 10, line 6 skipping to change at page 13, line 19
<listen> <listen>
<endpoint> <endpoint>
<name>Intranet-facing listener</name> <name>Intranet-facing listener</name>
<https> <https>
<tcp-server-parameters> <tcp-server-parameters>
<local-address>11.22.33.44</local-address> <local-address>11.22.33.44</local-address>
</tcp-server-parameters> </tcp-server-parameters>
<tls-client-parameters> <tls-client-parameters>
<client-identity> <client-identity>
<certificate> <certificate>
<local-definition> <keystore-reference>
<public-key-format>ct:subject-public-key-info-format\ <asymmetric-key>rsa-asymmetric-key</asymmetric-key>
</public-key-format> <certificate>ex-rsa-cert</certificate>
<public-key>base64encodedvalue==</public-key> </keystore-reference>
<private-key-format>ct:rsa-private-key-format</priva\
te-key-format>
<private-key>base64encodedvalue==</private-key>
<cert>base64encodedvalue==</cert>
</local-definition>
</certificate> </certificate>
</client-identity> </client-identity>
<server-authentication> <server-authentication>
<ca-certs> <ca-certs>
<truststore-reference>trusted-server-ca-certs</trustst\ <truststore-reference>trusted-server-ca-certs</trustst\
ore-reference> ore-reference>
</ca-certs> </ca-certs>
<ee-certs> <ee-certs>
<truststore-reference>trusted-server-ee-certs</trustst\ <truststore-reference>trusted-server-ee-certs</trustst\
ore-reference> ore-reference>
skipping to change at page 10, line 47 skipping to change at page 14, line 8
</client-identity> </client-identity>
</http-client-parameters> </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.ietf-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.ietf-netconf-http-client-server].
<CODE BEGINS> file "ietf-restconf-client@2020-07-08.yang"
<CODE BEGINS> file "ietf-restconf-client@2020-05-20.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 12, line 26 skipping to change at page 15, line 34
(https://www.rfc-editor.org/info/rfcIIII); see the RFC (https://www.rfc-editor.org/info/rfcIIII); see the RFC
itself for full legal notices. itself for full legal notices.
The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL', The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL',
'SHALL NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED', 'SHALL NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED',
'NOT RECOMMENDED', 'MAY', and 'OPTIONAL' in this document 'NOT RECOMMENDED', 'MAY', and 'OPTIONAL' in this document
are to be interpreted as described in BCP 14 (RFC 2119) are to be interpreted as described in BCP 14 (RFC 2119)
(RFC 8174) when, and only when, they appear in all (RFC 8174) when, and only when, they appear in all
capitals, as shown here."; capitals, as shown here.";
revision 2020-05-20 { revision 2020-07-08 {
description description
"Initial version"; "Initial version";
reference reference
"RFC IIII: RESTCONF Client and Server Models"; "RFC IIII: RESTCONF Client and Server Models";
} }
// Features // Features
feature https-initiate { feature https-initiate {
description description
skipping to change at page 13, line 42 skipping to change at page 16, line 49
choice transport { choice transport {
mandatory true; mandatory true;
description description
"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 {
must 'tls-client-parameters/client-identity
or http-client-parameters/client-identity';
description description
"Specifies HTTPS-specific transport "Specifies HTTPS-specific transport
configuration."; configuration.";
container tcp-client-parameters { container tcp-client-parameters {
description description
"A wrapper around the TCP client parameters "A wrapper around the TCP client parameters
to avoid name collisions."; to avoid name collisions.";
uses tcpc:tcp-client-grouping { uses tcpc:tcp-client-grouping {
refine "remote-port" { refine "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.";
} }
} }
} }
container tls-client-parameters { container tls-client-parameters {
must 'client-identity' {
description
"NETCONF/TLS clients MUST pass some
authentication credentials.";
}
description description
"A wrapper around the TLS client parameters "A wrapper around the TLS client parameters
to avoid name collisions."; to avoid name collisions.";
uses tlsc:tls-client-grouping; uses tlsc:tls-client-grouping;
} }
container http-client-parameters { container http-client-parameters {
description description
"A wrapper around the HTTP client parameters "A wrapper around the HTTP client parameters
to avoid name collisions."; to avoid name collisions.";
uses httpc:http-client-grouping; uses httpc:http-client-grouping;
skipping to change at page 15, line 47 skipping to change at page 19, line 4
description description
"A wrapper around the RESTCONF client parameters "A wrapper around the RESTCONF client parameters
to avoid name collisions."; to avoid name collisions.";
uses rcc:restconf-client-grouping; uses rcc:restconf-client-grouping;
} }
} }
} }
case https { case https {
if-feature "https-listen"; if-feature "https-listen";
container https { container https {
must 'tls-client-parameters/client-identity
or http-client-parameters/client-identity';
description description
"HTTPS-specific listening configuration for inbound "HTTPS-specific listening configuration for inbound
connections."; connections.";
container tcp-server-parameters { container tcp-server-parameters {
description description
"A wrapper around the TCP client parameters "A wrapper around the TCP client parameters
to avoid name collisions."; to avoid name collisions.";
uses tcps:tcp-server-grouping { uses tcps:tcp-server-grouping {
refine "local-port" { refine "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.";
} }
} }
} }
container tls-client-parameters { container tls-client-parameters {
must 'client-identity' {
description
"NETCONF/TLS clients MUST pass some
authentication credentials.";
}
description description
"A wrapper around the TLS client parameters "A wrapper around the TLS client parameters
to avoid name collisions."; to avoid name collisions.";
uses tlsc:tls-client-grouping; uses tlsc:tls-client-grouping;
} }
container http-client-parameters { container http-client-parameters {
description description
"A wrapper around the HTTP client parameters "A wrapper around the HTTP client parameters
to avoid name collisions."; to avoid name collisions.";
uses httpc:http-client-grouping; uses httpc:http-client-grouping;
skipping to change at page 21, line 26 skipping to change at page 24, line 27
// this module. // this module.
container restconf-client { container restconf-client {
uses restconf-client-app-grouping; uses restconf-client-app-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 "ietf-restconf-server" Module
The RESTCONF server model presented in this section supports both The RESTCONF server model presented in this section supports both
listening for connections as well as initiating call-home listening for connections as well as initiating call-home
connections. connections.
YANG feature statements are used to enable implementations to YANG feature statements are used to enable implementations to
advertise which potentially uncommon parts of the model the RESTCONF advertise which potentially uncommon parts of the model the RESTCONF
server supports. server supports.
3.1. Tree Diagram 3.1. Data Model Overview
The following tree diagram [RFC8340] provides an overview of the data 3.1.1. Features
model for the "ietf-restconf-server" module.
This tree diagram only shows the nodes defined in this module; it The following diagram lists all the "feature" statements defined in
does show the nodes defined by "grouping" statements used by this the "ietf-restconf-server" module:
module.
Please see Appendix A.2 for a tree diagram that illustrates what the Features:
module looks like with all the "grouping" statements expanded. +-- http-listen
+-- https-listen
+-- https-call-home
module: ietf-restconf-server 3.1.2. Groupings
+--rw restconf-server
+---u restconf-server-app-grouping The following diagram lists all the "grouping" statements defined in
the "ietf-restconf-server" module:
Groupings:
+-- restconf-server-grouping
+-- restconf-server-listen-stack-grouping
+-- restconf-server-callhome-stack-grouping
+-- restconf-server-app-grouping
Each of these groupings are presented in the following subsections.
3.1.2.1. The "restconf-server-grouping" Grouping
The following tree diagram [RFC8340] illustrates the "restconf-
server-grouping" grouping:
grouping restconf-server-grouping grouping restconf-server-grouping
+-- client-identity-mappings +-- client-identity-mappings
+---u x509c2n:cert-to-name +---u x509c2n:cert-to-name
Comments:
* The "restconf-server-grouping" defines the configuration for just
"RESTCONF" part of a protocol stack. It does not, for instance,
define any configuration for the "TCP", "TLS", or "HTTP" protocol
layers (for that, see Section 3.1.2.2 and Section 3.1.2.3).
* The "client-identity-mappings" node, which must be enabled by
"feature" statements, defines a mapping from certificate fields to
RESTCONF user names.
* For the referenced grouping statement(s):
- The "cert-to-name" grouping is discussed in Section 4.1 of
[RFC7407].
3.1.2.2. The "restconf-server-listen-stack-grouping" Grouping
The following tree diagram [RFC8340] illustrates the "restconf-
server-listen-stack-grouping" grouping:
grouping restconf-server-listen-stack-grouping grouping restconf-server-listen-stack-grouping
+-- (transport) +-- (transport)
+--:(http) {http-listen}? +--:(http) {http-listen}?
| +-- http | +-- http
| +-- external-endpoint! | +-- external-endpoint!
| | +-- address inet:ip-address | | +-- address inet:ip-address
| | +-- port? inet:port-number | | +-- port? inet:port-number
| +-- tcp-server-parameters | +-- tcp-server-parameters
| | +---u tcps:tcp-server-grouping | | +---u tcps:tcp-server-grouping
| +-- http-server-parameters | +-- http-server-parameters
skipping to change at page 22, line 29 skipping to change at page 26, line 28
+--:(https) {https-listen}? +--:(https) {https-listen}?
+-- https +-- https
+-- tcp-server-parameters +-- tcp-server-parameters
| +---u tcps:tcp-server-grouping | +---u tcps:tcp-server-grouping
+-- tls-server-parameters +-- tls-server-parameters
| +---u tlss:tls-server-grouping | +---u tlss:tls-server-grouping
+-- http-server-parameters +-- http-server-parameters
| +---u https:http-server-grouping | +---u https:http-server-grouping
+-- restconf-server-parameters +-- restconf-server-parameters
+---u rcs:restconf-server-grouping +---u rcs:restconf-server-grouping
Comments:
* The "restconf-server-listen-stack-grouping" defines the
configuration for a full RESTCONF protocol stack for RESTCONF
servers that listen for standard connections from RESTCONF
clients, as opposed to initiating call-home [RFC8071] connections.
* The "transport" choice node enables both the HTTP and HTTPS
transports to be configured, with each option enabled by a
"feature" statement. The HTTP option is provided to support cases
where a TLS-terminator is deployed in front of the RESTCONF-
server.
* For the referenced grouping statement(s):
- The "tcp-server-grouping" grouping is discussed in
Section 4.1.2.1 of [I-D.ietf-netconf-tcp-client-server].
- The "tls-server-grouping" grouping is discussed in
Section 4.1.2.1 of [I-D.ietf-netconf-tls-client-server].
- The "http-server-grouping" grouping is discussed in
Section 3.1.2.1 of [I-D.ietf-netconf-http-client-server].
- The "restconf-server-grouping" is discussed in Section 3.1.2.1
of this document.
3.1.2.3. The "restconf-server-callhome-stack-grouping" Grouping
The following tree diagram [RFC8340] illustrates the "restconf-
server-callhome-stack-grouping" grouping:
grouping restconf-server-callhome-stack-grouping grouping restconf-server-callhome-stack-grouping
+-- (transport) +-- (transport)
+--:(https) {https-listen}? +--:(https) {https-listen}?
+-- https +-- https
+-- tcp-client-parameters +-- tcp-client-parameters
| +---u tcpc:tcp-client-grouping | +---u tcpc:tcp-client-grouping
+-- tls-server-parameters +-- tls-server-parameters
| +---u tlss:tls-server-grouping | +---u tlss:tls-server-grouping
+-- http-server-parameters +-- http-server-parameters
| +---u https:http-server-grouping | +---u https:http-server-grouping
+-- restconf-server-parameters +-- restconf-server-parameters
+---u rcs:restconf-server-grouping +---u rcs:restconf-server-grouping
Comments:
* The "restconf-server-callhome-stack-grouping" defines the
configuration for a full RESTCONF protocol stack, for RESTCONF
servers that initiate call-home [RFC8071] connections to RESTCONF
clients.
* The "transport" choice node enables transport options to be
configured. This document only defines an "https" option, but
other options MAY be augmented in.
* For the referenced grouping statement(s):
- The "tcp-client-grouping" grouping is discussed in
Section 3.1.2.1 of [I-D.ietf-netconf-tcp-client-server].
- The "tls-server-grouping" grouping is discussed in
Section 4.1.2.1 of [I-D.ietf-netconf-tls-client-server].
- The "http-server-grouping" grouping is discussed in
Section 3.1.2.1 of [I-D.ietf-netconf-http-client-server].
- The "restconf-server-grouping" is discussed in Section 3.1.2.1
of this document.
3.1.2.4. The "restconf-server-app-grouping" Grouping
The following tree diagram [RFC8340] illustrates the "restconf-
server-app-grouping" grouping:
grouping restconf-server-app-grouping grouping restconf-server-app-grouping
+-- listen! {http-listen or https-listen}? +-- listen! {http-listen or https-listen}?
| +-- endpoint* [name] | +-- endpoint* [name]
| +-- name? string | +-- name? string
| +---u restconf-server-listen-stack-grouping | +---u restconf-server-listen-stack-grouping
+-- call-home! {https-call-home}? +-- call-home! {https-call-home}?
+-- restconf-client* [name] +-- restconf-client* [name]
+-- name? string +-- name? string
+-- endpoints +-- endpoints
| +-- endpoint* [name] | +-- endpoint* [name]
skipping to change at page 23, line 18 skipping to change at page 28, line 30
| | +-- persistent! | | +-- persistent!
| +--:(periodic-connection) | +--:(periodic-connection)
| +-- periodic! | +-- periodic!
| +-- period? uint16 | +-- period? uint16
| +-- anchor-time? yang:date-and-time | +-- anchor-time? yang:date-and-time
| +-- idle-timeout? uint16 | +-- idle-timeout? uint16
+-- reconnect-strategy +-- reconnect-strategy
+-- start-with? enumeration +-- start-with? enumeration
+-- max-attempts? uint8 +-- max-attempts? uint8
Comments:
* The "restconf-server-app-grouping" defines the configuration for a
RESTCONF server that supports both listening for connections from
RESTCONF clients as well as initiatiating call-home connections to
RESTCONF clients.
* Both the "listen" and "call-home" subtrees must be enabled by
"feature" statements.
* For the referenced grouping statement(s):
- The "restconf-server-listen-stack-grouping" grouping is
discussed in Section 3.1.2.2 in this document.
- The "restconf-server-callhome-stack-grouping" grouping is
discussed in Section 3.1.2.3 in this document.
3.1.3. Protocol-accessible Nodes
The following diagram lists all the protocol-accessible nodes defined
in the "ietf-restconf-server" module:
module: ietf-restconf-server
+--rw restconf-server
+---u restconf-server-app-grouping
Comments:
* Protocol-accessible nodes are those nodes that are accessible when
the module is "implemented", as described in Section 5.6.5 of
[RFC7950].
* For the "ietf-restconf-server" module, the protocol-accessible
nodes are an instance of the "restconf-server-app-grouping"
discussed in Section 3.1.2.4 grouping.
* The reason for why "restconf-server-app-grouping" exists separate
from the protocol-accessible nodes definition is so as to enable
instances of restconf-server-app-grouping to be instantiated in
other locations, as may be needed or desired by some modules.
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 2 This example is consistent with the examples presented in Section 2.2
of [I-D.ietf-netconf-trust-anchors] and Section 3.2 of of [I-D.ietf-netconf-trust-anchors] and Section 2.2 of
[I-D.ietf-netconf-keystore]. [I-D.ietf-netconf-keystore].
========== NOTE: '\' line wrapping per BCP XXX (RFC XXXX) =========== =============== NOTE: '\' line wrapping per RFC 8792 ================
<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:ct="urn:ietf:params:xml:ns:yang:ietf-crypto-types" xmlns:ct="urn:ietf:params:xml:ns:yang:ietf-crypto-types"
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>restconf/https</name>
<https> <https>
<tcp-server-parameters> <tcp-server-parameters>
<local-address>11.22.33.44</local-address> <local-address>11.22.33.44</local-address>
</tcp-server-parameters> </tcp-server-parameters>
<tls-server-parameters> <tls-server-parameters>
<server-identity> <server-identity>
<certificate> <certificate>
<local-definition> <keystore-reference>
<public-key-format>ct:subject-public-key-info-format\ <asymmetric-key>rsa-asymmetric-key</asymmetric-key>
</public-key-format> <certificate>ex-rsa-cert</certificate>
<public-key>base64encodedvalue==</public-key> </keystore-reference>
<private-key-format>ct:rsa-private-key-format</priva\
te-key-format>
<private-key>base64encodedvalue==</private-key>
<cert>base64encodedvalue==</cert>
</local-definition>
</certificate> </certificate>
</server-identity> </server-identity>
<client-authentication> <client-authentication>
<ca-certs> <ca-certs>
<truststore-reference>trusted-client-ca-certs</trustst\ <truststore-reference>trusted-client-ca-certs</trustst\
ore-reference> ore-reference>
</ca-certs> </ca-certs>
<ee-certs> <ee-certs>
<truststore-reference>trusted-client-ee-certs</trustst\ <truststore-reference>trusted-client-ee-certs</trustst\
ore-reference> ore-reference>
skipping to change at page 25, line 15 skipping to change at page 31, line 15
<remote-address>east.example.com</remote-address> <remote-address>east.example.com</remote-address>
<keepalives> <keepalives>
<idle-time>15</idle-time> <idle-time>15</idle-time>
<max-probes>3</max-probes> <max-probes>3</max-probes>
<probe-interval>30</probe-interval> <probe-interval>30</probe-interval>
</keepalives> </keepalives>
</tcp-client-parameters> </tcp-client-parameters>
<tls-server-parameters> <tls-server-parameters>
<server-identity> <server-identity>
<certificate> <certificate>
<local-definition> <keystore-reference>
<public-key-format>ct:subject-public-key-info-fo\ <asymmetric-key>rsa-asymmetric-key</asymmetric-k\
rmat</public-key-format> ey>
<public-key>base64encodedvalue==</public-key> <certificate>ex-rsa-cert</certificate>
<private-key-format>ct:rsa-private-key-format</p\ </keystore-reference>
rivate-key-format>
<private-key>base64encodedvalue==</private-key>
<cert>base64encodedvalue==</cert>
</local-definition>
</certificate> </certificate>
</server-identity> </server-identity>
<client-authentication> <client-authentication>
<ca-certs> <ca-certs>
<truststore-reference>trusted-client-ca-certs</tru\ <truststore-reference>trusted-client-ca-certs</tru\
ststore-reference> ststore-reference>
</ca-certs> </ca-certs>
<ee-certs> <ee-certs>
<truststore-reference>trusted-client-ee-certs</tru\ <truststore-reference>trusted-client-ee-certs</tru\
ststore-reference> ststore-reference>
skipping to change at page 26, line 28 skipping to change at page 32, line 24
<remote-address>west.example.com</remote-address> <remote-address>west.example.com</remote-address>
<keepalives> <keepalives>
<idle-time>15</idle-time> <idle-time>15</idle-time>
<max-probes>3</max-probes> <max-probes>3</max-probes>
<probe-interval>30</probe-interval> <probe-interval>30</probe-interval>
</keepalives> </keepalives>
</tcp-client-parameters> </tcp-client-parameters>
<tls-server-parameters> <tls-server-parameters>
<server-identity> <server-identity>
<certificate> <certificate>
<local-definition> <keystore-reference>
<public-key-format>ct:subject-public-key-info-fo\ <asymmetric-key>rsa-asymmetric-key</asymmetric-k\
rmat</public-key-format> ey>
<public-key>base64encodedvalue==</public-key> <certificate>ex-rsa-cert</certificate>
<private-key-format>ct:rsa-private-key-format</p\ </keystore-reference>
rivate-key-format>
<private-key>base64encodedvalue==</private-key>
<cert>base64encodedvalue==</cert>
</local-definition>
</certificate> </certificate>
</server-identity> </server-identity>
<client-authentication> <client-authentication>
<ca-certs> <ca-certs>
<truststore-reference>trusted-client-ca-certs</tru\ <truststore-reference>trusted-client-ca-certs</tru\
ststore-reference> ststore-reference>
</ca-certs> </ca-certs>
<ee-certs> <ee-certs>
<truststore-reference>trusted-client-ee-certs</tru\ <truststore-reference>trusted-client-ee-certs</tru\
ststore-reference> ststore-reference>
skipping to change at page 27, line 45 skipping to change at page 33, line 37
<start-with>last-connected</start-with> <start-with>last-connected</start-with>
<max-attempts>3</max-attempts> <max-attempts>3</max-attempts>
</reconnect-strategy> </reconnect-strategy>
</restconf-client> </restconf-client>
</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.ietf-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.ietf-netconf-http-client-server].
<CODE BEGINS> file "ietf-restconf-server@2020-05-20.yang" <CODE BEGINS> file "ietf-restconf-server@2020-07-08.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 38 skipping to change at page 35, line 30
(https://www.rfc-editor.org/info/rfcIIII); see the RFC (https://www.rfc-editor.org/info/rfcIIII); see the RFC
itself for full legal notices. itself for full legal notices.
The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL', The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL',
'SHALL NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED', 'SHALL NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED',
'NOT RECOMMENDED', 'MAY', and 'OPTIONAL' in this document 'NOT RECOMMENDED', 'MAY', and 'OPTIONAL' in this document
are to be interpreted as described in BCP 14 (RFC 2119) are to be interpreted as described in BCP 14 (RFC 2119)
(RFC 8174) when, and only when, they appear in all (RFC 8174) when, and only when, they appear in all
capitals, as shown here."; capitals, as shown here.";
revision 2020-05-20 { revision 2020-07-08 {
description description
"Initial version"; "Initial version";
reference reference
"RFC IIII: RESTCONF Client and Server Models"; "RFC IIII: RESTCONF Client and Server Models";
} }
// Features // Features
feature http-listen { feature http-listen {
description description
skipping to change at page 39, line 22 skipping to change at page 45, line 15
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 groupings defined in 4.1. The "ietf-restconf-client" YANG Module
[I-D.kwatsen-netconf-tcp-client-server],
[I-D.ietf-netconf-tls-client-server], and
[I-D.kwatsen-netconf-http-client-server]. Please see the Security
Considerations section in those documents for concerns related those
groupings.
The YANG modules defined in this document are designed to be accessed The "ietf-restconf-client" YANG module defines data nodes that are
via YANG based management protocols, such as NETCONF [RFC6241] and designed to be accessed via YANG based management protocols, such as
RESTCONF [RFC8040]. Both of these protocols have mandatory-to- NETCONF [RFC6241] and RESTCONF [RFC8040]. Both of these protocols
implement secure transport layers (e.g., SSH, TLS) with mutual have mandatory-to-implement secure transport layers (e.g., SSH, TLS)
authentication. with mutual 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 the YANG modules that are None of the readable data nodes in this YANG module are considered
writable/creatable/deletable (i.e., config true, which is the sensitive or vulnerable in network environments. The NACM "default-
default). Some of these data nodes may be considered sensitive or deny-all" extension has not been set for any data nodes defined in
vulnerable in some network environments. Write operations (e.g., this module.
edit-config) to these data nodes without proper protection can have a
negative effect on network operations. These are the subtrees and
data nodes and their sensitivity/vulnerability:
None of the subtrees or data nodes in the modules defined in this None of the writable data nodes in this YANG module are considered
document need to be protected from write operations. sensitive or vulnerable in network environments. The NACM "default-
deny-write" extension has not been set for any data nodes defined in
this module.
Some of the readable data nodes in the YANG modules may be considered This module does not define any RPCs, actions, or notifications, and
sensitive or vulnerable in some network environments. It is thus thus the security consideration for such is not provided here.
important to control read access (e.g., via get, get-config, or
notification) to these data nodes. These are the subtrees and data
nodes and their sensitivity/vulnerability:
None of the subtrees or data nodes in the modules defined in this Please be aware that this module uses groupings defined in other RFCs
document need to be protected from read operations. that define data nodes that do set the NACM "default-deny-all" and
"default-deny-write" extensions.
Some of the RPC operations in the YANG modules may be considered 4.2. The "ietf-restconf-server" YANG Module
sensitive or vulnerable in some network environments. It is thus
important to control access to these operations. These are the
operations and their sensitivity/vulnerability:
The modules defined in this document do not define any 'RPC' or The "ietf-restconf-server" YANG module defines data nodes that are
'action' statements. designed to be accessed via YANG based management protocols, such as
NETCONF [RFC6241] and RESTCONF [RFC8040]. Both of these protocols
have mandatory-to-implement secure transport layers (e.g., SSH, TLS)
with mutual authentication.
The NETCONF access control model (NACM) [RFC8341] provides the means
to restrict access for particular users to a pre-configured subset of
all available protocol operations and content.
None of the readable data nodes in this YANG module are considered
sensitive or vulnerable in network environments. The NACM "default-
deny-all" extension has not been set for any data nodes defined in
this module.
None of the writable data nodes in this YANG module are considered
sensitive or vulnerable in network environments. The NACM "default-
deny-write" extension has not been set for any data nodes defined in
this module.
This module does not define any RPCs, actions, or notifications, and
thus the security consideration for such is not provided here.
Please be aware that this module uses groupings defined in other RFCs
that define data nodes that do set the NACM "default-deny-all" and
"default-deny-write" extensions.
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 41, line 9 skipping to change at page 47, line 19
name: ietf-restconf-server name: ietf-restconf-server
namespace: urn:ietf:params:xml:ns:yang:ietf-restconf-server namespace: urn:ietf:params:xml:ns:yang:ietf-restconf-server
prefix: ncs prefix: ncs
reference: RFC IIII reference: RFC IIII
6. References 6. References
6.1. Normative References 6.1. Normative References
[I-D.ietf-netconf-keystore] [I-D.ietf-netconf-http-client-server]
Watsen, K., "A YANG Data Model for a Keystore", draft-
ietf-netconf-keystore-16 (work in progress), March 2020.
[I-D.ietf-netconf-tls-client-server]
Watsen, K., Wu, G., and L. Xia, "YANG Groupings for TLS
Clients and TLS Servers", draft-ietf-netconf-tls-client-
server-18 (work in progress), March 2020.
[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-05 Servers", Work in Progress, Internet-Draft, draft-ietf-
(work in progress), November 2019. netconf-http-client-server-03, 20 May 2020,
<https://tools.ietf.org/html/draft-ietf-netconf-http-
client-server-03>.
[I-D.kwatsen-netconf-tcp-client-server] [I-D.ietf-netconf-keystore]
Watsen, K., "A YANG Data Model for a Keystore", Work in
Progress, Internet-Draft, draft-ietf-netconf-keystore-17,
20 May 2020, <https://tools.ietf.org/html/draft-ietf-
netconf-keystore-17>.
[I-D.ietf-netconf-tcp-client-server]
Watsen, K. and M. Scharf, "YANG Groupings for TCP Clients Watsen, K. and M. Scharf, "YANG Groupings for TCP Clients
and TCP Servers", draft-kwatsen-netconf-tcp-client- and TCP Servers", Work in Progress, Internet-Draft, draft-
server-02 (work in progress), April 2019. ietf-netconf-tcp-client-server-06, 16 June 2020,
<https://tools.ietf.org/html/draft-ietf-netconf-tcp-
client-server-06>.
[I-D.ietf-netconf-tls-client-server]
Watsen, K. and G. Wu, "YANG Groupings for TLS Clients and
TLS Servers", Work in Progress, Internet-Draft, draft-
ietf-netconf-tls-client-server-19, 20 May 2020,
<https://tools.ietf.org/html/draft-ietf-netconf-tls-
client-server-19>.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>. <https://www.rfc-editor.org/info/rfc2119>.
[RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for [RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for
the Network Configuration Protocol (NETCONF)", RFC 6020, the Network Configuration Protocol (NETCONF)", RFC 6020,
DOI 10.17487/RFC6020, October 2010, DOI 10.17487/RFC6020, October 2010,
<https://www.rfc-editor.org/info/rfc6020>. <https://www.rfc-editor.org/info/rfc6020>.
skipping to change at page 42, line 15 skipping to change at page 48, 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-crypto-types]
Watsen, K., "Common YANG Data Types for Cryptography",
Work in Progress, Internet-Draft, draft-ietf-netconf-
crypto-types-15, 20 May 2020,
<https://tools.ietf.org/html/draft-ietf-netconf-crypto-
types-15>.
[I-D.ietf-netconf-netconf-client-server]
Watsen, K., "NETCONF Client and Server Models", Work in
Progress, Internet-Draft, draft-ietf-netconf-netconf-
client-server-19, 20 May 2020,
<https://tools.ietf.org/html/draft-ietf-netconf-netconf-
client-server-19>.
[I-D.ietf-netconf-restconf-client-server]
Watsen, K., "RESTCONF Client and Server Models", Work in
Progress, Internet-Draft, draft-ietf-netconf-restconf-
client-server-19, 20 May 2020,
<https://tools.ietf.org/html/draft-ietf-netconf-restconf-
client-server-19>.
[I-D.ietf-netconf-ssh-client-server]
Watsen, K. and G. Wu, "YANG Groupings for SSH Clients and
SSH Servers", Work in Progress, Internet-Draft, draft-
ietf-netconf-ssh-client-server-19, 20 May 2020,
<https://tools.ietf.org/html/draft-ietf-netconf-ssh-
client-server-19>.
[I-D.ietf-netconf-trust-anchors] [I-D.ietf-netconf-trust-anchors]
Watsen, K., "A YANG Data Model for a Truststore", draft- Watsen, K., "A YANG Data Model for a Truststore", Work in
ietf-netconf-trust-anchors-09 (work in progress), March Progress, Internet-Draft, draft-ietf-netconf-trust-
2020. anchors-10, 20 May 2020, <https://tools.ietf.org/html/
draft-ietf-netconf-trust-anchors-10>.
[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>.
[RFC8340] Bjorklund, M. and L. Berger, Ed., "YANG Tree Diagrams", [RFC8340] Bjorklund, M. and L. Berger, Ed., "YANG Tree Diagrams",
BCP 215, RFC 8340, DOI 10.17487/RFC8340, March 2018, BCP 215, RFC 8340, DOI 10.17487/RFC8340, March 2018,
<https://www.rfc-editor.org/info/rfc8340>. <https://www.rfc-editor.org/info/rfc8340>.
[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>.
[RFC8342] Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K.,
and R. Wilton, "Network Management Datastore Architecture
(NMDA)", RFC 8342, DOI 10.17487/RFC8342, March 2018,
<https://www.rfc-editor.org/info/rfc8342>.
[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>.
6.3. URIs
[1] https://tools.ietf.org/html/draft-ietf-netconf-crypto-types
[2] https://tools.ietf.org/html/draft-ietf-netconf-trust-anchors
[3] https://tools.ietf.org/html/draft-ietf-netconf-keystore
[4] https://tools.ietf.org/html/draft-ietf-netconf-tcp-client-server
[5] https://tools.ietf.org/html/draft-ietf-netconf-ssh-client-server
[6] https://tools.ietf.org/html/draft-ietf-netconf-tls-client-server
[7] https://tools.ietf.org/html/draft-ietf-netconf-http-client-server
[8] https://tools.ietf.org/html/draft-ietf-netconf-netconf-client-
server
[9] https://tools.ietf.org/html/draft-ietf-netconf-restconf-client-
server
Appendix A. Expanded Tree Diagrams Appendix A. Expanded Tree Diagrams
A.1. Expanded Tree Diagram for 'ietf-restconf-client' A.1. Expanded Tree Diagram for 'ietf-restconf-client'
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. model for the "ietf-restconf-client" module.
This tree diagram shows all the nodes defined in this module, This tree diagram shows all the nodes defined in this module,
including those defined by "grouping" statements used by 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 Please see Section 2.1 for a tree diagram that illustrates what the
module looks like without all the "grouping" statements expanded. module looks like without all the "grouping" statements expanded.
skipping to change at page 44, line 18 skipping to change at page 50, line 15
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. model for the "ietf-restconf-client" module.
This tree diagram shows all the nodes defined in this module, This tree diagram shows all the nodes defined in this module,
including those defined by "grouping" statements used by 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 Please see Section 2.1 for a tree diagram that illustrates what the
module looks like without all the "grouping" statements expanded. module looks like without all the "grouping" statements expanded.
========== NOTE: '\\' line wrapping per BCP XXX (RFC XXXX) ========== XNSERT_TEXT_FROM_FILE(refs/ietf-restconf-client-tree.txt)
module: ietf-restconf-client
+--rw restconf-client
+--rw initiate! {https-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
| | | | {local-binding-supported}?
| | | +--rw local-port? inet:port-number
| | | | {local-binding-supported}?
| | | +--rw keepalives!
| | | {keepalives-supported}?
| | | +--rw idle-time uint16
| | | +--rw max-probes uint16
| | | +--rw probe-interval uint16
| | +--rw tls-client-parameters
| | | +--rw client-identity
| | | | +--rw (auth-type)?
| | | | +--:(certificate)
| | | | | {x509-certificate-auth}?
| | | | | +--rw certificate
| | | | | +--rw (local-or-keystore)
| | | | | +--:(local)
| | | | | | {local-definiti\
\ons-supported}?
| | | | | | +--rw local-definition
| | | | | | +--rw public-key-f\
\ormat
| | | | | | | identityref
| | | | | | +--rw public-key
| | | | | | | binary
| | | | | | +--rw private-key-\
\format?
| | | | | | | identityref
| | | | | | +--rw (private-key\
\-type)
| | | | | | | +--:(private-ke\
\y)
| | | | | | | | +--rw privat\
\e-key?
| | | | | | | | bina\
\ry
| | | | | | | +--:(hidden-pri\
\vate-key)
| | | | | | | | +--rw hidden\
\-private-key?
| | | | | | | | empty
| | | | | | | +--:(encrypted-\
\private-key)
| | | | | | | +--rw encryp\
\ted-private-key
| | | | | | | +--rw (ke\
\y-type)
| | | | | | | | +--:(s\
\ymmetric-key-ref)
| | | | | | | | | +--\
\rw symmetric-key-ref? leafref
| | | | | | | | | \
\ {keystore-supported}?
| | | | | | | | +--:(a\
\symmetric-key-ref)
| | | | | | | | +--\
\rw asymmetric-key-ref? leafref
| | | | | | | | \
\ {keystore-supported}?
| | | | | | | +--rw val\
\ue?
| | | | | | | b\
\inary
| | | | | | +--rw cert?
| | | | | | | end-entity\
\-cert-cms
| | | | | | +---n certificate-\
\expiration
| | | | | | | +-- expiration-\
\date
| | | | | | | yang:da\
\te-and-time
| | | | | | +---x generate-cer\
\tificate-signing-request
| | | | | | {certifica\
\te-signing-request-generation}?
| | | | | | +---w input
| | | | | | | +---w subject
| | | | | | | | bina\
\ry
| | | | | | | +---w attrib\
\utes?
| | | | | | | bina\
\ry
| | | | | | +--ro output
| | | | | | +--ro certif\
\icate-signing-request
| | | | | | ct:c\
\sr
| | | | | +--:(keystore)
| | | | | {keystore-suppo\
\rted}?
| | | | | +--rw keystore-refere\
\nce
| | | | | +--rw asymmetric-k\
\ey?
| | | | | | ks:asymmet\
\ric-key-ref
| | | | | +--rw certificate?\
\ leafref
| | | | +--:(raw-public-key)
| | | | | {raw-public-key-auth}?
| | | | | +--rw raw-private-key
| | | | | +--rw (local-or-keystore)
| | | | | +--:(local)
| | | | | | {local-definiti\
\ons-supported}?
| | | | | | +--rw local-definition
| | | | | | +--rw public-key-f\
\ormat
| | | | | | | identityref
| | | | | | +--rw public-key
| | | | | | | binary
| | | | | | +--rw private-key-\
\format?
| | | | | | | identityref
| | | | | | +--rw (private-key\
\-type)
| | | | | | +--:(private-ke\
\y)
| | | | | | | +--rw privat\
\e-key?
| | | | | | | bina\
\ry
| | | | | | +--:(hidden-pri\
\vate-key)
| | | | | | | +--rw hidden\
\-private-key?
| | | | | | | empty
| | | | | | +--:(encrypted-\
\private-key)
| | | | | | +--rw encryp\
\ted-private-key
| | | | | | +--rw (ke\
\y-type)
| | | | | | | +--:(s\
\ymmetric-key-ref)
| | | | | | | | +--\
\rw symmetric-key-ref? leafref
| | | | | | | | \
\ {keystore-supported}?
| | | | | | | +--:(a\
\symmetric-key-ref)
| | | | | | | +--\
\rw asymmetric-key-ref? leafref
| | | | | | | \
\ {keystore-supported}?
| | | | | | +--rw val\
\ue?
| | | | | | b\
\inary
| | | | | +--:(keystore)
| | | | | {keystore-suppo\
\rted}?
| | | | | +--rw keystore-refere\
\nce?
| | | | | ks:asymmetric\
\-key-ref
| | | | +--:(psk) {psk-auth}?
| | | | +--rw psk
| | | | +--rw (local-or-keystore)
| | | | +--:(local)
| | | | | {local-definiti\
\ons-supported}?
| | | | | +--rw local-definition
| | | | | +--rw key-format?
| | | | | | identityref
| | | | | +--rw (key-type)
| | | | | | +--:(key)
| | | | | | | +--rw key?
| | | | | | | bina\
\ry
| | | | | | +--:(hidden-key)
| | | | | | | +--rw hidden\
\-key?
| | | | | | | empty
| | | | | | +--:(encrypted-\
\key)
| | | | | | +--rw encryp\
\ted-key
| | | | | | +--rw (ke\
\y-type)
| | | | | | | +--:(s\
\ymmetric-key-ref)
| | | | | | | | +--\
\rw symmetric-key-ref? leafref
| | | | | | | | \
\ {keystore-supported}?
| | | | | | | +--:(a\
\symmetric-key-ref)
| | | | | | | +--\
\rw asymmetric-key-ref? leafref
| | | | | | | \
\ {keystore-supported}?
| | | | | | +--rw val\
\ue?
| | | | | | b\
\inary
| | | | | +--rw id?
| | | | | string
| | | | | {ks:local-\
\definitions-supported}?
| | | | +--:(keystore)
| | | | {keystore-suppo\
\rted}?
| | | | +--rw keystore-refere\
\nce?
| | | | ks:symmetric-\
\key-ref
| | | +--rw server-authentication
| | | | +--rw ca-certs!
| | | | | {x509-certificate-auth}?
| | | | | +--rw (local-or-truststore)
| | | | | +--:(local)
| | | | | | {local-definitions-su\
\pported}?
| | | | | | +--rw local-definition
| | | | | | +--rw cert*
| | | | | | | trust-anchor-cer\
\t-cms
| | | | | | +---n certificate-expira\
\tion
| | | | | | +-- expiration-date
| | | | | | yang:date-and\
\-time
| | | | | +--:(truststore)
| | | | | {truststore-supported\
\,certificates}?
| | | | | +--rw truststore-reference?
| | | | | ts:certificate-bag-\
\ref
| | | | +--rw ee-certs!
| | | | | {x509-certificate-auth}?
| | | | | +--rw (local-or-truststore)
| | | | | +--:(local)
| | | | | | {local-definitions-su\
\pported}?
| | | | | | +--rw local-definition
| | | | | | +--rw cert*
| | | | | | | trust-anchor-cer\
\t-cms
| | | | | | +---n certificate-expira\
\tion
| | | | | | +-- expiration-date
| | | | | | yang:date-and\
\-time
| | | | | +--:(truststore)
| | | | | {truststore-supported\
\,certificates}?
| | | | | +--rw truststore-reference?
| | | | | ts:certificate-bag-\
\ref
| | | | +--rw raw-public-keys!
| | | | | {raw-public-key-auth}?
| | | | | +--rw (local-or-truststore)
| | | | | +--:(local)
| | | | | | {local-definitions-su\
\pported}?
| | | | | | +--rw local-definition
| | | | | | +--rw public-key* [name]
| | | | | | +--rw name
| | | | | | | string
| | | | | | +--rw public-key-form\
\at
| | | | | | | identityref
| | | | | | +--rw public-key
| | | | | | binary
| | | | | +--:(truststore)
| | | | | {truststore-supported\
\,public-keys}?
| | | | | +--rw truststore-reference?
| | | | | ts:public-key-bag-r\
\ef
| | | | +--rw psks! {psk-auth}?
| | | +--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 peer-allowed-to-send? empty
| | | +--rw test-peer-aliveness!
| | | +--rw max-wait? uint16
| | | +--rw max-attempts? uint8
| | +--rw http-client-parameters
| | | +--rw client-identity!
| | | | +--rw (auth-type)?
| | | | +--:(basic)
| | | | +--rw basic {basic-auth}?
| | | | +--rw user-id string
| | | | +--rw password string
| | | +--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
| | | | | {local-binding-supported}?
| | | | +--rw local-port?
| | | | | inet:port-number
| | | | | {local-binding-supported}?
| | | | +--rw keepalives!
| | | | {keepalives-supported}?
| | | | +--rw idle-time uint16
| | | | +--rw max-probes uint16
| | | | +--rw probe-interval uint16
| | | +--rw tls-client-parameters
| | | | +--rw client-identity
| | | | | +--rw (auth-type)?
| | | | | +--:(certificate)
| | | | | | {x509-certificate-\
\auth}?
| | | | | | +--rw certificate
| | | | | | +--rw (local-or-keyst\
\ore)
| | | | | | +--:(local)
| | | | | | | {local-de\
\finitions-supported}?
| | | | | | | +--rw local-def\
\inition
| | | | | | | +--rw public\
\-key-format
| | | | | | | | iden\
\tityref
| | | | | | | +--rw public\
\-key
| | | | | | | | bina\
\ry
| | | | | | | +--rw privat\
\e-key-format?
| | | | | | | | iden\
\tityref
| | | | | | | +--rw (priva\
\te-key-type)
| | | | | | | | +--:(priv\
\ate-key)
| | | | | | | | | +--rw \
\private-key?
| | | | | | | | | \
\ binary
| | | | | | | | +--:(hidd\
\en-private-key)
| | | | | | | | | +--rw \
\hidden-private-key?
| | | | | | | | | \
\ empty
| | | | | | | | +--:(encr\
\ypted-private-key)
| | | | | | | | +--rw \
\encrypted-private-key
| | | | | | | | +--\
\rw (key-type)
| | | | | | | | | \
\+--:(symmetric-key-ref)
| | | | | | | | | \
\| +--rw symmetric-key-ref? leafref
| | | | | | | | | \
\| {keystore-supported}?
| | | | | | | | | \
\+--:(asymmetric-key-ref)
| | | | | | | | | \
\ +--rw asymmetric-key-ref? leafref
| | | | | | | | | \
\ {keystore-supported}?
| | | | | | | | +--\
\rw value?
| | | | | | | | \
\ binary
| | | | | | | +--rw cert?
| | | | | | | | end-\
\entity-cert-cms
| | | | | | | +---n certif\
\icate-expiration
| | | | | | | | +-- expir\
\ation-date
| | | | | | | | y\
\ang:date-and-time
| | | | | | | +---x genera\
\te-certificate-signing-request
| | | | | | | {cer\
\tificate-signing-request-generation}?
| | | | | | | +---w inp\
\ut
| | | | | | | | +---w \
\subject
| | | | | | | | | \
\ binary
| | | | | | | | +---w \
\attributes?
| | | | | | | | \
\ binary
| | | | | | | +--ro out\
\put
| | | | | | | +--ro \
\certificate-signing-request
| | | | | | | \
\ ct:csr
| | | | | | +--:(keystore)
| | | | | | {keystore\
\-supported}?
| | | | | | +--rw keystore-\
\reference
| | | | | | +--rw asymme\
\tric-key?
| | | | | | | ks:a\
\symmetric-key-ref
| | | | | | +--rw certif\
\icate? leafref
| | | | | +--:(raw-public-key)
| | | | | | {raw-public-key-au\
\th}?
| | | | | | +--rw raw-private-key
| | | | | | +--rw (local-or-keyst\
\ore)
| | | | | | +--:(local)
| | | | | | | {local-de\
\finitions-supported}?
| | | | | | | +--rw local-def\
\inition
| | | | | | | +--rw public\
\-key-format
| | | | | | | | iden\
\tityref
| | | | | | | +--rw public\
\-key
| | | | | | | | bina\
\ry
| | | | | | | +--rw privat\
\e-key-format?
| | | | | | | | iden\
\tityref
| | | | | | | +--rw (priva\
\te-key-type)
| | | | | | | +--:(priv\
\ate-key)
| | | | | | | | +--rw \
\private-key?
| | | | | | | | \
\ binary
| | | | | | | +--:(hidd\
\en-private-key)
| | | | | | | | +--rw \
\hidden-private-key?
| | | | | | | | \
\ empty
| | | | | | | +--:(encr\
\ypted-private-key)
| | | | | | | +--rw \
\encrypted-private-key
| | | | | | | +--\
\rw (key-type)
| | | | | | | | \
\+--:(symmetric-key-ref)
| | | | | | | | \
\| +--rw symmetric-key-ref? leafref
| | | | | | | | \
\| {keystore-supported}?
| | | | | | | | \
\+--:(asymmetric-key-ref)
| | | | | | | | \
\ +--rw asymmetric-key-ref? leafref
| | | | | | | | \
\ {keystore-supported}?
| | | | | | | +--\
\rw value?
| | | | | | | \
\ binary
| | | | | | +--:(keystore)
| | | | | | {keystore\
\-supported}?
| | | | | | +--rw keystore-\
\reference?
| | | | | | ks:asym\
\metric-key-ref
| | | | | +--:(psk) {psk-auth}?
| | | | | +--rw psk
| | | | | +--rw (local-or-keyst\
\ore)
| | | | | +--:(local)
| | | | | | {local-de\
\finitions-supported}?
| | | | | | +--rw local-def\
\inition
| | | | | | +--rw key-fo\
\rmat?
| | | | | | | iden\
\tityref
| | | | | | +--rw (key-t\
\ype)
| | | | | | | +--:(key)
| | | | | | | | +--rw \
\key?
| | | | | | | | \
\ binary
| | | | | | | +--:(hidd\
\en-key)
| | | | | | | | +--rw \
\hidden-key?
| | | | | | | | \
\ empty
| | | | | | | +--:(encr\
\ypted-key)
| | | | | | | +--rw \
\encrypted-key
| | | | | | | +--\
\rw (key-type)
| | | | | | | | \
\+--:(symmetric-key-ref)
| | | | | | | | \
\| +--rw symmetric-key-ref? leafref
| | | | | | | | \
\| {keystore-supported}?
| | | | | | | | \
\+--:(asymmetric-key-ref)
| | | | | | | | \
\ +--rw asymmetric-key-ref? leafref
| | | | | | | | \
\ {keystore-supported}?
| | | | | | | +--\
\rw value?
| | | | | | | \
\ binary
| | | | | | +--rw id?
| | | | | | stri\
\ng
| | | | | | {ks:\
\local-definitions-supported}?
| | | | | +--:(keystore)
| | | | | {keystore\
\-supported}?
| | | | | +--rw keystore-\
\reference?
| | | | | ks:symm\
\etric-key-ref
| | | | +--rw server-authentication
| | | | | +--rw ca-certs!
| | | | | | {x509-certificate-auth\
\}?
| | | | | | +--rw (local-or-truststore)
| | | | | | +--:(local)
| | | | | | | {local-definiti\
\ons-supported}?
| | | | | | | +--rw local-definition
| | | | | | | +--rw cert*
| | | | | | | | trust-anch\
\or-cert-cms
| | | | | | | +---n certificate-\
\expiration
| | | | | | | +-- expiration-\
\date
| | | | | | | yang:da\
\te-and-time
| | | | | | +--:(truststore)
| | | | | | {truststore-sup\
\ported,certificates}?
| | | | | | +--rw truststore-refe\
\rence?
| | | | | | ts:certificat\
\e-bag-ref
| | | | | +--rw ee-certs!
| | | | | | {x509-certificate-auth\
\}?
| | | | | | +--rw (local-or-truststore)
| | | | | | +--:(local)
| | | | | | | {local-definiti\
\ons-supported}?
| | | | | | | +--rw local-definition
| | | | | | | +--rw cert*
| | | | | | | | trust-anch\
\or-cert-cms
| | | | | | | +---n certificate-\
\expiration
| | | | | | | +-- expiration-\
\date
| | | | | | | yang:da\
\te-and-time
| | | | | | +--:(truststore)
| | | | | | {truststore-sup\
\ported,certificates}?
| | | | | | +--rw truststore-refe\
\rence?
| | | | | | ts:certificat\
\e-bag-ref
| | | | | +--rw raw-public-keys!
| | | | | | {raw-public-key-auth}?
| | | | | | +--rw (local-or-truststore)
| | | | | | +--:(local)
| | | | | | | {local-definiti\
\ons-supported}?
| | | | | | | +--rw local-definition
| | | | | | | +--rw public-key*
| | | | | | | [name]
| | | | | | | +--rw name
| | | | | | | | string
| | | | | | | +--rw public-ke\
\y-format
| | | | | | | | identit\
\yref
| | | | | | | +--rw public-key
| | | | | | | binary
| | | | | | +--:(truststore)
| | | | | | {truststore-sup\
\ported,public-keys}?
| | | | | | +--rw truststore-refe\
\rence?
| | | | | | ts:public-key\
\-bag-ref
| | | | | +--rw psks! {psk-auth}?
| | | | +--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 peer-allowed-to-send?
| | | | | empty
| | | | +--rw test-peer-aliveness!
| | | | +--rw max-wait? uint16
| | | | +--rw max-attempts? uint8
| | | +--rw http-client-parameters
| | | +--rw client-identity!
| | | +--rw (auth-type)?
| | | +--:(basic)
| | | +--rw basic {basic-auth}?
| | | +--rw user-id
| | | | string
| | | +--rw password
| | | string
| | +--rw restconf-client-parameters
| +--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! {http-listen or https-listen}?
+--rw idle-timeout? uint16
+--rw endpoint* [name]
+--rw name string
+--rw (transport)
+--:(http) {http-listen}?
| +--rw http
| +--rw tcp-server-parameters
| | +--rw local-address inet:ip-address
| | +--rw local-port? inet:port-number
| | +--rw keepalives! {keepalives-supported}?
| | +--rw idle-time uint16
| | +--rw max-probes uint16
| | +--rw probe-interval uint16
| +--rw http-client-parameters
| | +--rw client-identity!
| | | +--rw (auth-type)?
| | | +--:(basic)
| | | +--rw basic {basic-auth}?
| | | +--rw user-id string
| | | +--rw password string
| | +--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
| | | | {local-binding-supported}?
| | | +--rw local-port? inet:port-number
| | | | {local-binding-supported}?
| | | +--rw keepalives!
| | | {keepalives-supported}?
| | | +--rw idle-time uint16
| | | +--rw max-probes uint16
| | | +--rw probe-interval uint16
| | +--rw tls-client-parameters
| | | +--rw client-identity
| | | | +--rw (auth-type)?
| | | | +--:(certificate)
| | | | | {x509-certificate-auth}?
| | | | | +--rw certificate
| | | | | +--rw (local-or-keystore)
| | | | | +--:(local)
| | | | | | {local-definiti\
\ons-supported}?
| | | | | | +--rw local-definition
| | | | | | +--rw public-key-f\
\ormat
| | | | | | | identityref
| | | | | | +--rw public-key
| | | | | | | binary
| | | | | | +--rw private-key-\
\format?
| | | | | | | identityref
| | | | | | +--rw (private-key\
\-type)
| | | | | | | +--:(private-ke\
\y)
| | | | | | | | +--rw privat\
\e-key?
| | | | | | | | bina\
\ry
| | | | | | | +--:(hidden-pri\
\vate-key)
| | | | | | | | +--rw hidden\
\-private-key?
| | | | | | | | empty
| | | | | | | +--:(encrypted-\
\private-key)
| | | | | | | +--rw encryp\
\ted-private-key
| | | | | | | +--rw (ke\
\y-type)
| | | | | | | | +--:(s\
\ymmetric-key-ref)
| | | | | | | | | +--\
\rw symmetric-key-ref? leafref
| | | | | | | | | \
\ {keystore-supported}?
| | | | | | | | +--:(a\
\symmetric-key-ref)
| | | | | | | | +--\
\rw asymmetric-key-ref? leafref
| | | | | | | | \
\ {keystore-supported}?
| | | | | | | +--rw val\
\ue?
| | | | | | | b\
\inary
| | | | | | +--rw cert?
| | | | | | | end-entity\
\-cert-cms
| | | | | | +---n certificate-\
\expiration
| | | | | | | +-- expiration-\
\date
| | | | | | | yang:da\
\te-and-time
| | | | | | +---x generate-cer\
\tificate-signing-request
| | | | | | {certifica\
\te-signing-request-generation}?
| | | | | | +---w input
| | | | | | | +---w subject
| | | | | | | | bina\
\ry
| | | | | | | +---w attrib\
\utes?
| | | | | | | bina\
\ry
| | | | | | +--ro output
| | | | | | +--ro certif\
\icate-signing-request
| | | | | | ct:c\
\sr
| | | | | +--:(keystore)
| | | | | {keystore-suppo\
\rted}?
| | | | | +--rw keystore-refere\
\nce
| | | | | +--rw asymmetric-k\
\ey?
| | | | | | ks:asymmet\
\ric-key-ref
| | | | | +--rw certificate?\
\ leafref
| | | | +--:(raw-public-key)
| | | | | {raw-public-key-auth}?
| | | | | +--rw raw-private-key
| | | | | +--rw (local-or-keystore)
| | | | | +--:(local)
| | | | | | {local-definiti\
\ons-supported}?
| | | | | | +--rw local-definition
| | | | | | +--rw public-key-f\
\ormat
| | | | | | | identityref
| | | | | | +--rw public-key
| | | | | | | binary
| | | | | | +--rw private-key-\
\format?
| | | | | | | identityref
| | | | | | +--rw (private-key\
\-type)
| | | | | | +--:(private-ke\
\y)
| | | | | | | +--rw privat\
\e-key?
| | | | | | | bina\
\ry
| | | | | | +--:(hidden-pri\
\vate-key)
| | | | | | | +--rw hidden\
\-private-key?
| | | | | | | empty
| | | | | | +--:(encrypted-\
\private-key)
| | | | | | +--rw encryp\
\ted-private-key
| | | | | | +--rw (ke\
\y-type)
| | | | | | | +--:(s\
\ymmetric-key-ref)
| | | | | | | | +--\
\rw symmetric-key-ref? leafref
| | | | | | | | \
\ {keystore-supported}?
| | | | | | | +--:(a\
\symmetric-key-ref)
| | | | | | | +--\
\rw asymmetric-key-ref? leafref
| | | | | | | \
\ {keystore-supported}?
| | | | | | +--rw val\
\ue?
| | | | | | b\
\inary
| | | | | +--:(keystore)
| | | | | {keystore-suppo\
\rted}?
| | | | | +--rw keystore-refere\
\nce?
| | | | | ks:asymmetric\
\-key-ref
| | | | +--:(psk) {psk-auth}?
| | | | +--rw psk
| | | | +--rw (local-or-keystore)
| | | | +--:(local)
| | | | | {local-definiti\
\ons-supported}?
| | | | | +--rw local-definition
| | | | | +--rw key-format?
| | | | | | identityref
| | | | | +--rw (key-type)
| | | | | | +--:(key)
| | | | | | | +--rw key?
| | | | | | | bina\
\ry
| | | | | | +--:(hidden-key)
| | | | | | | +--rw hidden\
\-key?
| | | | | | | empty
| | | | | | +--:(encrypted-\
\key)
| | | | | | +--rw encryp\
\ted-key
| | | | | | +--rw (ke\
\y-type)
| | | | | | | +--:(s\
\ymmetric-key-ref)
| | | | | | | | +--\
\rw symmetric-key-ref? leafref
| | | | | | | | \
\ {keystore-supported}?
| | | | | | | +--:(a\
\symmetric-key-ref)
| | | | | | | +--\
\rw asymmetric-key-ref? leafref
| | | | | | | \
\ {keystore-supported}?
| | | | | | +--rw val\
\ue?
| | | | | | b\
\inary
| | | | | +--rw id?
| | | | | string
| | | | | {ks:local-\
\definitions-supported}?
| | | | +--:(keystore)
| | | | {keystore-suppo\
\rted}?
| | | | +--rw keystore-refere\
\nce?
| | | | ks:symmetric-\
\key-ref
| | | +--rw server-authentication
| | | | +--rw ca-certs!
| | | | | {x509-certificate-auth}?
| | | | | +--rw (local-or-truststore)
| | | | | +--:(local)
| | | | | | {local-definitions-su\
\pported}?
| | | | | | +--rw local-definition
| | | | | | +--rw cert*
| | | | | | | trust-anchor-cer\
\t-cms
| | | | | | +---n certificate-expira\
\tion
| | | | | | +-- expiration-date
| | | | | | yang:date-and\
\-time
| | | | | +--:(truststore)
| | | | | {truststore-supported\
\,certificates}?
| | | | | +--rw truststore-reference?
| | | | | ts:certificate-bag-\
\ref
| | | | +--rw ee-certs!
| | | | | {x509-certificate-auth}?
| | | | | +--rw (local-or-truststore)
| | | | | +--:(local)
| | | | | | {local-definitions-su\
\pported}?
| | | | | | +--rw local-definition
| | | | | | +--rw cert*
| | | | | | | trust-anchor-cer\
\t-cms
| | | | | | +---n certificate-expira\
\tion
| | | | | | +-- expiration-date
| | | | | | yang:date-and\
\-time
| | | | | +--:(truststore)
| | | | | {truststore-supported\
\,certificates}?
| | | | | +--rw truststore-reference?
| | | | | ts:certificate-bag-\
\ref
| | | | +--rw raw-public-keys!
| | | | | {raw-public-key-auth}?
| | | | | +--rw (local-or-truststore)
| | | | | +--:(local)
| | | | | | {local-definitions-su\
\pported}?
| | | | | | +--rw local-definition
| | | | | | +--rw public-key* [name]
| | | | | | +--rw name
| | | | | | | string
| | | | | | +--rw public-key-form\
\at
| | | | | | | identityref
| | | | | | +--rw public-key
| | | | | | binary
| | | | | +--:(truststore)
| | | | | {truststore-supported\
\,public-keys}?
| | | | | +--rw truststore-reference?
| | | | | ts:public-key-bag-r\
\ef
| | | | +--rw psks! {psk-auth}?
| | | +--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 peer-allowed-to-send? empty
| | | +--rw test-peer-aliveness!
| | | +--rw max-wait? uint16
| | | +--rw max-attempts? uint8
| | +--rw http-client-parameters
| | +--rw client-identity!
| | +--rw (auth-type)?
| | +--:(basic)
| | +--rw basic {basic-auth}?
| | +--rw user-id string
| | +--rw password string
| +--rw restconf-client-parameters
+--:(https) {https-listen}?
+--rw https
+--rw tcp-server-parameters
| +--rw local-address inet:ip-address
| +--rw local-port? inet:port-number
| +--rw keepalives! {keepalives-supported}?
| +--rw idle-time uint16
| +--rw max-probes uint16
| +--rw probe-interval uint16
+--rw tls-client-parameters
| +--rw client-identity
| | +--rw (auth-type)?
| | +--:(certificate)
| | | {x509-certificate-auth}?
| | | +--rw certificate
| | | +--rw (local-or-keystore)
| | | +--:(local)
| | | | {local-definitions-su\
\pported}?
| | | | +--rw local-definition
| | | | +--rw public-key-format
| | | | | identityref
| | | | +--rw public-key
| | | | | binary
| | | | +--rw private-key-format?
| | | | | identityref
| | | | +--rw (private-key-type)
| | | | | +--:(private-key)
| | | | | | +--rw private-key?
| | | | | | binary
| | | | | +--:(hidden-private-k\
\ey)
| | | | | | +--rw hidden-priva\
\te-key?
| | | | | | empty
| | | | | +--:(encrypted-privat\
\e-key)
| | | | | +--rw encrypted-pr\
\ivate-key
| | | | | +--rw (key-type)
| | | | | | +--:(symmetr\
\ic-key-ref)
| | | | | | | +--rw sym\
\metric-key-ref? leafref
| | | | | | | {\
\keystore-supported}?
| | | | | | +--:(asymmet\
\ric-key-ref)
| | | | | | +--rw asy\
\mmetric-key-ref? leafref
| | | | | | {\
\keystore-supported}?
| | | | | +--rw value?
| | | | | binary
| | | | +--rw cert?
| | | | | end-entity-cert-\
\cms
| | | | +---n certificate-expira\
\tion
| | | | | +-- expiration-date
| | | | | yang:date-and\
\-time
| | | | +---x generate-certifica\
\te-signing-request
| | | | {certificate-sig\
\ning-request-generation}?
| | | | +---w input
| | | | | +---w subject
| | | | | | binary
| | | | | +---w attributes?
| | | | | binary
| | | | +--ro output
| | | | +--ro certificate-\
\signing-request
| | | | ct:csr
| | | +--:(keystore)
| | | {keystore-supported}?
| | | +--rw keystore-reference
| | | +--rw asymmetric-key?
| | | | ks:asymmetric-ke\
\y-ref
| | | +--rw certificate? \
\leafref
| | +--:(raw-public-key)
| | | {raw-public-key-auth}?
| | | +--rw raw-private-key
| | | +--rw (local-or-keystore)
| | | +--:(local)
| | | | {local-definitions-su\
\pported}?
| | | | +--rw local-definition
| | | | +--rw public-key-format
| | | | | identityref
| | | | +--rw public-key
| | | | | binary
| | | | +--rw private-key-format?
| | | | | identityref
| | | | +--rw (private-key-type)
| | | | +--:(private-key)
| | | | | +--rw private-key?
| | | | | binary
| | | | +--:(hidden-private-k\
\ey)
| | | | | +--rw hidden-priva\
\te-key?
| | | | | empty
| | | | +--:(encrypted-privat\
\e-key)
| | | | +--rw encrypted-pr\
\ivate-key
| | | | +--rw (key-type)
| | | | | +--:(symmetr\
\ic-key-ref)
| | | | | | +--rw sym\
\metric-key-ref? leafref
| | | | | | {\
\keystore-supported}?
| | | | | +--:(asymmet\
\ric-key-ref)
| | | | | +--rw asy\
\mmetric-key-ref? leafref
| | | | | {\
\keystore-supported}?
| | | | +--rw value?
| | | | binary
| | | +--:(keystore)
| | | {keystore-supported}?
| | | +--rw keystore-reference?
| | | ks:asymmetric-key-r\
\ef
| | +--:(psk) {psk-auth}?
| | +--rw psk
| | +--rw (local-or-keystore)
| | +--:(local)
| | | {local-definitions-su\
\pported}?
| | | +--rw local-definition
| | | +--rw key-format?
| | | | identityref
| | | +--rw (key-type)
| | | | +--:(key)
| | | | | +--rw key?
| | | | | binary
| | | | +--:(hidden-key)
| | | | | +--rw hidden-key?
| | | | | empty
| | | | +--:(encrypted-key)
| | | | +--rw encrypted-key
| | | | +--rw (key-type)
| | | | | +--:(symmetr\
\ic-key-ref)
| | | | | | +--rw sym\
\metric-key-ref? leafref
| | | | | | {\
\keystore-supported}?
| | | | | +--:(asymmet\
\ric-key-ref)
| | | | | +--rw asy\
\mmetric-key-ref? leafref
| | | | | {\
\keystore-supported}?
| | | | +--rw value?
| | | | binary
| | | +--rw id?
| | | string
| | | {ks:local-defini\
\tions-supported}?
| | +--:(keystore)
| | {keystore-supported}?
| | +--rw keystore-reference?
| | ks:symmetric-key-ref
| +--rw server-authentication
| | +--rw ca-certs! {x509-certificate-auth}?
| | | +--rw (local-or-truststore)
| | | +--:(local)
| | | | {local-definitions-supporte\
\d}?
| | | | +--rw local-definition
| | | | +--rw cert*
| | | | | trust-anchor-cert-cms
| | | | +---n certificate-expiration
| | | | +-- expiration-date
| | | | yang:date-and-time
| | | +--:(truststore)
| | | {truststore-supported,certi\
\ficates}?
| | | +--rw truststore-reference?
| | | ts:certificate-bag-ref
| | +--rw ee-certs! {x509-certificate-auth}?
| | | +--rw (local-or-truststore)
| | | +--:(local)
| | | | {local-definitions-supporte\
\d}?
| | | | +--rw local-definition
| | | | +--rw cert*
| | | | | trust-anchor-cert-cms
| | | | +---n certificate-expiration
| | | | +-- expiration-date
| | | | yang:date-and-time
| | | +--:(truststore)
| | | {truststore-supported,certi\
\ficates}?
| | | +--rw truststore-reference?
| | | ts:certificate-bag-ref
| | +--rw raw-public-keys!
| | | {raw-public-key-auth}?
| | | +--rw (local-or-truststore)
| | | +--:(local)
| | | | {local-definitions-supporte\
\d}?
| | | | +--rw local-definition
| | | | +--rw public-key* [name]
| | | | +--rw name
| | | | | string
| | | | +--rw public-key-format
| | | | | identityref
| | | | +--rw public-key
| | | | binary
| | | +--:(truststore)
| | | {truststore-supported,publi\
\c-keys}?
| | | +--rw truststore-reference?
| | | ts:public-key-bag-ref
| | +--rw psks! {psk-auth}?
| +--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 peer-allowed-to-send? empty
| +--rw test-peer-aliveness!
| +--rw max-wait? uint16
| +--rw max-attempts? uint8
+--rw http-client-parameters
| +--rw client-identity!
| | +--rw (auth-type)?
| | +--:(basic)
| | +--rw basic {basic-auth}?
| | +--rw user-id string
| | +--rw password string
| +--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
| | | {local-binding-supported}?
| | +--rw local-port? inet:port-number
| | | {local-binding-supported}?
| | +--rw keepalives!
| | {keepalives-supported}?
| | +--rw idle-time uint16
| | +--rw max-probes uint16
| | +--rw probe-interval uint16
| +--rw tls-client-parameters
| | +--rw client-identity
| | | +--rw (auth-type)?
| | | +--:(certificate)
| | | | {x509-certificate-auth}?
| | | | +--rw certificate
| | | | +--rw (local-or-keystore)
| | | | +--:(local)
| | | | | {local-definiti\
\ons-supported}?
| | | | | +--rw local-definition
| | | | | +--rw public-key-f\
\ormat
| | | | | | identityref
| | | | | +--rw public-key
| | | | | | binary
| | | | | +--rw private-key-\
\format?
| | | | | | identityref
| | | | | +--rw (private-key\
\-type)
| | | | | | +--:(private-ke\
\y)
| | | | | | | +--rw privat\
\e-key?
| | | | | | | bina\
\ry
| | | | | | +--:(hidden-pri\
\vate-key)
| | | | | | | +--rw hidden\
\-private-key?
| | | | | | | empty
| | | | | | +--:(encrypted-\
\private-key)
| | | | | | +--rw encryp\
\ted-private-key
| | | | | | +--rw (ke\
\y-type)
| | | | | | | +--:(s\
\ymmetric-key-ref)
| | | | | | | | +--\
\rw symmetric-key-ref? leafref
| | | | | | | | \
\ {keystore-supported}?
| | | | | | | +--:(a\
\symmetric-key-ref)
| | | | | | | +--\
\rw asymmetric-key-ref? leafref
| | | | | | | \
\ {keystore-supported}?
| | | | | | +--rw val\
\ue?
| | | | | | b\
\inary
| | | | | +--rw cert?
| | | | | | end-entity\
\-cert-cms
| | | | | +---n certificate-\
\expiration
| | | | | | +-- expiration-\
\date
| | | | | | yang:da\
\te-and-time
| | | | | +---x generate-cer\
\tificate-signing-request
| | | | | {certifica\
\te-signing-request-generation}?
| | | | | +---w input
| | | | | | +---w subject
| | | | | | | bina\
\ry
| | | | | | +---w attrib\
\utes?
| | | | | | bina\
\ry
| | | | | +--ro output
| | | | | +--ro certif\
\icate-signing-request
| | | | | ct:c\
\sr
| | | | +--:(keystore)
| | | | {keystore-suppo\
\rted}?
| | | | +--rw keystore-refere\
\nce
| | | | +--rw asymmetric-k\
\ey?
| | | | | ks:asymmet\
\ric-key-ref
| | | | +--rw certificate?\
\ leafref
| | | +--:(raw-public-key)
| | | | {raw-public-key-auth}?
| | | | +--rw raw-private-key
| | | | +--rw (local-or-keystore)
| | | | +--:(local)
| | | | | {local-definiti\
\ons-supported}?
| | | | | +--rw local-definition
| | | | | +--rw public-key-f\
\ormat
| | | | | | identityref
| | | | | +--rw public-key
| | | | | | binary
| | | | | +--rw private-key-\
\format?
| | | | | | identityref
| | | | | +--rw (private-key\
\-type)
| | | | | +--:(private-ke\
\y)
| | | | | | +--rw privat\
\e-key?
| | | | | | bina\
\ry
| | | | | +--:(hidden-pri\
\vate-key)
| | | | | | +--rw hidden\
\-private-key?
| | | | | | empty
| | | | | +--:(encrypted-\
\private-key)
| | | | | +--rw encryp\
\ted-private-key
| | | | | +--rw (ke\
\y-type)
| | | | | | +--:(s\
\ymmetric-key-ref)
| | | | | | | +--\
\rw symmetric-key-ref? leafref
| | | | | | | \
\ {keystore-supported}?
| | | | | | +--:(a\
\symmetric-key-ref)
| | | | | | +--\
\rw asymmetric-key-ref? leafref
| | | | | | \
\ {keystore-supported}?
| | | | | +--rw val\
\ue?
| | | | | b\
\inary
| | | | +--:(keystore)
| | | | {keystore-suppo\
\rted}?
| | | | +--rw keystore-refere\
\nce?
| | | | ks:asymmetric\
\-key-ref
| | | +--:(psk) {psk-auth}?
| | | +--rw psk
| | | +--rw (local-or-keystore)
| | | +--:(local)
| | | | {local-definiti\
\ons-supported}?
| | | | +--rw local-definition
| | | | +--rw key-format?
| | | | | identityref
| | | | +--rw (key-type)
| | | | | +--:(key)
| | | | | | +--rw key?
| | | | | | bina\
\ry
| | | | | +--:(hidden-key)
| | | | | | +--rw hidden\
\-key?
| | | | | | empty
| | | | | +--:(encrypted-\
\key)
| | | | | +--rw encryp\
\ted-key
| | | | | +--rw (ke\
\y-type)
| | | | | | +--:(s\
\ymmetric-key-ref)
| | | | | | | +--\
\rw symmetric-key-ref? leafref
| | | | | | | \
\ {keystore-supported}?
| | | | | | +--:(a\
\symmetric-key-ref)
| | | | | | +--\
\rw asymmetric-key-ref? leafref
| | | | | | \
\ {keystore-supported}?
| | | | | +--rw val\
\ue?
| | | | | b\
\inary
| | | | +--rw id?
| | | | string
| | | | {ks:local-\
\definitions-supported}?
| | | +--:(keystore)
| | | {keystore-suppo\
\rted}?
| | | +--rw keystore-refere\
\nce?
| | | ks:symmetric-\
\key-ref
| | +--rw server-authentication
| | | +--rw ca-certs!
| | | | {x509-certificate-auth}?
| | | | +--rw (local-or-truststore)
| | | | +--:(local)
| | | | | {local-definitions-su\
\pported}?
| | | | | +--rw local-definition
| | | | | +--rw cert*
| | | | | | trust-anchor-cer\
\t-cms
| | | | | +---n certificate-expira\
\tion
| | | | | +-- expiration-date
| | | | | yang:date-and\
\-time
| | | | +--:(truststore)
| | | | {truststore-supported\
\,certificates}?
| | | | +--rw truststore-reference?
| | | | ts:certificate-bag-\
\ref
| | | +--rw ee-certs!
| | | | {x509-certificate-auth}?
| | | | +--rw (local-or-truststore)
| | | | +--:(local)
| | | | | {local-definitions-su\
\pported}?
| | | | | +--rw local-definition
| | | | | +--rw cert*
| | | | | | trust-anchor-cer\
\t-cms
| | | | | +---n certificate-expira\
\tion
| | | | | +-- expiration-date
| | | | | yang:date-and\
\-time
| | | | +--:(truststore)
| | | | {truststore-supported\
\,certificates}?
| | | | +--rw truststore-reference?
| | | | ts:certificate-bag-\
\ref
| | | +--rw raw-public-keys!
| | | | {raw-public-key-auth}?
| | | | +--rw (local-or-truststore)
| | | | +--:(local)
| | | | | {local-definitions-su\
\pported}?
| | | | | +--rw local-definition
| | | | | +--rw public-key* [name]
| | | | | +--rw name
| | | | | | string
| | | | | +--rw public-key-form\
\at
| | | | | | identityref
| | | | | +--rw public-key
| | | | | binary
| | | | +--:(truststore)
| | | | {truststore-supported\
\,public-keys}?
| | | | +--rw truststore-reference?
| | | | ts:public-key-bag-r\
\ef
| | | +--rw psks! {psk-auth}?
| | +--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 peer-allowed-to-send? empty
| | +--rw test-peer-aliveness!
| | +--rw max-wait? uint16
| | +--rw max-attempts? uint8
| +--rw http-client-parameters
| +--rw client-identity!
| +--rw (auth-type)?
| +--:(basic)
| +--rw basic {basic-auth}?
| +--rw user-id string
| +--rw password string
+--rw restconf-client-parameters
A.2. Expanded Tree Diagram for 'ietf-restconf-server' A.2. Expanded Tree Diagram for 'ietf-restconf-server'
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. model for the "ietf-restconf-server" module.
This tree diagram shows all the nodes defined in this module, This tree diagram shows all the nodes defined in this module,
including those defined by "grouping" statements used by 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 Please see Section 3.1 for a tree diagram that illustrates what the
module looks like without all the "grouping" statements expanded. module looks like without all the "grouping" statements expanded.
========== NOTE: '\\' line wrapping per BCP XXX (RFC XXXX) ========== XNSERT_TEXT_FROM_FILE(refs/ietf-restconf-server-tree.txt)
module: ietf-restconf-server
+--rw restconf-server
+--rw listen! {http-listen or https-listen}?
| +--rw endpoint* [name]
| +--rw name string
| +--rw (transport)
| +--:(http) {http-listen}?
| | +--rw http
| | +--rw external-endpoint!
| | | +--rw address inet:ip-address
| | | +--rw port? inet:port-number
| | +--rw tcp-server-parameters
| | | +--rw local-address inet:ip-address
| | | +--rw local-port? inet:port-number
| | | +--rw keepalives! {keepalives-supported}?
| | | +--rw idle-time uint16
| | | +--rw max-probes uint16
| | | +--rw probe-interval uint16
| | +--rw http-server-parameters
| | | +--rw server-name? string
| | | +--rw client-authentication!
| | | {client-auth-config-supported}?
| | | +--rw users
| | | +--rw user* [user-id]
| | | +--rw user-id string
| | | +--rw (auth-type)?
| | | +--:(basic)
| | | +--rw basic {basic-auth}?
| | | +--rw user-id? string
| | | +--rw password?
| | | ianach:crypt-hash
| | +--rw restconf-server-parameters
| | +--rw client-identity-mappings
| | +--rw cert-to-name* [id]
| | +--rw id uint32
| | +--rw fingerprint?
| | | x509c2n:tls-fingerprint
| | +--rw map-type identityref
| | +--rw name string
| +--:(https) {https-listen}?
| +--rw https
| +--rw tcp-server-parameters
| | +--rw local-address inet:ip-address
| | +--rw local-port? inet:port-number
| | +--rw keepalives! {keepalives-supported}?
| | +--rw idle-time uint16
| | +--rw max-probes uint16
| | +--rw probe-interval uint16
| +--rw tls-server-parameters
| | +--rw server-identity
| | | +--rw (auth-type)
| | | +--:(certificate)
| | | | {x509-certificate-auth}?
| | | | +--rw certificate
| | | | +--rw (local-or-keystore)
| | | | +--:(local)
| | | | | {local-definitions-su\
\pported}?
| | | | | +--rw local-definition
| | | | | +--rw public-key-format
| | | | | | identityref
| | | | | +--rw public-key
| | | | | | binary
| | | | | +--rw private-key-format?
| | | | | | identityref
| | | | | +--rw (private-key-type)
| | | | | | +--:(private-key)
| | | | | | | +--rw private-key?
| | | | | | | binary
| | | | | | +--:(hidden-private-k\
\ey)
| | | | | | | +--rw hidden-priva\
\te-key?
| | | | | | | empty
| | | | | | +--:(encrypted-privat\
\e-key)
| | | | | | +--rw encrypted-pr\
\ivate-key
| | | | | | +--rw (key-type)
| | | | | | | +--:(symmetr\
\ic-key-ref)
| | | | | | | | +--rw sym\
\metric-key-ref? leafref
| | | | | | | | {\
\keystore-supported}?
| | | | | | | +--:(asymmet\
\ric-key-ref)
| | | | | | | +--rw asy\
\mmetric-key-ref? leafref
| | | | | | | {\
\keystore-supported}?
| | | | | | +--rw value?
| | | | | | binary
| | | | | +--rw cert?
| | | | | | end-entity-cert-\
\cms
| | | | | +---n certificate-expira\
\tion
| | | | | | +-- expiration-date
| | | | | | yang:date-and\
\-time
| | | | | +---x generate-certifica\
\te-signing-request
| | | | | {certificate-sig\
\ning-request-generation}?
| | | | | +---w input
| | | | | | +---w subject
| | | | | | | binary
| | | | | | +---w attributes?
| | | | | | binary
| | | | | +--ro output
| | | | | +--ro certificate-\
\signing-request
| | | | | ct:csr
| | | | +--:(keystore)
| | | | {keystore-supported}?
| | | | +--rw keystore-reference
| | | | +--rw asymmetric-key?
| | | | | ks:asymmetric-ke\
\y-ref
| | | | +--rw certificate? \
\leafref
| | | +--:(raw-private-key)
| | | | {raw-public-key-auth}?
| | | | +--rw raw-private-key
| | | | +--rw (local-or-keystore)
| | | | +--:(local)
| | | | | {local-definitions-su\
\pported}?
| | | | | +--rw local-definition
| | | | | +--rw public-key-format
| | | | | | identityref
| | | | | +--rw public-key
| | | | | | binary
| | | | | +--rw private-key-format?
| | | | | | identityref
| | | | | +--rw (private-key-type)
| | | | | +--:(private-key)
| | | | | | +--rw private-key?
| | | | | | binary
| | | | | +--:(hidden-private-k\
\ey)
| | | | | | +--rw hidden-priva\
\te-key?
| | | | | | empty
| | | | | +--:(encrypted-privat\
\e-key)
| | | | | +--rw encrypted-pr\
\ivate-key
| | | | | +--rw (key-type)
| | | | | | +--:(symmetr\
\ic-key-ref)
| | | | | | | +--rw sym\
\metric-key-ref? leafref
| | | | | | | {\
\keystore-supported}?
| | | | | | +--:(asymmet\
\ric-key-ref)
| | | | | | +--rw asy\
\mmetric-key-ref? leafref
| | | | | | {\
\keystore-supported}?
| | | | | +--rw value?
| | | | | binary
| | | | +--:(keystore)
| | | | {keystore-supported}?
| | | | +--rw keystore-reference?
| | | | ks:asymmetric-key-r\
\ef
| | | +--:(psk) {psk-auth}?
| | | +--rw psk
| | | +--rw (local-or-keystore)
| | | +--:(local)
| | | | {local-definitions-su\
\pported}?
| | | | +--rw local-definition
| | | | +--rw key-format?
| | | | | identityref
| | | | +--rw (key-type)
| | | | | +--:(key)
| | | | | | +--rw key?
| | | | | | binary
| | | | | +--:(hidden-key)
| | | | | | +--rw hidden-key?
| | | | | | empty
| | | | | +--:(encrypted-key)
| | | | | +--rw encrypted-key
| | | | | +--rw (key-type)
| | | | | | +--:(symmetr\
\ic-key-ref)
| | | | | | | +--rw sym\
\metric-key-ref? leafref
| | | | | | | {\
\keystore-supported}?
| | | | | | +--:(asymmet\
\ric-key-ref)
| | | | | | +--rw asy\
\mmetric-key-ref? leafref
| | | | | | {\
\keystore-supported}?
| | | | | +--rw value?
| | | | | binary
| | | | +--rw id?
| | | | string
| | | | {ks:local-defini\
\tions-supported}?
| | | +--:(keystore)
| | | {keystore-supported}?
| | | +--rw keystore-reference?
| | | ks:symmetric-key-ref
| | +--rw client-authentication!
| | | {client-auth-config-supported}?
| | | +--rw ca-certs! {x509-certificate-auth}?
| | | | +--rw (local-or-truststore)
| | | | +--:(local)
| | | | | {local-definitions-supporte\
\d}?
| | | | | +--rw local-definition
| | | | | +--rw cert*
| | | | | | trust-anchor-cert-cms
| | | | | +---n certificate-expiration
| | | | | +-- expiration-date
| | | | | yang:date-and-time
| | | | +--:(truststore)
| | | | {truststore-supported,certi\
\ficates}?
| | | | +--rw truststore-reference?
| | | | ts:certificate-bag-ref
| | | +--rw ee-certs! {x509-certificate-auth}?
| | | | +--rw (local-or-truststore)
| | | | +--:(local)
| | | | | {local-definitions-supporte\
\d}?
| | | | | +--rw local-definition
| | | | | +--rw cert*
| | | | | | trust-anchor-cert-cms
| | | | | +---n certificate-expiration
| | | | | +-- expiration-date
| | | | | yang:date-and-time
| | | | +--:(truststore)
| | | | {truststore-supported,certi\
\ficates}?
| | | | +--rw truststore-reference?
| | | | ts:certificate-bag-ref
| | | +--rw raw-public-keys!
| | | | {raw-public-key-auth}?
| | | | +--rw (local-or-truststore)
| | | | +--:(local)
| | | | | {local-definitions-supporte\
\d}?
| | | | | +--rw local-definition
| | | | | +--rw public-key* [name]
| | | | | +--rw name
| | | | | | string
| | | | | +--rw public-key-format
| | | | | | identityref
| | | | | +--rw public-key
| | | | | binary
| | | | +--:(truststore)
| | | | {truststore-supported,publi\
\c-keys}?
| | | | +--rw truststore-reference?
| | | | ts:public-key-bag-ref
| | | +--rw psks! {psk-auth}?
| | +--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 peer-allowed-to-send? empty
| | +--rw test-peer-aliveness!
| | +--rw max-wait? uint16
| | +--rw max-attempts? uint8
| +--rw http-server-parameters
| | +--rw server-name? string
| | +--rw client-authentication!
| | {client-auth-config-supported}?
| | +--rw users
| | +--rw user* [user-id]
| | +--rw user-id string
| | +--rw (auth-type)?
| | +--:(basic)
| | +--rw basic {basic-auth}?
| | +--rw user-id? string
| | +--rw password?
| | ianach:crypt-hash
| +--rw restconf-server-parameters
| +--rw client-identity-mappings
| +--rw cert-to-name* [id]
| +--rw id uint32
| +--rw fingerprint?
| | x509c2n:tls-fingerprint
| +--rw map-type identityref
| +--rw name string
+--rw call-home! {https-call-home}?
+--rw restconf-client* [name]
+--rw name string
+--rw endpoints
| +--rw endpoint* [name]
| +--rw name string
| +--rw (transport)
| +--:(https) {https-listen}?
| +--rw https
| +--rw tcp-client-parameters
| | +--rw remote-address inet:host
| | +--rw remote-port? inet:port-number
| | +--rw local-address? inet:ip-address
| | | {local-binding-supported}?
| | +--rw local-port? inet:port-number
| | | {local-binding-supported}?
| | +--rw keepalives!
| | {keepalives-supported}?
| | +--rw idle-time uint16
| | +--rw max-probes uint16
| | +--rw probe-interval uint16
| +--rw tls-server-parameters
| | +--rw server-identity
| | | +--rw (auth-type)
| | | +--:(certificate)
| | | | {x509-certificate-auth}?
| | | | +--rw certificate
| | | | +--rw (local-or-keystore)
| | | | +--:(local)
| | | | | {local-definiti\
\ons-supported}?
| | | | | +--rw local-definition
| | | | | +--rw public-key-f\
\ormat
| | | | | | identityref
| | | | | +--rw public-key
| | | | | | binary
| | | | | +--rw private-key-\
\format?
| | | | | | identityref
| | | | | +--rw (private-key\
\-type)
| | | | | | +--:(private-ke\
\y)
| | | | | | | +--rw privat\
\e-key?
| | | | | | | bina\
\ry
| | | | | | +--:(hidden-pri\
\vate-key)
| | | | | | | +--rw hidden\
\-private-key?
| | | | | | | empty
| | | | | | +--:(encrypted-\
\private-key)
| | | | | | +--rw encryp\
\ted-private-key
| | | | | | +--rw (ke\
\y-type)
| | | | | | | +--:(s\
\ymmetric-key-ref)
| | | | | | | | +--\
\rw symmetric-key-ref? leafref
| | | | | | | | \
\ {keystore-supported}?
| | | | | | | +--:(a\
\symmetric-key-ref)
| | | | | | | +--\
\rw asymmetric-key-ref? leafref
| | | | | | | \
\ {keystore-supported}?
| | | | | | +--rw val\
\ue?
| | | | | | b\
\inary
| | | | | +--rw cert?
| | | | | | end-entity\
\-cert-cms
| | | | | +---n certificate-\
\expiration
| | | | | | +-- expiration-\
\date
| | | | | | yang:da\
\te-and-time
| | | | | +---x generate-cer\
\tificate-signing-request
| | | | | {certifica\
\te-signing-request-generation}?
| | | | | +---w input
| | | | | | +---w subject
| | | | | | | bina\
\ry
| | | | | | +---w attrib\
\utes?
| | | | | | bina\
\ry
| | | | | +--ro output
| | | | | +--ro certif\
\icate-signing-request
| | | | | ct:c\
\sr
| | | | +--:(keystore)
| | | | {keystore-suppo\
\rted}?
| | | | +--rw keystore-refere\
\nce
| | | | +--rw asymmetric-k\
\ey?
| | | | | ks:asymmet\
\ric-key-ref
| | | | +--rw certificate?\
\ leafref
| | | +--:(raw-private-key)
| | | | {raw-public-key-auth}?
| | | | +--rw raw-private-key
| | | | +--rw (local-or-keystore)
| | | | +--:(local)
| | | | | {local-definiti\
\ons-supported}?
| | | | | +--rw local-definition
| | | | | +--rw public-key-f\
\ormat
| | | | | | identityref
| | | | | +--rw public-key
| | | | | | binary
| | | | | +--rw private-key-\
\format?
| | | | | | identityref
| | | | | +--rw (private-key\
\-type)
| | | | | +--:(private-ke\
\y)
| | | | | | +--rw privat\
\e-key?
| | | | | | bina\
\ry
| | | | | +--:(hidden-pri\
\vate-key)
| | | | | | +--rw hidden\
\-private-key?
| | | | | | empty
| | | | | +--:(encrypted-\
\private-key)
| | | | | +--rw encryp\
\ted-private-key
| | | | | +--rw (ke\
\y-type)
| | | | | | +--:(s\
\ymmetric-key-ref)
| | | | | | | +--\
\rw symmetric-key-ref? leafref
| | | | | | | \
\ {keystore-supported}?
| | | | | | +--:(a\
\symmetric-key-ref)
| | | | | | +--\
\rw asymmetric-key-ref? leafref
| | | | | | \
\ {keystore-supported}?
| | | | | +--rw val\
\ue?
| | | | | b\
\inary
| | | | +--:(keystore)
| | | | {keystore-suppo\
\rted}?
| | | | +--rw keystore-refere\
\nce?
| | | | ks:asymmetric\
\-key-ref
| | | +--:(psk) {psk-auth}?
| | | +--rw psk
| | | +--rw (local-or-keystore)
| | | +--:(local)
| | | | {local-definiti\
\ons-supported}?
| | | | +--rw local-definition
| | | | +--rw key-format?
| | | | | identityref
| | | | +--rw (key-type)
| | | | | +--:(key)
| | | | | | +--rw key?
| | | | | | bina\
\ry
| | | | | +--:(hidden-key)
| | | | | | +--rw hidden\
\-key?
| | | | | | empty
| | | | | +--:(encrypted-\
\key)
| | | | | +--rw encryp\
\ted-key
| | | | | +--rw (ke\
\y-type)
| | | | | | +--:(s\
\ymmetric-key-ref)
| | | | | | | +--\
\rw symmetric-key-ref? leafref
| | | | | | | \
\ {keystore-supported}?
| | | | | | +--:(a\
\symmetric-key-ref)
| | | | | | +--\
\rw asymmetric-key-ref? leafref
| | | | | | \
\ {keystore-supported}?
| | | | | +--rw val\
\ue?
| | | | | b\
\inary
| | | | +--rw id?
| | | | string
| | | | {ks:local-\
\definitions-supported}?
| | | +--:(keystore)
| | | {keystore-suppo\
\rted}?
| | | +--rw keystore-refere\
\nce?
| | | ks:symmetric-\
\key-ref
| | +--rw client-authentication!
| | | {client-auth-config-supported}?
| | | +--rw ca-certs!
| | | | {x509-certificate-auth}?
| | | | +--rw (local-or-truststore)
| | | | +--:(local)
| | | | | {local-definitions-su\
\pported}?
| | | | | +--rw local-definition
| | | | | +--rw cert*
| | | | | | trust-anchor-cer\
\t-cms
| | | | | +---n certificate-expira\
\tion
| | | | | +-- expiration-date
| | | | | yang:date-and\
\-time
| | | | +--:(truststore)
| | | | {truststore-supported\
\,certificates}?
| | | | +--rw truststore-reference?
| | | | ts:certificate-bag-\
\ref
| | | +--rw ee-certs!
| | | | {x509-certificate-auth}?
| | | | +--rw (local-or-truststore)
| | | | +--:(local)
| | | | | {local-definitions-su\
\pported}?
| | | | | +--rw local-definition
| | | | | +--rw cert*
| | | | | | trust-anchor-cer\
\t-cms
| | | | | +---n certificate-expira\
\tion
| | | | | +-- expiration-date
| | | | | yang:date-and\
\-time
| | | | +--:(truststore)
| | | | {truststore-supported\
\,certificates}?
| | | | +--rw truststore-reference?
| | | | ts:certificate-bag-\
\ref
| | | +--rw raw-public-keys!
| | | | {raw-public-key-auth}?
| | | | +--rw (local-or-truststore)
| | | | +--:(local)
| | | | | {local-definitions-su\
\pported}?
| | | | | +--rw local-definition
| | | | | +--rw public-key* [name]
| | | | | +--rw name
| | | | | | string
| | | | | +--rw public-key-form\
\at
| | | | | | identityref
| | | | | +--rw public-key
| | | | | binary
| | | | +--:(truststore)
| | | | {truststore-supported\
\,public-keys}?
| | | | +--rw truststore-reference?
| | | | ts:public-key-bag-r\
\ef
| | | +--rw psks! {psk-auth}?
| | +--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 peer-allowed-to-send? empty
| | +--rw test-peer-aliveness!
| | +--rw max-wait? uint16
| | +--rw max-attempts? uint8
| +--rw http-server-parameters
| | +--rw server-name? string
| | +--rw client-authentication!
| | {client-auth-config-supported}?
| | +--rw users
| | +--rw user* [user-id]
| | +--rw user-id string
| | +--rw (auth-type)?
| | +--:(basic)
| | +--rw basic {basic-auth}?
| | +--rw user-id?
| | | string
| | +--rw password?
| | ianach:crypt-\
\hash
| +--rw restconf-server-parameters
| +--rw client-identity-mappings
| +--rw cert-to-name* [id]
| +--rw id uint32
| +--rw fingerprint?
| | x509c2n:tls-fingerprint
| +--rw map-type identityref
| +--rw name 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
Appendix B. Change Log Appendix B. Change Log
This section is to be removed before publishing as an RFC.
B.1. 00 to 01 B.1. 00 to 01
o Renamed "keychain" to "keystore". * Renamed "keychain" to "keystore".
B.2. 01 to 02 B.2. 01 to 02
o Filled in previously missing 'ietf-restconf-client' module. * Filled in previously missing 'ietf-restconf-client' module.
o Updated the ietf-restconf-server module to accommodate new * Updated the ietf-restconf-server module to accommodate new
grouping 'ietf-tls-server-grouping'. grouping 'ietf-tls-server-grouping'.
B.3. 02 to 03 B.3. 02 to 03
o Refined use of tls-client-grouping to add a must statement * 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). * Changed restconf-client??? to be a grouping (not a container).
B.4. 03 to 04 B.4. 03 to 04
o Added RFC 8174 to Requirements Language Section. * Added RFC 8174 to Requirements Language Section.
o Replaced refine statement in ietf-restconf-client to add a * 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 * 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 * 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 * Now tree diagrams reference ietf-netmod-yang-tree-diagrams
o Updated examples to inline key and certificates (no longer a * Updated examples to inline key and certificates (no longer a
leafref to keystore) leafref to keystore)
B.5. 04 to 05 B.5. 04 to 05
o Now tree diagrams reference ietf-netmod-yang-tree-diagrams * Now tree diagrams reference ietf-netmod-yang-tree-diagrams
o Updated examples to inline key and certificates (no longer a * Updated examples to inline key and certificates (no longer a
leafref to keystore) leafref to keystore)
B.6. 05 to 06 B.6. 05 to 06
o Fixed change log missing section issue. * Fixed change log missing section issue.
o Updated examples to match latest updates to the crypto-types, * 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. * Reduced line length of the YANG modules to fit within 69 columns.
B.7. 06 to 07 B.7. 06 to 07
o removed "idle-timeout" from "persistent" connection config. * removed "idle-timeout" from "persistent" connection config.
o Added "random-selection" for reconnection-strategy's "starts-with" * Added "random-selection" for reconnection-strategy's "starts-with"
enum. enum.
o Replaced "connection-type" choice default (persistent) with * Replaced "connection-type" choice default (persistent) with
"mandatory true". "mandatory true".
o Reduced the periodic-connection's "idle-timeout" from 5 to 2 * Reduced the periodic-connection's "idle-timeout" from 5 to 2
minutes. minutes.
o Replaced reconnect-timeout with period/anchor-time combo. * Replaced reconnect-timeout with period/anchor-time combo.
B.8. 07 to 08 B.8. 07 to 08
o Modified examples to be compatible with new crypto-types algs * Modified examples to be compatible with new crypto-types algs
B.9. 08 to 09 B.9. 08 to 09
o Corrected use of "mandatory true" for "address" leafs. * Corrected use of "mandatory true" for "address" leafs.
o Updated examples to reflect update to groupings defined in the * 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. * Updated to use groupings defined in new TCP and HTTP drafts.
o Updated copyright date, boilerplate template, affiliation, and * Updated copyright date, boilerplate template, affiliation, and
folding algorithm. folding algorithm.
B.10. 09 to 10 B.10. 09 to 10
o Reformatted YANG modules. * Reformatted YANG modules.
B.11. 10 to 11 B.11. 10 to 11
o Adjusted for the top-level "demux container" added to groupings * Adjusted for the top-level "demux container" added to groupings
imported from other modules. imported from other modules.
o Added "must" expressions to ensure that keepalives are not * Added "must" expressions to ensure that keepalives are not
configured for "periodic" connections. configured for "periodic" connections.
o Updated the boilerplate text in module-level "description" * Updated the boilerplate text in module-level "description"
statement to match copyeditor convention. statement to match copyeditor convention.
o Moved "expanded" tree diagrams to the Appendix. * Moved "expanded" tree diagrams to the Appendix.
B.12. 11 to 12 B.12. 11 to 12
o Removed the 'must' statement limiting keepalives in periodic * Removed the 'must' statement limiting keepalives in periodic
connections. connections.
o Updated models and examples to reflect removal of the "demux" * Updated models and examples to reflect removal of the "demux"
containers in the imported models. containers in the imported models.
o Updated the "periodic-connnection" description statements to * Updated the "periodic-connnection" description statements to
better describe behavior when connections are not closed better describe behavior when connections are not closed
gracefully. gracefully.
o Updated text to better reference where certain examples come from * Updated text to better reference where certain examples come from
(e.g., which Section in which draft). (e.g., which Section in which draft).
o In the server model, commented out the "must 'pinned-ca-certs or * In the server model, commented out the "must 'pinned-ca-certs or
pinned-client-certs'" statement to reflect change made in the TLS pinned-client-certs'" statement to reflect change made in the TLS
draft whereby the trust anchors MAY be defined externally. draft whereby the trust anchors MAY be defined externally.
o Replaced the 'listen', 'initiate', and 'call-home' features with * Replaced the 'listen', 'initiate', and 'call-home' features with
boolean expressions. boolean expressions.
B.13. 12 to 13 B.13. 12 to 13
o Updated to reflect changes in trust-anchors drafts (e.g., s/trust- * Updated to reflect changes in trust-anchors drafts (e.g., s/trust-
anchors/truststore/g + s/pinned.//) anchors/truststore/g + s/pinned.//)
o In ietf-restconf-server, Added 'http-listen' (not https-listen) * In ietf-restconf-server, Added 'http-listen' (not https-listen)
choice, to support case when server is behind a TLS-terminator. choice, to support case when server is behind a TLS-terminator.
o Refactored server module to be more like other 'server' models. * Refactored server module to be more like other 'server' models.
If folks like it, will also apply to the client model, as well as If folks like it, will also apply to the client model, as well as
to both the netconf client/server models. Now the 'restconf- to both the netconf client/server models. Now the 'restconf-
server-grouping' is just the RC-specific bits (i.e., the "demux" server-grouping' is just the RC-specific bits (i.e., the "demux"
container minus the container), 'restconf-server- container minus the container), 'restconf-server-
[listen|callhome]-stack-grouping' is the protocol stack for a [listen|callhome]-stack-grouping' is the protocol stack for a
single connection, and 'restconf-server-app-grouping' is single connection, and 'restconf-server-app-grouping' is
effectively what was before (both listen+callhome for many effectively what was before (both listen+callhome for many
inbound/outbound endpoints). inbound/outbound endpoints).
B.14. 13 to 14 B.14. 13 to 14
o Updated examples to reflect ietf-crypto-types change (e.g., * Updated examples to reflect ietf-crypto-types change (e.g.,
identities --> enumerations) identities --> enumerations)
o Adjusting from change in TLS client model (removing the top-level * Adjusting from change in TLS client model (removing the top-level
'certificate' container). 'certificate' container).
o Added "external-endpoint" to the "http-listen" choice in ietf- * Added "external-endpoint" to the "http-listen" choice in ietf-
restconf-server. restconf-server.
B.15. 14 to 15 B.15. 14 to 15
o Added missing "or https-listen" clause in a "must" expression. * Added missing "or https-listen" clause in a "must" expression.
o Refactored the client module similar to how the server module was * Refactored the client module similar to how the server module was
refactored in -13. Now the 'restconf-client-grouping' is just the refactored in -13. Now the 'restconf-client-grouping' is just the
RC-specific bits, the 'restconf-client-[initiate|listen]-stack- RC-specific bits, the 'restconf-client-[initiate|listen]-stack-
grouping' is the protocol stack for a single connection, and grouping' is the protocol stack for a single connection, and
'restconf-client-app-grouping' is effectively what was before 'restconf-client-app-grouping' is effectively what was before
(both listen+callhome for many inbound/outbound endpoints). (both listen+callhome for many inbound/outbound endpoints).
B.16. 15 to 16 B.16. 15 to 16
o Added refinement to make "cert-to-name/fingerprint" be mandatory * Added refinement to make "cert-to-name/fingerprint" be mandatory
false. false.
o Commented out refinement to "tls-server-grouping/client- * Commented out refinement to "tls-server-grouping/client-
authentication" until a better "must" expression is defined. authentication" until a better "must" expression is defined.
o Updated restconf-client example to reflect that http-client- * Updated restconf-client example to reflect that http-client-
grouping no longer has a "protocol-version" leaf. grouping no longer has a "protocol-version" leaf.
B.17. 16 to 17 B.17. 16 to 17
o Updated examples to include the "*-key-format" nodes. * Updated examples to include the "*-key-format" nodes.
o Updated examples to remove the "required" nodes. * Updated examples to remove the "required" nodes.
B.18. 17 to 18 B.18. 17 to 18
o Updated examples to reflect new "bag" addition to truststore. * Updated examples to reflect new "bag" addition to truststore.
B.19. 18 to 19 B.19. 18 to 19
o Updated examples to remove the 'algorithm' nodes. * Updated examples to remove the 'algorithm' nodes.
o Updated examples to reflect the new TLS keepalives structure. * Updated examples to reflect the new TLS keepalives structure.
o Removed the 'protocol-versions' node from the restconf-server * Removed the 'protocol-versions' node from the restconf-server
examples. examples.
o Added a "Note to Reviewers" note to first page. * Added a "Note to Reviewers" note to first page.
B.20. 19 to 20
* Moved and changed "must" statement so that either TLS *or* HTTP
auth must be configured.
* Expanded "Data Model Overview section(s) [remove "wall" of tree
diagrams].
* Updated the Security Considerations section.
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, Mehmet Ersue, Ramkumar Dhanapal, Balazs Bjorklund, Benoit Claise, Mehmet Ersue, Ramkumar Dhanapal, Balazs
Kovacs, Radek Krejci, David Lamparter, Ladislav Lhotka, Alan Luchuk, Kovacs, Radek Krejci, David Lamparter, Ladislav Lhotka, Alan Luchuk,
Tom Petch, Juergen Schoenwaelder, Phil Shafer, Sean Turner, Bert Tom Petch, Juergen Schoenwaelder, Phil Shafer, Sean Turner, Bert
Wijnen. Wijnen.
Author's Address Author's Address
Kent Watsen Kent Watsen
Watsen Networks Watsen Networks
EMail: kent+ietf@watsen.net Email: kent+ietf@watsen.net
 End of changes. 139 change blocks. 
2527 lines changed or deleted 659 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/