W3C home > Mailing lists > Public > public-webrtc@w3.org > March 2018

Re: Getting rid of SDP

From: Bernard Aboba <Bernard.Aboba@microsoft.com>
Date: Mon, 5 Mar 2018 20:45:53 +0000
To: Peter Thatcher <pthatcher@google.com>
CC: WebRTC WG <public-webrtc@w3.org>
Message-ID: <ABCB6816-BAE8-4FD8-963D-881163258478@microsoft.com>
On Mar 5, 2018, at 15:30, Peter Thatcher <pthatcher@google.com<mailto:pthatcher@google.com>> wrote:
Even though you have discussion in the IETF going on at dispatch@ietf.org<mailto:dispatch@ietf.org>, I think that it's worth having discussion here about the Web API side of things.  I think almost your entire proposal could be implemented in JS/wasm with the following Web APIs:

- SLICE (what I proposed two virtual interims ago as part of https://github.com/w3c/webrtc-ice)
- QUIC data streams (https://github.com/w3c/webrtc-quic)
- A low-level audio/video encoder/decoder API (like what I proposed at TPAC in 2017)

I think having those APIs available for your idea to be possible to implement in a web context (or other similar ideas) is a great direction to go.

[BA] A major advantage of the approach above is that it is modular and can deliver incremental functionality based on existing work in RTCWEB, ICE and QUIC WGs without an inherent dependency on RTPv3 or ICEv2 (though it can also accommodate those things if and when they become available).
Received on Monday, 5 March 2018 20:46:19 UTC

This archive was generated by hypermail 2.3.1 : Monday, 5 March 2018 20:46:20 UTC