- From: Philipel-WebRTC via GitHub <sysbot+gh@w3.org>
- Date: Mon, 01 Jul 2024 08:07:20 +0000
- To: public-webrtc@w3.org
Philipel-WebRTC has just created a new issue for https://github.com/w3c/webrtc-rtptransport: == Custom BWE without pacing is not well supported. == [Example 1 in UC2](https://github.com/w3c/webrtc-rtptransport/blob/main/explainer-use-case-2.md#example-1-custom-bwe) shows how BWE can be done at the app level even though pacing is done by the UA. This is based on the assumption that _only_ the `{packet size, send time, receive time}` is used for BWE, but that is not true in general. In WebRTC today we perform probing, and information about which packets was part of particular probe cluster and what the target probe rate was is only stored on the send side and is not part of any extension or feedback. When feedback is received about these packets then special BWE estimation logic kicks in. Custom BWE without pacing is still _technically_ supported but it will be hard to achieve a good result, so I suggest we either remove the example or make it clear that it is not a first class use case we intend to support. Please view or discuss this issue at https://github.com/w3c/webrtc-rtptransport/issues/56 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 1 July 2024 08:07:22 UTC