Skip to main content

QUIC Version Aliasing

Document Type Expired Internet-Draft (individual)
Expired & archived
Author Martin Duke
Last updated 2023-11-06 (Latest revision 2023-04-25)
Replaces draft-ietf-quic-version-aliasing
RFC stream (None)
Intended RFC status (None)
Additional resources GitHub Repository
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date (None)
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:


The QUIC transport protocol preserves its future extensibility partly by specifying its version number. There will be a relatively small number of published version numbers for the foreseeable future. This document provides a method for clients and servers to negotiate the use of other version numbers in subsequent connections and encrypts Initial Packets using secret keys instead of standard ones. If a sizeable subset of QUIC connections use this mechanism, this should prevent middlebox ossification around the current set of published version numbers and the contents of QUIC Initial packets, as well as improving the protocol's privacy properties.


Martin Duke

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)