Peer-to-Peer Connections for the QUIC Transport Protocol
draft-perkins-quic-p2p-mux-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Colin Perkins | ||
| Last updated | 2019-09-12 (Latest revision 2019-03-11) | ||
| 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
The QUIC transport protocol is intended to be a general purpose transport, but is currently defined for client-server operation only. To be applicable to all use cases, it needs to develop support for peer-to-peer connection establishment. This memo describes how this can be done, in outline form. Future work is needed to determine if such peer-to-peer use of QUIC is desirable and, if so, to define a complete and workable standard for peer-to-peer QUIC connection establishment.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)