RFC 9368: Compatible Version Negotiation for QUIC
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC9368
- Published
- May 2023
- Authors
- D. Schinazi; E. Rescorla
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- wit
- Pages
- 15
- Also known as
- —
- Updates:
- RFC 8999
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9429JavaScript Session Establishment Protocol (JSEP)Current
April 2024
- RFC 9298Proxying UDP in HTTPUpdated
August 2022
- RFC 9297HTTP Datagrams and the Capsule ProtocolCurrent
August 2022
- RFC 9484Proxying IP in HTTPCurrent
October 2023
- RFC 9204QPACK: Field Compression for HTTP/3Current
June 2022
- RFC 9114HTTP/3Current
June 2022
- RFC 8829JavaScript Session Establishment Protocol (JSEP)Obsoleted
January 2021
- RFC 9959Careful Resume: Convergence of Congestion Control from Retained StateCurrent
May 2026
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?