User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/49.0.2623.54 Safari/537.36 Steps to reproduce: Currently there is no DSCP support for WebRTC traffic(Voice/Video primarily) Actual results: Currently there is no DSCP support for WebRTC traffic(Voice/Video primarily) Expected results: DSCP support should be enabled for WebRTC traffic(Voice/Video primarily). Currently Chrome/Opera supports this via 'googDscp' constraint - Without this, WebRTC based enterprise solutions could not support Firefox on the QoS feature front.
Status: UNCONFIRMED → NEW
backlog: --- → webrtc/webaudio+
Component: WebRTC → WebRTC: Networking
Ever confirmed: true
Priority: -- → P2
In a enterprise environment, the administrator has the privileges to configure DSCP setting applied to VoIP calls apart from the default value. The same would be configured for all traffic routers and switches in a network to have some form of Quality of Service mechanism (QoS). So request a slight modification in bug description to allow custom DSCP values from the application to be set on webrtc traffic instead of default value 46 on the voice/video packets. This will be very much inline with VOIP enterprise product offerings.
See https://datatracker.ietf.org/doc/draft-ietf-rtcweb-transports/?include_text=1 https://datatracker.ietf.org/doc/draft-ietf-tsvwg-rtcweb-qos/?include_text=1 and http://w3c.github.io/webrtc-pc/#priority-and-qos-model These IIRC do not allow for 'custom' DSCP markings, but do allow for prioritizing based on the application (JS application) requesting it. No interface has been proposed at the JS layer to set custom values, though tsvwg-rtcweb-qos seems to presume it would: "DSCP values are in principle site specific, with each site selecting its own code points for controlling per-hop-behavior to influence the QoS for transport-layer flows. However in the WebRTC use cases, the browsers need to set them to something when there is no site specific information." This bug is about providing the support mentioned in the spec (and in fact should be at least two bugs: one for DSCP support in the network code, one for priority support in the DOM API that affects the DSCP markings. Separately, if you want support for custom DSCP codepoints from JS, you'll need to file an issue (or PR) on the webrtc w3 spec (and soon).
Mass change P2->P3 to align with new Mozilla triage process.
Priority: P2 → P3
You need to log in before you can comment on or make changes to this bug.