QUIC-LB: Generating Routable QUIC Connection IDs
draft-duke-quic-load-balancers-06
| Document | Type |
Replaced Internet-Draft
(candidate for quic WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Martin Duke , Nick Banks | ||
| Last updated | 2019-12-11 (Latest revision 2019-11-04) | ||
| Replaced by | draft-ietf-quic-load-balancers | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | Call For Adoption By WG Issued | |
| Document shepherd | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-quic-load-balancers | |
| Consensus boilerplate | Unknown | ||
| 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 connection IDs allow continuation of connections across address/ port 4-tuple changes, and can store routing information for stateless or low-state load balancers. They also can prevent linkability of connections across deliberate address migration through the use of protected communications between client and server. This creates issues for load-balancing intermediaries. This specification standardizes methods for encoding routing information and proposes an optional protocol called QUIC-LB to exchange the parameters of that encoding. This framework also enables offload of other QUIC functions to trusted intermediaries, given the explicit cooperation of the QUIC server.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)