CLUE Protocol Data Channel
draft-holmberg-clue-datachannel-04
Document | Type |
Replaced Internet-Draft
(clue WG)
Expired & archived
|
|
---|---|---|---|
Author | Christer Holmberg | ||
Last updated | 2014-03-13 | ||
Replaced by | RFC 8850 | ||
RFC stream | Internet Engineering Task Force (IETF) | ||
Intended RFC status | (None) | ||
Formats | |||
Additional resources | Mailing list discussion | ||
Stream | WG state | Adopted by a WG | |
Document shepherd | (None) | ||
IESG | IESG state | Replaced by draft-ietf-clue-datachannel | |
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
This document defines how to use the WebRTC Data Channel mechanism, together with the Data Channel Establishment Protocol (DCEP) in order to establish a data channel, referred to as CLUE Data Channel, for transporting CLUE protocol messages between two CLUE entities. The document defines the SCTP considerations specific to a CLUE Data Channel, the SDP offer/answer procedures for negotiating the establishment of, and the DCEP procedures for opening, a CLUE Data Channel. Details and procedures associated with the CLUE protocol are outside the scope of this document.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)