From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-vk0-x22c.google.com (mail-vk0-x22c.google.com [IPv6:2607:f8b0:400c:c05::22c]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by huchra.bufferbloat.net (Postfix) with ESMTPS id 831FE21F293 for ; Tue, 27 Oct 2015 09:16:38 -0700 (PDT) Received: by vkfw189 with SMTP id w189so123666947vkf.2 for ; Tue, 27 Oct 2015 09:16:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=PcgnF2x4GVmXSsm8zJIWXm3CZSEmspb8BIhXcwmAY1Y=; b=jqmxJYW93f2Y+LA3gDaMibxuobRPw0xbm/pbS5d344oFvaNnTlKCUa9EN4TYeWVBgp FEzWcjrColTqtJtJrNR6j45ECAodqGK+dR6mgXe5ya7mk9n6RIJU/fkIA8Tg+ez+l6D9 tfHA79gjECAA32LSiqaKRQmhCL6EwhP3CKpOvqMKhpVFd1zj/lyGWS650DAJLy1Ehwsq brcTcu7KjCvz4/5WCbbMj9Zmnu8JrzEMZ/LwfLJlN8NIeLOJQZJnY493/bXInxj2ftI+ lJBJH/gO1V/iZyvEkYU1sVis6K1zEqGrklzUyxSKIrYa41uOjBDpCq5E01VSRBib19aa /3CQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=PcgnF2x4GVmXSsm8zJIWXm3CZSEmspb8BIhXcwmAY1Y=; b=TvHjjjhLJNXHDVUpNbnyB1ZmoY/nVAEvLXBcBA0W9ZWSddPMBLo21JD1ErKyBxaoLe TTH4/JkUVWcO547GfKSlBXuT/ZH8vn9uj6B8bQOSoIo8yh6MAXTaOMX9gt1MdKxkx2uz ojovURj3+woNV45iP1UIsx01oik3vSjioA0ktKU2PTlsESWNNh1rbUv7CLC4NtJcg8iy /GeAtrqe56JLYfNJWrFfKSWVDkuTpmvfzVYNwsJ4BZis1U0i6r8AUTyLnxRvxQlU8iOo GnlWMqnPHebBovAAEyMeUs2K3o0R9G9ELRbxjN5bXoR3bXu/0hHEDobdvlQHC8hXcJPE D+/A== X-Gm-Message-State: ALoCoQno1QhXDGzUeTJ9Vke4/EsWcGBgzYMzxL7IZq7XsI5f5PyhNgLzoF4c6hCdp/qFI5+MdSrx X-Received: by 10.31.185.6 with SMTP id j6mr24048465vkf.98.1445962596837; Tue, 27 Oct 2015 09:16:36 -0700 (PDT) MIME-Version: 1.0 Received: by 10.31.170.201 with HTTP; Tue, 27 Oct 2015 09:16:17 -0700 (PDT) In-Reply-To: <7AE5EAF1-4177-466F-AEFA-3198F03F24B7@gmx.de> References: <5627B90D.8070106@alvestrand.no> <43B59C2F-4B64-4318-8339-04903AF2A6AC@cisco.com> <34EEB0FF-1922-42B5-A778-9BB66B7C4FDC@csperkins.org> <7AE5EAF1-4177-466F-AEFA-3198F03F24B7@gmx.de> From: Justin Uberti Date: Tue, 27 Oct 2015 09:16:17 -0700 Message-ID: To: Sebastian Moeller Content-Type: multipart/alternative; boundary=001a113bf89ef1c75e05231866c5 X-Mailman-Approved-At: Wed, 28 Oct 2015 08:16:01 -0700 Cc: "Pal Martinsen \(palmarti\)" , "aqm@ietf.org" , "cake@lists.bufferbloat.net" , "rmcat@ietf.org" , "rtcweb@ietf.org" , Colin Perkins Subject: Re: [Cake] [rmcat] [rtcweb] Catching up on diffserv markings X-BeenThere: cake@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: Cake - FQ_codel the next generation List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Oct 2015 16:17:00 -0000 --001a113bf89ef1c75e05231866c5 Content-Type: text/plain; charset=UTF-8 On Tue, Oct 27, 2015 at 1:06 AM, Sebastian Moeller wrote: > Hi Justin, > > > On Oct 22, 2015, at 21:54 , Justin Uberti 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. --001a113bf89ef1c75e05231866c5 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable


On Tue, Oct 27, 2015 at 1:06 AM, Sebastian Moeller &l= t;moeller0@gmx.de&= gt; 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 ca= n read the received ECN markings.
>
> iOS9 added support for this within the kernel, and it's used for T= CP, but not exposed to userspace. There is an open Radar bug asking for thi= s info to be exposed to userspace.
>
> FWIW, Chrome supports setting the DSCP markings if you set a magic par= ameter. But it's not on by default, mainly because we've never done= the auditing necessary to ensure this doesn't randomly break in variou= s dimly-lit parts of the internet.

=C2=A0 =C2=A0 =C2=A0 =C2=A0 Slightly related question, is this DSCP = marking capability restricted to webrtc packets or is there a way to make c= hrome use (arbitrary) DSCP marks for all its packets? For exercising differ= ent priority banding schemes such an option would be perfect (say to test w= hether 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).<= br>

The option that currently exists only w= orks for WebRTC packets.=C2=A0
--001a113bf89ef1c75e05231866c5--