- From: Bernard Aboba via GitHub <sysbot+gh@w3.org>
- Date: Mon, 27 Jul 2020 19:36:09 +0000
- To: public-webrtc-logs@w3.org
@dom @alvestrand I am not sure what work is being referred to here. IETF considered support for an RTP-based data channel and rejected it in favor of SCTP/DTLS/UDP and a gateway between RTCDataChannel and RTT, standardized [here](https://tools.ietf.org/html/draft-ietf-mmusic-t140-usage-data-channel). Given that the WebRTC API already supports the IETF-standardized solution, I am wondering whether there is any reason to consider alternatives. Have we had developer, governmental or telecom industry feedback that indicates that plan A is unworkable? Since implementing RFC 4103 (RTT over RTP) as a codec wouldn't be helpful, Plan B might involve something like WASM-based encoding/decoding of RTT, possibly in concert with the Insertable Streams API. -- GitHub Notification of comment by aboba Please view or discuss this issue at https://github.com/w3c/webrtc-charter/pull/58#issuecomment-664596457 using your GitHub account
Received on Monday, 27 July 2020 19:36:11 UTC