QUIC (quic) Internet Drafts

      
 QUIC-LB: Generating Routable QUIC Connection IDs
 
 draft-ietf-quic-load-balancers-21.txt
 Date: 27/08/2025
 Authors: Martin Duke, Nick Banks, Christian Huitema
 Working Group: QUIC (quic)
 QUIC address migration allows clients to change their IP address while maintaining connection state. To reduce the ability of an observer to link two IP addresses, clients and servers use new connection IDs when they communicate via different client addresses. This poses a problem for traditional "layer-4" load balancers that route packets via the IP address and port 4-tuple. This specification provides a standardized means of securely encoding routing information in the server's connection IDs so that a properly configured load balancer can route packets with migrated addresses correctly. As it proposes a structured connection ID format, it also provides a means of connection IDs self-encoding their length to aid some hardware offloads.
 qlog: Structured Logging for Network Protocols
 
 draft-ietf-quic-qlog-main-schema-12.txt
 Date: 07/07/2025
 Authors: Robin Marx, Luca Niccolini, Marten Seemann, Lucas Pardue
 Working Group: QUIC (quic)
 qlog provides extensible structured logging for network protocols, allowing for easy sharing of data that benefits common debug and analysis methods and tooling. This document describes key concepts of qlog: formats, files, traces, events, and extension points. This definition includes the high-level log file schemas, and generic event schemas. Requirements and guidelines for creating protocol- specific event schemas are also presented. All schemas are defined independent of serialization format, allowing logs to be represented in various ways such as JSON, CSV, or protobuf. Note to Readers Note to RFC editor: Please remove this section before publication. Feedback and discussion are welcome at https://github.com/quicwg/qlog (https://github.com/quicwg/qlog). Readers are advised to refer to the "editor's draft" at that URL for an up-to-date version of this document.
 QUIC event definitions for qlog
 
 draft-ietf-quic-qlog-quic-events-11.txt
 Date: 07/07/2025
 Authors: Robin Marx, Luca Niccolini, Marten Seemann, Lucas Pardue
 Working Group: QUIC (quic)
 This document describes a qlog event schema containing concrete qlog event definitions and their metadata for the core QUIC protocol and selected extensions. Note to Readers Note to RFC editor: Please remove this section before publication. Feedback and discussion are welcome at https://github.com/quicwg/qlog (https://github.com/quicwg/qlog). Readers are advised to refer to the "editor's draft" at that URL for an up-to-date version of this document.
 HTTP/3 qlog event definitions
 
 draft-ietf-quic-qlog-h3-events-11.txt
 Date: 07/07/2025
 Authors: Robin Marx, Luca Niccolini, Marten Seemann, Lucas Pardue
 Working Group: QUIC (quic)
 This document defines a qlog event schema containing concrete events for the core HTTP/3 protocol and selected extensions. Note to Readers Note to RFC editor: Please remove this section before publication. Feedback and discussion are welcome at https://github.com/quicwg/qlog (https://github.com/quicwg/qlog). Readers are advised to refer to the "editor's draft" at that URL for an up-to-date version of this document.
 Multipath Extension for QUIC
 
 draft-ietf-quic-multipath-16.txt
 Date: 21/08/2025
 Authors: Yanmei Liu, Yunfei Ma, Quentin De Coninck, Olivier Bonaventure, Christian Huitema, Mirja Kuehlewind
 Working Group: QUIC (quic)
 This document specifies a multipath extension for the QUIC protocol to enable the simultaneous usage of multiple paths for a single connection. Discussion Venues This note is to be removed before publishing as an RFC. Discussion of this document takes place on the QUIC Working Group mailing list (quic@ietf.org), which is archived at https://mailarchive.ietf.org/arch/browse/quic/. Source for this draft and an issue tracker can be found at https://github.com/quicwg/multipath.
 QUIC Stream Resets with Partial Delivery
 
 draft-ietf-quic-reliable-stream-reset-07.txt
 Date: 14/06/2025
 Authors: Marten Seemann, Kazuho Oku
 Working Group: QUIC (quic)
 QUIC defines a RESET_STREAM frame to abort sending on a stream. When a sender resets a stream, it also stops retransmitting STREAM frames for this stream in the event of packet loss. On the receiving side, there is no guarantee that any data sent on that stream is delivered. This document defines a new QUIC frame, the RESET_STREAM_AT frame, that allows resetting a stream, while guaranteeing delivery of stream data up to a certain byte offset.
 Extended Key Update for QUIC
 
 draft-ietf-quic-extended-key-update-01.txt
 Date: 07/07/2025
 Authors: Yaroslav Rosomakho, Hannes Tschofenig, Tirumaleswar Reddy.K
 Working Group: QUIC (quic)
 This document specifies an Extended Key Update mechanism for the QUIC protocol, building on the foundation of the TLS Extended Key Update. The TLS Extended Key Update specification enhances the TLS protocol by introducing key updates with forward secrecy, eliminating the need to perform a full handshake. This feature is particularly beneficial for maintaining security in scenarios involving long-lived connections. This specification replaces the QUIC Key Update mechanism described in the "Using TLS to Secure QUIC" specification.

