draft-ietf-netconf-tls-client-server-01.txt   draft-ietf-netconf-tls-client-server-02.txt 
NETCONF Working Group K. Watsen NETCONF Working Group K. Watsen
Internet-Draft Juniper Networks Internet-Draft Juniper Networks
Intended status: Standards Track November 3, 2016 Intended status: Standards Track G. Wu
Expires: May 7, 2017 Expires: September 14, 2017 Cisco Systems
March 13, 2017
TLS Client and Server Models TLS Client and Server Models
draft-ietf-netconf-tls-client-server-01 draft-ietf-netconf-tls-client-server-02
Abstract Abstract
This document defines two YANG modules, one defines groupings for a This document defines three YANG modules: the first defines groupings
generic TLS client and the other defines groupings for a generic TLS for a generic TLS client, the second defines groupings for a generic
server. It is intended that these groupings will be used by TLS server, and the third defines common identities and groupings
applications using the TLS protocol. used by both the client and the server. It is intended that these
groupings will be used by applications using the TLS protocol.
Editorial Note (To be removed by RFC Editor) Editorial Note (To be removed by RFC Editor)
This draft contains many placeholder values that need to be replaced This draft contains many placeholder values that need to be replaced
with finalized values at the time of publication. This note with finalized values at the time of publication. This note
summarizes all of the substitutions that are needed. No other RFC summarizes all of the substitutions that are needed. No other RFC
Editor instructions are specified elsewhere in this document. Editor instructions are specified elsewhere in this document.
This document contains references to other drafts in progress, both This document contains references to other drafts in progress, both
in the Normative References section, as well as in body text in the Normative References section, as well as in body text
throughout. Please update the following references to reflect their throughout. Please update the following references to reflect their
final RFC assignments: final RFC assignments:
o draft-ietf-netconf-keystore o I-D.ietf-netconf-keystore
Artwork in this document contains shorthand references to drafts in Artwork in this document contains shorthand references to drafts in
progress. Please apply the following replacements: 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 "YYYY" --> the assigned RFC value for draft-ietf-netconf-keystore o "YYYY" --> the assigned RFC value for I-D.ietf-netconf-keystore
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 "2016-11-02" --> the publication date of this draft o "2017-03-13" --> the publication date of this draft
The following two Appendix sections are to be removed prior to The following two Appendix sections are to be removed prior to
publication: publication:
o Appendix A. Change Log o Appendix A. Change Log
o Appendix B. Open Issues 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-
skipping to change at page 2, line 20 skipping to change at page 2, line 21
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 May 7, 2017. This Internet-Draft will expire on September 14, 2017.
Copyright Notice Copyright Notice
Copyright (c) 2016 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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
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 . . . . . . . . . . . . . . . . . . . . . . 4
2. The TLS Client Model . . . . . . . . . . . . . . . . . . . . 4 2. The TLS Client Model . . . . . . . . . . . . . . . . . . . . 4
2.1. Tree Diagram . . . . . . . . . . . . . . . . . . . . . . 4 2.1. Tree Diagram . . . . . . . . . . . . . . . . . . . . . . 4
2.2. Example Usage . . . . . . . . . . . . . . . . . . . . . . 4 2.2. Example Usage . . . . . . . . . . . . . . . . . . . . . . 5
2.3. YANG Model . . . . . . . . . . . . . . . . . . . . . . . 5 2.3. YANG Model . . . . . . . . . . . . . . . . . . . . . . . 5
3. The TLS Server Model . . . . . . . . . . . . . . . . . . . . 7 3. The TLS Server Model . . . . . . . . . . . . . . . . . . . . 8
3.1. Tree Diagram . . . . . . . . . . . . . . . . . . . . . . 7 3.1. Tree Diagram . . . . . . . . . . . . . . . . . . . . . . 8
3.2. Example Usage . . . . . . . . . . . . . . . . . . . . . . 8 3.2. Example Usage . . . . . . . . . . . . . . . . . . . . . . 9
3.3. YANG Model . . . . . . . . . . . . . . . . . . . . . . . 8 3.3. YANG Model . . . . . . . . . . . . . . . . . . . . . . . 9
4. Security Considerations . . . . . . . . . . . . . . . . . . . 11 4. The TLS Common Model . . . . . . . . . . . . . . . . . . . . 12
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11 4.1. Tree Diagram . . . . . . . . . . . . . . . . . . . . . . 13
5.1. The IETF XML Registry . . . . . . . . . . . . . . . . . . 11 4.2. Example Usage . . . . . . . . . . . . . . . . . . . . . . 13
5.2. The YANG Module Names Registry . . . . . . . . . . . . . 12 4.3. YANG Model . . . . . . . . . . . . . . . . . . . . . . . 13
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 12 5. Security Considerations . . . . . . . . . . . . . . . . . . . 21
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 12 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 22
7.1. Normative References . . . . . . . . . . . . . . . . . . 12 6.1. The IETF XML Registry . . . . . . . . . . . . . . . . . . 22
7.2. Informative References . . . . . . . . . . . . . . . . . 13 6.2. The YANG Module Names Registry . . . . . . . . . . . . . 22
Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 14 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 22
A.1. server-model-09 to 00 . . . . . . . . . . . . . . . . . . 14 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 23
Appendix B. Open Issues . . . . . . . . . . . . . . . . . . . . 14 8.1. Normative References . . . . . . . . . . . . . . . . . . 23
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 14 8.2. Informative References . . . . . . . . . . . . . . . . . 24
Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 25
A.1. server-model-09 to 00 . . . . . . . . . . . . . . . . . . 25
A.2. 00 to 01 . . . . . . . . . . . . . . . . . . . . . . . . 25
A.3. 01 to 02 . . . . . . . . . . . . . . . . . . . . . . . . 25
Appendix B. Open Issues . . . . . . . . . . . . . . . . . . . . 25
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 25
1. Introduction 1. Introduction
This document defines two YANG [RFC6020] modules, one defines This document defines three YANG [RFC7950] modules: the first defines
groupings for a generic TLS client and the other defines groupings a grouping for a generic TLS client, the second defines a grouping
for a generic TLS server (TLS is defined in [RFC5246]). It is for a generic TLS server, and the third defines identities and
intended that these groupings will be used by applications using the groupings common to both the client and the server (TLS is defined in
TLS protocol. For instance, these groupings could be used to help [RFC5246]). It is intended that these groupings will be used by
define the data model for an HTTPS [RFC2818] server or a NETCONF over applications using the TLS protocol. For instance, these groupings
TLS [RFC7589] based server. could be used to help define the data model for an HTTPS [RFC2818]
server or a NETCONF over TLS [RFC7589] based server.
The two YANG modules in this document each define two groupings. One The client and server YANG modules in this document each define one
grouping defines everything other than what's needed for the TCP grouping, which is focused on just TLS-specific configuration, and
[RFC793] protocol layer. The other grouping uses the first grouping specifically avoids any transport-level configuration, such as what
while adding TCP layer specifics (e.g., addresses to connect to, ports to listen-on or connect-to. This enables applications the
ports to listen on, etc.). This separation is done in order to opportunity to define their own strategy for how the underlying TCP
enable applications the opportunity to define their own strategy for connection is established. For instance, applications supporting
how the underlying TCP connection is established. For instance, NETCONF Call Home [RFC8071] could use the grouping for the TLS parts
applications supporting NETCONF Call Home it provides, while adding data nodes for the TCP-level call-home
[draft-ietf-netconf-call-home] could use the first grouping for the configuration.
TLS parts it provides, while adding data nodes for the reversed TCP
layer.
1.1. Terminology 1.1. Terminology
The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119]. document are to be interpreted as described in RFC 2119 [RFC2119].
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
skipping to change at page 4, line 19 skipping to change at page 4, line 30
means a presence container, and "*" denotes a list and leaf-list. means a presence container, and "*" denotes a list and leaf-list.
o Parentheses enclose choice and case nodes, and case nodes are also o Parentheses enclose choice and case nodes, and case nodes are also
marked with a colon (":"). marked with a colon (":").
o Ellipsis ("...") stands for contents of subtrees that are not o Ellipsis ("...") stands for contents of subtrees that are not
shown. shown.
2. The TLS Client Model 2. The TLS Client Model
EDITOR NOTE: Please ignore this section, it is incomplete. The TLS client model presented in this section contains one YANG
grouping, to just configure the TLS client omitting, for instance,
The TLS client model presented in this section contains two YANG any configuration for which IP address or port the client should
groupings, one for a client that initiates the underlying TCP connect to.
connection and another for a client that has had the TCP connection
opened for it already (e.g., call home).
Both of these groupings reference data nodes defined by the Keystore This grouping references data nodes defined by the keystore model
model [draft-ietf-netconf-keystore]. For instance, a reference to [I-D.ietf-netconf-keystore]. For instance, a reference to the
the keystore model is made to indicate which trusted CA certificate a keystore model is made to indicate which trusted CA certificate a
client should use to authenticate the server's certificate. client should use to authenticate the server's certificate.
2.1. Tree Diagram 2.1. Tree Diagram
The following tree diagram presents the data model for the two The following tree diagram presents the data model for the grouping
groupings defined in the ietf-tls-client module. defined in the ietf-tls-client module. Please see Section 1.2 for
tree diagram notation.
module: ietf-tls-client module: ietf-tls-client
groupings: groupings:
initiating-tls-client-grouping tls-client-grouping
+---- some-TBD-tcp-client-stuff? string +---- server-auth
+---- some-TBD-tls-client-stuff? string | +---- trusted-ca-certs?
| | -> /ks:keystore/trusted-certificates/name
non-initiating-tls-client-grouping | +---- trusted-server-certs?
+---- some-TBD-tls-client-stuff? string | -> /ks:keystore/trusted-certificates/name
+---- client-auth
| +---- (auth-type)?
| +--:(certificate)
| +---- certificate? leafref
+---- hello-params {tls-client-hello-params-config}?
+---- tls-versions
| +---- tls-version* identityref
+---- cipher-suites
+---- cipher-suite* identityref
2.2. Example Usage 2.2. Example Usage
This section shows how it would appear if the initiating-tls-client- This section shows how it would appear if the tls-client-grouping
grouping were populated with some data. This example is consistent were populated with some data. This example is consistent with the
with the examples presented in Section 2.2 of examples presented in Section 2.2 of [I-D.ietf-netconf-keystore].
[draft-ietf-netconf-keystore].
FIXME <!-- hypothetical example, as groupings don't have instance data -->
<tls-client xmlns="urn:ietf:params:xml:ns:yang:ietf-tls-client">
2.3. YANG Model <!-- which certificates will this client trust -->
<server-auth>
<trusted-ca-certs>deployment-specific-ca-certs</trusted-ca-certs>
<trusted-server-certs>explicitly-trusted-client-certs</trusted-server-certs>
</server-auth>
This YANG module has a normative references to [RFC6991] and <!-- how this client will authenticate itself to the server -->
[draft-ietf-netconf-keystore]. <client-auth>
<certificate>builtin-idevid-cert</certificate>
</client-auth>
<CODE BEGINS> file "ietf-tls-client@2016-11-02.yang" </tls-client>
// Editor's Note: 2.3. YANG Model
// This module is incomplete at this time. Below is
// just a skeleton so there's something in the draft. This YANG module has a normative references to [RFC6991] and
// Please ignore this module for now! [I-D.ietf-netconf-keystore].
<CODE BEGINS> file "ietf-tls-client@2017-03-13.yang"
module ietf-tls-client { module ietf-tls-client {
yang-version 1.1; yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-tls-client"; namespace "urn:ietf:params:xml:ns:yang:ietf-tls-client";
prefix "tlsc"; prefix "tlsc";
/*
import ietf-inet-types { import ietf-tls-common {
prefix inet; prefix tlscom;
revision-date 2017-03-13; // stable grouping definitions
reference reference
"RFC 6991: Common YANG Data Types"; "RFC XXXX: TLS Client and Server Models";
} }
import ietf-keystore { import ietf-keystore {
prefix ks; prefix ks;
reference reference
"RFC YYYY: Keystore Model"; "RFC YYYY: Keystore Model";
} }
*/
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>
WG Chair: Mehmet Ersue Author: Kent Watsen
<mailto:mehmet.ersue@nsn.com>
WG Chair: Mahesh Jethanandani
<mailto:mjethanandani@gmail.com>
Editor: Kent Watsen
<mailto:kwatsen@juniper.net>"; <mailto:kwatsen@juniper.net>";
description description
"This module defines a reusable grouping for a TLS client that "This module defines a reusable grouping for a TLS client that
can be used as a basis for specific TLS client instances. can be used as a basis for specific TLS client instances.
Copyright (c) 2014 IETF Trust and the persons identified as Copyright (c) 2014 IETF Trust and the persons identified as
authors of the code. All rights reserved. authors of the code. All rights reserved.
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 "2016-11-02" { revision "2017-03-13" {
description description
"Initial version"; "Initial version";
reference reference
"RFC XXXX: TLS Client and Server Models"; "RFC XXXX: TLS Client and Server Models";
} }
grouping initiating-tls-client-grouping { feature tls-client-hello-params-config {
description description
"A reusable grouping for a TLS client that initiates the "TLS hello message parameters are configurable on a TLS
underlying TCP transport connection."; client.";
leaf some-TBD-tcp-client-stuff {
type string;
description "";
}
uses non-initiating-tls-client-grouping;
} }
grouping non-initiating-tls-client-grouping { grouping tls-client-grouping {
description description
"A reusable grouping for a TLS client that does not initiate "A reusable grouping for configuring a TLS client without
the underlying TCP transport connection."; any consideration for how an underlying TCP session is
leaf some-TBD-tls-client-stuff { established.";
type string;
description ""; container server-auth {
description
"Trusted server identities.";
leaf trusted-ca-certs {
type leafref {
path "/ks:keystore/ks:trusted-certificates/ks:name";
}
description
"A reference to a list of certificate authority (CA)
certificates used by the TLS client to authenticate
TLS server certificates.";
}
leaf trusted-server-certs {
type leafref {
path "/ks:keystore/ks:trusted-certificates/ks:name";
}
description
"A reference to a list of server certificates used by
the TLS client to authenticate TLS server certificates.
A server certificate is authenticated if it is an
exact match to a configured trusted server certificate.";
}
} }
}
container client-auth {
description
"The credentials used by the client to authenticate to
the TLS server.";
choice auth-type {
description
"The authentication type.";
leaf certificate {
type leafref {
path "/ks:keystore/ks:keys/ks:key/ks:certificates"
+ "/ks:certificate/ks:name";
}
description
"A certificates to be used for user authentication.";
}
}
}
container hello-params {
if-feature tls-client-hello-params-config;
uses tlscom:hello-params-grouping;
description
"Configurable parameters for the TLS hello message.";
}
} // end tls-client-grouping
} }
<CODE ENDS> <CODE ENDS>
3. The TLS Server Model 3. The TLS Server Model
The TLS server model presented in this section contains two YANG The TLS server model presented in this section contains one YANG
groupings, one for a server that opens a socket to accept TCP grouping, for just the TLS-level configuration omitting, for
connections and another for a server that has had the TCP connection instance, configuration for which ports to open to listen for
opened for it already (e.g., inetd). connections on.
Both of these groupings reference data nodes defined by the Keystore This grouping references data nodes defined by the keystore model
model [draft-ietf-netconf-keystore]. For instance, a reference to [I-D.ietf-netconf-keystore]. For instance, a reference to the
the keystore model is made to indicate the certificate a server keystore model is made to indicate which certificate a server should
should present. present.
3.1. Tree Diagram 3.1. Tree Diagram
The following tree diagram presents the data model for the two The following tree diagram presents the data model for the grouping
groupings defined in the ietf-tls-server module. defined in the ietf-tls-server module. Please see Section 1.2 for
tree diagram notation.
module: ietf-tls-server
groupings:
listening-tls-server-grouping
+---- address? inet:ip-address
+---- port? inet:port-number
+---- certificates
| +---- certificate* [name]
| +---- name? -> /ks:keystore/private-keys/private-key/cert
ificate-chains/certificate-chain/name
+---- client-auth
+---- trusted-ca-certs? -> /ks:keystore/trusted-certific
ates/name
+---- trusted-client-certs? -> /ks:keystore/trusted-certific
ates/name
non-listening-tls-server-grouping module: ietf-tls-server
+---- certificates groupings:
| +---- certificate* [name] tls-server-grouping
| +---- name? -> /ks:keystore/private-keys/private-key/cert +---- certificates
ificate-chains/certificate-chain/name | +---- certificate* [name]
+---- client-auth | +---- name? leafref
+---- trusted-ca-certs? -> /ks:keystore/trusted-certific +---- client-auth
ates/name | +---- trusted-ca-certs?
+---- trusted-client-certs? -> /ks:keystore/trusted-certific | | -> /ks:keystore/trusted-certificates/name
ates/name | +---- trusted-client-certs?
| -> /ks:keystore/trusted-certificates/name
+---- hello-params {tls-server-hello-params-config}?
+---- tls-versions
| +---- tls-version* identityref
+---- cipher-suites
+---- cipher-suite* identityref
3.2. Example Usage 3.2. Example Usage
This section shows how it would appear if the listening-tls-server- This section shows how it would appear if the tls-server-grouping
grouping were populated with some data. This example is consistent were populated with some data. This example is consistent with the
with the examples presented in Section 2.2 of examples presented in Section 2.2 of [I-D.ietf-netconf-keystore].
[draft-ietf-netconf-keystore].
<listening-tls-server <!-- hypothetical example, groupings don't have instance data -->
xmlns="urn:ietf:params:xml:ns:yang:ietf-tls-server">
<port>6513</port> <tls-server
<certificates> xmlns="urn:ietf:params:xml:ns:yang:ietf-tls-server">
<certificate> <certificates>
<name>ex-key-sect571r1-cert</name> <certificate>
</certificate> <name>tls-ec-cert</name>
</certificates> </certificate>
<client-auth> </certificates>
<trusted-ca-certs> <client-auth>
deployment-specific-ca-certs <trusted-ca-certs>deployment-specific-ca-certs</trusted-ca-certs>
</trusted-ca-certs> <trusted-client-certs>explicitly-trusted-client-certs</trusted-client-certs>
<trusted-client-certs> </client-auth>
explicitly-trusted-client-certs </tls-server>
</trusted-client-certs>
</client-auth>
</listening-tls-server>
3.3. YANG Model 3.3. YANG Model
This YANG module has a normative references to [RFC6991], and This YANG module has a normative references to [RFC6991], and
[draft-ietf-netconf-keystore]. [I-D.ietf-netconf-keystore].
<CODE BEGINS> file "ietf-tls-server@2016-11-02.yang" <CODE BEGINS> file "ietf-tls-server@2017-03-13.yang"
module ietf-tls-server { module ietf-tls-server {
yang-version 1.1; yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-tls-server"; namespace "urn:ietf:params:xml:ns:yang:ietf-tls-server";
prefix "tlss"; prefix "tlss";
import ietf-inet-types { import ietf-tls-common {
prefix inet; prefix tlscom;
revision-date 2017-03-13; // stable grouping definitions
reference reference
"RFC 6991: Common YANG Data Types"; "RFC XXXX: TLS Client and Server Models";
} }
import ietf-keystore { import ietf-keystore {
prefix ks; prefix ks;
reference reference
"RFC YYYY: Keystore Model"; "RFC YYYY: Keystore Model";
} }
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>
WG Chair: Mehmet Ersue Author: Kent Watsen
<mailto:mehmet.ersue@nsn.com>
WG Chair: Mahesh Jethanandani
<mailto:mjethanandani@gmail.com>
Editor: Kent Watsen
<mailto:kwatsen@juniper.net>"; <mailto:kwatsen@juniper.net>";
description description
"This module defines a reusable grouping for a TLS server that "This module defines a reusable grouping for a TLS server that
can be used as a basis for specific TLS server instances. can be used as a basis for specific TLS server instances.
Copyright (c) 2014 IETF Trust and the persons identified as Copyright (c) 2014 IETF Trust and the persons identified as
authors of the code. All rights reserved. authors of the code. All rights reserved.
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 "2016-11-02" { revision "2017-03-13" {
description description
"Initial version"; "Initial version";
reference reference
"RFC XXXX: TLS Client and Server Models"; "RFC XXXX: TLS Client and Server Models";
} }
feature tls-server-hello-params-config {
description
"TLS hello message parameters are configurable on a TLS
server.";
}
// grouping // grouping
grouping non-listening-tls-server-grouping { grouping tls-server-grouping {
description description
"A reusable grouping for a TLS server that can be used as a "A reusable grouping for configuring a TLS server without
basis for specific TLS server instances."; any consideration for how underlying TCP sessions are
established.";
container certificates { container certificates {
description description
"The list of certificates the TLS server will present when "The list of certificates the TLS server will present when
establishing a TLS connection in its Certificate message, establishing a TLS connection in its Certificate message,
as defined in Section 7.4.2 in RRC 5246."; as defined in Section 7.4.2 in RRC 5246.";
reference reference
"RFC 5246: "RFC 5246:
The Transport Layer Security (TLS) Protocol Version 1.2"; The Transport Layer Security (TLS) Protocol Version 1.2";
list certificate { list certificate {
key name; key name;
min-elements 1; min-elements 1;
description description
"An unordered list of certificates the TLS server can pick "An unordered list of certificates the TLS server can pick
from when sending its Server Certificate message."; from when sending its Server Certificate message.";
reference reference
"RFC 5246: The TLS Protocol, Section 7.4.2"; "RFC 5246: The TLS Protocol, Section 7.4.2";
leaf name { leaf name {
type leafref { type leafref {
path "/ks:keystore/ks:private-keys/ks:private-key/" path "/ks:keystore/ks:keys/ks:key/ks:certificates/"
+ "ks:certificate-chains/ks:certificate-chain/" + "ks:certificate/ks:name";
+ "ks:name";
} }
description description
"The name of the certificate in the keystore."; "The name of the certificate in the keystore.";
} }
} }
} }
container client-auth { container client-auth {
description description
"A reference to a list of trusted certificate authority (CA) "A reference to a list of trusted certificate authority (CA)
skipping to change at page 11, line 4 skipping to change at page 12, line 18
} }
description description
"A reference to a list of certificate authority (CA) "A reference to a list of certificate authority (CA)
certificates used by the TLS server to authenticate certificates used by the TLS server to authenticate
TLS client certificates."; TLS client certificates.";
} }
leaf trusted-client-certs { leaf trusted-client-certs {
type leafref { type leafref {
path "/ks:keystore/ks:trusted-certificates/ks:name"; path "/ks:keystore/ks:trusted-certificates/ks:name";
} }
description description
"A reference to a list of client certificates used by "A reference to a list of client certificates used by
the TLS server to authenticate TLS client certificates. the TLS server to authenticate TLS client certificates.
A clients certificate is authenticated if it is an A clients certificate is authenticated if it is an
exact match to a configured trusted client certificate."; exact match to a configured trusted client certificate.";
} }
} }
}
grouping listening-tls-server-grouping { container hello-params {
description if-feature tls-server-hello-params-config;
"A reusable grouping for a TLS server that can be used as a uses tlscom:hello-params-grouping;
basis for specific TLS server instances.";
leaf address {
type inet:ip-address;
description
"The IP address of the interface to listen on. The TLS
server will listen on all interfaces if no value is
specified. Please note that some addresses have special
meanings (e.g., '0.0.0.0' and '::').";
}
leaf port {
type inet:port-number;
description description
"The local port number on this interface the TLS server "Configurable parameters for the TLS hello message.";
listens on. When this grouping is used, it is RECOMMENDED
that refine statement is used to either set a default port
value or to set mandatory true.";
} }
uses non-listening-tls-server-grouping;
} } // end tls-server-grouping
} }
<CODE ENDS> <CODE ENDS>
4. Security Considerations 4. The TLS Common Model
5. IANA Considerations The TLS common model presented in this section contains identities
and groupings common to both TLS clients and TLS servers. The hello-
params-grouping can be used to configure the list of TLS algorithms
permitted by the TLS client or TLS server. The lists of algorithms
are ordered such that, if multiple algorithms are permitted by the
client, the algorithm that appears first in its list that is also
permitted by the server is used for the TLS transport layer
connection. The ability to restrict the the algorithms allowed is
provided in this grouping for TLS clients and TLS servers that are
capable of doing so and may serve to make TLS clients and TLS servers
compliant with security policies.
5.1. The IETF XML Registry Features are defined for algorithms that are OPTIONAL or are not
widely supported by popular implementations. Note that the list of
algorithms is not exhaustive.
This document registers two URIs in the IETF XML registry [RFC2119]. 4.1. Tree Diagram
Following the format in [RFC3688], the following registrations are
requested: The following tree diagram presents the data model for the grouping
defined in the ietf-tls-common module. Please see Section 1.2 for
tree diagram notation.
module: ietf-tls-common
groupings:
hello-params-grouping
+---- tls-versions
| +---- tls-version* identityref
+---- cipher-suites
+---- cipher-suite* identityref
4.2. Example Usage
This section shows how it would appear if the transport-params-
grouping were populated with some data.
<!-- hypothetical example, as groupings don't have instance data -->
<hello-params xmlns="urn:ietf:params:xml:ns:yang:ietf-tls-common">
<tls-versions>
<tls-version>tls-1.2</tls-version>
</tls-versions>
<cipher-suites>
<cipher-suite>ecdhe-rsa-with-3des-ede-cbc-sha</cipher-suite>
<cipher-suite>dhe-rsa-with-aes-128-cbc-sha</cipher-suite>
<cipher-suite>rsa-with-aes-128-cbc-sha</cipher-suite>
<cipher-suite>rsa-with-3des-ede-cbc-sha</cipher-suite>
</cipher-suites>
</hello-params>
4.3. YANG Model
This YANG module has a normative references to [RFC4492], [RFC5246],
[RFC5288], and [RFC5289].
<CODE BEGINS> file "ietf-tls-common@2017-03-13.yang"
module ietf-tls-common {
yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-tls-common";
prefix "tlscom";
organization
"IETF NETCONF (Network Configuration) Working Group";
contact
"WG Web: <http://tools.ietf.org/wg/netconf/>
WG List: <mailto:netconf@ietf.org>
Author: Kent Watsen
<mailto:kwatsen@juniper.net>
Author: Gary Wu
<mailto:garywu@cisco.com>";
description
"This module defines a common features, identities, and groupings
for Transport Layer Security (TLS).
Copyright (c) 2017 IETF Trust and the persons identified as
authors of the code. All rights reserved.
Redistribution and use in source and binary forms, with or
without modification, is permitted pursuant to, and subject
to the license terms contained in, the Simplified BSD
License set forth in Section 4.c of the IETF Trust's
Legal Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC XXXX; see
the RFC itself for full legal notices.";
revision "2017-03-13" {
description
"Initial version";
reference
"RFC XXXX: TLS Client and Server Models";
}
// features
feature tls-ecc {
description
"Elliptic Curve Cryptography (ECC) is supported for TLS.";
reference
"RFC 4492: Elliptic Curve Cryptography (ECC) Cipher Suites
for Transport Layer Security (TLS)";
}
feature tls-dhe {
description
"Ephemeral Diffie-Hellman key exchange is supported for TLS.";
reference
"RFC 5246: The Transport Layer Security (TLS) Protocol
Version 1.2";
}
feature tls-3des {
description
"The Triple-DES block cipher is supported for TLS.";
reference
"RFC 5246: The Transport Layer Security (TLS) Protocol
Version 1.2";
}
feature tls-gcm {
description
"The Galois/Counter Mode authenticated encryption mode is
supported for TLS.";
reference
"RFC 5288: AES Galois Counter Mode (GCM) Cipher Suites for TLS";
}
feature tls-sha2 {
description
"The SHA2 family of cryptographic hash functions is supported
for TLS.";
reference
"FIPS PUB 180-4: Secure Hash Standard (SHS)";
}
// identities
identity tls-version-base {
description
"Base identity used to identify TLS protocol versions.";
}
identity tls-1.2 {
base tls-version-base;
description
"TLS protocol version 1.2.";
reference
"RFC 5246: The Transport Layer Security (TLS) Protocol
Version 1.2";
}
identity cipher-suite-base {
description
"Base identity used to identify TLS cipher suites.";
}
identity rsa-with-aes-128-cbc-sha {
base cipher-suite-base;
description
"Cipher suite TLS_RSA_WITH_AES_128_CBC_SHA.";
reference
"RFC 5246: The Transport Layer Security (TLS) Protocol
Version 1.2";
}
identity rsa-with-aes-256-cbc-sha {
base cipher-suite-base;
description
"Cipher suite TLS_RSA_WITH_AES_256_CBC_SHA.";
reference
"RFC 5246: The Transport Layer Security (TLS) Protocol
Version 1.2";
}
identity rsa-with-aes-128-cbc-sha256 {
base cipher-suite-base;
if-feature tls-sha2;
description
"Cipher suite TLS_RSA_WITH_AES_128_CBC_SHA256.";
reference
"RFC 5246: The Transport Layer Security (TLS) Protocol
Version 1.2";
}
identity rsa-with-aes-256-cbc-sha256 {
base cipher-suite-base;
if-feature tls-sha2;
description
"Cipher suite TLS_RSA_WITH_AES_256_CBC_SHA256.";
reference
"RFC 5246: The Transport Layer Security (TLS) Protocol
Version 1.2";
}
identity dhe-rsa-with-aes-128-cbc-sha {
base cipher-suite-base;
if-feature tls-dhe;
description
"Cipher suite TLS_DHE_RSA_WITH_AES_128_CBC_SHA.";
reference
"RFC 5246: The Transport Layer Security (TLS) Protocol
Version 1.2";
}
identity dhe-rsa-with-aes-256-cbc-sha {
base cipher-suite-base;
if-feature tls-dhe;
description
"Cipher suite TLS_DHE_RSA_WITH_AES_256_CBC_SHA.";
reference
"RFC 5246: The Transport Layer Security (TLS) Protocol
Version 1.2";
}
identity dhe-rsa-with-aes-128-cbc-sha256 {
base cipher-suite-base;
if-feature "tls-dhe and tls-sha2";
description
"Cipher suite TLS_DHE_RSA_WITH_AES_128_CBC_SHA256.";
reference
"RFC 5246: The Transport Layer Security (TLS) Protocol
Version 1.2";
}
identity dhe-rsa-with-aes-256-cbc-sha256 {
base cipher-suite-base;
if-feature "tls-dhe and tls-sha2";
description
"Cipher suite TLS_DHE_RSA_WITH_AES_256_CBC_SHA256.";
reference
"RFC 5246: The Transport Layer Security (TLS) Protocol
Version 1.2";
}
identity ecdhe-ecdsa-with-aes-128-cbc-sha256 {
base cipher-suite-base;
if-feature "tls-ecc and tls-sha2";
description
"Cipher suite TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256.";
reference
"RFC 5289: TLS Elliptic Curve Cipher Suites with
SHA-256/384 and AES Galois Counter Mode (GCM)";
}
identity ecdhe-ecdsa-with-aes-256-cbc-sha384 {
base cipher-suite-base;
if-feature "tls-ecc and tls-sha2";
description
"Cipher suite TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384.";
reference
"RFC 5289: TLS Elliptic Curve Cipher Suites with
SHA-256/384 and AES Galois Counter Mode (GCM)";
}
identity ecdhe-rsa-with-aes-128-cbc-sha256 {
base cipher-suite-base;
if-feature "tls-ecc and tls-sha2";
description
"Cipher suite TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256.";
reference
"RFC 5289: TLS Elliptic Curve Cipher Suites with
SHA-256/384 and AES Galois Counter Mode (GCM)";
}
identity ecdhe-rsa-with-aes-256-cbc-sha384 {
base cipher-suite-base;
if-feature "tls-ecc and tls-sha2";
description
"Cipher suite TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384.";
reference
"RFC 5289: TLS Elliptic Curve Cipher Suites with
SHA-256/384 and AES Galois Counter Mode (GCM)";
}
identity ecdhe-ecdsa-with-aes-128-gcm-sha256 {
base cipher-suite-base;
if-feature "tls-ecc and tls-gcm and tls-sha2";
description
"Cipher suite TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256.";
reference
"RFC 5289: TLS Elliptic Curve Cipher Suites with
SHA-256/384 and AES Galois Counter Mode (GCM)";
}
identity ecdhe-ecdsa-with-aes-256-gcm-sha384 {
base cipher-suite-base;
if-feature "tls-ecc and tls-gcm and tls-sha2";
description
"Cipher suite TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384.";
reference
"RFC 5289: TLS Elliptic Curve Cipher Suites with
SHA-256/384 and AES Galois Counter Mode (GCM)";
}
identity ecdhe-rsa-with-aes-128-gcm-sha256 {
base cipher-suite-base;
if-feature "tls-ecc and tls-gcm and tls-sha2";
description
"Cipher suite TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256.";
reference
"RFC 5289: TLS Elliptic Curve Cipher Suites with
SHA-256/384 and AES Galois Counter Mode (GCM)";
}
identity ecdhe-rsa-with-aes-256-gcm-sha384 {
base cipher-suite-base;
if-feature "tls-ecc and tls-gcm and tls-sha2";
description
"Cipher suite TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384.";
reference
"RFC 5289: TLS Elliptic Curve Cipher Suites with
SHA-256/384 and AES Galois Counter Mode (GCM)";
}
identity rsa-with-3des-ede-cbc-sha {
base cipher-suite-base;
if-feature tls-3des;
description
"Cipher suite TLS_RSA_WITH_3DES_EDE_CBC_SHA.";
reference
"RFC 5246: The Transport Layer Security (TLS) Protocol
Version 1.2";
}
identity ecdhe-rsa-with-3des-ede-cbc-sha {
base cipher-suite-base;
if-feature "tls-ecc and tls-3des";
description
"Cipher suite TLS_ECDHE_RSA_WITH_3DES_EDE_CBC_SHA.";
reference
"RFC 4492: Elliptic Curve Cryptography (ECC) Cipher Suites
for Transport Layer Security (TLS)";
}
identity ecdhe-rsa-with-aes-128-cbc-sha {
base cipher-suite-base;
if-feature "tls-ecc";
description
"Cipher suite TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA.";
reference
"RFC 4492: Elliptic Curve Cryptography (ECC) Cipher Suites
for Transport Layer Security (TLS)";
}
identity ecdhe-rsa-with-aes-256-cbc-sha {
base cipher-suite-base;
if-feature "tls-ecc";
description
"Cipher suite TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA.";
reference
"RFC 4492: Elliptic Curve Cryptography (ECC) Cipher Suites
for Transport Layer Security (TLS)";
}
// groupings
grouping hello-params-grouping {
description
"A reusable grouping for TLS hello message parameters. For
configurable parameters, a zero-element leaf-list indicates the
system default configuration for that parameter.";
reference
"RFC 5246: The Transport Layer Security (TLS) Protocol
Version 1.2";
container tls-versions {
description
"Parameters regarding TLS versions.";
leaf-list tls-version {
type identityref {
base tls-version-base;
}
description
"Allowed TLS protocol versions.";
}
}
container cipher-suites {
description
"Parameters regarding cipher suites.";
leaf-list cipher-suite {
type identityref {
base cipher-suite-base;
}
ordered-by user;
description
"Cipher suites in order of descending preference.";
}
}
}
}
<CODE ENDS>
5. Security Considerations
The YANG module defined in this document is designed to be accessed
via YANG based management protocols, such as NETCONF [RFC6241] and
RESTCONF [RFC8040]. Both of these protocols have mandatory-to-
implement secure transport layers (e.g., SSH, TLS) with mutual
authentication.
The NETCONF access control model (NACM) [RFC6536] provides the means
to restrict access for particular users to a pre-configured subset of
all available protocol operations and content.
There are a number of data nodes defined in this YANG module that are
writable/creatable/deletable (i.e., config true, which is the
default). These data nodes may be considered sensitive or vulnerable
in some network environments. Write operations (e.g., edit-config)
to these data nodes without proper protection can have a negative
effect on network operations. These are the subtrees and data nodes
and their sensitivity/vulnerability:
/: The entire data tree defined by this module is sensitive to
write operations. For instance, the addition or removal of
references to keys, certificates, trusted anchors, etc., can
dramatically alter the implemented security policy. However,
no NACM annotations are applied as the data SHOULD be editable
by users other than a designated 'recovery session'.
Some of the readable data nodes in this YANG module may be considered
sensitive or vulnerable in some network environments. It is thus
important to control read access (e.g., via get, get-config, or
notification) to these data nodes. These are the subtrees and data
nodes and their sensitivity/vulnerability:
NONE
Some of the RPC operations in this YANG module may be considered
sensitive or vulnerable in some network environments. It is thus
important to control access to these operations. These are the
operations and their sensitivity/vulnerability:
NONE
6. IANA Considerations
6.1. The IETF XML Registry
This document registers three URIs in the IETF XML registry
[RFC3688]. Following the format in [RFC3688], the following
registrations are requested:
URI: urn:ietf:params:xml:ns:yang:ietf-tls-client URI: urn:ietf:params:xml:ns:yang:ietf-tls-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-tls-server URI: urn:ietf:params:xml:ns:yang:ietf-tls-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 URI: urn:ietf:params:xml:ns:yang:ietf-tls-common
Registrant Contact: The NETCONF WG of the IETF.
XML: N/A, the requested URI is an XML namespace.
This document registers two YANG modules in the YANG Module Names 6.2. The YANG Module Names Registry
registry [RFC6020]. Following the format in [RFC6020], the the
This document registers three YANG modules in the YANG Module Names
registry [RFC7950]. Following the format in [RFC7950], the the
following registrations are requested: following registrations are requested:
name: ietf-tls-client name: ietf-tls-client
namespace: urn:ietf:params:xml:ns:yang:ietf-tls-client namespace: urn:ietf:params:xml:ns:yang:ietf-tls-client
prefix: tlsc prefix: tlsc
reference: RFC XXXX reference: RFC XXXX
name: ietf-tls-server name: ietf-tls-server
namespace: urn:ietf:params:xml:ns:yang:ietf-tls-server namespace: urn:ietf:params:xml:ns:yang:ietf-tls-server
prefix: tlss prefix: tlss
reference: RFC XXXX reference: RFC XXXX
6. Acknowledgements name: ietf-tls-common
namespace: urn:ietf:params:xml:ns:yang:ietf-tls-common
prefix: tlss
reference: RFC XXXX
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, David Lamparter, Alan Luchuk,
Ladislav Lhotka, Radek Krejci, Tom Petch, Juergen Schoenwaelder, Phil Ladislav Lhotka, Radek Krejci, Tom Petch, Juergen Schoenwaelder, Phil
Shafer, Sean Turner, and Bert Wijnen. Shafer, Sean Turner, and Bert Wijnen.
7. References 8. References
7.1. Normative References 8.1. Normative References
[draft-ietf-netconf-keystore] [I-D.ietf-netconf-keystore]
Watsen, K., "Keystore Model", draft-ieft-netconf- Watsen, K. and G. Wu, "Keystore Model", draft-ietf-
keystore-00 (work in progress), 2016, netconf-keystore-00 (work in progress), October 2016.
<https://datatracker.ietf.org/html/draft-ieft-netconf-
keystore>.
[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>.
[RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for [RFC4492] Blake-Wilson, S., Bolyard, N., Gupta, V., Hawk, C., and B.
the Network Configuration Protocol (NETCONF)", RFC 6020, Moeller, "Elliptic Curve Cryptography (ECC) Cipher Suites
DOI 10.17487/RFC6020, October 2010, for Transport Layer Security (TLS)", RFC 4492,
<http://www.rfc-editor.org/info/rfc6020>. DOI 10.17487/RFC4492, May 2006,
<http://www.rfc-editor.org/info/rfc4492>.
[RFC5246] Dierks, T. and E. Rescorla, "The Transport Layer Security
(TLS) Protocol Version 1.2", RFC 5246,
DOI 10.17487/RFC5246, August 2008,
<http://www.rfc-editor.org/info/rfc5246>.
[RFC5288] Salowey, J., Choudhury, A., and D. McGrew, "AES Galois
Counter Mode (GCM) Cipher Suites for TLS", RFC 5288,
DOI 10.17487/RFC5288, August 2008,
<http://www.rfc-editor.org/info/rfc5288>.
[RFC5289] Rescorla, E., "TLS Elliptic Curve Cipher Suites with SHA-
256/384 and AES Galois Counter Mode (GCM)", RFC 5289,
DOI 10.17487/RFC5289, August 2008,
<http://www.rfc-editor.org/info/rfc5289>.
[RFC6536] Bierman, A. and M. Bjorklund, "Network Configuration
Protocol (NETCONF) Access Control Model", RFC 6536,
DOI 10.17487/RFC6536, March 2012,
<http://www.rfc-editor.org/info/rfc6536>.
[RFC6991] Schoenwaelder, J., Ed., "Common YANG Data Types", [RFC6991] Schoenwaelder, J., Ed., "Common YANG Data Types",
RFC 6991, DOI 10.17487/RFC6991, July 2013, RFC 6991, DOI 10.17487/RFC6991, July 2013,
<http://www.rfc-editor.org/info/rfc6991>. <http://www.rfc-editor.org/info/rfc6991>.
[RFC7589] Badra, M., Luchuk, A., and J. Schoenwaelder, "Using the [RFC7589] Badra, M., Luchuk, A., and J. Schoenwaelder, "Using the
NETCONF Protocol over Transport Layer Security (TLS) with NETCONF Protocol over Transport Layer Security (TLS) with
Mutual X.509 Authentication", RFC 7589, Mutual X.509 Authentication", RFC 7589,
DOI 10.17487/RFC7589, June 2015, DOI 10.17487/RFC7589, June 2015,
<http://www.rfc-editor.org/info/rfc7589>. <http://www.rfc-editor.org/info/rfc7589>.
7.2. Informative References [RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language",
RFC 7950, DOI 10.17487/RFC7950, August 2016,
<http://www.rfc-editor.org/info/rfc7950>.
[draft-ietf-netconf-call-home] 8.2. Informative References
Watsen, K., "NETCONF Call Home and RESTCONF Call Home",
draft-ieft-netconf-call-home-17 (work in progress), 2015,
<https://datatracker.ietf.org/html/draft-ieft-netconf-
call-home-17>.
[RFC2818] Rescorla, E., "HTTP Over TLS", RFC 2818, [RFC2818] Rescorla, E., "HTTP Over TLS", RFC 2818,
DOI 10.17487/RFC2818, May 2000, DOI 10.17487/RFC2818, May 2000,
<http://www.rfc-editor.org/info/rfc2818>. <http://www.rfc-editor.org/info/rfc2818>.
[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 [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed.,
(TLS) Protocol Version 1.2", RFC 5246, and A. Bierman, Ed., "Network Configuration Protocol
DOI 10.17487/RFC5246, August 2008, (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011,
<http://www.rfc-editor.org/info/rfc5246>. <http://www.rfc-editor.org/info/rfc6241>.
[RFC793] Postel, J., "TRANSMISSION CONTROL PROTOCOL", STD 7, [RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF
September 1981, <https://www.ietf.org/rfc/rfc793.txt>. Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017,
<http://www.rfc-editor.org/info/rfc8040>.
[RFC8071] Watsen, K., "NETCONF Call Home and RESTCONF Call Home",
RFC 8071, DOI 10.17487/RFC8071, February 2017,
<http://www.rfc-editor.org/info/rfc8071>.
Appendix A. Change Log Appendix A. Change Log
A.1. server-model-09 to 00 A.1. server-model-09 to 00
o This draft was split out from draft-ietf-netconf-server-model-09. o This draft was split out from draft-ietf-netconf-server-model-09.
o Noted that '0.0.0.0' and '::' might have special meanings. o Noted that '0.0.0.0' and '::' might have special meanings.
A.2. 00 to 01
o Renamed "keychain" to "keystore".
A.3. 01 to 02
o Removed the groupings containing transport-level configuration.
Now modules contain only the transport-independent groupings.
o Filled in previously incomplete 'ietf-tls-client' module.
o Added cipher suites for various algorithms into new 'ietf-tls-
common' module.
Appendix B. Open Issues Appendix B. Open Issues
Please see: https://github.com/netconf-wg/tls-client-server/issues. Please see: https://github.com/netconf-wg/tls-client-server/issues.
Author's Address Authors' Addresses
Kent Watsen Kent Watsen
Juniper Networks Juniper Networks
EMail: kwatsen@juniper.net EMail: kwatsen@juniper.net
Gary Wu
Cisco Systems
EMail: garywu@cisco.com
 End of changes. 75 change blocks. 
238 lines changed or deleted 758 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/