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

"Priority and QoS model"

From: Stefan Håkansson LK <stefan.lk.hakansson@ericsson.com>
Date: Sun, 18 Jun 2017 06:39:40 +0000
To: "public-webrtc@w3.org" <public-webrtc@w3.org>
Message-ID: <AM5PR0701MB2724E468D7C77F3DFD4C3629C9C70@AM5PR0701MB2724.eurprd07.prod.outlook.com>
Hi all,

the section "Priority and QoS model" [1] basically gives the JS 
application the options "very-low", "low", "medium" and "high" and then 
references RTCWEB-TRANSPORT section 4 and TSVWG-RTCWEB-QOS.

RTCWEB-TRANSPORT section 4 in turn describes "local prioritization" and 
use of DSCP (with references to TSVWG-RTCWEB-QOS for the later).

Both "local prioritization" and DSCP use are phrased as "SHOULD". This 
means that there may be no local prioritization and/or no DSCP marking 
made even though a specific priority is requested, and the application 
would not know.

I think this is what we agreed back when this was discussed, but I just 
wanted to check that the group thinks this is fine.


[1] http://w3c.github.io/webrtc-pc/#priority-and-qos-model
Received on Sunday, 18 June 2017 06:40:22 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 15:19:51 UTC