From: Sebastian Moeller <moeller0@gmx.de>
To: Justin Uberti <juberti@google.com>
Cc: "Pal Martinsen \(palmarti\)" <palmarti@cisco.com>,
"aqm@ietf.org" <aqm@ietf.org>,
"cake@lists.bufferbloat.net" <cake@lists.bufferbloat.net>,
"rmcat@ietf.org" <rmcat@ietf.org>,
"rtcweb@ietf.org" <rtcweb@ietf.org>,
Colin Perkins <csp@csperkins.org>
Subject: Re: [Cake] [rmcat] [rtcweb] Catching up on diffserv markings
Date: Tue, 27 Oct 2015 18:04:59 +0100 [thread overview]
Message-ID: <3976D747-F6DA-4AC4-BCAB-D2B420E25B2D@gmx.de> (raw)
In-Reply-To: <CAOJ7v-3XcDyWGpMY3kgVWOCJed+wcUe1-LM3VCvye45Nva3Snw@mail.gmail.com>
Hi Justin,
On Oct 27, 2015, at 17:16 , Justin Uberti <juberti@google.com> wrote:
>
>
> On Tue, Oct 27, 2015 at 1:06 AM, Sebastian Moeller <moeller0@gmx.de> wrote:
> Hi Justin,
>
>
> On Oct 22, 2015, at 21:54 , Justin Uberti <juberti@google.com> wrote:
>
> > At present I'm not aware of any widely-deployed OS where an app can read the received ECN markings.
> >
> > iOS9 added support for this within the kernel, and it's used for TCP, but not exposed to userspace. There is an open Radar bug asking for this info to be exposed to userspace.
> >
> > FWIW, Chrome supports setting the DSCP markings if you set a magic parameter. But it's not on by default, mainly because we've never done the auditing necessary to ensure this doesn't randomly break in various dimly-lit parts of the internet.
>
> Slightly related question, is this DSCP marking capability restricted to webrtc packets or is there a way to make chrome use (arbitrary) DSCP marks for all its packets? For exercising different priority banding schemes such an option would be perfect (say to test whether a aqm+qos system will allow snappy browsing even with heavy download/upload/bittorrent traffic in other priority bands; this test is especially interesting if all traffic sources can reside on the same host, as this is a quite common set-up in home networks, one computer that does everything concurrently and where the users still want a decent browsing experience).
>
> The option that currently exists only works for WebRTC packets.
Ah, thanks, that is a pity. It would be really sweet for testing different qos systems. I guess on a linux machine I should e able to fake it with a local iptable rule…
Best Regards
Sebastian
next prev parent reply other threads:[~2015-10-27 17:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-21 15:51 [Cake] " Dave Taht
2015-10-21 16:10 ` [Cake] [rtcweb] " Harald Alvestrand
2015-10-22 7:48 ` Pal Martinsen (palmarti)
2015-10-22 9:13 ` Colin Perkins
2015-10-22 19:54 ` [Cake] [rmcat] " Justin Uberti
2015-10-23 13:29 ` Jonathan Morton
2015-10-23 13:31 ` Loganaden Velvindron
2015-10-27 8:06 ` Sebastian Moeller
2015-10-27 16:16 ` Justin Uberti
2015-10-27 17:04 ` Sebastian Moeller [this message]
2015-10-29 15:25 ` Piers O'Hanlon
2015-10-22 20:02 ` [Cake] [aqm] " Christian Huitema
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/cake.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3976D747-F6DA-4AC4-BCAB-D2B420E25B2D@gmx.de \
--to=moeller0@gmx.de \
--cc=aqm@ietf.org \
--cc=cake@lists.bufferbloat.net \
--cc=csp@csperkins.org \
--cc=juberti@google.com \
--cc=palmarti@cisco.com \
--cc=rmcat@ietf.org \
--cc=rtcweb@ietf.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox