%% You should probably cite rfc8864 instead of this I-D. @techreport{ietf-mmusic-data-channel-sdpneg-16, number = {draft-ietf-mmusic-data-channel-sdpneg-16}, type = {Internet-Draft}, institution = {Internet Engineering Task Force}, publisher = {Internet Engineering Task Force}, note = {Work in Progress}, url = {https://datatracker.ietf.org/doc/draft-ietf-mmusic-data-channel-sdpneg/16/}, author = {Keith Drage and Maridi R. Makaraju (Raju) and Juergen Stoetzer-Bradler and Richard Ejzak and Jerome Marcon and Roni Even}, title = {{SDP-based Data Channel Negotiation}}, pagetotal = 42, year = 2017, month = dec, day = 25, abstract = {The Real-Time Communication in WEB-browsers (RTCWeb) working group is charged to provide protocols to support direct interactive rich communications 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 (Stream Control Transmission Protocol), 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. 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 (which is defined by the IETF "ControLling mUltiple streams for tElepresence" working group). This document is intended to be used wherever data channels are used.}, }