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: Wed, 2 Aug 2017 16:04:46 +0200
Message-ID: <CALiegfncCfF+2VHaB5TE=fVnEKu1fyK252FyLu0PzN8fB9gQJg@mail.gmail.com>
To: "Cullen Jennings (fluffy)" <fluffy@cisco.com>
Cc: "public-webrtc@w3.org" <public-webrtc@w3.org>
On Wed, Aug 2, 2017 at 3:54 PM, Cullen Jennings (fluffy)
<fluffy@cisco.com> wrote:
> I agree it is a different case but given the JS has no good way to know the current state of the congestion controller, it often turns out this is a better approach. Without it is is hard to decide what bitrate you want to assign to each track as you don't know the total available bandwidth.

The server can signal the sending BWE and sending bitrate (or the app
can get it via RTCStats) to the app so the JS can be aware of such a
value. Or easier, the server tells the app what the maximum bitrate
must be for a given track and the JS applies it via [...].

> Uh, setting the b= lines in SDP would do this. Am I missing why this does not work ?

Try that in PlanB ;)

Iñaki Baz Castillo
Received on Wednesday, 2 August 2017 14:05:31 UTC

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