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 DSCP Control API #325
Comments
tagging @thaloun |
Thanks for this. Can you please write an explainer (see https://w3ctag.github.io/explainers) about this so we can properly evaluate? |
@alvestrand: we quickly discussed today and there's a question about what problem this solves. An explainer would go a long way, as would example code. Without some motivation and context, it's hard to understand what this feature is for, who it helps, and what risks we run. |
DSCP isn't disambiguated anywhere in the spec, which I think should be considered a bug. (At least I have not a slight clue what that is.) |
We don't quite know what to do with this issue, and it's been dangling for quite a bit. We'll close it for now as - happy to discuss this in person next week during TPAC if still needs our input. |
There is an explainer for the spec https://github.com/w3c/webrtc-dscp-exp/blob/master/explainer.md (sorry this wasn't pointed out earlier) |
こんにちはTAG!
I'm requesting a TAG review of:
Further details (optional):
You should also know that this is a minor control surface added to the WebRTC spec to split up an existing feature (priority) into two independent components (local prioritization and DSCP codepoint usage) without making changes to already-agreed documents.
We'd prefer the TAG provide feedback as (please select one):
The text was updated successfully, but these errors were encountered: