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

setting bandwidth

From: Cullen Jennings (fluffy) <fluffy@cisco.com>
Date: Wed, 24 Jul 2013 04:26:10 +0000
To: Stefan Håkansson LK <stefan.lk.hakansson@ericsson.com>
CC: "public-webrtc@w3.org" <public-webrtc@w3.org>
Message-ID: <C5E08FE080ACFD4DAE31E4BDBF944EB1136084A1@xmb-aln-x02.cisco.com>

On Jul 18, 2013, at 6:21 AM, Stefan Håkansson LK <stefan.lk.hakansson@ericsson.com> wrote:

> 2. Setting BW for a MediaStreamTrack
> ------------------------------------
> Why: There are situations where a suitable start bit-rate can be known, 
> or guessed. If this knowledge could be used the perceived end-user 
> quality could be improved (since a higher quality is available from 
> start since there is no need to start at a really low bit-rate).
> 
> There are also situations where it could be beneficial if min and max 
> bit-rates to be used can be influenced.
> 
> * The app developer may know that below a certain bit-rate the quality 
> is so bad that the browser could stop sending it, and likewise there may 
> be knowledge about a bit-rate above which the quality does not improve.
> 
> * There are situations when there is an agreement between the service 
> provider and the connectivity provider about min and max bit-rates.
> 
> What: Again, this depends on how much BW info is included in the SDP. 
> But my understanding is that there should be some (since RTCP rates to 
> be used are based on this info IIUC).

I agree and think we need to a couple things here. One is setting the limits for the bandwidth but the  other is using the stats interface to read the current bandwidth being used. 
Received on Wednesday, 24 July 2013 04:26:38 UTC

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