draft-ietf-netconf-tls-client-server-06.txt   draft-ietf-netconf-tls-client-server-07.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: December 6, 2018 Cisco Systems Expires: March 24, 2019 Cisco Systems
June 4, 2018 September 20, 2018
YANG Groupings for TLS Clients and TLS Servers YANG Groupings for TLS Clients and TLS Servers
draft-ietf-netconf-tls-client-server-06 draft-ietf-netconf-tls-client-server-07
Abstract Abstract
This document defines three YANG modules: the first defines groupings This document defines three YANG modules: the first defines groupings
for a generic TLS client, the second defines groupings for a generic for a generic TLS client, the second defines groupings for a generic
TLS server, and the third defines common identities and groupings TLS server, and the third defines common identities and groupings
used by both the client and the server. It is intended that these used by both the client and the server. It is intended that these
groupings will be used by applications using the TLS protocol. 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)
skipping to change at page 1, line 49 skipping to change at page 1, line 49
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 I-D.ietf-netconf-trust- o "YYYY" --> the assigned RFC value for I-D.ietf-netconf-trust-
anchors anchors
o "ZZZZ" --> the assigned RFC value for I-D.ietf-netconf-keystore o "ZZZZ" --> 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 "2018-06-04" --> the publication date of this draft o "2018-09-20" --> the publication date of this draft
The following Appendix section is to be removed prior to publication: The following Appendix section is to be removed prior to publication:
o Appendix A. Change Log o Appendix A. Change Log
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on December 6, 2018. This Internet-Draft will expire on March 24, 2019.
Copyright Notice Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the Copyright (c) 2018 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
(https://trustee.ietf.org/license-info) in effect on the date of (https://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 46 skipping to change at page 2, line 46
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
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4
3. The TLS Client Model . . . . . . . . . . . . . . . . . . . . 4 3. The TLS Client Model . . . . . . . . . . . . . . . . . . . . 4
3.1. Tree Diagram . . . . . . . . . . . . . . . . . . . . . . 4 3.1. Tree Diagram . . . . . . . . . . . . . . . . . . . . . . 4
3.2. Example Usage . . . . . . . . . . . . . . . . . . . . . . 5 3.2. Example Usage . . . . . . . . . . . . . . . . . . . . . . 4
3.3. YANG Module . . . . . . . . . . . . . . . . . . . . . . . 7 3.3. YANG Module . . . . . . . . . . . . . . . . . . . . . . . 6
4. The TLS Server Model . . . . . . . . . . . . . . . . . . . . 10 4. The TLS Server Model . . . . . . . . . . . . . . . . . . . . 9
4.1. Tree Diagram . . . . . . . . . . . . . . . . . . . . . . 10 4.1. Tree Diagram . . . . . . . . . . . . . . . . . . . . . . 9
4.2. Example Usage . . . . . . . . . . . . . . . . . . . . . . 11 4.2. Example Usage . . . . . . . . . . . . . . . . . . . . . . 10
4.3. YANG Module . . . . . . . . . . . . . . . . . . . . . . . 13 4.3. YANG Module . . . . . . . . . . . . . . . . . . . . . . . 12
5. The TLS Common Model . . . . . . . . . . . . . . . . . . . . 16 5. The TLS Common Model . . . . . . . . . . . . . . . . . . . . 15
5.1. Tree Diagram . . . . . . . . . . . . . . . . . . . . . . 16 5.1. Tree Diagram . . . . . . . . . . . . . . . . . . . . . . 15
5.2. Example Usage . . . . . . . . . . . . . . . . . . . . . . 17 5.2. Example Usage . . . . . . . . . . . . . . . . . . . . . . 16
5.3. YANG Module . . . . . . . . . . . . . . . . . . . . . . . 17 5.3. YANG Module . . . . . . . . . . . . . . . . . . . . . . . 16
6. Security Considerations . . . . . . . . . . . . . . . . . . . 25 6. Security Considerations . . . . . . . . . . . . . . . . . . . 24
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 26 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 25
7.1. The IETF XML Registry . . . . . . . . . . . . . . . . . . 26 7.1. The IETF XML Registry . . . . . . . . . . . . . . . . . . 25
7.2. The YANG Module Names Registry . . . . . . . . . . . . . 27 7.2. The YANG Module Names Registry . . . . . . . . . . . . . 26
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 27 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 26
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 27 8.1. Normative References . . . . . . . . . . . . . . . . . . 26
9.1. Normative References . . . . . . . . . . . . . . . . . . 27 8.2. Informative References . . . . . . . . . . . . . . . . . 28
9.2. Informative References . . . . . . . . . . . . . . . . . 29 Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 29
Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 30 A.1. 00 to 01 . . . . . . . . . . . . . . . . . . . . . . . . 29
A.1. 00 to 01 . . . . . . . . . . . . . . . . . . . . . . . . 30 A.2. 01 to 02 . . . . . . . . . . . . . . . . . . . . . . . . 29
A.2. 01 to 02 . . . . . . . . . . . . . . . . . . . . . . . . 30 A.3. 02 to 03 . . . . . . . . . . . . . . . . . . . . . . . . 29
A.3. 02 to 03 . . . . . . . . . . . . . . . . . . . . . . . . 30 A.4. 03 to 04 . . . . . . . . . . . . . . . . . . . . . . . . 29
A.4. 03 to 04 . . . . . . . . . . . . . . . . . . . . . . . . 30 A.5. 04 to 05 . . . . . . . . . . . . . . . . . . . . . . . . 30
A.5. 04 to 05 . . . . . . . . . . . . . . . . . . . . . . . . 31 A.6. 05 to 06 . . . . . . . . . . . . . . . . . . . . . . . . 30
A.6. 05 to 06 . . . . . . . . . . . . . . . . . . . . . . . . 31 A.7. 06 to 07 . . . . . . . . . . . . . . . . . . . . . . . . 30
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 31 Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 30
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 30
1. Introduction 1. Introduction
This document defines three YANG 1.1 [RFC7950] modules: the first This document defines three YANG 1.1 [RFC7950] modules: the first
defines a grouping for a generic TLS client, the second defines a defines a grouping for a generic TLS client, the second defines a
grouping for a generic TLS server, and the third defines identities grouping for a generic TLS server, and the third defines identities
and groupings common to both the client and the server (TLS is and groupings common to both the client and the server (TLS is
defined in [RFC5246]). It is intended that these groupings will be defined in [RFC5246]). It is intended that these groupings will be
used by applications using the TLS protocol. For instance, these used by applications using the TLS protocol. For instance, these
groupings could be used to help define the data model for an HTTPS groupings could be used to help define the data model for an HTTPS
skipping to change at page 3, line 48 skipping to change at page 3, line 49
grouping, which is focused on just TLS-specific configuration, and grouping, which is focused on just TLS-specific configuration, and
specifically avoids any transport-level configuration, such as what specifically avoids any transport-level configuration, such as what
ports to listen-on or connect-to. This affords applications the ports to listen-on or connect-to. This affords applications the
opportunity to define their own strategy for how the underlying TCP opportunity to define their own strategy for how the underlying TCP
connection is established. For instance, applications supporting connection is established. For instance, applications supporting
NETCONF Call Home [RFC8071] could use the "ssh-server-grouping" NETCONF Call Home [RFC8071] could use the "ssh-server-grouping"
grouping for the TLS parts it provides, while adding data nodes for grouping for the TLS parts it provides, while adding data nodes for
the TCP-level call-home configuration. the TCP-level call-home configuration.
The modules defined in this document uses groupings defined in The modules defined in this document uses groupings defined in
[I-D.ietf-netconf-keystore] enabling keys to be either locally [I-D.ietf-netconf-keystore] enabling keys to be either locally
defined or a reference to globally configured values. defined or a reference to globally configured values.
2. Terminology 2. Terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in BCP "OPTIONAL" in this document are to be interpreted as described in BCP
14 [RFC2119] [RFC8174] when, and only when, they appear in all 14 [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here. capitals, as shown here.
3. The TLS Client Model 3. The TLS Client Model
3.1. Tree Diagram 3.1. Tree Diagram
This section provides two tree diagrams [RFC8340] for the "ietf-tls- This section provides a tree diagram [RFC8340] for the "ietf-tls-
client" module, the first with used groupings expanded and the second client" module that does not have groupings expanded.
with used groupings not expanded.
The following tree diagram has used groupings expanded:
module: ietf-tls-client module: ietf-tls-client
grouping tls-client-grouping grouping server-auth-grouping
+-- client-identity
| +-- (auth-type)?
| +--:(certificate)
| +-- certificate
| +-- (local-or-keystore)
| +--:(local)
| | +-- algorithm
| | | ct:key-algorithm-ref
| | +-- public-key binary
| | +-- private-key union
| | +-- cert
| | | ct:end-entity-cert-cms
| | +---n certificate-expiration
| | +-- expiration-date? yang:date-and-time
| +--:(keystore) {keystore-implemented}?
| +-- reference
| ks:asymmetric-key-certificate-ref
+-- server-auth +-- server-auth
| +-- pinned-ca-certs? ta:pinned-certificates-ref +-- pinned-ca-certs? ta:pinned-certificates-ref
| +-- pinned-server-certs? ta:pinned-certificates-ref | {ta:x509-certificates}?
+-- hello-params {tls-client-hello-params-config}? +-- pinned-server-certs? ta:pinned-certificates-ref
+-- tls-versions {ta:x509-certificates}?
| +-- tls-version* identityref
+-- cipher-suites
+-- cipher-suite* identityref
The following tree diagram does not have the groupings expanded:
[Note: '\' line wrapping for formatting only]
module: ietf-tls-client
grouping tls-client-grouping grouping tls-client-grouping
+---u client-identity-grouping
+---u server-auth-grouping
+---u hello-params-grouping
grouping client-identity-grouping
+-- client-identity +-- client-identity
| +-- (auth-type)? +-- (auth-type)?
| +--:(certificate) +--:(certificate)
| +-- certificate +-- certificate
| +---u ks:local-or-keystore-end-entity-certificate-gr\ +---u client-identity-grouping
ouping grouping hello-params-grouping
+-- server-auth
| +-- pinned-ca-certs? ta:pinned-certificates-ref
| +-- pinned-server-certs? ta:pinned-certificates-ref
+-- hello-params {tls-client-hello-params-config}? +-- hello-params {tls-client-hello-params-config}?
+---u tlscmn:hello-params-grouping +---u hello-params-grouping
3.2. Example Usage 3.2. Example Usage
This section presents two examples showing the tls-client-grouping This section presents two examples showing the tls-client-grouping
populated with some data. These examples are effectively the same populated with some data. These examples are effectively the same
except the first configures the client identity using a local key except the first configures the client identity using a local key
while the second uses a key configured in a keystore. Both examples while the second uses a key configured in a keystore. Both examples
are consistent with the examples presented in Section 3 of are consistent with the examples presented in Section 3 of
[I-D.ietf-netconf-trust-anchors] and Section 3.2 of [I-D.ietf-netconf-trust-anchors] and Section 3.2 of
[I-D.ietf-netconf-keystore]. [I-D.ietf-netconf-keystore].
skipping to change at page 7, line 31 skipping to change at page 6, line 31
ver-certs> ver-certs>
</server-auth> </server-auth>
</tls-client> </tls-client>
3.3. YANG Module 3.3. YANG Module
This YANG module has normative references to This YANG module has normative references to
[I-D.ietf-netconf-trust-anchors] and [I-D.ietf-netconf-keystore]. [I-D.ietf-netconf-trust-anchors] and [I-D.ietf-netconf-keystore].
<CODE BEGINS> file "ietf-tls-client@2018-06-04.yang" <CODE BEGINS> file "ietf-tls-client@2018-09-20.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-tls-common { import ietf-tls-common {
prefix tlscmn; prefix tlscmn;
revision-date 2018-06-04; // stable grouping definitions revision-date 2018-09-20; // stable grouping definitions
reference reference
"RFC XXXX: YANG Groupings for TLS Clients and TLS Servers"; "RFC XXXX: YANG Groupings for TLS Clients and TLS Servers";
} }
import ietf-trust-anchors { import ietf-trust-anchors {
prefix ta; prefix ta;
reference reference
"RFC YYYY: YANG Data Model for Global Trust Anchors"; "RFC YYYY: YANG Data Model for Global Trust Anchors";
} }
skipping to change at page 8, line 38 skipping to change at page 7, line 38
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 "2018-06-04" { revision "2018-09-20" {
description description
"Initial version"; "Initial version";
reference reference
"RFC XXXX: YANG Groupings for TLS Clients and TLS Servers"; "RFC XXXX: YANG Groupings for TLS Clients and TLS Servers";
} }
// features // features
feature tls-client-hello-params-config { feature tls-client-hello-params-config {
description description
skipping to change at page 9, line 14 skipping to change at page 8, line 14
} }
// groupings // groupings
grouping tls-client-grouping { grouping tls-client-grouping {
description description
"A reusable grouping for configuring a TLS client without "A reusable grouping for configuring a TLS client without
any consideration for how an underlying TCP session is any consideration for how an underlying TCP session is
established."; established.";
uses client-identity-grouping;
uses server-auth-grouping;
uses hello-params-grouping;
}
grouping client-identity-grouping {
description
"A reusable grouping for configuring a TLS client identity.";
container client-identity { container client-identity {
description description
"The credentials used by the client to authenticate to "The credentials used by the client to authenticate to
the TLS server."; the TLS server.";
choice auth-type { choice auth-type {
description description
"The authentication type."; "The authentication type.";
container certificate { container certificate {
uses ks:local-or-keystore-end-entity-certificate-grouping; uses ks:local-or-keystore-end-entity-certificate-grouping;
description description
"A locally-defined or referenced certificate "A locally-defined or referenced certificate
to be used for client authentication."; to be used for client authentication.";
reference reference
"RFC ZZZZ: YANG Data Model for a 'Keystore' Mechanism"; "RFC ZZZZ: YANG Data Model for a 'Keystore' Mechanism";
} }
} }
} // end client-identity } // end client-identity
} // end client-identity-grouping
grouping server-auth-grouping {
description
"A reusable grouping for configuring TLS server
authentication.";
container server-auth { container server-auth {
must 'pinned-ca-certs or pinned-server-certs'; must 'pinned-ca-certs or pinned-server-certs';
description description
"Trusted server identities."; "Trusted server identities.";
leaf pinned-ca-certs { leaf pinned-ca-certs {
if-feature "ta:x509-certificates";
type ta:pinned-certificates-ref; type ta:pinned-certificates-ref;
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 client to authenticate certificates used by the TLS client to authenticate
TLS server certificates. A server certificate is TLS server certificates. A server certificate is
authenticated if it has a valid chain of trust to authenticated if it has a valid chain of trust to
a configured pinned CA certificate."; a configured pinned CA certificate.";
} }
leaf pinned-server-certs { leaf pinned-server-certs {
if-feature "ta:x509-certificates";
type ta:pinned-certificates-ref; type ta:pinned-certificates-ref;
description description
"A reference to a list of server certificates used by "A reference to a list of server certificates used by
the TLS client to authenticate TLS server certificates. the TLS client to authenticate TLS server certificates.
A server certificate is authenticated if it is an A server certificate is authenticated if it is an
exact match to a configured pinned server certificate."; exact match to a configured pinned server certificate.";
} }
} }
} // end server-auth-grouping
grouping hello-params-grouping {
description
"A reusable grouping for configuring a TLS transport
parameters.";
container hello-params { container hello-params {
if-feature tls-client-hello-params-config; if-feature tls-client-hello-params-config;
uses tlscmn:hello-params-grouping; uses tlscmn:hello-params-grouping;
description description
"Configurable parameters for the TLS hello message."; "Configurable parameters for the TLS hello message.";
} }
} // end transport-params-grouping
} // end tls-client-grouping
} }
<CODE ENDS> <CODE ENDS>
4. The TLS Server Model 4. The TLS Server Model
4.1. Tree Diagram 4.1. Tree Diagram
This section provides two tree diagrams [RFC8340] for the "ietf-tls- This section provides a tree diagram [RFC8340] for the "ietf-tls-
server" module, the first with used groupings expanded and the second server" module that does not have groupings expanded.
with used groupings not expanded.
The following tree diagram has used groupings expanded:
module: ietf-tls-server module: ietf-tls-server
grouping tls-server-grouping grouping hello-params-grouping
+-- server-identity
| +-- (local-or-keystore)
| +--:(local)
| | +-- algorithm ct:key-algorithm-ref
| | +-- public-key binary
| | +-- private-key union
| | +-- cert ct:end-entity-cert-cms
| | +---n certificate-expiration
| | +-- expiration-date? yang:date-and-time
| +--:(keystore) {keystore-implemented}?
| +-- reference
| ks:asymmetric-key-certificate-ref
+-- client-auth
| +-- pinned-ca-certs? ta:pinned-certificates-ref
| +-- pinned-client-certs? ta:pinned-certificates-ref
+-- hello-params {tls-server-hello-params-config}? +-- hello-params {tls-server-hello-params-config}?
+-- tls-versions +---u hello-params-grouping
| +-- tls-version* identityref grouping server-identity-grouping
+-- cipher-suites
+-- cipher-suite* identityref
The following tree diagram does not have the used groupings expanded:
module: ietf-tls-server
grouping tls-server-grouping
+-- server-identity +-- server-identity
| +---u ks:local-or-keystore-end-entity-certificate-grouping +---u server-identity-grouping
grouping tls-server-grouping
+---u server-identity-grouping
+---u client-auth-grouping
+---u hello-params-grouping
grouping client-auth-grouping
+-- client-auth +-- client-auth
| +-- pinned-ca-certs? ta:pinned-certificates-ref +-- pinned-ca-certs? ta:pinned-certificates-ref
| +-- pinned-client-certs? ta:pinned-certificates-ref | {ta:x509-certificates}?
+-- hello-params {tls-server-hello-params-config}? +-- pinned-client-certs? ta:pinned-certificates-ref
+---u tlscmn:hello-params-grouping {ta:x509-certificates}?
4.2. Example Usage 4.2. Example Usage
This section presents two examples showing the tls-server-grouping This section presents two examples showing the tls-server-grouping
populated with some data. These examples are effectively the same populated with some data. These examples are effectively the same
except the first configures the server identity using a local key except the first configures the server identity using a local key
while the second uses a key configured in a keystore. Both examples while the second uses a key configured in a keystore. Both examples
are consistent with the examples presented in Section 3 of are consistent with the examples presented in Section 3 of
[I-D.ietf-netconf-trust-anchors] and Section 3.2 of [I-D.ietf-netconf-trust-anchors] and Section 3.2 of
[I-D.ietf-netconf-keystore]. [I-D.ietf-netconf-keystore].
skipping to change at page 13, line 29 skipping to change at page 12, line 10
ent-certs> ent-certs>
</client-auth> </client-auth>
</tls-server> </tls-server>
4.3. YANG Module 4.3. YANG Module
This YANG module has a normative references to [RFC5246], This YANG module has a normative references to [RFC5246],
[I-D.ietf-netconf-trust-anchors] and [I-D.ietf-netconf-keystore]. [I-D.ietf-netconf-trust-anchors] and [I-D.ietf-netconf-keystore].
<CODE BEGINS> file "ietf-tls-server@2018-06-04.yang" <CODE BEGINS> file "ietf-tls-server@2018-09-20.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-tls-common { import ietf-tls-common {
prefix tlscmn; prefix tlscmn;
revision-date 2018-06-04; // stable grouping definitions revision-date 2018-09-20; // stable grouping definitions
reference reference
"RFC XXXX: YANG Groupings for TLS Clients and TLS Servers"; "RFC XXXX: YANG Groupings for TLS Clients and TLS Servers";
} }
import ietf-trust-anchors { import ietf-trust-anchors {
prefix ta; prefix ta;
reference reference
"RFC YYYY: YANG Data Model for Global Trust Anchors"; "RFC YYYY: YANG Data Model for Global Trust Anchors";
} }
skipping to change at page 14, line 37 skipping to change at page 13, line 18
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 "2018-06-04" { revision "2018-09-20" {
description description
"Initial version"; "Initial version";
reference reference
"RFC XXXX: YANG Groupings for TLS Clients and TLS Servers"; "RFC XXXX: YANG Groupings for TLS Clients and TLS Servers";
} }
// features // features
feature tls-server-hello-params-config { feature tls-server-hello-params-config {
description description
skipping to change at page 15, line 4 skipping to change at page 13, line 32
"RFC XXXX: YANG Groupings for TLS Clients and TLS Servers"; "RFC XXXX: YANG Groupings for TLS Clients and TLS Servers";
} }
// features // features
feature tls-server-hello-params-config { feature tls-server-hello-params-config {
description description
"TLS hello message parameters are configurable on a TLS "TLS hello message parameters are configurable on a TLS
server."; server.";
} }
// groupings // groupings
grouping tls-server-grouping { grouping tls-server-grouping {
description description
"A reusable grouping for configuring a TLS server without "A reusable grouping for configuring a TLS server without
any consideration for how underlying TCP sessions are any consideration for how underlying TCP sessions are
established."; established.";
uses server-identity-grouping;
uses client-auth-grouping;
uses hello-params-grouping;
}
grouping server-identity-grouping {
description
"A reusable grouping for configuring a TLS server identity.";
container server-identity { container server-identity {
description description
"A locally-defined or referenced end-entity certificate, "A locally-defined or referenced end-entity certificate,
including any configured intermediate certificates, the including any configured intermediate certificates, the
TLS server will present when establishing a TLS connection TLS server will present when establishing a TLS connection
in its Certificate message, as defined in Section 7.4.2 in its Certificate message, as defined in Section 7.4.2
in RFC 5246."; in RFC 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
RFC ZZZZ: RFC ZZZZ:
YANG Data Model for a 'Keystore' Mechanism"; YANG Data Model for a 'Keystore' Mechanism";
uses ks:local-or-keystore-end-entity-certificate-grouping; uses ks:local-or-keystore-end-entity-certificate-grouping;
} }
} // end server-identity-grouping
grouping client-auth-grouping {
description
"A reusable grouping for configuring a TLS client
authentication.";
container client-auth { container client-auth {
description description
"A reference to a list of pinned certificate authority (CA) "A reference to a list of pinned certificate authority (CA)
certificates and a reference to a list of pinned client certificates and a reference to a list of pinned client
certificates."; certificates.";
leaf pinned-ca-certs { leaf pinned-ca-certs {
if-feature "ta:x509-certificates";
type ta:pinned-certificates-ref; type ta:pinned-certificates-ref;
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. A client certificate is TLS client certificates. A client certificate is
authenticated if it has a valid chain of trust to authenticated if it has a valid chain of trust to
a configured pinned CA certificate."; a configured pinned CA certificate.";
reference reference
"RFC YYYY: YANG Data Model for Global Trust Anchors"; "RFC YYYY: YANG Data Model for Global Trust Anchors";
} }
leaf pinned-client-certs { leaf pinned-client-certs {
if-feature "ta:x509-certificates";
type ta:pinned-certificates-ref; type ta:pinned-certificates-ref;
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 pinned client certificate."; exact match to a configured pinned client certificate.";
reference reference
"RFC YYYY: YANG Data Model for Global Trust Anchors"; "RFC YYYY: YANG Data Model for Global Trust Anchors";
} }
} }
} // end client-auth-grouping
grouping hello-params-grouping {
description
"A reusable grouping for configuring a TLS transport
parameters.";
container hello-params { container hello-params {
if-feature tls-server-hello-params-config; if-feature tls-server-hello-params-config;
uses tlscmn:hello-params-grouping; uses tlscmn:hello-params-grouping;
description description
"Configurable parameters for the TLS hello message."; "Configurable parameters for the TLS hello message.";
} }
} // end tls-server-grouping } // end tls-server-grouping
} }
skipping to change at page 17, line 27 skipping to change at page 16, line 27
<cipher-suites> <cipher-suites>
<cipher-suite>tlscmn:dhe-rsa-with-aes-128-cbc-sha</cipher-suite> <cipher-suite>tlscmn:dhe-rsa-with-aes-128-cbc-sha</cipher-suite>
<cipher-suite>tlscmn:rsa-with-aes-128-cbc-sha</cipher-suite> <cipher-suite>tlscmn:rsa-with-aes-128-cbc-sha</cipher-suite>
<cipher-suite>tlscmn:rsa-with-3des-ede-cbc-sha</cipher-suite> <cipher-suite>tlscmn:rsa-with-3des-ede-cbc-sha</cipher-suite>
</cipher-suites> </cipher-suites>
</hello-params> </hello-params>
5.3. YANG Module 5.3. YANG Module
This YANG module has a normative references to [RFC2246], [RFC4346], This YANG module has a normative references to [RFC2246], [RFC4346],
[RFC4492], [RFC5246], [RFC5288], and [RFC5289]. [RFC5246], [RFC5288], [RFC5289], and [RFC8422].
<CODE BEGINS> file "ietf-tls-common@2018-06-04.yang" This YANG module has a informative references to [RFC2246],
[RFC4346], and [RFC5246].
<CODE BEGINS> file "ietf-tls-common@2018-09-20.yang"
module ietf-tls-common { module ietf-tls-common {
yang-version 1.1; yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-tls-common"; namespace "urn:ietf:params:xml:ns:yang:ietf-tls-common";
prefix "tlscmn"; prefix "tlscmn";
organization organization
"IETF NETCONF (Network Configuration) Working Group"; "IETF NETCONF (Network Configuration) Working Group";
contact contact
skipping to change at page 18, line 18 skipping to change at page 17, line 22
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 "2018-06-04" { revision "2018-09-20" {
description description
"Initial version"; "Initial version";
reference reference
"RFC XXXX: YANG Groupings for TLS Clients and TLS Servers"; "RFC XXXX: YANG Groupings for TLS Clients and TLS Servers";
} }
// features // features
feature tls-1_0 { feature tls-1_0 {
description description
skipping to change at page 18, line 49 skipping to change at page 18, line 4
Version 1.1"; Version 1.1";
} }
feature tls-1_2 { feature tls-1_2 {
description description
"TLS Protocol Version 1.2 is supported."; "TLS Protocol Version 1.2 is supported.";
reference reference
"RFC 5246: The Transport Layer Security (TLS) Protocol "RFC 5246: The Transport Layer Security (TLS) Protocol
Version 1.2"; Version 1.2";
} }
feature tls-ecc { feature tls-ecc {
description description
"Elliptic Curve Cryptography (ECC) is supported for TLS."; "Elliptic Curve Cryptography (ECC) is supported for TLS.";
reference reference
"RFC 4492: Elliptic Curve Cryptography (ECC) Cipher Suites "RFC 8422: Elliptic Curve Cryptography (ECC) Cipher Suites
for Transport Layer Security (TLS)"; for Transport Layer Security (TLS)";
} }
feature tls-dhe { feature tls-dhe {
description description
"Ephemeral Diffie-Hellman key exchange is supported for TLS."; "Ephemeral Diffie-Hellman key exchange is supported for TLS.";
reference reference
"RFC 5246: The Transport Layer Security (TLS) Protocol "RFC 5246: The Transport Layer Security (TLS) Protocol
Version 1.2"; Version 1.2";
} }
skipping to change at page 24, line 16 skipping to change at page 23, line 20
"RFC 5246: The Transport Layer Security (TLS) Protocol "RFC 5246: The Transport Layer Security (TLS) Protocol
Version 1.2"; Version 1.2";
} }
identity ecdhe-rsa-with-3des-ede-cbc-sha { identity ecdhe-rsa-with-3des-ede-cbc-sha {
base cipher-suite-base; base cipher-suite-base;
if-feature "tls-ecc and tls-3des"; if-feature "tls-ecc and tls-3des";
description description
"Cipher suite TLS_ECDHE_RSA_WITH_3DES_EDE_CBC_SHA."; "Cipher suite TLS_ECDHE_RSA_WITH_3DES_EDE_CBC_SHA.";
reference reference
"RFC 4492: Elliptic Curve Cryptography (ECC) Cipher Suites "RFC 8422: Elliptic Curve Cryptography (ECC) Cipher Suites
for Transport Layer Security (TLS)"; for Transport Layer Security (TLS)";
} }
identity ecdhe-rsa-with-aes-128-cbc-sha { identity ecdhe-rsa-with-aes-128-cbc-sha {
base cipher-suite-base; base cipher-suite-base;
if-feature "tls-ecc"; if-feature "tls-ecc";
description description
"Cipher suite TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA."; "Cipher suite TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA.";
reference reference
"RFC 4492: Elliptic Curve Cryptography (ECC) Cipher Suites "RFC 8422: Elliptic Curve Cryptography (ECC) Cipher Suites
for Transport Layer Security (TLS)"; for Transport Layer Security (TLS)";
} }
identity ecdhe-rsa-with-aes-256-cbc-sha { identity ecdhe-rsa-with-aes-256-cbc-sha {
base cipher-suite-base; base cipher-suite-base;
if-feature "tls-ecc"; if-feature "tls-ecc";
description description
"Cipher suite TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA."; "Cipher suite TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA.";
reference reference
"RFC 4492: Elliptic Curve Cryptography (ECC) Cipher Suites "RFC 8422: Elliptic Curve Cryptography (ECC) Cipher Suites
for Transport Layer Security (TLS)"; for Transport Layer Security (TLS)";
} }
// groupings // groupings
grouping hello-params-grouping { grouping hello-params-grouping {
description description
"A reusable grouping for TLS hello message parameters."; "A reusable grouping for TLS hello message parameters.";
reference reference
"RFC 5246: The Transport Layer Security (TLS) Protocol "RFC 5246: The Transport Layer Security (TLS) Protocol
skipping to change at page 25, line 48 skipping to change at page 25, line 5
<CODE ENDS> <CODE ENDS>
6. Security Considerations 6. Security Considerations
The YANG modules defined in this document are designed to be accessed The YANG modules defined in this document are designed to be accessed
via YANG based management protocols, such as NETCONF [RFC6241] and via YANG based management protocols, such as NETCONF [RFC6241] and
RESTCONF [RFC8040]. Both of these protocols have mandatory-to- RESTCONF [RFC8040]. Both of these protocols have mandatory-to-
implement secure transport layers (e.g., SSH, TLS) with mutual implement secure transport layers (e.g., SSH, TLS) with mutual
authentication. authentication.
The NETCONF access control model (NACM) [RFC6536] provides the means The NETCONF access control model (NACM) [RFC8341] provides the means
to restrict access for particular users to a pre-configured subset of to restrict access for particular users to a pre-configured subset of
all available protocol operations and content. all available protocol operations and content.
Since the modules defined in this document only define groupings, Since the modules defined in this document only define groupings,
these considerations are primarily for the designers of other modules these considerations are primarily for the designers of other modules
that use these groupings. that use these groupings.
There are a number of data nodes defined in the YANG modules that are There are a number of data nodes defined in the YANG modules that are
writable/creatable/deletable (i.e., config true, which is the writable/creatable/deletable (i.e., config true, which is the
default). These data nodes may be considered sensitive or vulnerable default). These data nodes may be considered sensitive or vulnerable
skipping to change at page 26, line 44 skipping to change at page 25, line 48
sensitive or vulnerable in some network environments. It is thus sensitive or vulnerable in some network environments. It is thus
important to control access to these operations. These are the important to control access to these operations. These are the
operations and their sensitivity/vulnerability: operations and their sensitivity/vulnerability:
NONE NONE
7. IANA Considerations 7. IANA Considerations
7.1. The IETF XML Registry 7.1. The IETF XML Registry
This document registers three URIs in the IETF XML registry This document registers three URIs in the "ns" subregistry of the
[RFC3688]. Following the format in [RFC3688], the following IETF XML Registry [RFC3688]. Following the format in [RFC3688], the
registrations are requested: 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.
URI: urn:ietf:params:xml:ns:yang:ietf-tls-common URI: urn:ietf:params:xml:ns:yang:ietf-tls-common
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.
7.2. The YANG Module Names Registry 7.2. The YANG Module Names Registry
This document registers three YANG modules in the YANG Module Names This document registers three YANG modules in the YANG Module Names
registry [RFC7950]. Following the format in [RFC7950], the the registry [RFC6020]. Following the format in [RFC6020], 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
name: ietf-tls-common name: ietf-tls-common
namespace: urn:ietf:params:xml:ns:yang:ietf-tls-common namespace: urn:ietf:params:xml:ns:yang:ietf-tls-common
prefix: tlscmn prefix: tlscmn
reference: RFC XXXX reference: RFC XXXX
8. Acknowledgements 8. References
The authors would like to thank for following for lively discussions
on list and in the halls (ordered by last name): Andy Bierman, Martin
Bjorklund, Benoit Claise, Mehmet Ersue, Balazs Kovacs, David
Lamparter, Alan Luchuk, Ladislav Lhotka, Radek Krejci, Tom Petch,
Juergen Schoenwaelder, Phil Shafer, Sean Turner, and Bert Wijnen.
9. References
9.1. Normative References 8.1. Normative References
[I-D.ietf-netconf-keystore] [I-D.ietf-netconf-keystore]
Watsen, K., "YANG Data Model for a "Keystore" Mechanism", Watsen, K., "YANG Data Model for a Centralized Keystore
draft-ietf-netconf-keystore-04 (work in progress), October Mechanism", draft-ietf-netconf-keystore-06 (work in
2017. progress), September 2018.
[I-D.ietf-netconf-trust-anchors] [I-D.ietf-netconf-trust-anchors]
Watsen, K., "YANG Data Model for Global Trust Anchors", Watsen, K., "YANG Data Model for Global Trust Anchors",
draft-ietf-netconf-trust-anchors-00 (work in progress), draft-ietf-netconf-trust-anchors-01 (work in progress),
June 2018. September 2018.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>. <https://www.rfc-editor.org/info/rfc2119>.
[RFC2246] Dierks, T. and C. Allen, "The TLS Protocol Version 1.0",
RFC 2246, DOI 10.17487/RFC2246, January 1999,
<https://www.rfc-editor.org/info/rfc2246>.
[RFC4346] Dierks, T. and E. Rescorla, "The Transport Layer Security
(TLS) Protocol Version 1.1", RFC 4346,
DOI 10.17487/RFC4346, April 2006,
<https://www.rfc-editor.org/info/rfc4346>.
[RFC4492] Blake-Wilson, S., Bolyard, N., Gupta, V., Hawk, C., and B.
Moeller, "Elliptic Curve Cryptography (ECC) Cipher Suites
for Transport Layer Security (TLS)", RFC 4492,
DOI 10.17487/RFC4492, May 2006,
<https://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,
<https://www.rfc-editor.org/info/rfc5246>.
[RFC5288] Salowey, J., Choudhury, A., and D. McGrew, "AES Galois [RFC5288] Salowey, J., Choudhury, A., and D. McGrew, "AES Galois
Counter Mode (GCM) Cipher Suites for TLS", RFC 5288, Counter Mode (GCM) Cipher Suites for TLS", RFC 5288,
DOI 10.17487/RFC5288, August 2008, DOI 10.17487/RFC5288, August 2008,
<https://www.rfc-editor.org/info/rfc5288>. <https://www.rfc-editor.org/info/rfc5288>.
[RFC5289] Rescorla, E., "TLS Elliptic Curve Cipher Suites with SHA- [RFC5289] Rescorla, E., "TLS Elliptic Curve Cipher Suites with SHA-
256/384 and AES Galois Counter Mode (GCM)", RFC 5289, 256/384 and AES Galois Counter Mode (GCM)", RFC 5289,
DOI 10.17487/RFC5289, August 2008, DOI 10.17487/RFC5289, August 2008,
<https://www.rfc-editor.org/info/rfc5289>. <https://www.rfc-editor.org/info/rfc5289>.
[RFC6536] Bierman, A. and M. Bjorklund, "Network Configuration [RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for
Protocol (NETCONF) Access Control Model", RFC 6536, the Network Configuration Protocol (NETCONF)", RFC 6020,
DOI 10.17487/RFC6536, March 2012, DOI 10.17487/RFC6020, October 2010,
<https://www.rfc-editor.org/info/rfc6536>. <https://www.rfc-editor.org/info/rfc6020>.
[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,
<https://www.rfc-editor.org/info/rfc7589>. <https://www.rfc-editor.org/info/rfc7589>.
[RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language", [RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language",
RFC 7950, DOI 10.17487/RFC7950, August 2016, RFC 7950, DOI 10.17487/RFC7950, August 2016,
<https://www.rfc-editor.org/info/rfc7950>. <https://www.rfc-editor.org/info/rfc7950>.
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/info/rfc8174>. May 2017, <https://www.rfc-editor.org/info/rfc8174>.
9.2. Informative References [RFC8341] Bierman, A. and M. Bjorklund, "Network Configuration
Access Control Model", STD 91, RFC 8341,
DOI 10.17487/RFC8341, March 2018,
<https://www.rfc-editor.org/info/rfc8341>.
[RFC8422] Nir, Y., Josefsson, S., and M. Pegourie-Gonnard, "Elliptic
Curve Cryptography (ECC) Cipher Suites for Transport Layer
Security (TLS) Versions 1.2 and Earlier", RFC 8422,
DOI 10.17487/RFC8422, August 2018,
<https://www.rfc-editor.org/info/rfc8422>.
8.2. Informative References
[RFC2246] Dierks, T. and C. Allen, "The TLS Protocol Version 1.0",
RFC 2246, DOI 10.17487/RFC2246, January 1999,
<https://www.rfc-editor.org/info/rfc2246>.
[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,
<https://www.rfc-editor.org/info/rfc2818>. <https://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,
<https://www.rfc-editor.org/info/rfc3688>. <https://www.rfc-editor.org/info/rfc3688>.
[RFC4346] Dierks, T. and E. Rescorla, "The Transport Layer Security
(TLS) Protocol Version 1.1", RFC 4346,
DOI 10.17487/RFC4346, April 2006,
<https://www.rfc-editor.org/info/rfc4346>.
[RFC5246] Dierks, T. and E. Rescorla, "The Transport Layer Security
(TLS) Protocol Version 1.2", RFC 5246,
DOI 10.17487/RFC5246, August 2008,
<https://www.rfc-editor.org/info/rfc5246>.
[RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed.,
and A. Bierman, Ed., "Network Configuration Protocol and A. Bierman, Ed., "Network Configuration Protocol
(NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011, (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011,
<https://www.rfc-editor.org/info/rfc6241>. <https://www.rfc-editor.org/info/rfc6241>.
[RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF [RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF
Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017, Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017,
<https://www.rfc-editor.org/info/rfc8040>. <https://www.rfc-editor.org/info/rfc8040>.
[RFC8071] Watsen, K., "NETCONF Call Home and RESTCONF Call Home", [RFC8071] Watsen, K., "NETCONF Call Home and RESTCONF Call Home",
skipping to change at page 31, line 17 skipping to change at page 30, line 17
o Merged changes from co-author. o Merged changes from co-author.
A.6. 05 to 06 A.6. 05 to 06
o Updated to use trust anchors from trust-anchors draft (was o Updated to use trust anchors from trust-anchors draft (was
keystore draft) keystore draft)
o Now Uses new keystore grouping enabling asymmetric key to be o Now Uses new keystore grouping enabling asymmetric key to be
either locally defined or a reference to the keystore. either locally defined or a reference to the keystore.
A.7. 06 to 07
o factored the tls-[client|server]-groupings into more reusable
groupings.
o added if-feature statements for the new "x509-certificates"
feature defined in draft-ietf-netconf-trust-anchors.
Acknowledgements
The authors would like to thank for following for lively discussions
on list and in the halls (ordered by last name): Andy Bierman, Martin
Bjorklund, Benoit Claise, Mehmet Ersue, Balazs Kovacs, David
Lamparter, Alan Luchuk, Ladislav Lhotka, Radek Krejci, Tom Petch,
Juergen Schoenwaelder, Phil Shafer, Sean Turner, and Bert Wijnen.
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 Systems Cisco Systems
 End of changes. 66 change blocks. 
179 lines changed or deleted 179 lines changed or added

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