| Internet-Draft | Groupings for QUIC clients and servers | July 2025 |
| Andersson | Expires 6 January 2026 | [Page] |
This document defines five 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 as well as initial modules for the IANA registries "QUIC Versions" and "QUIC Transport Parameters".¶
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 6 January 2026.¶
Copyright (c) 2025 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.¶
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.¶
The following terms are defined in [RFC7950] and are not redefined here: client, data model, data tree, feature, extension, module, leaf, leaf-list, and server.¶
This section defines a YANG 1.1 module called "ietf-quic-common".¶
This section presents an overview of of the "ietf-quic-common" module in terms of features and groupings.¶
The "ietf-quic-common" module defines the following "grouping" statement:¶
This grouping is presented in the following subsection.¶
The following tree diagram [RFC8340] illustrates the "quic-common" grouping:¶
grouping transport-parameters:
+-- version? uint32
+-- initial-rtt? uint32
+-- congestion-control-algorithm? string
+-- max-idle-timeout? uint32
¶
Comments:¶
<CODE BEGINS> file "ietf-quic-common@2025-07-06.yang"¶
module ietf-quic-common {
yang-version 1.1;
namespace
"urn:ietf:params:xml:ns:yang:ietf-quic-common";
prefix quiccmn;
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 a reusable grouping that is common for
QUIC clients and QUIC servers. This grouping statement is
used by both 'ietf-quic-client' and 'ietf-quic-server'
modules.
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 2025-07-06 {
description
"Initial version";
reference
"RFC AAAA: YANG Groupings for QUIC Clients and QUIC Servers";
}
// Groupings
grouping transport-parameters {
description
"A reusable grouping for QUIC Transport Parameters.";
reference
"RFC 9000: QUIC: A UDP-Based Multiplexed and Secure Transport
RFC 9002: QUIC Loss Detection and Congestion Control
RFC 9312: Manageability of the QUIC Transport Protocol";
leaf version { type uint32; }
leaf initial-rtt { type uint32; }
leaf congestion-control-algorithm { type string; }
leaf max-idle-timeout { type uint32; }
leaf initial-max-streams-bidi { type uint32; }
leaf initial-max-streams-uni { type uint32; }
leaf keep-alive-interval { type uint32; }
}
}
¶
<CODE ENDS>¶
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 [RFC9645] 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 quic-client:
+---u tlsc:tls-client-grouping
| {tlscmn:tls13 and not tlscmn:tls12}?
+---u udpc:udp-client
+---u quiccmn:transport-parameters
¶
Comments:¶
This YANG module has normative references to [RFC9645] and [I-D.ietf-netconf-udp-client-server].¶
<CODE BEGINS> file "ietf-quic-client@2025-07-06.yang"¶
module ietf-quic-client {
yang-version 1.1;
namespace
"urn:ietf:params:xml:ns:yang:ietf-quic-client";
prefix quicc;
import ietf-quic-common {
prefix quiccmn;
reference
"RFC AAAA: YANG Groupings for QUIC Clients and QUIC Servers";
}
import ietf-tls-client {
prefix tlsc;
reference
"RFC 9645: YANG Groupings for TLS Clients and TLS Servers";
}
import ietf-tls-common {
prefix tlscmn;
reference
"RFC 9645: 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 2025-07-06 {
description
"Initial version";
reference
"RFC AAAA: YANG Groupings for QUIC Clients and QUIC Servers";
}
// Groupings
grouping quic-client {
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;
uses quiccmn:transport-parameters;
}
}
¶
<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 [RFC9645] 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 quic-server:
+---u tlss:tls-server-grouping
| {tlscmn:tls13 and not tlscmn:tls12}?
+---u udps:udp-server
+---u quiccmn:transport-parameters
¶
Comments:¶
This YANG module has normative references to [RFC9645] and [I-D.ietf-netconf-udp-client-server].¶
<CODE BEGINS> file "ietf-quic-server@2025-07-06.yang"¶
module ietf-quic-server {
yang-version 1.1;
namespace
"urn:ietf:params:xml:ns:yang:ietf-quic-server";
prefix quics;
import ietf-quic-common {
prefix quiccmn;
reference
"RFC AAAA: YANG Groupings for QUIC Clients and QUIC Servers";
}
import ietf-tls-server {
prefix tlss;
reference
"RFC 9645: YANG Groupings for TLS Clients and TLS Servers";
}
import ietf-tls-common {
prefix tlscmn;
reference
"RFC 9645: 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 2025-07-06 {
description
"Initial version";
reference
"RFC AAAA: YANG Groupings for QUIC Clients and QUIC Servers";
}
// Features
// FIXME feature quic-call-home
// Groupings
grouping quic-server {
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;
uses quiccmn:transport-parameters;
}
}
¶
<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 [RFC9645] 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 five 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-common Registrant Contact: The IESG. XML: N/A, the requested URI is an XML namespace. 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. URI: urn:ietf:params:xml:ns:yang:iana-quic-versions Registrant Contact: IANA XML: N/A, the requested URI is an XML namespace. URI: urn:ietf:params:xml:ns:yang:iana-quic-transport Registrant Contact: IANA XML: N/A, the requested URI is an XML namespace.¶
This document registers five 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-common namespace: urn:ietf:params:xml:ns:yang:ietf-quic-common prefix: quiccmn RFC: AAAA 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 name: iana-quic-versions namespace: urn:ietf:params:xml:ns:yang:iana-quic-versions prefix: iana-quic-versions RFC: AAAA name: iana-quic-transport namespace: urn:ietf:params:xml:ns:yang:iana-quic-transport prefix: iana-quic-transport RFC: AAAA¶
The initial YANG modules are created with the iana-yang tool from <https://github.com/llhotka/iana-yang>.¶
IANA is requested to maintain a YANG module called "iana-quic-versions" that shadows the "QUIC Versions" registry [IANA-QUIC-VERSIONS].¶
Ths registry defines a YANG enumeration for each QUIC versions.¶
An initial version of this module can be found in Appendix A.1.¶
IANA is requested to maintain a YANG module called "iana-quic-transport" that shadows the "QUIC Transport Parameters" registry [IANA-QUIC-TRANSPORT].¶
Ths registry defines a YANG enumeration for each QUIC transport parameter.¶
An initial version of this module can be found in Appendix A.2.¶
The initial YANG modules are created with the iana-yang tool from <https://github.com/llhotka/iana-yang>.¶
This YANG module has normative references to [RFC9000] and [RFC9369].¶
<CODE BEGINS> file "iana-quic-versions@2024-03-21.yang"¶
module iana-quic-versions {
yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:iana-quic-versions";
prefix iana-quic-versions;
organization
"Internet Assigned Numbers Authority (IANA)";
contact
"Internet Assigned Numbers Authority
ICANN
12025 Waterfront Drive, Suite 300
Los Angeles, CA 90094
Tel: +1 424 254 5300
<mailto:iana@iana.org>";
description
"This YANG module translates IANA registry 'QUIC Versions' to
YANG derived types.
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 was generated from the
corresponding IANA registry using an XSLT stylesheet from the
'iana-yang' project (https://github.com/llhotka/iana-yang).";
reference
"QUIC (https://www.iana.org/assignments/quic/)";
revision 2024-03-21 {
description
"Current revision as of the revision date specified in the XML
representation of the registry page.";
reference
"https://www.iana.org/assignments/quic/quic.xml";
}
/* Typedefs */
typedef quic-version {
type enumeration {
enum 0x00000000 {
description
"(permanent) Reserved for Version Negotiation";
reference
"RFC 9000";
}
enum 0x00000001 {
description
"(permanent)";
reference
"RFC 9000";
}
enum 0x51303433 {
description
"(provisional) Google QUIC Q043";
}
enum 0x51303436 {
description
"(provisional) Google QUIC Q046";
}
enum 0x51303530 {
description
"(provisional) Google QUIC Q050";
}
enum 0x6b3343cf {
description
"(permanent)";
reference
"RFC 9369";
}
enum 0x709a50c4 {
description
"(provisional) QUIC v2 draft codepoint";
reference
"RFC 9369";
}
}
description
"This enumeration type defines QUIC protocol versions.";
reference
"RFC 9000: QUIC: A UDP-Based Multiplexed and Secure
Transport";
}
typedef version {
type quic-version;
description
"This type allows reference to a QUIC version using the
assigned value.";
}
}
¶
<CODE ENDS>¶
This YANG module has normative references to [RFC9000], [RFC9221], [RFC9368], and [RFC9287].¶
<CODE BEGINS> file "iana-quic-transport@2024-03-21.yang"¶
module iana-quic-transport {
yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:iana-quic-transport";
prefix iana-quic-transport;
organization
"Internet Assigned Numbers Authority (IANA)";
contact
"Internet Assigned Numbers Authority
ICANN
12025 Waterfront Drive, Suite 300
Los Angeles, CA 90094
Tel: +1 424 254 5300
<mailto:iana@iana.org>";
description
"This YANG module translates IANA registry 'QUIC Transport
Parameters' to YANG derived types.
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 was generated from the
corresponding IANA registry using an XSLT stylesheet from the
'iana-yang' project (https://github.com/llhotka/iana-yang).";
reference
"QUIC (https://www.iana.org/assignments/quic/)";
revision 2024-03-21 {
description
"Current revision as of the revision date specified in the XML
representation of the registry page.";
reference
"https://www.iana.org/assignments/quic/quic.xml";
}
/* Typedefs */
typedef quic-transport-parameter {
type enumeration {
enum original_destination_connection_id {
value 0x00;
description
"(permanent)";
reference
"RFC 9000";
}
enum max_idle_timeout {
value 0x01;
description
"(permanent)";
reference
"RFC 9000";
}
enum stateless_reset_token {
value 0x02;
description
"(permanent)";
reference
"RFC 9000";
}
enum max_udp_payload_size {
value 0x03;
description
"(permanent)";
reference
"RFC 9000";
}
enum initial_max_data {
value 0x04;
description
"(permanent)";
reference
"RFC 9000";
}
enum initial_max_stream_data_bidi_local {
value 0x05;
description
"(permanent)";
reference
"RFC 9000";
}
enum initial_max_stream_data_bidi_remote {
value 0x06;
description
"(permanent)";
reference
"RFC 9000";
}
enum initial_max_stream_data_uni {
value 0x07;
description
"(permanent)";
reference
"RFC 9000";
}
enum initial_max_streams_bidi {
value 0x08;
description
"(permanent)";
reference
"RFC 9000";
}
enum initial_max_streams_uni {
value 0x09;
description
"(permanent)";
reference
"RFC 9000";
}
enum ack_delay_exponent {
value 0x0a;
description
"(permanent)";
reference
"RFC 9000";
}
enum max_ack_delay {
value 0x0b;
description
"(permanent)";
reference
"RFC 9000";
}
enum disable_active_migration {
value 0x0c;
description
"(permanent)";
reference
"RFC 9000";
}
enum preferred_address {
value 0x0d;
description
"(permanent)";
reference
"RFC 9000";
}
enum active_connection_id_limit {
value 0x0e;
description
"(permanent)";
reference
"RFC 9000";
}
enum initial_source_connection_id {
value 0x0f;
description
"(permanent)";
reference
"RFC 9000";
}
enum retry_source_connection_id {
value 0x10;
description
"(permanent)";
reference
"RFC 9000";
}
enum version_information {
value 0x11;
description
"(permanent)";
reference
"RFC 9368";
}
enum max_datagram_frame_size {
value 0x20;
description
"(permanent)";
reference
"RFC 9221";
}
enum discard {
value 0x173e;
description
"(provisional) Receiver silently discards.";
reference
"https://github.com/quicwg/base-drafts/wiki
/Quantum-Readiness-test";
}
enum google_handshake_message {
value 0x26ab;
description
"(provisional) Used to carry Google internal handshake
message";
}
enum grease_quic_bit {
value 0x2ab2;
description
"(permanent)";
reference
"RFC 9287";
}
enum initial_rtt {
value 0x3127;
description
"(provisional) Initial RTT in microseconds";
}
enum google_connection_options {
value 0x3128;
description
"(provisional) Google connection options for
experimentation";
}
enum user_agent {
value 0x3129;
status deprecated;
description
"(provisional) User agent string (deprecated)";
}
enum google_version {
value 0x4752;
description
"(provisional) Google QUIC version downgrade prevention";
}
enum version_information_draft {
value 0xff73db;
status deprecated;
description
"(provisional) Deprecated; use version_information
instead";
reference
"draft-ietf-quic-version-negotiation-13";
}
enum min_ack_delay {
value 0xff04de1b;
description
"(provisional)";
reference
"draft-ietf-quic-ack-frequency-07";
}
enum enable_multipath {
value 0x0f739bbc1b666d05;
description
"(provisional)";
reference
"draft-ietf-quic-multipath-05";
}
enum enable_multipath-06 {
value 0x0f739bbc1b666d06;
description
"(provisional)";
reference
"draft-ietf-quic-multipath-06";
}
enum bdp_frame {
value 0x4143414213370002;
description
"(provisional)";
reference
"draft-misell-quic-bdp-token-02";
}
}
description
"This enumeration type defines QUIC transport parameters.";
reference
"RFC 9000: QUIC: A UDP-Based Multiplexed and Secure
Transport";
}
typedef transport-parameter {
type quic-transport-parameter;
description
"This type allows reference to a QUIC transport parameters
using the assigned value.";
}
}
¶
<CODE ENDS>¶