Negotiation Data Channels Using the Session Description Protocol (SDP)
Draft of message to be sent after approval:
From: The IESG <firstname.lastname@example.org> To: IETF-Announce <email@example.com> Cc: firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, The IESG <email@example.com>, Bo Burman <firstname.lastname@example.org>, email@example.com, firstname.lastname@example.org, email@example.com Subject: Protocol Action: 'SDP-based Data Channel Negotiation' to Proposed Standard (draft-ietf-mmusic-data-channel-sdpneg-28.txt) The IESG has approved the following document: - 'SDP-based Data Channel Negotiation' (draft-ietf-mmusic-data-channel-sdpneg-28.txt) as Proposed Standard This document is the product of the Multiparty Multimedia Session Control Working Group. The IESG contact persons are Adam Roach, Alexey Melnikov and Barry Leiba. A URL of this Internet Draft is: https://datatracker.ietf.org/doc/draft-ietf-mmusic-data-channel-sdpneg/
Technical Summary: The Real-Time Communication in WEB-browsers (RTCWeb) working group has defined the concept of bi-directional data channels running on top of the Stream Control Transmission Protocol (SCTP), where each data channel might be used to transport other protocols, called subprotocols. Data channel setup can be done using either the in-band Data Channel Establishment Protocol (DCEP) or using some out-of-band non-DCEP protocol. This document specifies how the SDP (Session Description Protocol) offer/answer exchange can be used to achieve such an out-of-band non-DCEP negotiation. Working Group Summary: The document was reviewed and discussed multiple times by a fair number of MMUSIC members (listed in Acknowledgements section). There was no particular controversy of note. There was some post publication-request discussion about the IANA registration requirements, but those have been resolved. Document Quality: Nokia (former Alcatel-Lucent) implemented an earlier version of the draft, but no other implementations are known to the shepherd. The CLUE WG also makes use of WebRTC datachannel as the "CLUE channel" in their specifications and should therefore have seen some implementation. Personnel: The Document Shepherd is Bo Burman. The Responsible AD at the time of IETF LC was Ben Campbell. The Responsible AD for IESG evaluation and subsequent handling is Adam Roach.