RFC 9369: QUIC Version 2
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC9369
- Published
- May 2023
- Authors
- M. Duke
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- wit
- Pages
- 14
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9368Compatible Version Negotiation for QUICCurrent
May 2023
- RFC 9388Content Delivery Network Interconnection (CDNI) Footprint Types: Country Subdivision Code and Footprint UnionCurrent
July 2023
- RFC 9335Completely Encrypting RTP Header Extensions and Contributing SourcesCurrent
January 2023
- RFC 9332Dual-Queue Coupled Active Queue Management (AQM) for Low Latency, Low Loss, and Scalable Throughput (L4S)Current
January 2023
- RFC 9406HyStart++: Modified Slow Start for TCPCurrent
May 2023
- RFC 9331The Explicit Congestion Notification (ECN) Protocol for Low Latency, Low Loss, and Scalable Throughput (L4S)Current
January 2023
- RFC 9330Low Latency, Low Loss, and Scalable Throughput (L4S) Internet Service: ArchitectureCurrent
January 2023
- RFC 9328RTP Payload Format for Versatile Video Coding (VVC)Current
December 2022
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?