QUIC-LB: Generating Routable QUIC Connection IDs
draft-ietf-quic-load-balancers-21
| Document | Type |
Expired Internet-Draft
(quic WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Martin Duke , Nick Banks , Christian Huitema | ||
| Last updated | 2026-02-28 (Latest revision 2025-08-27) | ||
| Replaces | draft-duke-quic-load-balancers | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | Proposed Standard | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | WG Document | |
| Associated WG milestone |
|
||
| Document shepherd | (None) | ||
| IESG | IESG state | Expired | |
| Consensus boilerplate | Yes | ||
| 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:
Abstract
QUIC address migration allows clients to change their IP address while maintaining connection state. To reduce the ability of an observer to link two IP addresses, clients and servers use new connection IDs when they communicate via different client addresses. This poses a problem for traditional "layer-4" load balancers that route packets via the IP address and port 4-tuple. This specification provides a standardized means of securely encoding routing information in the server's connection IDs so that a properly configured load balancer can route packets with migrated addresses correctly. As it proposes a structured connection ID format, it also provides a means of connection IDs self-encoding their length to aid some hardware offloads.
Authors
Martin Duke
Nick Banks
Christian Huitema
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)