W3C home > Mailing lists > Public > public-webrtc@w3.org > November 2017

Re: A very short extension spec: DSCP codepoint control

From: Stefan Håkansson LK <stefan.lk.hakansson@ericsson.com>
Date: Wed, 29 Nov 2017 09:41:24 +0000
To: Harald Alvestrand <harald@alvestrand.no>, "public-webrtc@w3.org" <public-webrtc@w3.org>
Message-ID: <HE1PR07MB3418807FF35DDCD1121D554FC93B0@HE1PR07MB3418.eurprd07.prod.outlook.com>
On 28/11/17 18:20, Harald Alvestrand wrote:
> Picking up on a post-Singapore action item:
> 
> I've written a very short (VERY short) spec for an extension to
> webrtc-pc that allows one to control the setting of packet-level
> priority separate from queue-management priority.
> 
> This is at https://github.com/alvestrand/webrtc-dscp-exp
> 
> Best starting point is probably the explainer:
> 
> https://github.com/alvestrand/webrtc-dscp-exp/blob/master/explainer.md

for my understanding (looking at the examples), is it right that the 
order you do things in matter, i.e.

pc = new RTCPeerConnection();
sender1 = pc.addTrack(track1);
sender2 = pc.addTrack(track2);
parameters = await sender1.getParameters();
parameters.encodings[0].priority = "high";
parameters.encodings[0].networkPriority = "low";
sender1.encodingParameters.setParameters(parameters);

would give "low" networkPriority while

pc = new RTCPeerConnection();
sender1 = pc.addTrack(track1);
sender2 = pc.addTrack(track2);
parameters = await sender1.getParameters();
parameters.encodings[0].networkPriority = "low";
parameters.encodings[0].priority = "high";
sender1.encodingParameters.setParameters(parameters);

would give "high" networkPriority (since .priority = "high" overrides)?

> 
> 
> The question now is - what now?
> 
> Possible actions include adopting this in the WG, asking for adoption as
> a WICG spec, or keeping it as an individual contribution.
> 
> 
> What do people prefer?
> 
> 
> Harald
> 
> 
> 
> 
Received on Wednesday, 29 November 2017 09:42:03 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 29 November 2017 09:42:05 UTC