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

Re: API or spec to limit a certain sending track

From: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
Date: Sat, 5 Aug 2017 07:51:09 +1000
Message-ID: <CAHp8n2=Ui5N5gBNb83qGUFQPVXxnHijtrV3W1A1LQCNP9g57NQ@mail.gmail.com>
To: Iñaki Baz Castillo <ibc@aliax.net>
Cc: public-webrtc <public-webrtc@w3.org>, Stefan Håkansson LK <stefan.lk.hakansson@ericsson.com>
This solution from Atlassian might help on the SDP side:

Best Regards,

On 4 Aug. 2017 7:13 pm, "Iñaki Baz Castillo" <ibc@aliax.net> wrote:

On Fri, Aug 4, 2017 at 11:01 AM, Stefan Håkansson LK
<stefan.lk.hakansson@ericsson.com> wrote:

> I fully understand the pain trying to do magic with a toolbox that is
> not complete and with defects on some of the tools available - but I
> guess that is what you can expect at this stage!

Yep. For now I'll go with an approach that handles separate transports
(different WebRTC PeerConnections or different ORTC
Ice+DtlsTransports) for sending video tracks for which I need
different bitrate limits, so I should be able to limit a specific
video track via REMB (generated by the server) or even using b=AS.

Iñaki Baz Castillo
Received on Friday, 4 August 2017 21:51:32 UTC

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