- From: youenn fablet <yfablet@apple.com>
- Date: Thu, 24 May 2018 16:48:20 -0700
- To: Bernard Aboba <Bernard.Aboba@microsoft.com>
- Cc: WebRTC WG <public-webrtc@w3.org>
> On May 23, 2018, at 9:06 AM, Bernard Aboba <Bernard.Aboba@microsoft.com> wrote: > > Youenn said: > > "It would also be interesting in a world where we would use the QUIC API on the web page server QUIC connection." > > [BA] By "QUIC API" do you mean the WebRTC-QUIC API? > https://w3c.github.io/webrtc-quic/ > > That API is for peer-to-peer use (e.g. the QuicTransport constructor requires an IceTransport) How is it different though? They are all a QUIC connection on which we might want to send either structured data or media data. I agree that the security model is different, but let’s say we restrict this API to same-origin contexts only (plus maybe an opt-in by the server). Then, doesn’t it makes sense to allow using the QUIC server connection in the same way you would do for peer-to-peer? FWIW, if we define such an API, we should make it as good as possible, and not care about RTP too much, if not at all. RTP is the protocol in use for WebRTC currently, maybe it should also have its own API. It is then up to the other APIs (encoder/decoder) that could be used in conjunction with either QUIC or RTP to be designed adequately. Y
Received on Thursday, 24 May 2018 23:48:44 UTC