W3C home > Mailing lists > Public > public-webrtc@w3.org > July 2015

Re: I have created a PR for RtpEncodingParameters.maxBitrate

From: Luis López Fernández <luis.lopez@urjc.es>
Date: Mon, 20 Jul 2015 11:44:16 +0200
CC: Randell Jesup <randell-ietf@jesup.org>, public-webrtc <public-webrtc@w3.org>
Message-ID: <596B16A5-40B3-463D-82C7-B4B060C742C8@urjc.es>
To: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
If you allow me to see it from other (developer) perspective, there is a relevant number of WebRTC applications using MCU or SFU for group communications and one-to-many distributions. In such applications, setting maxBitrate in absolute terms makes possible to control and plan better the scalability of the infrastructure. For example, feedback from developers in the Kurento mailing list shows a lot of people mangling the SDP for adding  b=as:max-bw lines in order to have this feature. IMO it would be a plus to enable it directly at the API level in absolute terms, which by the way is compatible with enabling also setting it relatively.

Best.

L.

El 19/07/2015, a las 05:07, Silvia Pfeiffer <silviapfeiffer1@gmail.com> escribió:

> As a developer, I would really like to see controls that are relative
> to these boundaries, not absolute numbers. E.g. I'd like to tell each
> outgoing/incoming video stream to use no more than 25% of my available
> bandwidth - which would then adapt to the available bandwidth (looks
> like RTP would then also need to negotiate the minimum of the two).
> Then, e.g., the data channel should use no more than 40% of my
> available bandwidth - since it's bursty, it can take a bit more.
Received on Monday, 20 July 2015 09:44:51 UTC

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