QUIC Multiplexing
draft-aboba-avtcore-quic-multiplexing-04
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Dr. Bernard D. Aboba , Peter Thatcher , Colin Perkins | ||
| Last updated | 2019-07-27 (Latest revision 2020-01-28) | ||
| 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
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 other protocols used in WebRTC on a single UDP port. This memo discusses options for demultiplexing.
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.)