Quic Workgroup RFCs
Browse Quic Workgroup RFCs by Number
- RFC8999 - Version-Independent Properties of QUIC
- This document defines the properties of the QUIC transport protocol that are common to all versions of the protocol.
- RFC9000 - QUIC: A UDP-Based Multiplexed and Secure Transport
- This document defines the core of the QUIC transport protocol. QUIC provides applications with flow-controlled streams for structured communication, low-latency connection establishment, and network path migration. QUIC includes security measures that ensure confidentiality, integrity, and availability in a range of deployment circumstances. Accompanying documents describe the integration of TLS for key negotiation, loss detection, and an exemplary congestion control algorithm.
- RFC9001 - Using TLS to Secure QUIC
- This document describes how Transport Layer Security (TLS) is used to secure QUIC.
- RFC9002 - QUIC Loss Detection and Congestion Control
- This document describes loss detection and congestion control mechanisms for QUIC.
- RFC9114 - HTTP/3
- The QUIC transport protocol has several features that are desirable in a transport for HTTP, such as stream multiplexing, per-stream flow control, and low-latency connection establishment. This document describes a mapping of HTTP semantics over QUIC. This document also identifies HTTP/2 features that are subsumed by QUIC and describes how HTTP/2 extensions can be ported to HTTP/3.
- RFC9204 - QPACK: Field Compression for HTTP/3
- This specification defines QPACK: a compression format for efficiently representing HTTP fields that is to be used in HTTP/3. This is a variation of HPACK compression that seeks to reduce head-of-line blocking.
- RFC9221 - An Unreliable Datagram Extension to QUIC
- This document defines an extension to the QUIC transport protocol to add support for sending and receiving unreliable datagrams over a QUIC connection.
- RFC9287 - Greasing the QUIC Bit
- This document describes a method for negotiating the ability to send an arbitrary value for the second-most significant bit in QUIC packets.
- RFC9308 - Applicability of the QUIC Transport Protocol
- This document discusses the applicability of the QUIC transport protocol, focusing on caveats impacting application protocol development and deployment over QUIC. Its intended audience is designers of application protocol mappings to QUIC and implementors of these application protocols.
- RFC9312 - Manageability of the QUIC Transport Protocol
- This document discusses manageability of the QUIC transport protocol and focuses on the implications of QUIC's design and wire image on network operations involving QUIC traffic. It is intended as a "user's manual" for the wire image to provide guidance for network operators and equipment vendors who rely on the use of transport-aware network functions.
- RFC9368 - Compatible Version Negotiation for QUIC
- QUIC does not provide a complete version negotiation mechanism but instead only provides a way for the server to indicate that the version the client chose is unacceptable. This document describes a version negotiation mechanism that allows a client and server to select a mutually supported version. Optionally, if the client's chosen version and the negotiated version share a compatible first flight format, the negotiation can take place without incurring an extra round trip. This document updates RFC 8999.
- RFC9369 - QUIC Version 2
- This document specifies QUIC version 2, which is identical to QUIC version 1 except for some trivial details. Its purpose is to combat various ossification vectors and exercise the version negotiation framework. It also serves as a template for the minimum changes in any future version of QUIC.
- Note that "version 2" is an informal name for this proposal that indicates it is the second version of QUIC to be published as a Standards Track document. The protocol specified here uses a version number other than 2 in the wire image, in order to minimize ossification risks.
