SDP-based "SCTP over DTLS" data channel negotiation
draft-ejzak-mmusic-data-channel-sdpneg-00

The information below is for an old version of the document
Document Type Expired Internet-Draft (individual)
Last updated 2014-08-18 (latest revision 2014-02-14)
Replaces draft-ejzak-dispatch-webrtc-data-channel-sdpneg
Replaced by draft-ietf-mmusic-data-channel-sdpneg
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
pdf 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-ejzak-mmusic-data-channel-sdpneg-00.txt

Abstract

The Real-Time Communication in WEB-browsers (RTCWeb) working group is charged to provide protocols to support direct interactive rich communication using audio, video, and data between two peers' web- browsers. For the support of data communication, the RTCWeb working group has in particular defined the concept of bi-directional data channels over SCTP, where each data channel might be used to transport other protocols, called sub-protocols. Data channel setup can be done using either the in-band WebRTC Data Channel protocol or some external (in-band or out-of-band) negotiation. This document specifies how the SDP offer/answer exchange can be used to achieve such an external negotiation. Even though data channels are designed for RTCWeb use initially they may be used by other protocols like, but not limited to, the CLUE protocol. This document is intended to be used whereever data channels are used.

Authors

Keith Drage (keith.drage@alcatel-lucent.com)
Richard Ejzak (richard.ejzak@gmail.com)
Jerome Marcon

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)