draft-ietf-netconf-tls-client-server-08.txt   draft-ietf-netconf-tls-client-server-09.txt 
NETCONF Working Group K. Watsen NETCONF Working Group K. Watsen
Internet-Draft Juniper Networks Internet-Draft Watsen Networks
Intended status: Standards Track G. Wu Intended status: Standards Track G. Wu
Expires: April 25, 2019 Cisco Systems Expires: September 10, 2019 Cisco Systems
L. Xia L. Xia
Huawei Huawei
October 22, 2018 March 9, 2019
YANG Groupings for TLS Clients and TLS Servers YANG Groupings for TLS Clients and TLS Servers
draft-ietf-netconf-tls-client-server-08 draft-ietf-netconf-tls-client-server-09
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 2, line 5 skipping to change at page 2, line 5
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-10-22" --> the publication date of this draft o "2019-03-09" --> 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 April 25, 2019. This Internet-Draft will expire on September 10, 2019.
Copyright Notice Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the Copyright (c) 2019 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
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
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 . . . . . . . . . . . . . . . . . . . . . . 4 3.2. Example Usage . . . . . . . . . . . . . . . . . . . . . . 5
3.3. YANG Module . . . . . . . . . . . . . . . . . . . . . . . 6 3.3. YANG Module . . . . . . . . . . . . . . . . . . . . . . . 6
4. The TLS Server Model . . . . . . . . . . . . . . . . . . . . 9 4. The TLS Server Model . . . . . . . . . . . . . . . . . . . . 10
4.1. Tree Diagram . . . . . . . . . . . . . . . . . . . . . . 9 4.1. Tree Diagram . . . . . . . . . . . . . . . . . . . . . . 10
4.2. Example Usage . . . . . . . . . . . . . . . . . . . . . . 10 4.2. Example Usage . . . . . . . . . . . . . . . . . . . . . . 11
4.3. YANG Module . . . . . . . . . . . . . . . . . . . . . . . 12 4.3. YANG Module . . . . . . . . . . . . . . . . . . . . . . . 13
5. The TLS Common Model . . . . . . . . . . . . . . . . . . . . 15 5. The TLS Common Model . . . . . . . . . . . . . . . . . . . . 17
5.1. Tree Diagram . . . . . . . . . . . . . . . . . . . . . . 24 5.1. Tree Diagram . . . . . . . . . . . . . . . . . . . . . . 25
5.2. Example Usage . . . . . . . . . . . . . . . . . . . . . . 24 5.2. Example Usage . . . . . . . . . . . . . . . . . . . . . . 25
5.3. YANG Module . . . . . . . . . . . . . . . . . . . . . . . 24 5.3. YANG Module . . . . . . . . . . . . . . . . . . . . . . . 25
6. Security Considerations . . . . . . . . . . . . . . . . . . . 33 6. Security Considerations . . . . . . . . . . . . . . . . . . . 34
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 34 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 35
7.1. The IETF XML Registry . . . . . . . . . . . . . . . . . . 34 7.1. The IETF XML Registry . . . . . . . . . . . . . . . . . . 35
7.2. The YANG Module Names Registry . . . . . . . . . . . . . 34 7.2. The YANG Module Names Registry . . . . . . . . . . . . . 35
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 35 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 36
8.1. Normative References . . . . . . . . . . . . . . . . . . 35 8.1. Normative References . . . . . . . . . . . . . . . . . . 36
8.2. Informative References . . . . . . . . . . . . . . . . . 36 8.2. Informative References . . . . . . . . . . . . . . . . . 37
Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 38 Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 39
A.1. 00 to 01 . . . . . . . . . . . . . . . . . . . . . . . . 38 A.1. 00 to 01 . . . . . . . . . . . . . . . . . . . . . . . . 39
A.2. 01 to 02 . . . . . . . . . . . . . . . . . . . . . . . . 38 A.2. 01 to 02 . . . . . . . . . . . . . . . . . . . . . . . . 39
A.3. 02 to 03 . . . . . . . . . . . . . . . . . . . . . . . . 38 A.3. 02 to 03 . . . . . . . . . . . . . . . . . . . . . . . . 39
A.4. 03 to 04 . . . . . . . . . . . . . . . . . . . . . . . . 38 A.4. 03 to 04 . . . . . . . . . . . . . . . . . . . . . . . . 39
A.5. 04 to 05 . . . . . . . . . . . . . . . . . . . . . . . . 39 A.5. 04 to 05 . . . . . . . . . . . . . . . . . . . . . . . . 40
A.6. 05 to 06 . . . . . . . . . . . . . . . . . . . . . . . . 39 A.6. 05 to 06 . . . . . . . . . . . . . . . . . . . . . . . . 40
A.7. 06 to 07 . . . . . . . . . . . . . . . . . . . . . . . . 39 A.7. 06 to 07 . . . . . . . . . . . . . . . . . . . . . . . . 40
A.8. 07 to 08 . . . . . . . . . . . . . . . . . . . . . . . . 39 A.8. 07 to 08 . . . . . . . . . . . . . . . . . . . . . . . . 40
Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 39 A.9. 08 to 09 . . . . . . . . . . . . . . . . . . . . . . . . 40
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 39 Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 40
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 41
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 4, line 5 skipping to change at page 4, line 5
The client and server YANG modules in this document each define one The client and server YANG modules in this document each define one
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 use 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 a tree diagram [RFC8340] for the "ietf-tls- This section provides a tree diagram [RFC8340] for the "ietf-tls-
client" module that does not have groupings expanded. client" module that does not have groupings expanded.
module: ietf-tls-client module: ietf-tls-client
grouping server-auth-grouping
+-- server-auth
+-- pinned-ca-certs? ta:pinned-certificates-ref
| {ta:x509-certificates}?
+-- pinned-server-certs? ta:pinned-certificates-ref
{ta:x509-certificates}?
grouping tls-client-grouping grouping tls-client-grouping
+---u client-identity-grouping +---u client-identity-grouping
+---u server-auth-grouping +---u server-auth-grouping
+---u hello-params-grouping +---u hello-params-grouping
+---u keepalives-grouping
grouping client-identity-grouping grouping client-identity-grouping
+-- client-identity +-- tls-client-identity
+-- (auth-type)? +-- (auth-type)?
+--:(certificate) +--:(certificate)
+-- certificate +-- certificate
+---u client-identity-grouping +---u client-identity-grouping
grouping server-auth-grouping
+-- tls-server-auth
+-- pinned-ca-certs? ta:pinned-certificates-ref
| {ta:x509-certificates}?
+-- pinned-server-certs? ta:pinned-certificates-ref
{ta:x509-certificates}?
grouping hello-params-grouping grouping hello-params-grouping
+-- hello-params {tls-client-hello-params-config}? +-- tls-hello-params {tls-client-hello-params-config}?
+---u hello-params-grouping +---u hello-params-grouping
grouping keepalives-grouping
+-- tls-keepalives {tls-client-keepalives}?
+-- max-wait? uint16
+-- max-attempts? uint8
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].
The following example configures the client identity using a local The following example configures the client identity using a local
key: key:
[Note: '\' line wrapping for formatting only] ========== NOTE: '\\' line wrapping per BCP XX (RFC XXXX) ===========
<tls-client xmlns="urn:ietf:params:xml:ns:yang:ietf-tls-client"> <tls-client xmlns="urn:ietf:params:xml:ns:yang:ietf-tls-client">
<!-- how this client will authenticate itself to the server --> <!-- how this client will authenticate itself to the server -->
<client-identity> <tls-client-identity>
<certificate> <certificate>
<algorithm xmlns:ct="urn:ietf:params:xml:ns:yang:ietf-crypto-t\ <local-definition>
ypes">ct:rsa2048</algorithm> <algorithm xmlns:ct="urn:ietf:params:xml:ns:yang:ietf-crypto\
<private-key>base64encodedvalue==</private-key> \-types">ct:rsa2048</algorithm>
<public-key>base64encodedvalue==</public-key> <private-key>base64encodedvalue==</private-key>
<cert>base64encodedvalue==</cert> <public-key>base64encodedvalue==</public-key>
<cert>base64encodedvalue==</cert>
</local-definition>
</certificate> </certificate>
</client-identity> </tls-client-identity>
<!-- which certificates will this client trust --> <!-- which certificates will this client trust -->
<server-auth> <tls-server-auth>
<pinned-ca-certs>explicitly-trusted-server-ca-certs</pinned-ca-c\ <pinned-ca-certs>explicitly-trusted-server-ca-certs</pinned-ca-c\
erts> \erts>
<pinned-server-certs>explicitly-trusted-server-certs</pinned-ser\ <pinned-server-certs>explicitly-trusted-server-certs</pinned-ser\
ver-certs> \ver-certs>
</server-auth> </tls-server-auth>
<tls-keepalives>
<max-wait>30</max-wait>
<max-attempts>3</max-attempts>
</tls-keepalives>
</tls-client> </tls-client>
The following example configures the client identity using a key from The following example configures the client identity using a key from
the keystore: the keystore:
[Note: '\' line wrapping for formatting only] ========== NOTE: '\\' line wrapping per BCP XX (RFC XXXX) ===========
<tls-client xmlns="urn:ietf:params:xml:ns:yang:ietf-tls-client"> <tls-client xmlns="urn:ietf:params:xml:ns:yang:ietf-tls-client">
<!-- how this client will authenticate itself to the server --> <!-- how this client will authenticate itself to the server -->
<client-identity> <tls-client-identity>
<certificate> <certificate>
<reference>ex-rsa-cert</reference> <keystore-reference>ex-rsa-cert</keystore-reference>
</certificate> </certificate>
</client-identity> </tls-client-identity>
<!-- which certificates will this client trust --> <!-- which certificates will this client trust -->
<server-auth> <tls-server-auth>
<pinned-ca-certs>explicitly-trusted-server-ca-certs</pinned-ca-c\ <pinned-ca-certs>explicitly-trusted-server-ca-certs</pinned-ca-c\
erts> \erts>
<pinned-server-certs>explicitly-trusted-server-certs</pinned-ser\ <pinned-server-certs>explicitly-trusted-server-certs</pinned-ser\
ver-certs> \ver-certs>
</server-auth> </tls-server-auth>
<tls-keepalives>
<max-wait>30</max-wait>
<max-attempts>3</max-attempts>
</tls-keepalives>
</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-10-22.yang" <CODE BEGINS> file "ietf-tls-client@2019-03-09.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-10-22; // stable grouping definitions revision-date 2019-03-09; // 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";
}
import ietf-keystore { }
prefix ks;
reference
"RFC ZZZZ: YANG Data Model for a 'Keystore' Mechanism";
}
organization import ietf-keystore {
"IETF NETCONF (Network Configuration) Working Group"; prefix ks;
reference
"RFC ZZZZ: YANG Data Model for a 'Keystore' Mechanism";
}
contact organization
"WG Web: <http://datatracker.ietf.org/wg/netconf/> "IETF NETCONF (Network Configuration) Working Group";
WG List: <mailto:netconf@ietf.org>
Author: Kent Watsen contact
<mailto:kwatsen@juniper.net> "WG Web: <http://datatracker.ietf.org/wg/netconf/>
WG List: <mailto:netconf@ietf.org>
Author: Kent Watsen <mailto:kent+ietf@watsen.net>
Author: Gary Wu <mailto:garywu@cisco.com>";
Author: Gary Wu description
<mailto:garywu@cisco.com>"; "This module defines reusable groupings for TLS clients that
can be used as a basis for specific TLS client instances.
description The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL',
"This module defines a reusable grouping for a TLS client that 'SHALL NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED',
can be used as a basis for specific TLS client instances. 'NOT RECOMMENDED', 'MAY', and 'OPTIONAL' in this document
are to be interpreted as described in BCP 14 [RFC2119]
[RFC8174] when, and only when, they appear in all
capitals, as shown here.
Copyright (c) 2018 IETF Trust and the persons identified as Copyright (c) 2019 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 "2018-10-22" { revision "2019-03-09" {
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 {
description
"TLS hello message parameters are configurable on a TLS
client.";
}
feature tls-client-hello-params-config { feature tls-client-keepalives {
description description
"TLS hello message parameters are configurable on a TLS "Per socket TLS keepalive parameters are configurable for
client."; TLS clients on the server implementing this feature.";
}
} // Groupings
// groupings grouping tls-client-grouping {
description
"A reusable grouping for configuring a TLS client without
any consideration for how an underlying TCP session is
established.";
uses client-identity-grouping;
uses server-auth-grouping;
uses hello-params-grouping;
uses keepalives-grouping;
}
grouping tls-client-grouping { grouping client-identity-grouping {
description description
"A reusable grouping for configuring a TLS client without "A reusable grouping for configuring a TLS client identity.";
any consideration for how an underlying TCP session is container tls-client-identity {
established."; description
uses client-identity-grouping; "The credentials used by the client to authenticate to
uses server-auth-grouping; the TLS server.";
uses hello-params-grouping;
}
grouping client-identity-grouping { choice auth-type {
description description
"A reusable grouping for configuring a TLS client identity."; "The authentication type.";
container client-identity { container certificate {
description uses
"The credentials used by the client to authenticate to ks:local-or-keystore-end-entity-cert-with-key-grouping;
the TLS server."; description
"A locally-defined or referenced certificate
to be used for client authentication.";
reference
"RFC ZZZZ: YANG Data Model for a 'Keystore' Mechanism";
}
}
choice auth-type { }
description }
"The authentication type.";
container certificate {
uses ks:local-or-keystore-end-entity-cert-with-key-grouping;
description
"A locally-defined or referenced certificate
to be used for client authentication.";
reference
"RFC ZZZZ: YANG Data Model for a 'Keystore' Mechanism";
}
}
} // end client-identity
} // end client-identity-grouping
grouping server-auth-grouping { grouping server-auth-grouping {
description description
"A reusable grouping for configuring TLS server "A reusable grouping for configuring TLS server
authentication."; authentication.";
container server-auth { container tls-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"; 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"; 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 { grouping hello-params-grouping {
description description
"A reusable grouping for configuring a TLS transport "A reusable grouping for configuring a TLS transport
parameters."; parameters.";
container hello-params { container tls-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 }
} grouping keepalives-grouping {
<CODE ENDS> description
"A reusable grouping for configuring TLS client keepalive
parameters.";
container tls-keepalives {
if-feature "tls-client-keepalives";
description
"Configures the keep-alive policy, to proactively test
the aliveness of the TLS server. An unresponsive
TLS server is dropped after approximately max-wait
* max-attempts seconds.";
leaf max-wait {
type uint16 {
range "1..max";
}
units seconds;
default 30;
description
"Sets the amount of time in seconds after which if no data
has been received from the TLS server, a TLS-level message
will be sent to test the aliveness of the TLS server.";
}
leaf max-attempts {
type uint8;
default 3;
description
"Sets the maximum number of sequential keep-alive messages
that can fail to obtain a response from the TLS server
before assuming the TLS server is no longer alive.";
}
}
}
}
<CODE ENDS>
4. The TLS Server Model 4. The TLS Server Model
4.1. Tree Diagram 4.1. Tree Diagram
This section provides a tree diagram [RFC8340] for the "ietf-tls- This section provides a tree diagram [RFC8340] for the "ietf-tls-
server" module that does not have groupings expanded. server" module that does not have groupings expanded.
module: ietf-tls-server module: ietf-tls-server
grouping hello-params-grouping
+-- hello-params {tls-server-hello-params-config}?
+---u hello-params-grouping
grouping server-identity-grouping
+-- server-identity
+---u server-identity-grouping
grouping tls-server-grouping grouping tls-server-grouping
+---u server-identity-grouping +---u server-identity-grouping
+---u client-auth-grouping +---u client-auth-grouping
+---u hello-params-grouping +---u hello-params-grouping
+---u keepalives-grouping
grouping server-identity-grouping
+-- tls-server-identity
+---u server-identity-grouping
grouping client-auth-grouping grouping client-auth-grouping
+-- client-auth +-- tls-client-auth
+-- pinned-ca-certs? ta:pinned-certificates-ref +-- pinned-ca-certs? ta:pinned-certificates-ref
| {ta:x509-certificates}? | {ta:x509-certificates}?
+-- pinned-client-certs? ta:pinned-certificates-ref +-- pinned-client-certs? ta:pinned-certificates-ref
{ta:x509-certificates}? {ta:x509-certificates}?
grouping hello-params-grouping
+-- tls-hello-params {tls-server-hello-params-config}?
+---u hello-params-grouping
grouping keepalives-grouping
+-- tls-keepalives {tls-server-keepalives}?
+-- max-wait? uint16
+-- max-attempts? uint8
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].
The following example configures the server identity using a local The following example configures the server identity using a local
key: key:
[Note: '\' line wrapping for formatting only] ========== NOTE: '\\' line wrapping per BCP XX (RFC XXXX) ===========
<tls-server xmlns="urn:ietf:params:xml:ns:yang:ietf-tls-server"> <tls-server xmlns="urn:ietf:params:xml:ns:yang:ietf-tls-server">
<!-- how this server will authenticate itself to the client --> <!-- how this server will authenticate itself to the client -->
<server-identity> <tls-server-identity>
<algorithm xmlns:ct="urn:ietf:params:xml:ns:yang:ietf-crypto-typ\ <local-definition>
es">ct:rsa2048</algorithm> <algorithm xmlns:ct="urn:ietf:params:xml:ns:yang:ietf-crypto-t\
<private-key>base64encodedvalue==</private-key> \ypes">ct:rsa2048</algorithm>
<public-key>base64encodedvalue==</public-key> <private-key>base64encodedvalue==</private-key>
<cert>base64encodedvalue==</cert> <public-key>base64encodedvalue==</public-key>
</server-identity> <cert>base64encodedvalue==</cert>
</local-definition>
</tls-server-identity>
<!-- which certificates will this server trust --> <!-- which certificates will this server trust -->
<client-auth> <tls-client-auth>
<pinned-ca-certs>explicitly-trusted-client-ca-certs</pinned-ca-c\ <pinned-ca-certs>explicitly-trusted-client-ca-certs</pinned-ca-c\
erts> \erts>
<pinned-client-certs>explicitly-trusted-client-certs</pinned-cli\ <pinned-client-certs>explicitly-trusted-client-certs</pinned-cli\
ent-certs> \ent-certs>
</client-auth> </tls-client-auth>
</tls-server> </tls-server>
The following example configures the server identity using a key from The following example configures the server identity using a key from
the keystore: the keystore:
[Note: '\' line wrapping for formatting only] ========== NOTE: '\\' line wrapping per BCP XX (RFC XXXX) ===========
<tls-server xmlns="urn:ietf:params:xml:ns:yang:ietf-tls-server"> <tls-server xmlns="urn:ietf:params:xml:ns:yang:ietf-tls-server">
<!-- how this server will authenticate itself to the client --> <!-- how this server will authenticate itself to the client -->
<server-identity> <tls-server-identity>
<reference>ex-rsa-cert</reference> <keystore-reference>ex-rsa-cert</keystore-reference>
</server-identity> </tls-server-identity>
<!-- which certificates will this server trust --> <!-- which certificates will this server trust -->
<client-auth> <tls-client-auth>
<pinned-ca-certs>explicitly-trusted-client-ca-certs</pinned-ca-c\ <pinned-ca-certs>explicitly-trusted-client-ca-certs</pinned-ca-c\
erts> \erts>
<pinned-client-certs>explicitly-trusted-client-certs</pinned-cli\ <pinned-client-certs>explicitly-trusted-client-certs</pinned-cli\
ent-certs> \ent-certs>
</client-auth> </tls-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-10-22.yang" <CODE BEGINS> file "ietf-tls-server@2019-03-09.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-10-22; // stable grouping definitions revision-date 2019-03-09; // 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 12, line 42 skipping to change at page 13, line 41
reference reference
"RFC ZZZZ: YANG Data Model for a 'Keystore' Mechanism"; "RFC ZZZZ: YANG Data Model for a 'Keystore' Mechanism";
} }
organization organization
"IETF NETCONF (Network Configuration) Working Group"; "IETF NETCONF (Network Configuration) Working Group";
contact contact
"WG Web: <http://datatracker.ietf.org/wg/netconf/> "WG Web: <http://datatracker.ietf.org/wg/netconf/>
WG List: <mailto:netconf@ietf.org> WG List: <mailto:netconf@ietf.org>
Author: Kent Watsen <mailto:kent+ietf@watsen.net>
Author: Kent Watsen Author: Gary Wu <mailto:garywu@cisco.com>";
<mailto:kwatsen@juniper.net>
Author: Gary Wu
<mailto:garywu@cisco.com>";
description description
"This module defines a reusable grouping for a TLS server that "This module defines reusable groupings for TLS servers 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) 2018 IETF Trust and the persons identified as The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL',
'SHALL NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED',
'NOT RECOMMENDED', 'MAY', and 'OPTIONAL' in this document
are to be interpreted as described in BCP 14 [RFC2119]
[RFC8174] when, and only when, they appear in all
capitals, as shown here.
Copyright (c) 2019 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 "2018-10-22" { revision "2019-03-09" {
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
"TLS hello message parameters are configurable on a TLS "TLS hello message parameters are configurable on a TLS
server."; server.";
} }
// groupings feature tls-server-keepalives {
description
"Per socket TLS keepalive parameters are configurable for
TLS servers on the server implementing this feature.";
}
// 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 server-identity-grouping;
uses client-auth-grouping; uses client-auth-grouping;
uses hello-params-grouping; uses hello-params-grouping;
uses keepalives-grouping;
} }
grouping server-identity-grouping { grouping server-identity-grouping {
description description
"A reusable grouping for configuring a TLS server identity."; "A reusable grouping for configuring a TLS server identity.";
container server-identity { container tls-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-cert-with-key-grouping; uses ks:local-or-keystore-end-entity-cert-with-key-grouping;
} }
} // end server-identity-grouping }
grouping client-auth-grouping { grouping client-auth-grouping {
description description
"A reusable grouping for configuring a TLS client "A reusable grouping for configuring a TLS client
authentication."; authentication.";
container client-auth { container tls-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"; 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
skipping to change at page 14, line 43 skipping to change at page 16, line 4
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"; 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 { grouping hello-params-grouping {
description description
"A reusable grouping for configuring a TLS transport "A reusable grouping for configuring a TLS transport
parameters."; parameters.";
container hello-params { container tls-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 grouping keepalives-grouping {
description
"A reusable grouping for configuring TLS server keepalive
parameters.";
container tls-keepalives {
if-feature "tls-server-keepalives";
description
"Configures the keep-alive policy, to proactively test
the aliveness of the TLS client. An unresponsive
TLS client is dropped after approximately max-wait
* max-attempts seconds.";
leaf max-wait {
type uint16 {
range "1..max";
}
units seconds;
default 30;
description
"Sets the amount of time in seconds after which if no data
has been received from the TLS client, a TLS-level message
will be sent to test the aliveness of the TLS client.";
}
leaf max-attempts {
type uint8;
default 3;
description
"Sets the maximum number of sequential keep-alive messages
that can fail to obtain a response from the TLS client
before assuming the TLS client is no longer alive.";
}
}
}
} }
<CODE ENDS> <CODE ENDS>
5. The TLS Common Model 5. The TLS Common Model
The TLS common model presented in this section contains identities The TLS common model presented in this section contains identities
and groupings common to both TLS clients and TLS servers. The hello- and groupings common to both TLS clients and TLS servers. The hello-
params-grouping can be used to configure the list of TLS algorithms params-grouping can be used to configure the list of TLS algorithms
permitted by the TLS client or TLS server. The lists of algorithms permitted by the TLS client or TLS server. The lists of algorithms
are ordered such that, if multiple algorithms are permitted by the are ordered such that, if multiple algorithms are permitted by the
client, the algorithm that appears first in its list that is also client, the algorithm that appears first in its list that is also
permitted by the server is used for the TLS transport layer permitted by the server is used for the TLS transport layer
connection. The ability to restrict the the algorithms allowed is connection. The ability to restrict the algorithms allowed is
provided in this grouping for TLS clients and TLS servers that are 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 capable of doing so and may serve to make TLS clients and TLS servers
compliant with local security policies. This model supports both compliant with local security policies. This model supports both
TLS1.2 [RFC5246] and TLS 1.3 [RFC8446]. TLS1.2 [RFC5246] and TLS 1.3 [RFC8446].
TLS 1.2 and TLS 1.3 have different ways defining their own supported TLS 1.2 and TLS 1.3 have different ways defining their own supported
cryptographic algorithms, see TLS and DTLS IANA registries page cryptographic algorithms, see TLS and DTLS IANA registries page
(https://www.iana.org/assignments/tls-parameters/tls- (https://www.iana.org/assignments/tls-parameters/tls-
parameters.xhtml): parameters.xhtml):
skipping to change at page 24, line 39 skipping to change at page 25, line 39
</tls-versions> </tls-versions>
<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 [RFC4346], [RFC5246],
[RFC5246], [RFC5288], [RFC5289], and [RFC8422]. [RFC5288], [RFC5289], and [RFC8422].
This YANG module has a informative references to [RFC2246], This YANG module has a informative references to [RFC2246],
[RFC4346], and [RFC5246]. [RFC4346], [RFC5246], and [RFC8446].
<CODE BEGINS> file "ietf-tls-common@2018-10-22.yang" <CODE BEGINS> file "ietf-tls-common@2019-03-09.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
"WG Web: <http://datatracker.ietf.org/wg/netconf/> "WG Web: <http://datatracker.ietf.org/wg/netconf/>
WG List: <mailto:netconf@ietf.org> WG List: <mailto:netconf@ietf.org>
Author: Kent Watsen <mailto:kent+ietf@watsen.net>
Author: Kent Watsen Author: Gary Wu <mailto:garywu@cisco.com>";
<mailto:kwatsen@juniper.net>
Author: Gary Wu
<mailto:garywu@cisco.com>";
description description
"This module defines a common features, identities, and groupings "This module defines a common features, identities, and
for Transport Layer Security (TLS). groupings for Transport Layer Security (TLS).
Copyright (c) 2018 IETF Trust and the persons identified as The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL',
'SHALL NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED',
'NOT RECOMMENDED', 'MAY', and 'OPTIONAL' in this document
are to be interpreted as described in BCP 14 [RFC2119]
[RFC8174] when, and only when, they appear in all
capitals, as shown here.
Copyright (c) 2019 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 "2018-10-22" { revision "2019-03-09" {
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
"TLS Protocol Version 1.0 is supported."; "TLS Protocol Version 1.0 is supported.";
reference reference
"RFC 2246: The TLS Protocol Version 1.0"; "RFC 2246: The TLS Protocol Version 1.0";
} }
feature tls-1_1 { feature tls-1_1 {
description description
skipping to change at page 26, line 18 skipping to change at page 27, line 18
} }
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-1_3 {
description
"TLS Protocol Version 1.2 is supported.";
reference
"RFC 8446: The Transport Layer Security (TLS) Protocol
Version 1.3";
}
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 8422: 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
skipping to change at page 27, line 11 skipping to change at page 28, line 19
} }
feature tls-sha2 { feature tls-sha2 {
description description
"The SHA2 family of cryptographic hash functions is supported "The SHA2 family of cryptographic hash functions is supported
for TLS."; for TLS.";
reference reference
"FIPS PUB 180-4: Secure Hash Standard (SHS)"; "FIPS PUB 180-4: Secure Hash Standard (SHS)";
} }
// identities // Identities
identity tls-version-base { identity tls-version-base {
description description
"Base identity used to identify TLS protocol versions."; "Base identity used to identify TLS protocol versions.";
} }
identity tls-1.0 { identity tls-1.0 {
base tls-version-base; base tls-version-base;
if-feature tls-1_0; if-feature tls-1_0;
description description
skipping to change at page 32, line 10 skipping to change at page 33, line 18
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 8422: 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
Version 1.2"; Version 1.2";
container tls-versions { container tls-versions {
description description
skipping to change at page 33, line 4 skipping to change at page 34, line 12
description description
"Acceptable cipher suites in order of descending "Acceptable cipher suites in order of descending
preference. The configured host key algorithms should preference. The configured host key algorithms should
be compatible with the algorithm used by the configured be compatible with the algorithm used by the configured
private key. Please see Section 5 of RFC XXXX for private key. Please see Section 5 of RFC XXXX for
valid combinations. valid combinations.
If this leaf-list is not configured (has zero elements) If this leaf-list is not configured (has zero elements)
the acceptable cipher suites are implementation- the acceptable cipher suites are implementation-
defined."; defined.";
reference reference
"RFC XXXX: YANG Groupings for TLS Clients and TLS Servers"; "RFC XXXX: YANG Groupings for TLS Clients and TLS Servers";
} }
} }
} // end hello-params-grouping }
} }
<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.
skipping to change at page 34, line 37 skipping to change at page 35, line 43
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 [RFC6020]. Following the format in [RFC6020], the the registry [RFC6020]. Following the format in [RFC6020], the following
following registrations are requested: 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
skipping to change at page 35, line 25 skipping to change at page 36, line 25
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. References 8. References
8.1. Normative References 8.1. Normative References
[I-D.ietf-netconf-crypto-types] [I-D.ietf-netconf-crypto-types]
Watsen, K., "Common YANG Data Types for Cryptography", Watsen, K. and H. Wang, "Common YANG Data Types for
draft-ietf-netconf-crypto-types-01 (work in progress), Cryptography", draft-ietf-netconf-crypto-types-02 (work in
September 2018. progress), October 2018.
[I-D.ietf-netconf-keystore] [I-D.ietf-netconf-keystore]
Watsen, K., "YANG Data Model for a Centralized Keystore Watsen, K., "YANG Data Model for a Centralized Keystore
Mechanism", draft-ietf-netconf-keystore-06 (work in Mechanism", draft-ietf-netconf-keystore-08 (work in
progress), September 2018. progress), March 2019.
[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-01 (work in progress), draft-ietf-netconf-trust-anchors-03 (work in progress),
September 2018. March 2019.
[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>.
[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>.
skipping to change at page 39, line 27 skipping to change at page 40, line 27
A.7. 06 to 07 A.7. 06 to 07
o factored the tls-[client|server]-groupings into more reusable o factored the tls-[client|server]-groupings into more reusable
groupings. groupings.
o added if-feature statements for the new "x509-certificates" o added if-feature statements for the new "x509-certificates"
feature defined in draft-ietf-netconf-trust-anchors. feature defined in draft-ietf-netconf-trust-anchors.
A.8. 07 to 08 A.8. 07 to 08
o Added a number of compatibility matricies to Section 5 (thanks o Added a number of compatibility matrices to Section 5 (thanks
Frank!) Frank!)
o Claified that any configured "cipher-suite" values need to be o Clarified that any configured "cipher-suite" values need to be
compatible with the configured private key. compatible with the configured private key.
A.9. 08 to 09
o Updated examples to reflect update to groupings defined in the
keystore draft.
o Add TLS keepalives features and groupings.
o Prefixed top-level TLS grouping nodes with 'tls-' and support
mashups.
o Updated copyright date, boilerplate template, affiliation, and
folding algorithm.
Acknowledgements 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, Balazs Kovacs, David Bjorklund, Benoit Claise, Mehmet Ersue, Balazs Kovacs, David
Lamparter, Alan Luchuk, Ladislav Lhotka, Radek Krejci, Tom Petch, Lamparter, Alan Luchuk, Ladislav Lhotka, Radek Krejci, Tom Petch,
Juergen Schoenwaelder, Phil Shafer, Sean Turner, and Bert Wijnen. Juergen Schoenwaelder, Phil Shafer, Sean Turner, and Bert Wijnen.
Authors' Addresses Authors' Addresses
Kent Watsen Kent Watsen
Juniper Networks Watsen Networks
EMail: kwatsen@juniper.net EMail: kent+ietf@watsen.net
Gary Wu Gary Wu
Cisco Systems Cisco Systems
EMail: garywu@cisco.com EMail: garywu@cisco.com
Liang Xia Liang Xia
Huawei Huawei
EMail: frank.xialiang@huawei.com EMail: frank.xialiang@huawei.com
 End of changes. 111 change blocks. 
276 lines changed or deleted 406 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/