#325: WebRTC DSCP Control API

Visit on Github.

Opened Nov 15, 2018

こんにちは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):

  • open issues in our Github repo for each point of feedback
  • open a single issue in our Github repo for the entire review
  • leave review feedback as a comment in this issue and @-notify [github usernames]

Discussions

Comment by @alvestrand Nov 15, 2018 (See Github)

tagging @thaloun

Comment by @torgo Feb 5, 2019 (See Github)

Thanks for this. Can you please write an explainer (see https://w3ctag.github.io/explainers) about this so we can properly evaluate?

Comment by @slightlyoff Feb 5, 2019 (See Github)

@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.

Comment by @cynthia Feb 5, 2019 (See Github)

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.)

Comment by @cynthia Sep 10, 2019 (See Github)

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.

Comment by @dontcallmedom Oct 30, 2019 (See Github)

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)