QUIC Version Aliasing
draft-ietf-quic-version-aliasing-00
| Document | Type | Replaced Internet-Draft (quic WG) | |
|---|---|---|---|
| Last updated | 2020-04-06 | ||
| Replaced by | draft-duke-quic-version-aliasing | ||
| Stream | IETF | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized (tools)
htmlized
bibtex
|
||
| Stream | WG state | WG Document | |
| Document shepherd | No shepherd assigned | ||
| IESG | IESG state | Replaced by draft-duke-quic-version-aliasing | |
| Consensus Boilerplate | Unknown | ||
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-ietf-quic-version-aliasing-00.txt
Abstract
The QUIC transport protocol [QUIC-TRANSPORT] 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. 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.
Authors
Martin Duke (martin.h.duke@gmail.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)