QUIC (quic) Internet Drafts


      
 QUIC-LB: Generating Routable QUIC Connection IDs
 
 draft-ietf-quic-load-balancers-19.txt
 Date: 05/02/2024
 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.
 Main logging schema for qlog
 
 draft-ietf-quic-qlog-main-schema-08.txt
 Date: 04/03/2024
 Authors: Robin Marx, Luca Niccolini, Marten Seemann, Lucas Pardue
 Working Group: QUIC (quic)
This document defines qlog, an extensible high-level schema for a standardized logging format. It allows easy sharing of data, benefitting common debug and analysis methods and tooling. The high- level schema is independent of protocol; separate documents extend qlog for protocol-specific data. The schema is also independent of serialization format, allowing logs to be represented in many 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. Concrete examples of integrations of this schema in various programming languages can be found at https://github.com/quiclog/ qlog/ (https://github.com/quiclog/qlog/).
 QUIC event definitions for qlog
 
 draft-ietf-quic-qlog-quic-events-07.txt
 Date: 04/03/2024
 Authors: Robin Marx, Luca Niccolini, Marten Seemann, Lucas Pardue
 Working Group: QUIC (quic)
This document describes concrete qlog event definitions and their metadata for QUIC events. These events can then be embedded in the higher level schema defined in [QLOG-MAIN]. 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. Concrete examples of integrations of this schema in various programming languages can be found at https://github.com/quiclog/ qlog/ (https://github.com/quiclog/qlog/).
 HTTP/3 qlog event definitions
 
 draft-ietf-quic-qlog-h3-events-07.txt
 Date: 04/03/2024
 Authors: Robin Marx, Luca Niccolini, Marten Seemann, Lucas Pardue
 Working Group: QUIC (quic)
This document describes concrete qlog event definitions and their metadata for HTTP/3-related events. These events can then be embedded in the higher level schema defined in [QLOG-MAIN]. 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. Concrete examples of integrations of this schema in various programming languages can be found at https://github.com/quiclog/ qlog/ (https://github.com/quiclog/qlog/).
 QUIC Acknowledgment Frequency
 
 draft-ietf-quic-ack-frequency-08.txt
 Date: 04/03/2024
 Authors: Jana Iyengar, Ian Swett, Mirja Kuehlewind
 Working Group: QUIC (quic)
This document specifies an extension to QUIC that permits an endpoint to request that its peer changes its behavior when sending or delaying acknowledgments. Note to Readers Discussion of this draft takes place on the QUIC working group mailing list (quic@ietf.org), which is archived at https://mailarchive.ietf.org/arch/search/?email_list=quic. Source code and issues list for this draft can be found at https://github.com/quicwg/ack-frequency. Working Group information can be found at https://github.com/quicwg.
 Multipath Extension for QUIC
 
 draft-ietf-quic-multipath-07.txt
 Date: 10/04/2024
 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/mirjak/draft-lmbdhk-quic-multipath.
 QUIC Stream Resets with Partial Delivery
 
 draft-ietf-quic-reliable-stream-reset-06.txt
 Date: 28/02/2024
 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.


data-group-menu-data-url="/group/groupmenu.json"> Skip to main content

QUIC (quic)

WG Name QUIC
Acronym quic
Area Web and Internet Transport (wit)
State Active
Charter charter-ietf-quic-03 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 Zaheduzzaman Sarker
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. This includes the specification of new versions of QUIC.
    
     * Maintenance and evolution of the existing QUIC extensions specified by the WG.
    

    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 and higher-layer protocols (simply called "application protocols" in the rest of this charter) that have adopted QUIC as a transport.

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

  3. 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 specifications to publicly document deployed proprietary extensions or to enable wider experimentation with proposed new protocol features.

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.

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.

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 work area.

Milestones

Order Milestone Associated documents
Last 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
QUIC Acknowledgement Frequency to IESG draft-ietf-quic-ack-frequency
Next QUIC-LB: Generating Routable QUIC Connection IDs to IESG draft-ietf-quic-load-balancers

Done milestones

Order Milestone Associated documents
Done QUIC Version 2 to IESG draft-ietf-quic-v2
Done Version Negotiation Extension to IESG draft-ietf-quic-version-negotiation
Done Greasing the QUIC bit to IESG draft-ietf-quic-bit-grease
Done Datagram Extension to IESG draft-ietf-quic-datagram
Done QUIC Applicability and Manageability Statement to IESG

2 new milestones currently in Area Director review.