#560: WebRTC Priority Control API
Discussions
Comment by @torgo Oct 14, 2020 (See Github)
Hi @caribouW3 – can you provide a little more detail in the explainer? In particular, an articulated "user need" e.g. "this will make WebRTC user experience better by xxx" and more of a description of what is therefore proposed?
Comment by @alvestrand Nov 23, 2020 (See Github)
hi @torgo and apologies for a slow response - I am reading through the first 4 paragraphs of https://github.com/w3c/webrtc-priority/blob/master/explainer.md and scratching my head about how to do better - those 4 paragraphs lay out:
- Why prioritization is needed (need)
- Why the user wants to prioritize some streams over others (user need)
- Why there needs to be both local prioritization and network prioritization
- That this specification gives a means to control that. (what is proposed)
Looking at your question - could you go into a little more detail about why those 4 paragraphs fail to communicate with you?
I added a fifth paragraph, saying "if the user uses this API, he can achieve the desired result" - does that help?
Comment by @alvestrand Jan 6, 2021 (See Github)
ping @torgo - still don't know how to address this issue.
Comment by @ylafon Jan 27, 2021 (See Github)
After reviewing this with @cynthia , it sounds good to us (provided the sound track has proper priority). Thanks!
OpenedSep 24, 2020
Saluton TAG!
I'm requesting a TAG review of the WebRTC Priority Control API.
(Note: discussion had started in https://github.com/w3ctag/design-reviews/issues/465)
This API defines a control surface for manipulating the network control bits (DSCP bits) of outgoing WebRTC packets, and the queueing priority of outgoing WebRTC packets under congestion.
Further details:
We'd prefer the TAG provide feedback as (please delete all but the desired option):
☂️ open a single issue in our GitHub repo for the entire review