Path Selection for Multiple Paths In QUIC
draft-dawkins-quic-multipath-selection-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Spencer Dawkins | ||
| Last updated | 2021-12-04 (Latest revision 2021-06-02) | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| 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:
Abstract
In QUIC working group discussions about proposals to use multiple paths, an obvious question came up - given multiple paths, how does QUIC select paths to send packets over? The answer to that question may inform decisions in the QUIC working group about the scope of any multipath extensions considered for experimentation and adoption. This document is intended to summarize aspects of path selection from those contributions and conversations. It is recognized that path selection is not the only important open question about QUIC Multipath, but other open questions are out of scope for this document.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)