| Internet-Draft | Groupings for QUIC clients and servers | June 2024 |
| Andersson | Expires 1 January 2025 | [Page] |
This document defines two YANG 1.1 modules to support the configuration of QUIC clients and QUIC servers. The modules include basic parameters for configuring QUIC based clients and servers.¶
This draft contains placeholder values that need to be replaced with finalized values at the time of publication. This note summarizes all of the substitutions that are needed. No other RFC Editor instructions are specified elsewhere in this document.¶
Artwork in this document contains shorthand references to drafts in progress. Please apply the following replacements:¶
This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.¶
Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at https://datatracker.ietf.org/drafts/current/.¶
Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."¶
This Internet-Draft will expire on 1 January 2025.¶
Copyright (c) 2024 IETF Trust and the persons identified as the document authors. All rights reserved.¶
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Revised BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Revised BSD License.¶
This documents defines two YANG 1.1 [RFC7950] modules to support the configuration of QUIC clients and QUIC servers (QUIC is defined in [RFC9000]), either as standalone or in conjunction with configuration of other protocol layers.¶
This section defines a YANG 1.1 module called "ietf-quic-client".¶
This section presents an overview of of the "ietf-quic-client" module in terms of features and groupings.¶
The module itself does not define any features. However, in order to require TLS 1.3 the following "if-feature" is defined "tlscmn:tls13 not tlscmn:tls12". For QUIC TLS requirements see [RFC9001].¶
For further details about available features see the "ietf-tls-client" and "ietf-udp-client" modules. defined in [I-D.ietf-netconf-tls-client-server] and [I-D.ietf-netconf-udp-client-server] respectively.¶
The "ietf-quic-client" module defines the following "grouping" statement:¶
This grouping is presented in the following subsection.¶
The following tree diagram [RFC8340] illustrates the "quic-client-grouping" grouping:¶
module: ietf-quic-client
grouping quic-client-grouping:
+---u tlsc:tls-client-grouping
| {tlscmn:tls13 and not tlscmn:tls12}?
+---u udpc:udp-client-grouping
¶
Comments:¶
This YANG module has normative references to [I-D.ietf-netconf-tls-client-server] and [I-D.ietf-netconf-udp-client-server].¶
<CODE BEGINS> file "ietf-quic-client@2024-06-30.yang"¶
module ietf-quic-client {
yang-version 1.1;
namespace
"urn:ietf:params:xml:ns:yang:ietf-quic-client";
prefix quicc;
import ietf-tls-client {
prefix tlsc;
reference
"RFC BBBB: YANG Groupings for TLS Clients and TLS Servers";
}
import ietf-tls-common {
prefix tlscmn;
reference
"RFC BBBB: YANG Groupings for TLS Clients and TLS Servers";
}
import ietf-udp-client {
prefix udpc;
reference
"RFC CCCC: YANG Groupings for UDP Clients and UDP Servers";
}
organization
"IETF NETCONF (Network Configuration) Working Group";
contact
"WG List: NETCONF WG list <mailto:netconf@ietf.org>
WG Web: https://datatracker.ietf.org/wg/netconf
Author: Per Andersson <mailto:per.ietf@ionio.se>";
description
"This module defines reusable groupings for QUIC clients that
can be used as a basis for specific QUIC client instances.
Copyright (c) 2024 IETF Trust and the persons identified
as authors of the code. All rights reserved.
Redistribution and use in source and binary forms, with
or without modification, is permitted pursuant to, and
subject to the license terms contained in, the Revised
BSD License set forth in Section 4.c of the IETF Trust's
Legal Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC AAAA
(https://www.rfc-editor.org/info/rfcAAAA); see the RFC
itself for full legal notices.
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 (RFC 2119)
(RFC 8174) when, and only when, they appear in all
capitals, as shown here.";
revision 2024-06-30 {
description
"Initial version";
reference
"RFC AAAA: YANG Groupings for QUIC Clients and QUIC Servers";
}
// Groupings
grouping quic-client-grouping {
description
"Grouping to configure a QUIC client.";
reference
"RFC 9000: QUIC: A UDP-Based Multiplexed and Secure Transport";
uses tlsc:tls-client-grouping {
if-feature "tlscmn:tls13 and not tlscmn:tls12";
description
"QUIC requires that TLS 1.3 (or later) is used.";
reference
"RFC 9001: Using TLS to Secure QUIC";
}
uses udpc:udp-client-grouping;
}
}
¶
<CODE ENDS>¶
This section defines a YANG 1.1 module called "ietf-quic-server".¶
This section presents an overview of of the "ietf-quic-server" module in terms of features and groupings.¶
The module itself does not define any features. However, in order to require TLS 1.3 the following "if-feature" is defined "tlscmn:tls13 not tlscmn:tls12". For QUIC TLS requirements see [RFC9001].¶
For further details about available features see the "ietf-tls-server" and "ietf-udp-server" modules, defined in [I-D.ietf-netconf-tls-client-server] and [I-D.ietf-netconf-udp-client-server] respectively.¶
The "ietf-quic-server" module defines the following "grouping" statement:¶
This grouping is presented in the following subsection.¶
The following tree diagram [RFC8340] illustrates the "quic-server-grouping" grouping:¶
module: ietf-quic-server
grouping quic-server-grouping:
+---u tlss:tls-server-grouping
| {tlscmn:tls13 and not tlscmn:tls12}?
+---u udps:udp-server-grouping
¶
Comments:¶
This YANG module has normative references to [I-D.ietf-netconf-tls-client-server] and [I-D.ietf-netconf-udp-client-server].¶
<CODE BEGINS> file "ietf-quic-server@2024-06-30.yang"¶
module ietf-quic-server {
yang-version 1.1;
namespace
"urn:ietf:params:xml:ns:yang:ietf-quic-server";
prefix quicc;
import ietf-tls-server {
prefix tlss;
reference
"RFC BBBB: YANG Groupings for TLS Clients and TLS Servers";
}
import ietf-tls-common {
prefix tlscmn;
reference
"RFC BBBB: YANG Groupings for TLS Clients and TLS Servers";
}
import ietf-udp-server {
prefix udps;
reference
"RFC CCCC: YANG Groupings for UDP Clients and UDP Servers";
}
organization
"IETF NETCONF (Network Configuration) Working Group";
contact
"WG List: NETCONF WG list <mailto:netconf@ietf.org>
WG Web: https://datatracker.ietf.org/wg/netconf
Author: Per Andersson <mailto:per.ietf@ionio.se>";
description
"This module defines reusable groupings for QUIC servers that
can be used as a basis for specific QUIC server instances.
Copyright (c) 2024 IETF Trust and the persons identified
as authors of the code. All rights reserved.
Redistribution and use in source and binary forms, with
or without modification, is permitted pursuant to, and
subject to the license terms contained in, the Revised
BSD License set forth in Section 4.c of the IETF Trust's
Legal Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC AAAA
(https://www.rfc-editor.org/info/rfcAAAA); see the RFC
itself for full legal notices.
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 (RFC 2119)
(RFC 8174) when, and only when, they appear in all
capitals, as shown here.";
revision 2024-06-30 {
description
"Initial version";
reference
"RFC AAAA: YANG Groupings for QUIC Clients and QUIC Servers";
}
// Groupings
grouping quic-server-grouping {
description
"Grouping to configure a QUIC server.";
reference
"RFC 9000: QUIC: A UDP-Based Multiplexed and Secure Transport";
uses tlss:tls-server-grouping {
if-feature "tlscmn:tls13 and not tlscmn:tls12";
description
"QUIC requires that TLS 1.3 (or later) is used.";
reference
"RFC 9001: Using TLS to Secure QUIC";
}
uses udps:udp-server-grouping;
}
}
¶
<CODE ENDS>¶
This section follows the template defined in Section 3.7.1 of [RFC8407].¶
The YANG modules specified in this document defines a schema for data that is designed to be accessed via network management protocols such as NETCONF [RFC6241] or RESTCONF [RFC8040]. The lowest NETCONF layer is the secure transport layer, and the mandatory-to-implement secure transport is Secure Shell (SSH) [RFC6242]. The lowest RESTCONF layer is HTTPS, and the mandatory-to-implement secure transport is TLS [RFC8446].¶
The Network Configuration Access Control Model (NACM) [RFC8341] provides the means to restrict access for particular NETCONF or RESTCONF users to a preconfigured subset of all available NETCONF or RESTCONF protocol operations and content.¶
The modules presented in this draft does not contain any protocol accessible nodes, and thus the security considerations for such are not provided here.¶
Furthermore, the modules defines groupings, these considerations are primarily for the designers of other modules that use these groupings.¶
Security considerations for the groupings used in the modules are discussed in [I-D.ietf-netconf-tls-client-server] and [I-D.ietf-netconf-udp-client-server], refer to these documents for further details.¶
Since the modules does not define any RPCs or actions or notifications, and thus the security considerations for such are not provided here.¶
This document registers two URIs in the "ns" subregistry of the IETF XML Registry [RFC3688] maintained at https://www.iana.org/assignments/xml-registry/xml-registry.xhtml#ns. Following the format in [RFC3688], the following registration is requested:¶
URI: urn:ietf:params:xml:ns:yang:ietf-quic-client Registrant Contact: The IESG. XML: N/A, the requested URI is an XML namespace. URI: urn:ietf:params:xml:ns:yang:ietf-quic-server Registrant Contact: The IESG. XML: N/A, the requested URI is an XML namespace.¶
This document registers two YANG modules in the YANG Module Names registry [RFC6020] maintained at https://www.iana.org/assignments/yang-parameters/yang-parameters.xhtml. Following the format defined in [RFC6020], the below registration is requested:¶
name: ietf-quic-client namespace: urn:ietf:params:xml:ns:yang:ietf-quic-client prefix: quicc RFC: AAAA name: ietf-quic-server namespace: urn:ietf:params:xml:ns:yang:ietf-quic-server prefix: quics RFC: AAAA¶