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

Re: API or spec to limit a certain sending track

From: Cullen Jennings (fluffy) <fluffy@cisco.com>
Date: Wed, 2 Aug 2017 08:24:50 -0600
Cc: "public-webrtc@w3.org" <public-webrtc@w3.org>
Message-Id: <43B67DCF-A7C7-4B1F-88F1-7688520ACBE3@cisco.com>
To: Iñaki Baz Castillo <ibc@aliax.net>

> On Aug 2, 2017, at 8:18 AM, Iñaki Baz Castillo <ibc@aliax.net> wrote:
> On Wed, Aug 2, 2017 at 4:08 PM, Cullen Jennings (fluffy)
> <fluffy@cisco.com> wrote:
>>>> Uh, setting the b= lines in SDP would do this. Am I missing why this does not work ?
>>> Try that in PlanB ;)
>> But you agree it works fine in the WebRTC spec even if some browser have not yet implemented all of WebRTC 1.0 ?
> No, I don't agree:
> 1) Mangling the SDP is not the way to go (and theoretically will be prohibited).

But this is not mangling SDP between CreateOffer and setLocat, it has having you server set bandwidth in the SDP.

> 2) Even if allowed, having to mangle the SDP and perform a fake SDP
> O/A local renegotiation is not cool at all. Note that, in my use case
> above, the bitrate limit is decided by the server at any time).

not sugesting that

> 3) It does not work in PlanB if I send two video tracks because b= is
> per media (and not per "ssrc").

Plan B is not part of webrtc and no idea why we are even discussing it on this list 

> -- 
> Iñaki Baz Castillo
> <ibc@aliax.net>
Received on Wednesday, 2 August 2017 14:25:06 UTC

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