-
Notifications
You must be signed in to change notification settings - Fork 57
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WebRTC Priority Control API #560
Comments
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? |
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:
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? |
ping @torgo - still don't know how to address this issue. |
After reviewing this with @cynthia , it sounds good to us (provided the sound track has proper priority). |
Saluton TAG!
I'm requesting a TAG review of the WebRTC Priority Control API.
(Note: discussion had started in #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.
@alvestrand, @caribouW3
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
The text was updated successfully, but these errors were encountered: