[webrtc-stats] availableOutgoingBitrate is also available when send-side BWE is not used (#740)

fippo has just created a new issue for https://github.com/w3c/webrtc-stats:

== availableOutgoingBitrate is also available when send-side BWE is not used ==
https://w3c.github.io/webrtc-stats/#dom-rtcicecandidatepairstats-availableoutgoingbitrate
stipulates that
> Implementations that do not calculate a sender-side estimate must leave this undefined.

This is not how Chromium/libwebrtc behave, it exposes the value received by REMB which makes a lot of sense to me.

For the corresponding available incoming bitrate this makes a bit more sense because this value can only be calculated when REMB is used while a send-side BWE does not have the full information.

Using a normative MUST seems overkill in both cases, this calls for "exist". Can fix but after #739 gets merged to avoid confusion. 

Please view or discuss this issue at https://github.com/w3c/webrtc-stats/issues/740 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Monday, 6 March 2023 09:47:41 UTC