draft-ietf-netconf-restconf-client-server-03.txt   draft-ietf-netconf-restconf-client-server-04.txt 
NETCONF Working Group K. Watsen NETCONF Working Group K. Watsen
Internet-Draft Juniper Networks Internet-Draft Juniper Networks
Intended status: Standards Track J. Schoenwaelder Intended status: Standards Track J. Schoenwaelder
Expires: December 15, 2017 Jacobs University Bremen Expires: January 4, 2018 Jacobs University Bremen
June 13, 2017 July 3, 2017
RESTCONF Client and Server Models RESTCONF Client and Server Models
draft-ietf-netconf-restconf-client-server-03 draft-ietf-netconf-restconf-client-server-04
Abstract Abstract
This document defines two YANG modules, one module to configure a This document defines two YANG modules, one module to configure a
RESTCONF client and the other module to configure a RESTCONF server. RESTCONF client and the other module to configure a RESTCONF server.
Both modules support the TLS transport protocol with both standard Both modules support the TLS transport protocol with both standard
RESTCONF and RESTCONF Call Home connections. RESTCONF and RESTCONF Call Home connections.
Editorial Note (To be removed by RFC Editor) Editorial Note (To be removed by RFC Editor)
skipping to change at page 1, line 46 skipping to change at page 1, line 46
progress. Please apply the following replacements: progress. Please apply the following replacements:
o "XXXX" --> the assigned RFC value for this draft o "XXXX" --> the assigned RFC value for this draft
o "ZZZZ" --> the assigned RFC value for I-D.ietf-netconf-tls-client- o "ZZZZ" --> the assigned RFC value for I-D.ietf-netconf-tls-client-
server server
Artwork in this document contains placeholder values for the date of Artwork in this document contains placeholder values for the date of
publication of this draft. Please apply the following replacement: publication of this draft. Please apply the following replacement:
o "2017-06-13" --> the publication date of this draft o "2017-07-03" --> the publication date of this draft
The following Appendix section is to be removed prior to publication: The following Appendix section is to be removed prior to publication:
o Appendix A. Change Log o Appendix A. 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 http://datatracker.ietf.org/drafts/current/. Drafts is at http://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 December 15, 2017. This Internet-Draft will expire on January 4, 2018.
Copyright Notice Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the Copyright (c) 2017 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
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 3, line 6 skipping to change at page 3, line 6
2.1. Tree Diagram . . . . . . . . . . . . . . . . . . . . . . 4 2.1. Tree Diagram . . . . . . . . . . . . . . . . . . . . . . 4
2.2. Example Usage . . . . . . . . . . . . . . . . . . . . . . 6 2.2. Example Usage . . . . . . . . . . . . . . . . . . . . . . 6
2.3. YANG Model . . . . . . . . . . . . . . . . . . . . . . . 8 2.3. YANG Model . . . . . . . . . . . . . . . . . . . . . . . 8
3. The RESTCONF Server Model . . . . . . . . . . . . . . . . . . 16 3. The RESTCONF Server Model . . . . . . . . . . . . . . . . . . 16
3.1. Tree Diagram . . . . . . . . . . . . . . . . . . . . . . 17 3.1. Tree Diagram . . . . . . . . . . . . . . . . . . . . . . 17
3.2. Example Usage . . . . . . . . . . . . . . . . . . . . . . 18 3.2. Example Usage . . . . . . . . . . . . . . . . . . . . . . 18
3.3. YANG Model . . . . . . . . . . . . . . . . . . . . . . . 20 3.3. YANG Model . . . . . . . . . . . . . . . . . . . . . . . 20
4. Security Considerations . . . . . . . . . . . . . . . . . . . 29 4. Security Considerations . . . . . . . . . . . . . . . . . . . 29
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 30 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 30
5.1. The IETF XML Registry . . . . . . . . . . . . . . . . . . 30 5.1. The IETF XML Registry . . . . . . . . . . . . . . . . . . 30
5.2. The YANG Module Names Registry . . . . . . . . . . . . . 30 5.2. The YANG Module Names Registry . . . . . . . . . . . . . 31
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 31 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 31
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 31 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 31
7.1. Normative References . . . . . . . . . . . . . . . . . . 31 7.1. Normative References . . . . . . . . . . . . . . . . . . 31
7.2. Informative References . . . . . . . . . . . . . . . . . 32 7.2. Informative References . . . . . . . . . . . . . . . . . 32
Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 33 Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 34
A.1. server-model-09 to 00 . . . . . . . . . . . . . . . . . . 33 A.1. server-model-09 to 00 . . . . . . . . . . . . . . . . . . 34
A.2. 00 to 01 . . . . . . . . . . . . . . . . . . . . . . . . 33 A.2. 00 to 01 . . . . . . . . . . . . . . . . . . . . . . . . 34
A.3. 01 to 02 . . . . . . . . . . . . . . . . . . . . . . . . 33 A.3. 01 to 02 . . . . . . . . . . . . . . . . . . . . . . . . 34
A.4. 02 to 03 . . . . . . . . . . . . . . . . . . . . . . . . 33 A.4. 02 to 03 . . . . . . . . . . . . . . . . . . . . . . . . 34
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 33 A.5. 03 to 04 . . . . . . . . . . . . . . . . . . . . . . . . 34
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 34
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 [RFC5246] RESTCONF server [RFC8040]. Both modules support the TLS [RFC5246]
transport protocol with both standard RESTCONF and RESTCONF Call Home transport protocol with both standard RESTCONF and RESTCONF Call Home
connections [RFC8071]. connections [RFC8071].
1.1. Terminology 1.1. Terminology
The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
document are to be interpreted as described in RFC 2119 [RFC2119]. "OPTIONAL" in this document are to be interpreted as described in BCP
14 [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here.
1.2. Tree Diagrams 1.2. Tree Diagrams
A simplified graphical representation of the data models is used in A simplified graphical representation of the data models is used in
this document. The meaning of the symbols in these diagrams is as this document. The meaning of the symbols in these diagrams is as
follows: follows:
o Brackets "[" and "]" enclose list keys. o Brackets "[" and "]" enclose list keys.
o Braces "{" and "}" enclose feature names, and indicate that the o Braces "{" and "}" enclose feature names, and indicate that the
skipping to change at page 4, line 27 skipping to change at page 4, line 30
groupings defined in [I-D.ietf-netconf-tls-client-server]. groupings defined in [I-D.ietf-netconf-tls-client-server].
All private keys and trusted certificates are held in the keystore All private keys and trusted certificates are held in the keystore
model defined in [I-D.ietf-netconf-keystore]. model defined in [I-D.ietf-netconf-keystore].
YANG feature statements are used to enable implementations to YANG feature statements are used to enable implementations to
advertise which parts of the model the RESTCONF client supports. advertise which parts of the model the RESTCONF client supports.
2.1. Tree Diagram 2.1. Tree Diagram
Just the container is displayed below, but there is also a grouping
that the container is using.
Note: all lines are folded at column 71 with no '\' character. Note: all lines are folded at column 71 with no '\' character.
module: ietf-restconf-client module: ietf-restconf-client
groupings: +--rw restconf-client
restconf-client +--rw initiate {initiate}?
+---- initiate {initiate}? | +--rw restconf-server* [name]
| +---- restconf-server* [name] | +--rw name string
| +---- name? string | +--rw (transport)
| +---- (transport) | | +--:(tls) {tls-initiate}?
| | +--:(tls) {tls-initiate}? | | +--rw tls
| | +---- tls | | +--rw endpoints
| | +---- endpoints | | | +--rw endpoint* [name]
| | | +---- endpoint* [name] | | | +--rw name string
| | | +---- name? string | | | +--rw address inet:host
| | | +---- address inet:host | | | +--rw port? inet:port-number
| | | +---- port? inet:port-number | | +--rw server-auth
| | +---- server-auth | | | +--rw trusted-ca-certs? leafref
| | | +---- trusted-ca-certs? leafref | | | +--rw trusted-server-certs? leafref
| | | +---- trusted-server-certs? leafref | | +--rw client-auth
| | +---- client-auth | | | +--rw (auth-type)
| | | +---- (auth-type)? | | | +--:(certificate)
| | | +--:(certificate) | | | +--rw certificate? leafref
| | | +---- certificate? leafref | | +--rw hello-params
| | +---- hello-params | | {tls-client-hello-params-config}?
| | {tls-client-hello-params-config}? | | +--rw tls-versions
| | +---- tls-versions | | | +--rw tls-version* identityref
| | | +---- tls-version* identityref | | +--rw cipher-suites
| | +---- cipher-suites | | +--rw cipher-suite* identityref
| | +---- cipher-suite* identityref | +--rw connection-type
| +---- connection-type | | +--rw (connection-type)?
| | +---- (connection-type)? | | +--:(persistent-connection)
| | +--:(persistent-connection) | | | +--rw persistent!
| | | +---- persistent! | | | +--rw idle-timeout? uint32
| | | +---- idle-timeout? uint32 | | | +--rw keep-alives
| | | +---- keep-alives | | | +--rw max-wait? uint16
| | | +---- max-wait? uint16 | | | +--rw max-attempts? uint8
| | | +---- max-attempts? uint8 | | +--:(periodic-connection)
| | +--:(periodic-connection) | | +--rw periodic!
| | +---- periodic! | | +--rw idle-timeout? uint16
| | +---- idle-timeout? uint16 | | +--rw reconnect-timeout? uint16
| | +---- reconnect-timeout? uint16 | +--rw reconnect-strategy
| +---- reconnect-strategy | +--rw start-with? enumeration
| +---- start-with? enumeration | +--rw max-attempts? uint8
| +---- max-attempts? uint8 +--rw listen {listen}?
+---- listen {listen}? +--rw max-sessions? uint16
+---- max-sessions? uint16 +--rw idle-timeout? uint16
+---- idle-timeout? uint16 +--rw endpoint* [name]
+---- endpoint* [name] +--rw name string
+---- name? string +--rw (transport)
+---- (transport) +--:(tls) {tls-listen}?
+--:(tls) {tls-listen}? +--rw tls
+---- tls +--rw address? inet:ip-address
+---- address? inet:ip-address +--rw port? inet:port-number
+---- port? inet:port-number +--rw server-auth
+---- server-auth | +--rw trusted-ca-certs? leafref
| +---- trusted-ca-certs? leafref | +--rw trusted-server-certs? leafref
| +---- trusted-server-certs? leafref +--rw client-auth
+---- client-auth | +--rw (auth-type)
| +---- (auth-type)? | +--:(certificate)
| +--:(certificate) | +--rw certificate? leafref
| +---- certificate? leafref +--rw hello-params
+---- hello-params {tls-client-hello-params-config}?
{tls-client-hello-params-config}? +--rw tls-versions
+---- tls-versions | +--rw tls-version* identityref
| +---- tls-version* identityref +--rw cipher-suites
+---- cipher-suites +--rw cipher-suite* identityref
+---- cipher-suite* identityref
endpoints-container
+---- endpoints
+---- endpoint* [name]
+---- name? string
+---- address inet:host
+---- port? inet:port-number
2.2. Example Usage 2.2. Example Usage
The following example illustrates configuring a RESTCONF client to The following example illustrates configuring a RESTCONF client to
initiate connections, as well as listening for call-home connections. initiate connections, as well as listening for call-home connections.
This example is consistent with the examples presented in Section 2.2 This example is consistent with the examples presented in Section 2.2
of [I-D.ietf-netconf-keystore]. of [I-D.ietf-netconf-keystore].
<restconf-client <restconf-client
skipping to change at page 8, line 8 skipping to change at page 8, line 8
<certificate>tls-ec-cert</certificate> <certificate>tls-ec-cert</certificate>
</client-auth> </client-auth>
</tls> </tls>
</endpoint> </endpoint>
</listen> </listen>
</restconf-client> </restconf-client>
2.3. YANG Model 2.3. YANG Model
This YANG module imports YANG types from [RFC6991] and [RFC7407]. This YANG module imports YANG types from [RFC6991] and [RFC7407].
<CODE BEGINS> file "ietf-restconf-client@2017-06-13.yang" <CODE BEGINS> file "ietf-restconf-client@2017-07-03.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-inet-types { import ietf-inet-types {
prefix inet; prefix inet;
reference reference
skipping to change at page 9, line 13 skipping to change at page 9, line 13
Redistribution and use in source and binary forms, with or Redistribution and use in source and binary forms, with or
without modification, is permitted pursuant to, and subject without modification, is permitted pursuant to, and subject
to the license terms contained in, the Simplified BSD to the license terms contained in, the Simplified BSD
License set forth in Section 4.c of the IETF Trust's License set forth in Section 4.c of the IETF Trust's
Legal Provisions Relating to IETF Documents Legal Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info). (http://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC XXXX; see This version of this YANG module is part of RFC XXXX; see
the RFC itself for full legal notices."; the RFC itself for full legal notices.";
revision "2017-06-13" { revision "2017-07-03" {
description description
"Initial version"; "Initial version";
reference reference
"RFC XXXX: RESTCONF Client and Server Models"; "RFC XXXX: RESTCONF Client and Server Models";
} }
// Features // Features
feature initiate { feature initiate {
description description
skipping to change at page 10, line 7 skipping to change at page 10, line 7
feature tls-listen { feature tls-listen {
description description
"The 'tls-listen' feature indicates that the RESTCONF client "The 'tls-listen' feature indicates that the RESTCONF client
supports opening a port to listen for incoming RESTCONF supports opening a port to listen for incoming RESTCONF
server call-home TLS connections."; server call-home TLS connections.";
reference reference
"RFC 8071: NETCONF Call Home and RESTCONF Call Home"; "RFC 8071: NETCONF Call Home and RESTCONF Call Home";
} }
container restconf-client {
uses restconf-client;
description
"Top-level container for RESTCONF client configuration.";
}
grouping restconf-client { grouping restconf-client {
description description
"Top-level grouping for RESTCONF client configuration."; "Top-level grouping for RESTCONF client configuration.";
container initiate { container initiate {
if-feature initiate; if-feature initiate;
description description
"Configures client initiating underlying TCP connections."; "Configures client initiating underlying TCP connections.";
list restconf-server { list restconf-server {
key name; key name;
skipping to change at page 10, line 41 skipping to change at page 10, line 47
if-feature tls-initiate; if-feature tls-initiate;
container tls { container tls {
description description
"Specifies TLS-specific transport configuration."; "Specifies TLS-specific transport configuration.";
uses endpoints-container { uses endpoints-container {
refine endpoints/endpoint/port { refine endpoints/endpoint/port {
default 443; default 443;
} }
} }
uses ts:tls-client-grouping { uses ts:tls-client-grouping {
refine "client-auth" { refine "client-auth/auth-type" {
must 'certificate'; mandatory true;
description description
"RESTCONF clients MUST pass a client certiticate."; "RESTCONF clients MUST pass some authentication
credentials.";
} }
} }
} }
} // end tls } // end tls
} // end transport } // end transport
container connection-type { container connection-type {
description description
"Indicates the kind of connection to use."; "Indicates the kind of connection to use.";
choice connection-type { choice connection-type {
skipping to change at page 15, line 21 skipping to change at page 15, line 28
description description
"The IP address to listen for call-home connections."; "The IP address to listen for call-home connections.";
} }
leaf port { leaf port {
type inet:port-number; type inet:port-number;
default 4336; default 4336;
description description
"The port number to listen for call-home connections."; "The port number to listen for call-home connections.";
} }
uses ts:tls-client-grouping { uses ts:tls-client-grouping {
refine "client-auth" { refine "client-auth/auth-type" {
must 'certificate'; mandatory true;
description description
"RESTCONF clients MUST pass a client certiticate."; "RESTCONF clients MUST pass some authentication
credentials.";
} }
} }
} }
} }
} // end transport } // end transport
} // end endpoint } // end endpoint
} // end listen } // end listen
} // end restconf-client } // end restconf-client
skipping to change at page 17, line 7 skipping to change at page 17, line 10
groupings defined in [I-D.ietf-netconf-tls-client-server]. groupings defined in [I-D.ietf-netconf-tls-client-server].
All private keys and trusted certificates are held in the keystore All private keys and trusted certificates are held in the keystore
model defined in [I-D.ietf-netconf-keystore]. model defined in [I-D.ietf-netconf-keystore].
YANG feature statements are used to enable implementations to YANG feature statements are used to enable implementations to
advertise which parts of the model the RESTCONF server supports. advertise which parts of the model the RESTCONF server supports.
3.1. Tree Diagram 3.1. Tree Diagram
Just the container is displayed below, but there is also a grouping
that the container is using.
Note: all lines are folded at column 71 with no '\' character. Note: all lines are folded at column 71 with no '\' character.
module: ietf-restconf-server module: ietf-restconf-server
+--rw restconf-server +--rw restconf-server
+--rw listen {listen}? +--rw listen {listen}?
| +--rw max-sessions? uint16 | +--rw max-sessions? uint16
| +--rw endpoint* [name] | +--rw endpoint* [name]
| +--rw name string | +--rw name string
| +--rw (transport) | +--rw (transport)
| +--:(tls) {tls-listen}? | +--:(tls) {tls-listen}?
skipping to change at page 20, line 38 skipping to change at page 20, line 44
</reconnect-strategy> </reconnect-strategy>
</restconf-client> </restconf-client>
</call-home> </call-home>
</restconf-server> </restconf-server>
3.3. YANG Model 3.3. YANG Model
This YANG module imports YANG types from [RFC6991] and [RFC7407]. This YANG module imports YANG types from [RFC6991] and [RFC7407].
<CODE BEGINS> file "ietf-restconf-server@2017-06-13.yang" <CODE BEGINS> file "ietf-restconf-server@2017-07-03.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-netconf-acm { //import ietf-netconf-acm {
// prefix nacm; // prefix nacm;
// reference // reference
// "RFC 6536: Network Configuration Protocol (NETCONF) // "RFC 6536: Network Configuration Protocol (NETCONF)
// Access Control Model"; // Access Control Model";
//} //}
import ietf-inet-types { import ietf-inet-types {
prefix inet; prefix inet;
reference reference
skipping to change at page 22, line 11 skipping to change at page 22, line 16
Redistribution and use in source and binary forms, with or Redistribution and use in source and binary forms, with or
without modification, is permitted pursuant to, and subject without modification, is permitted pursuant to, and subject
to the license terms contained in, the Simplified BSD to the license terms contained in, the Simplified BSD
License set forth in Section 4.c of the IETF Trust's License set forth in Section 4.c of the IETF Trust's
Legal Provisions Relating to IETF Documents Legal Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info). (http://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC XXXX; see This version of this YANG module is part of RFC XXXX; see
the RFC itself for full legal notices."; the RFC itself for full legal notices.";
revision "2017-06-13" { revision "2017-07-03" {
description description
"Initial version"; "Initial version";
reference reference
"RFC XXXX: RESTCONF Client and Server Models"; "RFC XXXX: RESTCONF Client and Server Models";
} }
// Features // Features
feature listen { feature listen {
description description
skipping to change at page 23, line 17 skipping to change at page 23, line 21
feature client-cert-auth { feature client-cert-auth {
description description
"The client-cert-auth feature indicates that the RESTCONF "The client-cert-auth feature indicates that the RESTCONF
server supports the ClientCertificate authentication scheme."; server supports the ClientCertificate authentication scheme.";
reference reference
"RFC ZZZZ: Client Authentication over New TLS Connection"; "RFC ZZZZ: Client Authentication over New TLS Connection";
} }
// top-level container // top-level container
container restconf-server { container restconf-server {
uses restconf-server;
description description
"Top-level container for RESTCONF server configuration."; "Top-level container for RESTCONF server configuration.";
}
grouping restconf-server {
description
"Top-level grouping for RESTCONF server configuration.";
container listen { container listen {
if-feature listen; if-feature listen;
description description
"Configures listen behavior"; "Configures listen behavior";
leaf max-sessions { leaf max-sessions {
type uint16; type uint16;
default 0; // should this be 'max'? default 0; // should this be 'max'?
description description
"Specifies the maximum number of concurrent sessions "Specifies the maximum number of concurrent sessions
skipping to change at page 24, line 19 skipping to change at page 24, line 30
special meanings (e.g., '0.0.0.0' and '::')."; special meanings (e.g., '0.0.0.0' and '::').";
} }
leaf port { leaf port {
type inet:port-number; type inet:port-number;
default 443; default 443;
description description
"The local port number on this interface the TLS server "The local port number on this interface the TLS server
listens on."; listens on.";
} }
uses ts:tls-server-grouping { uses ts:tls-server-grouping {
refine "client-auth" {
must 'trusted-ca-certs or trusted-client-certs';
description
"RESTCONF servers MUST be able to validate clients.";
}
augment "client-auth" { augment "client-auth" {
description description
"Augments in the cert-to-name structure."; "Augments in the cert-to-name structure.";
uses cert-maps-grouping; uses cert-maps-grouping;
} }
} }
} } // end tls container
} } // end tls case
} } // end transport
} } // end endpoint
} } // end listen
container call-home { container call-home {
if-feature call-home; if-feature call-home;
description description
"Configures call-home behavior"; "Configures call-home behavior";
list restconf-client { list restconf-client {
key name; key name;
description description
"List of RESTCONF clients the RESTCONF server is to "List of RESTCONF clients the RESTCONF server is to
initiate call-home connections to."; initiate call-home connections to.";
skipping to change at page 25, line 13 skipping to change at page 25, line 29
container tls { container tls {
description description
"Specifies TLS-specific call-home transport "Specifies TLS-specific call-home transport
configuration."; configuration.";
uses endpoints-container { uses endpoints-container {
refine endpoints/endpoint/port { refine endpoints/endpoint/port {
default 4336; default 4336;
} }
} }
uses ts:tls-server-grouping { uses ts:tls-server-grouping {
refine "client-auth" {
must 'trusted-ca-certs or trusted-client-certs';
description
"RESTCONF servers MUST be able to validate clients.";
}
augment "client-auth" { augment "client-auth" {
description description
"Augments in the cert-to-name structure."; "Augments in the cert-to-name structure.";
uses cert-maps-grouping; uses cert-maps-grouping;
} }
} }
} }
} }
} }
container connection-type { container connection-type {
skipping to change at page 31, line 23 skipping to change at page 31, line 47
Juergen Schoenwaelder and was partly funded by Flamingo, a Network of Juergen Schoenwaelder and was partly funded by Flamingo, a Network of
Excellence project (ICT-318488) supported by the European Commission Excellence project (ICT-318488) supported by the European Commission
under its Seventh Framework Programme. under its Seventh Framework Programme.
7. References 7. References
7.1. Normative References 7.1. Normative References
[I-D.ietf-netconf-keystore] [I-D.ietf-netconf-keystore]
Watsen, K., "Keystore Model", draft-ietf-netconf- Watsen, K., "Keystore Model", draft-ietf-netconf-
keystore-01 (work in progress), March 2017. keystore-02 (work in progress), June 2017.
[I-D.ietf-netconf-tls-client-server] [I-D.ietf-netconf-tls-client-server]
Watsen, K. and G. Wu, "TLS Client and Server Models", Watsen, K. and G. Wu, "TLS Client and Server Models",
draft-ietf-netconf-tls-client-server-02 (work in draft-ietf-netconf-tls-client-server-03 (work in
progress), March 2017. progress), June 2017.
[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,
<http://www.rfc-editor.org/info/rfc2119>. <http://www.rfc-editor.org/info/rfc2119>.
[RFC6536] Bierman, A. and M. Bjorklund, "Network Configuration [RFC6536] Bierman, A. and M. Bjorklund, "Network Configuration
Protocol (NETCONF) Access Control Model", RFC 6536, Protocol (NETCONF) Access Control Model", RFC 6536,
DOI 10.17487/RFC6536, March 2012, DOI 10.17487/RFC6536, March 2012,
<http://www.rfc-editor.org/info/rfc6536>. <http://www.rfc-editor.org/info/rfc6536>.
skipping to change at page 32, line 5 skipping to change at page 32, line 27
<http://www.rfc-editor.org/info/rfc6991>. <http://www.rfc-editor.org/info/rfc6991>.
[RFC7407] Bjorklund, M. and J. Schoenwaelder, "A YANG Data Model for [RFC7407] Bjorklund, M. and J. Schoenwaelder, "A YANG Data Model for
SNMP Configuration", RFC 7407, DOI 10.17487/RFC7407, SNMP Configuration", RFC 7407, DOI 10.17487/RFC7407,
December 2014, <http://www.rfc-editor.org/info/rfc7407>. December 2014, <http://www.rfc-editor.org/info/rfc7407>.
[RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language", [RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language",
RFC 7950, DOI 10.17487/RFC7950, August 2016, RFC 7950, DOI 10.17487/RFC7950, August 2016,
<http://www.rfc-editor.org/info/rfc7950>. <http://www.rfc-editor.org/info/rfc7950>.
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <http://www.rfc-editor.org/info/rfc8174>.
7.2. Informative References 7.2. Informative References
[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,
<http://www.rfc-editor.org/info/rfc3688>. <http://www.rfc-editor.org/info/rfc3688>.
[RFC5246] Dierks, T. and E. Rescorla, "The Transport Layer Security [RFC5246] Dierks, T. and E. Rescorla, "The Transport Layer Security
(TLS) Protocol Version 1.2", RFC 5246, (TLS) Protocol Version 1.2", RFC 5246,
DOI 10.17487/RFC5246, August 2008, DOI 10.17487/RFC5246, August 2008,
<http://www.rfc-editor.org/info/rfc5246>. <http://www.rfc-editor.org/info/rfc5246>.
skipping to change at page 33, line 32 skipping to change at page 34, line 32
o Updated the ietf-restconf-server module to accomodate new grouping o Updated the ietf-restconf-server module to accomodate new grouping
'ietf-tls-server-grouping'. 'ietf-tls-server-grouping'.
A.4. 02 to 03 A.4. 02 to 03
o Refined use of tls-client-grouping to add a must statement o Refined use of tls-client-grouping to add a must statement
indicating that the TLS client must specify a client-certificate. indicating that the TLS client must specify a client-certificate.
o Changed restconf-client??? to be a grouping (not a container). o Changed restconf-client??? to be a grouping (not a container).
A.5. 03 to 04
o Added RFC 8174 to Requirements Language Section.
o Replaced refine statement in ietf-restconf-client to add a
mandatory true.
o Added refine statement in ietf-restconf-server to add a must
statement.
o Now there are containers and groupings, for both the client and
server models.
Authors' Addresses Authors' Addresses
Kent Watsen Kent Watsen
Juniper Networks Juniper Networks
EMail: kwatsen@juniper.net EMail: kwatsen@juniper.net
Juergen Schoenwaelder Juergen Schoenwaelder
Jacobs University Bremen Jacobs University Bremen
EMail: j.schoenwaelder@jacobs-university.de EMail: j.schoenwaelder@jacobs-university.de
 End of changes. 31 change blocks. 
106 lines changed or deleted 147 lines changed or added

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