- From: Taylor Brandstetter via GitHub <sysbot+gh@w3.org>
- Date: Mon, 26 Jun 2017 08:58:24 +0000
- To: public-webrtc-logs@w3.org
I talked to Peter, and realized that the same enum is intended to affect both the DSCP markings used for the SCTP transport, and the priority used by the SCTP scheduler (see: https://datatracker.ietf.org/doc/draft-ietf-tsvwg-rtcweb-qos/?include_text=1). Which seems odd to me, since there's also the requirement that all packets over the same SCTP transport use the same DSCP marking. It would have made more sense to me to have one priority enum for the transport level (priority of data relative to audio/video), and one for the SCTP scheduling level (priority of data channels relative to each other). But unless the IETF side changes, we should have a single enum, and acknowledge somewhere that the names in the two IETF specs don't match up. There's still [this issue](https://github.com/w3c/webrtc-pc/issues/1423) though, about what you do with the priority value in the "open" message, which I added as a virtual interim topic. -- GitHub Notification of comment by taylor-b Please view or discuss this issue at https://github.com/w3c/webrtc-pc/pull/1400#issuecomment-311002183 using your GitHub account
Received on Monday, 26 June 2017 08:58:30 UTC