QUIC Multiplexing
draft-aboba-avtcore-quic-multiplexing-01
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Expired".
Expired & archived
|
|
|---|---|---|---|
| Authors | Dr. Bernard D. Aboba , Peter Thatcher , Colin Perkins | ||
| Last updated | 2018-05-02 (Latest revision 2017-10-29) | ||
| RFC stream | (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
If QUIC is to be used in a peer-to-peer manner, with NAT traversal, then it is necessary to be able to demultiplex QUIC and STUN flows running on a single UDP port. This memo discusses options for how to perform such demultiplexing. It also considers demultiplexing of QUIC and WebRTC traffic (both media and data) when running on a single UDP port.
Authors
Dr. Bernard D. Aboba
Peter Thatcher
Colin Perkins
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)