RTCWeb Datagram Connection
draft-ietf-rtcweb-data-channel-00
| Document | Type |
This is an older version of an Internet-Draft that was ultimately published as RFC 8831.
Expired & archived
|
|
|---|---|---|---|
| Authors | Randell Jesup , Salvatore Loreto , Michael Tüxen | ||
| Last updated | 2012-09-06 (Latest revision 2012-03-05) | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Formats | |||
| Reviews | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | WG Document | |
| Document shepherd | (None) | ||
| IESG | IESG state | Expired | |
| Consensus boilerplate | Unknown | ||
| 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 Web Real-Time Communication (WebRTC) working group is charged to provide protocol support for direct interactive rich communication using audio, video, and data between two peers' web-browsers. This document describes the non-media data transport aspects of the WebRTC framework. It provides an architectural overview of how the Stream Control Transmission Protocol (SCTP) is used in the WebRTC context as a generic transport service allowing Web Browser to exchange generic data from peer to peer.
Authors
Randell Jesup
Salvatore Loreto
Michael Tüxen
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)