Data Channels for RTCWEB
draft-thomson-rtcweb-data-00
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Author | Martin Thomson | ||
| Last updated | 2013-08-22 (latest revision 2013-02-18) | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized (tools)
htmlized
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus Boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
This Internet-Draft is no longer active. A copy of
the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-thomson-rtcweb-data-00.txt
https://www.ietf.org/archive/id/draft-thomson-rtcweb-data-00.txt
Abstract
RTCWEB have selected SCTP over DTLS over UDP with ICE for peer-to- peer data channels. There is some debate over the best way to negotiate channels. This proposal is a nose-to-tail description of an alternative to existing proposals.
Authors
Martin Thomson (martin.thomson@skype.net)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)