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

Re: [webrtc-pc] RTCPriorityType combines relative bitrate with QoS priority, which applications may not want.

From: Taylor Brandstetter via GitHub <sysbot+gh@w3.org>
Date: Wed, 11 Oct 2017 00:28:04 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-335646051-1507681669-sysbot+gh@w3.org>
> In practice, Windows only permits setting the DSCP code point on a per-socket, not per-packet basis.

Can't you use QOSSetFlow? From MSDN:

> This function is also used to notify the QoS subsystem of a flow change: for example ... if the QoS priority value requires adjustment for transferring or streaming different types of content over a single persistent socket connection.

Or are there practical limits to this?

> Does any other OS enable per-packet marking?

I thought POSIX OSes do, by calling `setsockopt` with `IP_TOS` or `IPV6_TCLASS` before sending the packet.

But anyway: even ignoring the issues related to QoS and multiple congestion controllers, it sounds like we agree that the "1:2" ratios are too limiting, and that mixing this up with QoS is undesirable.

GitHub Notification of comment by taylor-b
Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1625#issuecomment-335646051 using your GitHub account
Received on Wednesday, 11 October 2017 00:27:51 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:21:47 UTC