draft-ietf-netconf-restconf-client-server-20.txt   draft-ietf-netconf-restconf-client-server-21.txt 
NETCONF Working Group K. Watsen NETCONF Working Group K. Watsen
Internet-Draft Watsen Networks Internet-Draft Watsen Networks
Intended status: Standards Track 8 July 2020 Intended status: Standards Track 20 August 2020
Expires: 9 January 2021 Expires: 21 February 2021
RESTCONF Client and Server Models RESTCONF Client and Server Models
draft-ietf-netconf-restconf-client-server-20 draft-ietf-netconf-restconf-client-server-21
Abstract Abstract
This document defines two YANG modules, one module to configure a This document defines two YANG modules, one module to configure a
RESTCONF client and the other module to configure a RESTCONF server. RESTCONF client and the other module to configure a RESTCONF server.
Both modules support the TLS transport protocol with both standard Both modules support the TLS transport protocol with both standard
RESTCONF and RESTCONF Call Home connections. RESTCONF and RESTCONF Call Home connections.
Editorial Note (To be removed by RFC Editor) Editorial Note (To be removed by RFC Editor)
skipping to change at page 2, line 13 skipping to change at page 2, line 13
client-server client-server
* "HHHH" --> the assigned RFC value for draft-ietf-netconf-netconf- * "HHHH" --> the assigned RFC value for draft-ietf-netconf-netconf-
client-server client-server
* "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:
* "2020-07-08" --> the publication date of this draft * "2020-08-20" --> 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:
* Appendix B. Change Log * Appendix B. Change Log
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on 9 January 2021. This Internet-Draft will expire on 21 February 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 (https://trustee.ietf.org/ Provisions Relating to IETF Documents (https://trustee.ietf.org/
license-info) in effect on the date of publication of this document. license-info) in effect on the date of publication of this document.
Please review these documents carefully, as they describe your rights Please review these documents carefully, as they describe your rights
skipping to change at page 3, line 17 skipping to change at page 3, line 17
2. The "ietf-restconf-client" Module . . . . . . . . . . . . . . 5 2. The "ietf-restconf-client" Module . . . . . . . . . . . . . . 5
2.1. Data Model Overview . . . . . . . . . . . . . . . . . . . 6 2.1. Data Model Overview . . . . . . . . . . . . . . . . . . . 6
2.2. Example Usage . . . . . . . . . . . . . . . . . . . . . . 10 2.2. Example Usage . . . . . . . . . . . . . . . . . . . . . . 10
2.3. YANG Module . . . . . . . . . . . . . . . . . . . . . . . 14 2.3. YANG Module . . . . . . . . . . . . . . . . . . . . . . . 14
3. The "ietf-restconf-server" Module . . . . . . . . . . . . . . 24 3. The "ietf-restconf-server" Module . . . . . . . . . . . . . . 24
3.1. Data Model Overview . . . . . . . . . . . . . . . . . . . 24 3.1. Data Model Overview . . . . . . . . . . . . . . . . . . . 24
3.2. Example Usage . . . . . . . . . . . . . . . . . . . . . . 29 3.2. Example Usage . . . . . . . . . . . . . . . . . . . . . . 29
3.3. YANG Module . . . . . . . . . . . . . . . . . . . . . . . 33 3.3. YANG Module . . . . . . . . . . . . . . . . . . . . . . . 33
4. Security Considerations . . . . . . . . . . . . . . . . . . . 45 4. Security Considerations . . . . . . . . . . . . . . . . . . . 45
4.1. The "ietf-restconf-client" YANG Module . . . . . . . . . 45 4.1. The "ietf-restconf-client" YANG Module . . . . . . . . . 45
4.2. The "ietf-restconf-server" YANG Module . . . . . . . . . 45 4.2. The "ietf-restconf-server" YANG Module . . . . . . . . . 46
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 46 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 46
5.1. The IETF XML Registry . . . . . . . . . . . . . . . . . . 46 5.1. The "IETF XML" Registry . . . . . . . . . . . . . . . . . 46
5.2. The YANG Module Names Registry . . . . . . . . . . . . . 46 5.2. The "YANG Module Names" Registry . . . . . . . . . . . . 47
6. References . . . . . . . . . . . . . . . . . . . . . . . . . 47 6. References . . . . . . . . . . . . . . . . . . . . . . . . . 47
6.1. Normative References . . . . . . . . . . . . . . . . . . 47 6.1. Normative References . . . . . . . . . . . . . . . . . . 47
6.2. Informative References . . . . . . . . . . . . . . . . . 48 6.2. Informative References . . . . . . . . . . . . . . . . . 48
Appendix A. Expanded Tree Diagrams . . . . . . . . . . . . . . . 49 Appendix A. Expanded Tree Diagrams . . . . . . . . . . . . . . . 50
A.1. Expanded Tree Diagram for 'ietf-restconf-client' . . . . 50 A.1. Expanded Tree Diagram for 'ietf-restconf-client' . . . . 50
A.2. Expanded Tree Diagram for 'ietf-restconf-server' . . . . 50 A.2. Expanded Tree Diagram for 'ietf-restconf-server' . . . . 50
Appendix B. Change Log . . . . . . . . . . . . . . . . . . . . . 50 Appendix B. Change Log . . . . . . . . . . . . . . . . . . . . . 50
B.1. 00 to 01 . . . . . . . . . . . . . . . . . . . . . . . . 50 B.1. 00 to 01 . . . . . . . . . . . . . . . . . . . . . . . . 50
B.2. 01 to 02 . . . . . . . . . . . . . . . . . . . . . . . . 50 B.2. 01 to 02 . . . . . . . . . . . . . . . . . . . . . . . . 51
B.3. 02 to 03 . . . . . . . . . . . . . . . . . . . . . . . . 50 B.3. 02 to 03 . . . . . . . . . . . . . . . . . . . . . . . . 51
B.4. 03 to 04 . . . . . . . . . . . . . . . . . . . . . . . . 51 B.4. 03 to 04 . . . . . . . . . . . . . . . . . . . . . . . . 51
B.5. 04 to 05 . . . . . . . . . . . . . . . . . . . . . . . . 51 B.5. 04 to 05 . . . . . . . . . . . . . . . . . . . . . . . . 51
B.6. 05 to 06 . . . . . . . . . . . . . . . . . . . . . . . . 51 B.6. 05 to 06 . . . . . . . . . . . . . . . . . . . . . . . . 51
B.7. 06 to 07 . . . . . . . . . . . . . . . . . . . . . . . . 51 B.7. 06 to 07 . . . . . . . . . . . . . . . . . . . . . . . . 52
B.8. 07 to 08 . . . . . . . . . . . . . . . . . . . . . . . . 52 B.8. 07 to 08 . . . . . . . . . . . . . . . . . . . . . . . . 52
B.9. 08 to 09 . . . . . . . . . . . . . . . . . . . . . . . . 52 B.9. 08 to 09 . . . . . . . . . . . . . . . . . . . . . . . . 52
B.10. 09 to 10 . . . . . . . . . . . . . . . . . . . . . . . . 52 B.10. 09 to 10 . . . . . . . . . . . . . . . . . . . . . . . . 52
B.11. 10 to 11 . . . . . . . . . . . . . . . . . . . . . . . . 52 B.11. 10 to 11 . . . . . . . . . . . . . . . . . . . . . . . . 52
B.12. 11 to 12 . . . . . . . . . . . . . . . . . . . . . . . . 52 B.12. 11 to 12 . . . . . . . . . . . . . . . . . . . . . . . . 53
B.13. 12 to 13 . . . . . . . . . . . . . . . . . . . . . . . . 53 B.13. 12 to 13 . . . . . . . . . . . . . . . . . . . . . . . . 53
B.14. 13 to 14 . . . . . . . . . . . . . . . . . . . . . . . . 53 B.14. 13 to 14 . . . . . . . . . . . . . . . . . . . . . . . . 53
B.15. 14 to 15 . . . . . . . . . . . . . . . . . . . . . . . . 53 B.15. 14 to 15 . . . . . . . . . . . . . . . . . . . . . . . . 54
B.16. 15 to 16 . . . . . . . . . . . . . . . . . . . . . . . . 54 B.16. 15 to 16 . . . . . . . . . . . . . . . . . . . . . . . . 54
B.17. 16 to 17 . . . . . . . . . . . . . . . . . . . . . . . . 54 B.17. 16 to 17 . . . . . . . . . . . . . . . . . . . . . . . . 54
B.18. 17 to 18 . . . . . . . . . . . . . . . . . . . . . . . . 54 B.18. 17 to 18 . . . . . . . . . . . . . . . . . . . . . . . . 54
B.19. 18 to 19 . . . . . . . . . . . . . . . . . . . . . . . . 54 B.19. 18 to 19 . . . . . . . . . . . . . . . . . . . . . . . . 54
B.20. 19 to 20 . . . . . . . . . . . . . . . . . . . . . . . . 54 B.20. 19 to 20 . . . . . . . . . . . . . . . . . . . . . . . . 54
B.21. 20 to 21 . . . . . . . . . . . . . . . . . . . . . . . . 55
Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 55 Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 55
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 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].
skipping to change at page 4, line 25 skipping to change at page 4, line 25
This document presents one or more YANG modules [RFC7950] that are This document presents one or more YANG modules [RFC7950] that are
part of a collection of RFCs that work together to define part of a collection of RFCs that work together to define
configuration modules for clients and servers of both the NETCONF configuration modules for clients and servers of both the NETCONF
[RFC6241] and RESTCONF [RFC8040] protocols. [RFC6241] and RESTCONF [RFC8040] protocols.
The modules have been defined in a modular fashion to enable their 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 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 the time of this writing, with many more expected to be defined in
time. time.
The relationship between the various RFCs in the collection is The normative dependency relationship between the various RFCs in the
presented in the below diagram. The labels in the diagram represent collection is presented in the below diagram. The labels in the
the primary purpose provided by each RFC. Links the each RFC are diagram represent the primary purpose provided by each RFC.
provided below the diagram. Hyperlinks to each RFC are provided below the diagram.
crypto-types crypto-types
^ ^ ^ ^
/ \ / \
/ \ / \
truststore keystore truststore keystore
^ ^ ^ ^ ^ ^ ^ ^
| +---------+ | | | +---------+ | |
| | | | | | | |
| +------------+ | | +------------+ |
skipping to change at page 6, line 11 skipping to change at page 6, line 11
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. Data Model Overview 2.1. Data Model Overview
This section provides an overview of the "ietf-restconf-client"
module in terms of its features and groupings.
2.1.1. Features 2.1.1. Features
The following diagram lists all the "feature" statements defined in The following diagram lists all the "feature" statements defined in
the "ietf-restconf-client" module: the "ietf-restconf-client" module:
Features: Features:
+-- https-initiate +-- https-initiate
+-- http-listen +-- http-listen
+-- https-listen +-- https-listen
| The diagram above uses syntax that is similar to but not
| defined in [RFC8340].
2.1.2. Groupings 2.1.2. Groupings
The following diagram lists all the "grouping" statements defined in The following diagram lists all the "grouping" statements defined in
the "ietf-restconf-client" module: the "ietf-restconf-client" module:
Groupings: Groupings:
+-- restconf-client-grouping +-- restconf-client-grouping
+-- restconf-client-initiate-stack-grouping +-- restconf-client-initiate-stack-grouping
+-- restconf-client-listen-stack-grouping +-- restconf-client-listen-stack-grouping
+-- restconf-client-app-grouping +-- restconf-client-app-grouping
| The diagram above uses syntax that is similar to but not
| defined in [RFC8340].
Each of these groupings are presented in the following subsections. Each of these groupings are presented in the following subsections.
2.1.2.1. The "restconf-client-grouping" Grouping 2.1.2.1. The "restconf-client-grouping" Grouping
The following tree diagram [RFC8340] illustrates the "restconf- The following tree diagram [RFC8340] illustrates the "restconf-
client-grouping" grouping: client-grouping" grouping:
grouping restconf-client-grouping ---> <empty> grouping restconf-client-grouping ---> <empty>
Comments: Comments:
skipping to change at page 9, line 50 skipping to change at page 10, line 4
RESTCONF servers as well as receiving call-home connections from RESTCONF servers as well as receiving call-home connections from
RESTCONF servers. RESTCONF servers.
* Both the "initiate" and "listen" subtrees must be enabled by * Both the "initiate" and "listen" subtrees must be enabled by
"feature" statements. "feature" statements.
* For the referenced grouping statement(s): * For the referenced grouping statement(s):
- The "restconf-client-initiate-stack-grouping" grouping is - The "restconf-client-initiate-stack-grouping" grouping is
discussed in Section 2.1.2.2 in this document. discussed in Section 2.1.2.2 in this document.
- The "restconf-client-listen-stack-grouping" grouping is - The "restconf-client-listen-stack-grouping" grouping is
discussed in Section 2.1.2.3 in this document. discussed in Section 2.1.2.3 in this document.
2.1.3. Protocol-accessible Nodes 2.1.3. Protocol-accessible Nodes
The following diagram lists all the protocol-accessible nodes defined The following tree diagram [RFC8340] lists all the protocol-
in the "ietf-restconf-client" module: accessible nodes defined in the "ietf-restconf-client" module:
module: ietf-restconf-client module: ietf-restconf-client
+--rw restconf-client +--rw restconf-client
+---u restconf-client-app-grouping +---u restconf-client-app-grouping
Comments: Comments:
* Protocol-accessible nodes are those nodes that are accessible when * Protocol-accessible nodes are those nodes that are accessible when
the module is "implemented", as described in Section 5.6.5 of the module is "implemented", as described in Section 5.6.5 of
[RFC7950]. [RFC7950].
skipping to change at page 11, line 42 skipping to change at page 11, line 45
<test-peer-aliveness> <test-peer-aliveness>
<max-wait>30</max-wait> <max-wait>30</max-wait>
<max-attempts>3</max-attempts> <max-attempts>3</max-attempts>
</test-peer-aliveness> </test-peer-aliveness>
</keepalives> </keepalives>
</tls-client-parameters> </tls-client-parameters>
<http-client-parameters> <http-client-parameters>
<client-identity> <client-identity>
<basic> <basic>
<user-id>bob</user-id> <user-id>bob</user-id>
<password>secret</password> <cleartext-password>secret</cleartext-password>
</basic> </basic>
</client-identity> </client-identity>
</http-client-parameters> </http-client-parameters>
</https> </https>
</endpoint> </endpoint>
<endpoint> <endpoint>
<name>corp-fw2.example.com</name> <name>corp-fw2.example.com</name>
<https> <https>
<tcp-client-parameters> <tcp-client-parameters>
<remote-address>corp-fw2.example.com</remote-address> <remote-address>corp-fw2.example.com</remote-address>
skipping to change at page 12, line 42 skipping to change at page 12, line 45
<test-peer-aliveness> <test-peer-aliveness>
<max-wait>30</max-wait> <max-wait>30</max-wait>
<max-attempts>3</max-attempts> <max-attempts>3</max-attempts>
</test-peer-aliveness> </test-peer-aliveness>
</keepalives> </keepalives>
</tls-client-parameters> </tls-client-parameters>
<http-client-parameters> <http-client-parameters>
<client-identity> <client-identity>
<basic> <basic>
<user-id>bob</user-id> <user-id>bob</user-id>
<password>secret</password> <cleartext-password>secret</cleartext-password>
</basic> </basic>
</client-identity> </client-identity>
</http-client-parameters> </http-client-parameters>
</https> </https>
</endpoint> </endpoint>
</endpoints> </endpoints>
<connection-type> <connection-type>
<persistent/> <persistent/>
</connection-type> </connection-type>
</restconf-server> </restconf-server>
</initiate> </initiate>
<!-- endpoints to listen for RESTCONF Call Home connections on --> <!-- endpoints to listen for RESTCONF Call Home connections on -->
<listen> <listen>
<endpoint> <endpoint>
<name>Intranet-facing listener</name> <name>Intranet-facing listener</name>
<https> <https>
<tcp-server-parameters> <tcp-server-parameters>
<local-address>11.22.33.44</local-address> <local-address>11.22.33.44</local-address>
skipping to change at page 13, line 43 skipping to change at page 13, line 45
</ee-certs> </ee-certs>
</server-authentication> </server-authentication>
<keepalives> <keepalives>
<peer-allowed-to-send/> <peer-allowed-to-send/>
</keepalives> </keepalives>
</tls-client-parameters> </tls-client-parameters>
<http-client-parameters> <http-client-parameters>
<client-identity> <client-identity>
<basic> <basic>
<user-id>bob</user-id> <user-id>bob</user-id>
<password>secret</password> <cleartext-password>secret</cleartext-password>
</basic> </basic>
</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.ietf-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.ietf-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-08-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 15, line 34 skipping to change at page 15, line 36
(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-07-08 { revision 2020-08-20 {
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 24, line 39 skipping to change at page 24, line 41
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. Data Model Overview 3.1. Data Model Overview
This section provides an overview of the "ietf-restconf-server"
module in terms of its features and groupings.
3.1.1. Features 3.1.1. Features
The following diagram lists all the "feature" statements defined in The following diagram lists all the "feature" statements defined in
the "ietf-restconf-server" module: the "ietf-restconf-server" module:
Features: Features:
+-- http-listen +-- http-listen
+-- https-listen +-- https-listen
+-- https-call-home +-- https-call-home
| The diagram above uses syntax that is similar to but not
| defined in [RFC8340].
3.1.2. Groupings 3.1.2. Groupings
The following diagram lists all the "grouping" statements defined in The following diagram lists all the "grouping" statements defined in
the "ietf-restconf-server" module: the "ietf-restconf-server" module:
Groupings: Groupings:
+-- restconf-server-grouping +-- restconf-server-grouping
+-- restconf-server-listen-stack-grouping +-- restconf-server-listen-stack-grouping
+-- restconf-server-callhome-stack-grouping +-- restconf-server-callhome-stack-grouping
+-- restconf-server-app-grouping +-- restconf-server-app-grouping
| The diagram above uses syntax that is similar to but not
| defined in [RFC8340].
Each of these groupings are presented in the following subsections. Each of these groupings are presented in the following subsections.
3.1.2.1. The "restconf-server-grouping" Grouping 3.1.2.1. The "restconf-server-grouping" Grouping
The following tree diagram [RFC8340] illustrates the "restconf- The following tree diagram [RFC8340] illustrates the "restconf-
server-grouping" grouping: 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
skipping to change at page 28, line 49 skipping to change at page 29, line 7
* For the referenced grouping statement(s): * For the referenced grouping statement(s):
- The "restconf-server-listen-stack-grouping" grouping is - The "restconf-server-listen-stack-grouping" grouping is
discussed in Section 3.1.2.2 in this document. discussed in Section 3.1.2.2 in this document.
- The "restconf-server-callhome-stack-grouping" grouping is - The "restconf-server-callhome-stack-grouping" grouping is
discussed in Section 3.1.2.3 in this document. discussed in Section 3.1.2.3 in this document.
3.1.3. Protocol-accessible Nodes 3.1.3. Protocol-accessible Nodes
The following diagram lists all the protocol-accessible nodes defined The following tree diagram [RFC8340] lists all the protocol-
in the "ietf-restconf-server" module: accessible nodes defined in the "ietf-restconf-server" module:
module: ietf-restconf-server module: ietf-restconf-server
+--rw restconf-server +--rw restconf-server
+---u restconf-server-app-grouping +---u restconf-server-app-grouping
Comments: Comments:
* Protocol-accessible nodes are those nodes that are accessible when * Protocol-accessible nodes are those nodes that are accessible when
the module is "implemented", as described in Section 5.6.5 of the module is "implemented", as described in Section 5.6.5 of
[RFC7950]. [RFC7950].
skipping to change at page 33, line 41 skipping to change at page 33, line 47
</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.ietf-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.ietf-netconf-http-client-server]. [I-D.ietf-netconf-http-client-server].
<CODE BEGINS> file "ietf-restconf-server@2020-07-08.yang" <CODE BEGINS> file "ietf-restconf-server@2020-08-20.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";
} }
import ietf-inet-types { import ietf-inet-types {
prefix inet; prefix inet;
reference reference
"RFC 6991: Common YANG Data Types"; "RFC 6991: Common YANG Data Types";
} }
import ietf-x509-cert-to-name { import ietf-x509-cert-to-name {
prefix x509c2n; prefix x509c2n;
skipping to change at page 35, line 30 skipping to change at page 35, line 39
(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-07-08 { revision 2020-08-20 {
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 46, line 28 skipping to change at page 46, line 40
This module does not define any RPCs, actions, or notifications, and This module does not define any RPCs, actions, or notifications, and
thus the security consideration for such is not provided here. thus the security consideration for such is not provided here.
Please be aware that this module uses groupings defined in other RFCs 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 that define data nodes that do set the NACM "default-deny-all" and
"default-deny-write" extensions. "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
Registrant Contact: The NETCONF WG of the IETF. Registrant Contact: The NETCONF WG of the IETF.
XML: N/A, the requested URI is an XML namespace. XML: N/A, the requested URI is an XML namespace.
URI: urn:ietf:params:xml:ns:yang:ietf-restconf-server URI: urn:ietf:params:xml:ns:yang:ietf-restconf-server
Registrant Contact: The NETCONF WG of the IETF. Registrant Contact: The NETCONF WG of the IETF.
XML: N/A, the requested URI is an XML namespace. XML: N/A, the requested URI is an XML namespace.
5.2. The YANG Module Names Registry 5.2. The "YANG Module Names" Registry
This document registers two YANG modules in the YANG Module Names This document registers two YANG modules in the YANG Module Names
registry [RFC6020]. Following the format in [RFC6020], the the registry [RFC6020]. Following the format in [RFC6020], the following
following registrations are requested: registrations are requested:
name: ietf-restconf-client name: ietf-restconf-client
namespace: urn:ietf:params:xml:ns:yang:ietf-restconf-client namespace: urn:ietf:params:xml:ns:yang:ietf-restconf-client
prefix: ncc prefix: ncc
reference: RFC IIII reference: RFC IIII
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-http-client-server] [I-D.ietf-netconf-http-client-server]
Watsen, K., "YANG Groupings for HTTP Clients and HTTP Watsen, K., "YANG Groupings for HTTP Clients and HTTP
Servers", Work in Progress, Internet-Draft, draft-ietf- Servers", Work in Progress, Internet-Draft, draft-ietf-
netconf-http-client-server-03, 20 May 2020, netconf-http-client-server-04, 8 July 2020,
<https://tools.ietf.org/html/draft-ietf-netconf-http- <https://tools.ietf.org/html/draft-ietf-netconf-http-
client-server-03>. client-server-04>.
[I-D.ietf-netconf-keystore] [I-D.ietf-netconf-keystore]
Watsen, K., "A YANG Data Model for a Keystore", Work in Watsen, K., "A YANG Data Model for a Keystore", Work in
Progress, Internet-Draft, draft-ietf-netconf-keystore-17, Progress, Internet-Draft, draft-ietf-netconf-keystore-19,
20 May 2020, <https://tools.ietf.org/html/draft-ietf- 10 July 2020, <https://tools.ietf.org/html/draft-ietf-
netconf-keystore-17>. netconf-keystore-19>.
[I-D.ietf-netconf-tcp-client-server] [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", Work in Progress, Internet-Draft, draft- and TCP Servers", Work in Progress, Internet-Draft, draft-
ietf-netconf-tcp-client-server-06, 16 June 2020, ietf-netconf-tcp-client-server-07, 8 July 2020,
<https://tools.ietf.org/html/draft-ietf-netconf-tcp- <https://tools.ietf.org/html/draft-ietf-netconf-tcp-
client-server-06>. client-server-07>.
[I-D.ietf-netconf-tls-client-server] [I-D.ietf-netconf-tls-client-server]
Watsen, K. and G. Wu, "YANG Groupings for TLS Clients and Watsen, K. and G. Wu, "YANG Groupings for TLS Clients and
TLS Servers", Work in Progress, Internet-Draft, draft- TLS Servers", Work in Progress, Internet-Draft, draft-
ietf-netconf-tls-client-server-19, 20 May 2020, ietf-netconf-tls-client-server-21, 10 July 2020,
<https://tools.ietf.org/html/draft-ietf-netconf-tls- <https://tools.ietf.org/html/draft-ietf-netconf-tls-
client-server-19>. client-server-21>.
[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 48, line 37 skipping to change at page 48, line 42
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] [I-D.ietf-netconf-crypto-types]
Watsen, K., "Common YANG Data Types for Cryptography", Watsen, K., "YANG Data Types and Groupings for
Work in Progress, Internet-Draft, draft-ietf-netconf- Cryptography", Work in Progress, Internet-Draft, draft-
crypto-types-15, 20 May 2020, ietf-netconf-crypto-types-17, 10 July 2020,
<https://tools.ietf.org/html/draft-ietf-netconf-crypto- <https://tools.ietf.org/html/draft-ietf-netconf-crypto-
types-15>. types-17>.
[I-D.ietf-netconf-netconf-client-server] [I-D.ietf-netconf-netconf-client-server]
Watsen, K., "NETCONF Client and Server Models", Work in Watsen, K., "NETCONF Client and Server Models", Work in
Progress, Internet-Draft, draft-ietf-netconf-netconf- Progress, Internet-Draft, draft-ietf-netconf-netconf-
client-server-19, 20 May 2020, client-server-20, 8 July 2020,
<https://tools.ietf.org/html/draft-ietf-netconf-netconf- <https://tools.ietf.org/html/draft-ietf-netconf-netconf-
client-server-19>. client-server-20>.
[I-D.ietf-netconf-restconf-client-server] [I-D.ietf-netconf-restconf-client-server]
Watsen, K., "RESTCONF Client and Server Models", Work in Watsen, K., "RESTCONF Client and Server Models", Work in
Progress, Internet-Draft, draft-ietf-netconf-restconf- Progress, Internet-Draft, draft-ietf-netconf-restconf-
client-server-19, 20 May 2020, client-server-20, 8 July 2020,
<https://tools.ietf.org/html/draft-ietf-netconf-restconf- <https://tools.ietf.org/html/draft-ietf-netconf-restconf-
client-server-19>. client-server-20>.
[I-D.ietf-netconf-ssh-client-server] [I-D.ietf-netconf-ssh-client-server]
Watsen, K. and G. Wu, "YANG Groupings for SSH Clients and Watsen, K. and G. Wu, "YANG Groupings for SSH Clients and
SSH Servers", Work in Progress, Internet-Draft, draft- SSH Servers", Work in Progress, Internet-Draft, draft-
ietf-netconf-ssh-client-server-19, 20 May 2020, ietf-netconf-ssh-client-server-21, 10 July 2020,
<https://tools.ietf.org/html/draft-ietf-netconf-ssh- <https://tools.ietf.org/html/draft-ietf-netconf-ssh-
client-server-19>. client-server-21>.
[I-D.ietf-netconf-trust-anchors] [I-D.ietf-netconf-trust-anchors]
Watsen, K., "A YANG Data Model for a Truststore", Work in Watsen, K., "A YANG Data Model for a Truststore", Work in
Progress, Internet-Draft, draft-ietf-netconf-trust- Progress, Internet-Draft, draft-ietf-netconf-trust-
anchors-10, 20 May 2020, <https://tools.ietf.org/html/ anchors-12, 10 July 2020, <https://tools.ietf.org/html/
draft-ietf-netconf-trust-anchors-10>. draft-ietf-netconf-trust-anchors-12>.
[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
DOI 10.17487/RFC3688, January 2004, DOI 10.17487/RFC3688, January 2004,
<https://www.rfc-editor.org/info/rfc3688>. <https://www.rfc-editor.org/info/rfc3688>.
[RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed.,
and A. Bierman, Ed., "Network Configuration Protocol and A. Bierman, Ed., "Network Configuration Protocol
(NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011, (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011,
<https://www.rfc-editor.org/info/rfc6241>. <https://www.rfc-editor.org/info/rfc6241>.
skipping to change at page 54, line 38 skipping to change at page 55, line 4
* Updated examples to remove the 'algorithm' nodes. * Updated examples to remove the 'algorithm' nodes.
* Updated examples to reflect the new TLS keepalives structure. * Updated examples to reflect the new TLS keepalives structure.
* Removed the 'protocol-versions' node from the restconf-server * Removed the 'protocol-versions' node from the restconf-server
examples. examples.
* Added a "Note to Reviewers" note to first page. * Added a "Note to Reviewers" note to first page.
B.20. 19 to 20 B.20. 19 to 20
* Moved and changed "must" statement so that either TLS *or* HTTP * Moved and changed "must" statement so that either TLS *or* HTTP
auth must be configured. auth must be configured.
* Expanded "Data Model Overview section(s) [remove "wall" of tree * Expanded "Data Model Overview section(s) [remove "wall" of tree
diagrams]. diagrams].
* Updated the Security Considerations section. * Updated the Security Considerations section.
B.21. 20 to 21
* Cleaned up titles in the IANA Consideratons section
* Fixed issues found by the SecDir review of the "keystore" draft.
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
 End of changes. 53 change blocks. 
58 lines changed or deleted 81 lines changed or added

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