draft-ietf-netconf-netconf-client-server-02.txt   draft-ietf-netconf-netconf-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 G. Wu Intended status: Standards Track G. Wu
Expires: September 14, 2017 Cisco Networks Expires: December 15, 2017 Cisco Networks
J. Schoenwaelder J. Schoenwaelder
Jacobs University Bremen Jacobs University Bremen
March 13, 2017 June 13, 2017
NETCONF Client and Server Models NETCONF Client and Server Models
draft-ietf-netconf-netconf-client-server-02 draft-ietf-netconf-netconf-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
NETCONF client and the other module to configure a NETCONF server. NETCONF client and the other module to configure a NETCONF server.
Both modules support both the SSH and TLS transport protocols, and Both modules support both the SSH and TLS transport protocols, and
support both standard NETCONF and NETCONF Call Home connections. support both standard NETCONF and NETCONF 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 8 skipping to change at page 2, line 8
o "YYYY" --> the assigned RFC value for I-D.ietf-netconf-ssh-client- o "YYYY" --> the assigned RFC value for I-D.ietf-netconf-ssh-client-
server server
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 3, line 21 skipping to change at page 3, line 21
2.1. Tree Diagram . . . . . . . . . . . . . . . . . . . . . . 5 2.1. Tree Diagram . . . . . . . . . . . . . . . . . . . . . . 5
2.2. Example Usage . . . . . . . . . . . . . . . . . . . . . . 8 2.2. Example Usage . . . . . . . . . . . . . . . . . . . . . . 8
2.3. YANG Model . . . . . . . . . . . . . . . . . . . . . . . 10 2.3. YANG Model . . . . . . . . . . . . . . . . . . . . . . . 10
3. The NETCONF Server Model . . . . . . . . . . . . . . . . . . 19 3. The NETCONF Server Model . . . . . . . . . . . . . . . . . . 19
3.1. Tree Diagram . . . . . . . . . . . . . . . . . . . . . . 20 3.1. Tree Diagram . . . . . . . . . . . . . . . . . . . . . . 20
3.2. Example Usage . . . . . . . . . . . . . . . . . . . . . . 23 3.2. Example Usage . . . . . . . . . . . . . . . . . . . . . . 23
3.3. YANG Model . . . . . . . . . . . . . . . . . . . . . . . 26 3.3. YANG Model . . . . . . . . . . . . . . . . . . . . . . . 26
4. Design Considerations . . . . . . . . . . . . . . . . . . . . 37 4. Design Considerations . . . . . . . . . . . . . . . . . . . . 37
4.1. Support all NETCONF transports . . . . . . . . . . . . . 37 4.1. Support all NETCONF transports . . . . . . . . . . . . . 37
4.2. Enable each transport to select which keys to use . . . . 37 4.2. Enable each transport to select which keys to use . . . . 37
4.3. Support authenticating NETCONF clients certificates . . . 37 4.3. Support authenticating NETCONF clients certificates . . . 38
4.4. Support mapping authenticated NETCONF client certificates 4.4. Support mapping authenticated NETCONF client certificates
to usernames . . . . . . . . . . . . . . . . . . . . . . 38 to usernames . . . . . . . . . . . . . . . . . . . . . . 38
4.5. Support both listening for connections and call home . . 38 4.5. Support both listening for connections and call home . . 38
4.6. For Call Home connections . . . . . . . . . . . . . . . . 38 4.6. For Call Home connections . . . . . . . . . . . . . . . . 38
4.6.1. Support more than one NETCONF client . . . . . . . . 38 4.6.1. Support more than one NETCONF client . . . . . . . . 38
4.6.2. Support NETCONF clients having more than one endpoint 38 4.6.2. Support NETCONF clients having more than one endpoint 38
4.6.3. Support a reconnection strategy . . . . . . . . . . . 38 4.6.3. Support a reconnection strategy . . . . . . . . . . . 39
4.6.4. Support both persistent and periodic connections . . 39 4.6.4. Support both persistent and periodic connections . . 39
4.6.5. Reconnection strategy for periodic connections . . . 39 4.6.5. Reconnection strategy for periodic connections . . . 39
4.6.6. Keep-alives for persistent connections . . . . . . . 39 4.6.6. Keep-alives for persistent connections . . . . . . . 39
4.6.7. Customizations for periodic connections . . . . . . . 39 4.6.7. Customizations for periodic connections . . . . . . . 39
5. Security Considerations . . . . . . . . . . . . . . . . . . . 39 5. Security Considerations . . . . . . . . . . . . . . . . . . . 40
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 41 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 41
6.1. The IETF XML Registry . . . . . . . . . . . . . . . . . . 41 6.1. The IETF XML Registry . . . . . . . . . . . . . . . . . . 41
6.2. The YANG Module Names Registry . . . . . . . . . . . . . 41 6.2. The YANG Module Names Registry . . . . . . . . . . . . . 41
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 41 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 41
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 42 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 42
8.1. Normative References . . . . . . . . . . . . . . . . . . 42 8.1. Normative References . . . . . . . . . . . . . . . . . . 42
8.2. Informative References . . . . . . . . . . . . . . . . . 43 8.2. Informative References . . . . . . . . . . . . . . . . . 43
Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 44 Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 44
A.1. server-model-09 to 00 . . . . . . . . . . . . . . . . . . 44 A.1. server-model-09 to 00 . . . . . . . . . . . . . . . . . . 44
A.2. 00 to 01 . . . . . . . . . . . . . . . . . . . . . . . . 44 A.2. 00 to 01 . . . . . . . . . . . . . . . . . . . . . . . . 44
A.3. 01 to 02 . . . . . . . . . . . . . . . . . . . . . . . . 44 A.3. 01 to 02 . . . . . . . . . . . . . . . . . . . . . . . . 44
Appendix B. Open Issues . . . . . . . . . . . . . . . . . . . . 44 A.4. 02 to 03 . . . . . . . . . . . . . . . . . . . . . . . . 44
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 44 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 44
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 NETCONF client and the other module to configure a configure a NETCONF client and the other module to configure a
NETCONF server. Both modules support both the SSH and TLS transport NETCONF server. Both modules support both the SSH and TLS transport
protocols, and support both standard NETCONF and NETCONF Call Home protocols, and support both standard NETCONF and NETCONF Call Home
connections. connections.
skipping to change at page 5, line 15 skipping to change at page 5, line 15
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 NETCONF client supports. advertise which parts of the model the NETCONF 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-netconf-client module: ietf-netconf-client
+--rw netconf-client groupings:
+--rw initiate {initiate}? netconf-client
| +--rw netconf-server* [name] +---- initiate {initiate}?
| +--rw name string | +---- netconf-server* [name]
| +--rw (transport) | +---- name? string
| +---- (transport)
| | +--:(ssh) {ssh-initiate}? | | +--:(ssh) {ssh-initiate}?
| | | +--rw ssh | | | +---- ssh
| | | +--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-ssh-host-keys? | | | | +---- trusted-ssh-host-keys?
| | | | | -> /ks:keystore/trusted-host-keys/name | | | | | -> /ks:keystore/trusted-host-keys/name
| | | | +--rw trusted-ca-certs? leafref | | | | +---- trusted-ca-certs? leafref
| | | | | {sshcom:ssh-x509-certs}? | | | | | {sshcom:ssh-x509-certs}?
| | | | +--rw trusted-server-certs? leafref | | | | +---- trusted-server-certs? leafref
| | | | {sshcom:ssh-x509-certs}? | | | | {sshcom:ssh-x509-certs}?
| | | +--rw client-auth | | | +---- client-auth
| | | | +--rw username? string | | | | +---- username? string
| | | | +--rw (auth-type)? | | | | +---- (auth-type)?
| | | | +--:(certificate) | | | | +--:(certificate)
| | | | | +--rw certificate? leafref | | | | | +---- certificate? leafref
| | | | | {sshcom:ssh-x509-certs}? | | | | | {sshcom:ssh-x509-certs}?
| | | | +--:(public-key) | | | | +--:(public-key)
| | | | | +--rw public-key? | | | | | +---- public-key?
| | | | | -> /ks:keystore/keys/key/name | | | | | -> /ks:keystore/keys/key/name
| | | | +--:(password) | | | | +--:(password)
| | | | +--rw password? union | | | | +---- password? string
| | | +--rw transport-params | | | +---- transport-params
| | | {ssh-client-transport-params-config}? | | | {ssh-client-transport-params-config}?
| | | +--rw host-key | | | +---- host-key
| | | | +--rw host-key-alg* identityref | | | | +---- host-key-alg* identityref
| | | +--rw key-exchange | | | +---- key-exchange
| | | | +--rw key-exchange-alg* identityref | | | | +---- key-exchange-alg* identityref
| | | +--rw encryption | | | +---- encryption
| | | | +--rw encryption-alg* identityref | | | | +---- encryption-alg* identityref
| | | +--rw mac | | | +---- mac
| | | | +--rw mac-alg* identityref | | | | +---- mac-alg* identityref
| | | +--rw compression | | | +---- compression
| | | +--rw compression-alg* identityref | | | +---- compression-alg* identityref
| | +--:(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)
+--:(ssh) {ssh-listen}? +--:(ssh) {ssh-listen}?
| +--rw ssh | +---- ssh
| +--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-ssh-host-keys? | | +---- trusted-ssh-host-keys?
| | | -> /ks:keystore/trusted-host-keys/name | | | -> /ks:keystore/trusted-host-keys/name
| | +--rw trusted-ca-certs? leafref | | +---- trusted-ca-certs? leafref
| | | {sshcom:ssh-x509-certs}? | | | {sshcom:ssh-x509-certs}?
| | +--rw trusted-server-certs? leafref | | +---- trusted-server-certs? leafref
| | {sshcom:ssh-x509-certs}? | | {sshcom:ssh-x509-certs}?
| +--rw client-auth | +---- client-auth
| | +--rw username? string | | +---- username? string
| | +--rw (auth-type)? | | +---- (auth-type)?
| | +--:(certificate) | | +--:(certificate)
| | | +--rw certificate? leafref | | | +---- certificate? leafref
| | | {sshcom:ssh-x509-certs}? | | | {sshcom:ssh-x509-certs}?
| | +--:(public-key) | | +--:(public-key)
| | | +--rw public-key? | | | +---- public-key?
| | | -> /ks:keystore/keys/key/name | | | -> /ks:keystore/keys/key/name
| | +--:(password) | | +--:(password)
| | +--rw password? union | | +---- password? string
| +--rw transport-params | +---- transport-params
| {ssh-client-transport-params-config}? | {ssh-client-transport-params-config}?
| +--rw host-key | +---- host-key
| | +--rw host-key-alg* identityref | | +---- host-key-alg* identityref
| +--rw key-exchange | +---- key-exchange
| | +--rw key-exchange-alg* identityref | | +---- key-exchange-alg* identityref
| +--rw encryption | +---- encryption
| | +--rw encryption-alg* identityref | | +---- encryption-alg* identityref
| +--rw mac | +---- mac
| | +--rw mac-alg* identityref | | +---- mac-alg* identityref
| +--rw compression | +---- compression
| +--rw compression-alg* identityref | +---- compression-alg* identityref
+--:(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 NETCONF client to The following example illustrates configuring a NETCONF client to
initiate connections, using both the SSH and TLS transport protocols, initiate connections, using both the SSH and TLS transport protocols,
as well as listening for call-home connections, again using both the as well as listening for call-home connections, again using both the
SSH and TLS transport protocols. SSH and TLS transport protocols.
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].
skipping to change at page 10, line 8 skipping to change at page 10, line 8
<public-key>ex-rsa-key</public-key> <public-key>ex-rsa-key</public-key>
</client-auth> </client-auth>
</ssh> </ssh>
</endpoint> </endpoint>
</listen> </listen>
</netconf-client> </netconf-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-netconf-client@2017-03-13.yang" <CODE BEGINS> file "ietf-netconf-client@2017-06-13.yang"
module ietf-netconf-client { module ietf-netconf-client {
yang-version 1.1; yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-netconf-client"; namespace "urn:ietf:params:xml:ns:yang:ietf-netconf-client";
prefix "ncc"; prefix "ncc";
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-ssh-client { import ietf-ssh-client {
prefix ss; prefix ss;
revision-date 2017-03-13; // stable grouping definitions revision-date 2017-06-13; // stable grouping definitions
reference reference
"RFC YYYY: SSH Client and Server Models"; "RFC YYYY: SSH Client and Server Models";
} }
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/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 11, line 20 skipping to change at page 11, line 20
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: NETCONF Client and Server Models"; "RFC XXXX: NETCONF Client and Server Models";
} }
// Features // Features
feature initiate { feature initiate {
description description
skipping to change at page 12, line 33 skipping to change at page 12, line 33
feature tls-listen { feature tls-listen {
description description
"The 'tls-listen' feature indicates that the NETCONF client "The 'tls-listen' feature indicates that the NETCONF client
supports opening a port to listen for incoming NETCONF supports opening a port to listen for incoming NETCONF
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 netconf-client { grouping netconf-client {
description description
"Top-level container for NETCONF client configuration."; "Top-level grouping for NETCONF 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 netconf-server { list netconf-server {
key name; key name;
description description
"List of NETCONF servers the NETCONF client is to initiate "List of NETCONF servers the NETCONF client is to initiate
connections to."; connections to.";
skipping to change at page 13, line 31 skipping to change at page 13, line 31
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 6513; default 6513;
} }
} }
uses ts:tls-client-grouping; uses ts:tls-client-grouping {
refine "client-auth" {
must 'certificate';
description
"NETCONF/TLS 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 18, line 26 skipping to change at page 18, line 32
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 4335; default 4335;
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
"NETCONF/TLS clients MUST pass a client certiticate.";
}
}
} }
} }
} // end transport } // end transport
} // end endpoint } // end endpoint
} // end listen } // end listen
} // end netconf-client } // end netconf-client
grouping endpoints-container { grouping endpoints-container {
description description
skipping to change at page 26, line 20 skipping to change at page 26, line 30
<max-attempts>3</max-attempts> <max-attempts>3</max-attempts>
</reconnect-strategy> </reconnect-strategy>
</netconf-client> </netconf-client>
</call-home> </call-home>
</netconf-server> </netconf-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-netconf-server@2017-03-13.yang" <CODE BEGINS> file "ietf-netconf-server@2017-06-13.yang"
module ietf-netconf-server { module ietf-netconf-server {
yang-version 1.1; yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-netconf-server"; namespace "urn:ietf:params:xml:ns:yang:ietf-netconf-server";
prefix "ncs"; prefix "ncs";
import ietf-inet-types { import ietf-inet-types {
prefix inet; prefix inet;
reference reference
skipping to change at page 26, line 42 skipping to change at page 27, line 4
} }
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-ssh-server { import ietf-ssh-server {
prefix ss; prefix ss;
revision-date 2017-03-13; // stable grouping definitions revision-date 2017-06-13; // stable grouping definitions
reference reference
"RFC YYYY: SSH Client and Server Models"; "RFC YYYY: SSH Client and Server Models";
} }
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 27, line 34 skipping to change at page 27, line 43
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: NETCONF Client and Server Models"; "RFC XXXX: NETCONF Client and Server Models";
} }
// Features // Features
feature listen { feature listen {
description description
"The 'listen' feature indicates that the NETCONF server "The 'listen' feature indicates that the NETCONF server
supports opening a port to accept NETCONF client connections supports opening a port to accept NETCONF client connections
using at least one transport (e.g., SSH, TLS, etc.)."; using at least one transport (e.g., SSH, TLS, etc.).";
} }
feature ssh-listen { feature ssh-listen {
description description
"The 'ssh-listen' feature indicates that the NETCONF server "The 'ssh-listen' feature indicates that the NETCONF server
supports opening a port to accept NETCONF over SSH supports opening a port to accept NETCONF over SSH
client connections."; client connections.";
reference reference
"RFC 6242: Using the NETCONF Protocol over Secure Shell (SSH)"; "RFC 6242: Using the NETCONF Protocol over Secure Shell (SSH)";
} }
feature tls-listen { feature tls-listen {
skipping to change at page 41, line 41 skipping to change at page 41, line 45
name: ietf-netconf-server name: ietf-netconf-server
namespace: urn:ietf:params:xml:ns:yang:ietf-netconf-server namespace: urn:ietf:params:xml:ns:yang:ietf-netconf-server
prefix: ncs prefix: ncs
reference: RFC XXXX reference: RFC XXXX
7. Acknowledgements 7. 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.
8. References 8. References
8.1. Normative References 8.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-ssh-client-server] [I-D.ietf-netconf-ssh-client-server]
Watsen, K. and G. Wu, "SSH Client and Server Models", Watsen, K. and G. Wu, "SSH Client and Server Models",
draft-ietf-netconf-ssh-client-server-01 (work in draft-ietf-netconf-ssh-client-server-02 (work in
progress), November 2016. 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>.
[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,
<http://www.rfc-editor.org/info/rfc6241>. <http://www.rfc-editor.org/info/rfc6241>.
skipping to change at page 44, line 31 skipping to change at page 44, line 31
o Added to ietf-netconf-client ability to connected to a cluster of o Added to ietf-netconf-client ability to connected to a cluster of
endpoints, including a reconnection-strategy. endpoints, including a reconnection-strategy.
o Added to ietf-netconf-client the ability to configure connection- o Added to ietf-netconf-client the ability to configure connection-
type and also keep-alive strategy. type and also keep-alive strategy.
o Updated both modules to accomodate new groupings in the ssh/tls o Updated both modules to accomodate new groupings in the ssh/tls
drafts. drafts.
Appendix B. Open Issues A.4. 02 to 03
Please see: https://github.com/netconf-wg/netconf-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 'netconf-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
Gary Wu Gary Wu
Cisco Networks Cisco Networks
 End of changes. 56 change blocks. 
146 lines changed or deleted 165 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/