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

Re: To Stream or not to Stream

From: youenn fablet <yfablet@apple.com>
Date: Thu, 14 Jun 2018 13:58:57 -0700
Cc: public-webrtc@w3.org
Message-id: <D50C3CA2-D918-4372-B4B3-B0CB8178B3B8@apple.com>
To: Sergio Garcia Murillo <sergio.garcia.murillo@gmail.com>


> Le 14 juin 2018 à 6:10 AM, Sergio Garcia Murillo <sergio.garcia.murillo@gmail.com> a écrit :
> 
> Hi Harald,
> 
> Fair points. Let's get a few steps back.
> 
> I think we have quite a consensus that webrtc nv should provide lower level components than the current ones in WebRTC/ORTC, with a more fine grained control. In order to decide what components will be required to implement we have gathered the uses cases we want to support and couldn’t be done with current APIS (at least easily).

I agree with the use cases and the idea to move away from SDP.
It is unclear yet how that would translate into APIs, probably lower level than WebRTC current APIs for some of the use-cases.

> It also seems to be a consensus that we should split the current sender/receivers into encoders/decoders and transports and due to some of the use cases, we have jumped into deciding that we need raw access to media frames and rtp packets, and jumped even further into requesting and providing API proposals about how to implement that.

I do not think we reached consensus on the idea of splitting senders/receivers in smaller bricks.
There are some use cases that would benefit from this.
There has been concerns in the cost, complexity and feasibility of this approach.
We should also investigate alternatives to fulfil these use cases than going the splitting way.

Thanks,
	Y
Received on Thursday, 14 June 2018 20:59:25 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:18:42 UTC