W3C home > Mailing lists > Public > public-webrtc@w3.org > August 2017

Re: API or spec to limit a certain sending track

From: Iñaki Baz Castillo <ibc@aliax.net>
Date: Tue, 1 Aug 2017 20:08:20 +0200
Message-ID: <CALiegfk+Aji=8oMruqf87ViCCLPWNdL2qjRay=8WWJGYQPSegA@mail.gmail.com>
To: "Cullen Jennings (fluffy)" <fluffy@cisco.com>
Cc: "public-webrtc@w3.org" <public-webrtc@w3.org>
On Fri, Jul 28, 2017 at 4:38 PM, Cullen Jennings (fluffy)
<fluffy@cisco.com> wrote:
>
> Another approach is to use the priority API.

Honestly, I don't think that fits the use-case I exposed. I really
want to control the maximum bitrate of each sending track, not just
prioritizing one of them.


> It also depends on which side end wants to controls this. If the SFU is makeing the decisiong on what is important, then the best option is much differnt than if the JS in the browser is making the decision. Lots of SFU do use SDP to controls this thought I would not suggest that the client JS munging SDP was a good approach to this.

I'm open to both approaches (that's why I proposed client side and
server side posible approaches).

Regarding SDP mungling, I think I just dropped it. Anyhow, I don't
think it's possible to mungle a SDP to tell the browser "hey, send
this track with this max bitrate and this other track with this other
max bitrate".


-- 
Iñaki Baz Castillo
<ibc@aliax.net>
Received on Tuesday, 1 August 2017 18:09:04 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 15:19:51 UTC