- From: Harald Alvestrand via GitHub <sysbot+gh@w3.org>
- Date: Wed, 13 Jun 2018 06:01:51 +0000
- To: public-webrtc-logs@w3.org
I agree that more explanation of this use case is better. To @aboba's concern: The DSCP spec (which is a result of a desire to not reopen the IETF transport spec at the time the question came up) specifies how to set priority without affecting DSCP. Agree that the "configure the codec" language lacks context - when I wrote it, I intended it to mean "within the range that configuration permits" - ie a low bandwidth, high priority stream should be almost guaranteed to never experience congestion as long as there are bits to be had. Thought: One possibility in the "split things up" movement would be to take the entire priority extension and move it into what's currently called the DSCP spec, so that it's its own body of work. It's obviously had less implementation experience than a lot of other stuff! -- GitHub Notification of comment by alvestrand Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1888#issuecomment-396823257 using your GitHub account
Received on Wednesday, 13 June 2018 06:02:10 UTC