data-group-menu-data-url="/group/groupmenu.json">

QUIC (quic)

WG Name QUIC
Acronym quic
Area Web and Internet Transport (wit)
State Active
Charter charter-ietf-quic-04 Approved
Status update Show Changed 2020-03-09
Document dependencies
Additional resources Related Implementations
GitHub
GitHub notifications; read-only mailing list
Home Page
Slack channels for interop/implementers
Zulip Stream
Personnel Chairs Lucas Pardue, Matt Joras
Area Director Gorry Fairhurst
Mailing list Address quic@ietf.org
To subscribe https://www.ietf.org/mailman/listinfo/quic
Archive https://mailarchive.ietf.org/arch/browse/quic/
Chat Room address https://zulip.ietf.org/#narrow/stream/quic

Charter for Working Group

The QUIC WG originated the specifications describing version 1 of
QUIC, a UDP-based, stream-multiplexing, encrypted transport protocol.

The WG acts as the focal point for any QUIC-related work in the IETF.
It is chartered to pursue work in the areas detailed below:

  1. The first area of work is maintenance and evolution of the existing
    QUIC specifications:

  • Maintenance and evolution of the QUIC base specifications that
    describe its invariants, core transport mechanisms, security and
    privacy properties, loss detection and recovery, congestion control,
    version and extension negotiation, etc.

  • Maintenance and evolution of the existing QUIC extensions
    specified by the WG.

  • Specification of new versions of QUIC.

WG adoption of work items falling into this first area of work
needs to be strongly motivated by existing or ongoing production
deployments of QUIC at scale, and needs to carefully consider its
impact on the applications that have adopted QUIC as a transport.

  1. The second area of work is supporting the deployability of QUIC,
    which includes specifications, such as specification of a logging
    format and operation with load balancers; and informational documents
    such as applicability and manageability statements, and more.

  2. The third area of work is the specification of new extensions to
    QUIC.

  • The WG will primarily focus on extensions to the QUIC transport
    layer, i.e., extensions to QUIC that have broad applicability to
    multiple application protocols.

  • The WG may also publish Informational documents that
    publicly document deployed proprietary extensions or to enable
    wider experimentation with proposed new protocol features.

  1. The fourth area of work is the specification of how QUIC stream
    multiplexing and other application-oriented extensions (e.g. Datagram)
    can be adapted to work over a reliable and bidirectional byte stream
    substrate. When the substrate is insecure, TLS will be the default
    security provider; no effort will be made to enable unprotected
    communication without a security provider. Substrates must provide
    congestion-management capabilities applicable to their deployment
    environments.

Specifications published by the QUIC WG Specifications will be
published on the Standards Track providing they can demonstrate
sufficient maturity.

Specifications describing how new or existing application protocols
use the QUIC transport layer, called application protocol mappings
below, need not be specified in the QUIC WG, although they can. The
QUIC WG will collaborate with other groups that define such
application protocols that intend to use QUIC. New application
protocol mappings might require QUIC extensions and it may be
efficient to define these alongside the mapping specifications. Groups
that define application protocols using QUIC, or extensions to QUIC in
support of those protocols, are strongly requested to consult with the
QUIC WG and seek early and ongoing review of and collaboration on
proposals. This is intended to reduce the possibility of duplicate
work and/or conflicts with other extensions.

Defining new congestion control schemes is explicitly out of scope for
the WG. However, new QUIC extensions that support development and
experimentation with new congestion control schemes may fall under
the third area of work.

The QUIC WG originated HTTP/3, the mapping of HTTP to QUIC, and the
QPACK header compression scheme. These specifications are now
maintained in the HTTP WG.

Milestones

Order Milestone Associated documents
Last QUIC Retry Offload to IESG draft-ietf-quic-retry-offload
QUIC-LB: Generating Routable QUIC Connection IDs to IESG draft-ietf-quic-load-balancers
Multipath Extension to QUIC to IESG draft-ietf-quic-multipath
Qlog documents to IESG draft-ietf-quic-qlog-main-schema
draft-ietf-quic-qlog-quic-events
draft-ietf-quic-qlog-h3-events
Reliable Stream Resets to IESG draft-ietf-quic-reliable-stream-reset
Next QUIC Acknowledgement Frequency to IESG draft-ietf-quic-ack-frequency