draft-ietf-netconf-restconf-client-server-02.txt   draft-ietf-netconf-restconf-client-server-03.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: September 14, 2017 Jacobs University Bremen Expires: December 15, 2017 Jacobs University Bremen
March 13, 2017 June 13, 2017
RESTCONF Client and Server Models RESTCONF Client and Server Models
draft-ietf-netconf-restconf-client-server-02 draft-ietf-netconf-restconf-client-server-03
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-03-13" --> the publication date of this draft o "2017-06-13" --> the publication date of this draft
The following two Appendix sections are to be removed prior to The following Appendix section is to be removed prior to publication:
publication:
o Appendix A. Change Log o Appendix A. Change Log
o Appendix B. Open Issues
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 September 14, 2017. This Internet-Draft will expire on December 15, 2017.
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 2, line 51 skipping to change at page 2, line 49
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3 1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3
1.2. Tree Diagrams . . . . . . . . . . . . . . . . . . . . . . 3 1.2. Tree Diagrams . . . . . . . . . . . . . . . . . . . . . . 3
2. The RESTCONF Client Model . . . . . . . . . . . . . . . . . . 4 2. The RESTCONF Client Model . . . . . . . . . . . . . . . . . . 4
2.1. Tree Diagram . . . . . . . . . . . . . . . . . . . . . . 4 2.1. Tree Diagram . . . . . . . . . . . . . . . . . . . . . . 4
2.2. Example Usage . . . . . . . . . . . . . . . . . . . . . . 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 . . . . . . . . . . . . . . . . . . . . . . 16 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 . . . . . . . . . . . . . 30
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 30 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 31
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 31 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 31
7.1. Normative References . . . . . . . . . . . . . . . . . . 31 7.1. Normative References . . . . . . . . . . . . . . . . . . 31
7.2. Informative References . . . . . . . . . . . . . . . . . 31 7.2. Informative References . . . . . . . . . . . . . . . . . 32
Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 33 Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 33
A.1. server-model-09 to 00 . . . . . . . . . . . . . . . . . . 33 A.1. server-model-09 to 00 . . . . . . . . . . . . . . . . . . 33
A.2. 00 to 01 . . . . . . . . . . . . . . . . . . . . . . . . 33 A.2. 00 to 01 . . . . . . . . . . . . . . . . . . . . . . . . 33
A.3. 01 to 02 . . . . . . . . . . . . . . . . . . . . . . . . 33 A.3. 01 to 02 . . . . . . . . . . . . . . . . . . . . . . . . 33
Appendix B. Open Issues . . . . . . . . . . . . . . . . . . . . 33 A.4. 02 to 03 . . . . . . . . . . . . . . . . . . . . . . . . 33
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 33 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 33
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].
skipping to change at page 4, line 33 skipping to change at page 4, line 30
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
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
+--rw restconf-client groupings:
+--rw initiate {initiate}? restconf-client
| +--rw restconf-server* [name] +---- initiate {initiate}?
| +--rw name string | +---- restconf-server* [name]
| +--rw (transport) | +---- name? string
| | +--:(tls) {tls-initiate}? | +---- (transport)
| | +--rw tls | | +--:(tls) {tls-initiate}?
| | +--rw endpoints | | +---- tls
| | | +--rw endpoint* [name] | | +---- endpoints
| | | +--rw name string | | | +---- endpoint* [name]
| | | +--rw address inet:host | | | +---- name? string
| | | +--rw port? inet:port-number | | | +---- address inet:host
| | +--rw server-auth | | | +---- port? inet:port-number
| | | +--rw trusted-ca-certs? leafref | | +---- server-auth
| | | +--rw trusted-server-certs? leafref | | | +---- trusted-ca-certs? leafref
| | +--rw client-auth | | | +---- trusted-server-certs? leafref
| | | +--rw (auth-type)? | | +---- client-auth
| | | +--:(certificate) | | | +---- (auth-type)?
| | | +--rw certificate? leafref | | | +--:(certificate)
| | +--rw hello-params | | | +---- certificate? leafref
| | {tls-client-hello-params-config}? | | +---- hello-params
| | +--rw tls-versions | | {tls-client-hello-params-config}?
| | | +--rw tls-version* identityref | | +---- tls-versions
| | +--rw cipher-suites | | | +---- tls-version* identityref
| | +--rw cipher-suite* identityref | | +---- cipher-suites
| +--rw connection-type | | +---- cipher-suite* identityref
| | +--rw (connection-type)? | +---- connection-type
| | +--:(persistent-connection) | | +---- (connection-type)?
| | | +--rw persistent! | | +--:(persistent-connection)
| | | +--rw idle-timeout? uint32 | | | +---- persistent!
| | | +--rw keep-alives | | | +---- idle-timeout? uint32
| | | +--rw max-wait? uint16 | | | +---- keep-alives
| | | +--rw max-attempts? uint8 | | | +---- max-wait? uint16
| | +--:(periodic-connection) | | | +---- max-attempts? uint8
| | +--rw periodic! | | +--:(periodic-connection)
| | +--rw idle-timeout? uint16 | | +---- periodic!
| | +--rw reconnect-timeout? uint16 | | +---- idle-timeout? uint16
| +--rw reconnect-strategy | | +---- reconnect-timeout? uint16
| +--rw start-with? enumeration | +---- reconnect-strategy
| +--rw max-attempts? uint8 | +---- start-with? enumeration
+--rw listen {listen}? | +---- max-attempts? uint8
+--rw max-sessions? uint16 +---- listen {listen}?
+--rw idle-timeout? uint16 +---- max-sessions? uint16
+--rw endpoint* [name] +---- idle-timeout? uint16
+--rw name string +---- endpoint* [name]
+--rw (transport) +---- name? string
+--:(tls) {tls-listen}? +---- (transport)
+--rw tls +--:(tls) {tls-listen}?
+--rw address? inet:ip-address +---- tls
+--rw port? inet:port-number +---- address? inet:ip-address
+--rw server-auth +---- port? inet:port-number
| +--rw trusted-ca-certs? leafref +---- server-auth
| +--rw trusted-server-certs? leafref | +---- trusted-ca-certs? leafref
+--rw client-auth | +---- trusted-server-certs? leafref
| +--rw (auth-type)? +---- client-auth
| +--:(certificate) | +---- (auth-type)?
| +--rw certificate? leafref | +--:(certificate)
+--rw hello-params | +---- certificate? leafref
{tls-client-hello-params-config}? +---- hello-params
+--rw tls-versions {tls-client-hello-params-config}?
| +--rw tls-version* identityref +---- tls-versions
+--rw cipher-suites | +---- tls-version* identityref
+--rw cipher-suite* identityref +---- cipher-suites
+---- 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-03-13.yang" <CODE BEGINS> file "ietf-restconf-client@2017-06-13.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
"RFC 6991: Common YANG Data Types"; "RFC 6991: Common YANG Data Types";
} }
import ietf-tls-client { import ietf-tls-client {
prefix ts; prefix ts;
revision-date 2017-03-13; // stable grouping definitions revision-date 2017-06-13; // stable grouping definitions
reference reference
"RFC ZZZZ: TLS Client and Server Models"; "RFC ZZZZ: TLS Client and Server Models";
} }
organization organization
"IETF NETCONF (Network Configuration) Working Group"; "IETF NETCONF (Network Configuration) Working Group";
contact contact
"WG Web: <http://tools.ietf.org/wg/restconf/> "WG Web: <http://tools.ietf.org/wg/restconf/>
WG List: <mailto:restconf@ietf.org> WG List: <mailto:restconf@ietf.org>
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-03-13" { revision "2017-06-13" {
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 { grouping restconf-client {
description description
"Top-level container 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;
description description
"List of RESTCONF servers the RESTCONF client is to initiate "List of RESTCONF servers the RESTCONF client is to initiate
connections to."; connections to.";
skipping to change at page 10, line 40 skipping to change at page 10, line 40
case tls { case tls {
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" {
must 'certificate';
description
"RESTCONF clients MUST pass a client certiticate.";
}
}
} }
} // 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 {
description description
skipping to change at page 15, line 13 skipping to change at page 15, line 20
type inet:ip-address; type inet:ip-address;
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" {
must 'certificate';
description
"RESTCONF clients MUST pass a client certiticate.";
}
}
} }
} }
} // end transport } // end transport
} // end endpoint } // end endpoint
} // end listen } // end listen
} // end restconf-client } // end restconf-client
grouping endpoints-container { grouping endpoints-container {
description description
skipping to change at page 20, line 21 skipping to change at page 20, line 38
</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-03-13.yang" <CODE BEGINS> file "ietf-restconf-server@2017-06-13.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
skipping to change at page 20, line 50 skipping to change at page 21, line 20
} }
import ietf-x509-cert-to-name { import ietf-x509-cert-to-name {
prefix x509c2n; prefix x509c2n;
reference reference
"RFC 7407: A YANG Data Model for SNMP Configuration"; "RFC 7407: A YANG Data Model for SNMP Configuration";
} }
import ietf-tls-server { import ietf-tls-server {
prefix ts; prefix ts;
revision-date 2017-03-13; // stable grouping definitions revision-date 2017-06-13; // stable grouping definitions
reference reference
"RFC ZZZZ: TLS Client and Server Models"; "RFC ZZZZ: TLS Client and Server Models";
} }
organization organization
"IETF NETCONF (Network Configuration) Working Group"; "IETF NETCONF (Network Configuration) Working Group";
contact contact
"WG Web: <http://tools.ietf.org/wg/netconf/> "WG Web: <http://tools.ietf.org/wg/netconf/>
WG List: <mailto:netconf@ietf.org> WG List: <mailto:netconf@ietf.org>
skipping to change at page 21, line 41 skipping to change at page 22, line 11
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-03-13" { revision "2017-06-13" {
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
"The 'listen' feature indicates that the RESTCONF server "The 'listen' feature indicates that the RESTCONF server
supports opening a port to accept RESTCONF client connections supports opening a port to accept RESTCONF client connections
using at least one transport (e.g., TLS, etc.)."; using at least one transport (e.g., TLS, etc.).";
} }
feature tls-listen { feature tls-listen {
description description
"The 'tls-listen' feature indicates that the RESTCONF server "The 'tls-listen' feature indicates that the RESTCONF server
skipping to change at page 30, line 41 skipping to change at page 31, line 9
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 XXXX reference: RFC XXXX
6. Acknowledgements 6. 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, David Lamparter, Alan Luchuk, Bjorklund, Benoit Claise, Mehmet Ersue, Balazs Kovacs, David
Ladislav Lhotka, Radek Krejci, Tom Petch, Phil Shafer, Sean Turner, Lamparter, Alan Luchuk, Ladislav Lhotka, Radek Krejci, Tom Petch,
and Bert Wijnen. Phil Shafer, Sean Turner, and Bert Wijnen.
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. and G. Wu, "Keystore Model", draft-ietf- Watsen, K., "Keystore Model", draft-ietf-netconf-
netconf-keystore-00 (work in progress), October 2016. keystore-01 (work in progress), March 2017.
[I-D.ietf-netconf-tls-client-server] [I-D.ietf-netconf-tls-client-server]
Watsen, K., "TLS Client and Server Models", draft-ietf- Watsen, K. and G. Wu, "TLS Client and Server Models",
netconf-tls-client-server-01 (work in progress), November draft-ietf-netconf-tls-client-server-02 (work in
2016. progress), March 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 33, line 25 skipping to change at page 33, line 25
o Renamed "keychain" to "keystore". o Renamed "keychain" to "keystore".
A.3. 01 to 02 A.3. 01 to 02
o Filled in previously missing 'ietf-restconf-client' module. o Filled in previously missing 'ietf-restconf-client' module.
o Updated the ietf-restconf-server module to accomodate new grouping o Updated the ietf-restconf-server module to accomodate new grouping
'ietf-tls-server-grouping'. 'ietf-tls-server-grouping'.
Appendix B. Open Issues A.4. 02 to 03
Please see: https://github.com/netconf-wg/restconf-client-server/ o Refined use of tls-client-grouping to add a must statement
issues. indicating that the TLS client must specify a client-certificate.
o Changed restconf-client??? to be a grouping (not a container).
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
 End of changes. 27 change blocks. 
97 lines changed or deleted 117 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/