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

[webrtc-pc] Need for Initial Bitrate?

From: Varun Singh via GitHub <sysbot+gh@w3.org>
Date: Thu, 12 Oct 2017 17:45:27 +0000
To: public-webrtc@w3.org
Message-ID: <issues.opened-265028561-1507830312-sysbot+gh@w3.org>
vr000m has just created a new issue for https://github.com/w3c/webrtc-pc:

== Need for Initial Bitrate? ==
With the ongoing discussion in the relative bitrate and RTCPriority, I was wondering if providing the initial bitrate to the RTCSender was ever discussed. If it was, what was the outcome of that discussion?

If not, my strawman would be: 
This would be a local property for the send media side, and this would be input to the congestion control to start sending at and normal congestion control procedures would define what happens next.

A developer may want to use a past value from a previous call that just finished as the initial bitrate to override any default initial bitrate set by the implementor. This could of course be the tail bitrate (the last few seconds of the call), average/median/the maximum sustained in the call -- it would be up to the developer how they come up with the value. 

This is especially useful if the current default is higher than what the implementation thinks is the default start bitrate.

Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1635 using your GitHub account
Received on Thursday, 12 October 2017 17:45:24 UTC

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