Re: [w3ctag/design-reviews] WebRTC DSCP Control API (#465)

Note to @ylafon - the spec contains two parts - the local prioritization and the setting of DSCP code points.
I take it the local prioritization (which is prioritization among the client's own flows) is uncontroversial.

DSCP code points are usually the subject of network manager rule-setting; if the network is not configured to act on them, they will have no effect. So they can be considered "hints on relative priorities" sent from the host to the network.

The idea that such hints should be settable by the app has been accepted in the IETF for a very long time (years); I'm not eager to reopen that issue there. The relevant IOCTLs are available to all apps running natively on the host, so if we add another level of policing to their use, we're increasing the capability distance between native apps and Web apps. Still, a permissioned model might be a possibility here.

Apologies for the slow response.


-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/465#issuecomment-642513175