Technical Summary
This document defines how to use the WebRTC data channel mechanism in
order to realize a data channel, referred to as a CLUE data channel,
for transporting CLUE protocol messages between two CLUE entities.
The document defines how to describe the SCTP over DTLS association used
to realize the CLUE data channel using the Session Description
Protocol (SDP), and defines usage of the SDP-based "SCTP over DTLS" data
channel negotiation mechanism for establishing a CLUE data channel.
Details and procedures associated with the CLUE protocol, and the SDP
Offer/Answer procedures for negotiating usage of a CLUE data channel,
are outside the scope of this document.
Working Group Summary
There was some difficulty in deciding what mechanism to use to establish
the CLUE data channel: whether to the in-band mechanism of
draft-ietf-rtcweb-data-protocol, or the SDP offer/answer mechanism of
draft-ietf-mmusic-data-channel-sdpneg. Since offer/answer is heavily used
in CLUE, the O/A mechanism was preferred, but the work on defining it
lagged, and it isn't overtly supported in RTCWEB. But the work on that
draft has advanced well so that the group is now willing to accept that
dependency.
Document Quality
Are there existing implementations of the protocol?
One vendor has prototyped and demonstrated CLUE support in
their product.
Have a significant number of vendors indicated their plan to
implement the specification?
Beyond the prototype, no specific plans have yet been announced.
Are there any reviewers that
merit special mention as having done a thorough review,
e.g., one that resulted in important changes or a
conclusion that the document had no substantive issues?
None that stand out.
If there was a MIB Doctor, Media Type or other expert review,
what was its course (briefly)? In the case of a Media Type
review, on what date was the request posted?
None apply to this document
Personnel
Who is the Document Shepherd?
Paul Kyzivat
Who is the Responsible Area Director?
Adam Roach