From: Roland Bless <roland.bless@kit.edu>
To: Michael Welzl <michawe@ifi.uio.no>
Cc: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] [Ecn-sane] [iccrg] Fwd: [tcpPrague] Implementation and experimentation of TCP Prague/L4S hackaton at IETF104
Date: Sat, 23 Mar 2019 20:55:41 +0100 [thread overview]
Message-ID: <a7908bce-f747-b5bc-cb87-1e3e15fcfd8a@kit.edu> (raw)
In-Reply-To: <B634F202-E883-4145-A4AD-1CDC67965206@ifi.uio.no>
Hi Michael,
thanks for the pointer. Looking forward to the talk...
Regards
Roland
On 23.03.19 at 18:48 Michael Welzl wrote:
> Hi,
>
> I’ll do what academics do and add our own data point, below:
>
>> On Mar 23, 2019, at 4:19 PM, Roland Bless <roland.bless@kit.edu
>> <mailto:roland.bless@kit.edu>> wrote:
>>
>> Hi Mikael,
>>
>> On 23.03.19 at 11:02 Mikael Abrahamsson wrote:
>>> On Sat, 23 Mar 2019, Roland Bless wrote:
>>>
>>>> I suggest to use an additional DSCP to mark L4S packets.
>>>
>>> DSCP doesn't work end-to-end on the Internet, so what you're suggesting
>>> isn't a workable solution.
>>
>> It's true that DSCPs may be remarked, but RFC 2474
>> already stated
>>
>> Packets received with an unrecognized codepoint SHOULD be forwarded
>> as if they were marked for the Default behavior (see Sec. 4), and
>> their codepoints should not be changed.
>>
>> The rtcweb WG also counts on e2e DSCPs.
>> After the LE PHB experience I would suggest to probably use
>> DSCP 5 which has got better chances to survive ToS bleaching (maybe
>> around 80%), if I understand
>> https://www.sciencedirect.com/science/article/pii/S0140366417312835
>> correctly. Diffserv behavior is usually configurable and can be changed
>> without replacing the network gear.
>
> Runa Barik, Michael Welzl, Ahmed Mustafa Elmokashfi, Thomas Dreibholz,
> Stein Gjessing: "Can WebRTC QoS Work? A DSCP Measurement Study", 30th
> International Teletraffic Congress (ITC 30), 3 - 7 September 2018,
> Vienna, Austria.
> https://itc-conference.org/_Resources/Persistent/780df4482d0fe80f6180f523ebb9482c6869e98b/Barik18ITC30.pdf
>
> We didn’t measure undefined codepoints though, only EF, AF42 and CS1.
> Table 2 compares bleaching for these codepoints with the results in the
> paper you point to; it’s quite similar.
> Well yes, there’s a significant amount of bleaching, we can’t deny that.
> But sometimes the codepoint survives, and it seems to survive
> surprisingly long into the path (fig.4 in our paper).
>
> In the MAPRG session in Prague, Runa Barik will give a talk about the
> measured delay impact of such opportunistic use of these DSCP values by
> an end system.
>
> Cheers,
> Michael
>
next prev parent reply other threads:[~2019-03-23 19:55 UTC|newest]
Thread overview: 83+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-22 18:28 Victor Hou
2019-03-23 8:02 ` Roland Bless
2019-03-23 8:54 ` Luca Muscariello
2019-03-23 10:02 ` Mikael Abrahamsson
2019-03-23 15:03 ` Jonathan Morton
2019-03-23 19:52 ` Roland Bless
2019-03-23 15:19 ` Roland Bless
2019-03-23 17:16 ` Mikael Abrahamsson
2019-03-23 19:45 ` Roland Bless
2019-03-23 17:48 ` Michael Welzl
2019-03-23 18:31 ` Luca Muscariello
2019-03-23 18:40 ` Mikael Abrahamsson
2019-03-23 19:11 ` Michael Welzl
2019-03-23 21:04 ` Luca Muscariello
2019-03-23 19:55 ` Roland Bless [this message]
[not found] <AM0PR07MB48198660539171737E4CCAB1E0730@AM0PR07MB4819.eurprd07.prod.outlook.c om>
[not found] ` <d91a6a71-5898-9571-2a02-0d9d83839615@bobbriscoe.net>
2019-03-15 10:46 ` [Bloat] " Dave Taht
2019-03-15 13:01 ` Sebastian Moeller
2019-03-15 14:06 ` Dave Taht
2019-03-15 15:52 ` Sebastian Moeller
2019-03-15 17:01 ` [Bloat] [Ecn-sane] " David P. Reed
2019-03-15 17:45 ` Sebastian Moeller
2019-03-15 18:36 ` Mikael Abrahamsson
2019-03-15 19:23 ` Sebastian Moeller
2019-03-15 19:32 ` Jonathan Morton
2019-03-15 19:44 ` David P. Reed
2019-03-15 20:13 ` Jonathan Morton
2019-03-15 23:43 ` David P. Reed
2019-03-16 1:26 ` Jonathan Morton
2019-03-16 7:38 ` Sebastian Moeller
2019-03-16 18:56 ` Michael Richardson
2019-03-15 20:28 ` Jonathan Foulkes
2019-03-15 20:31 ` Dave Taht
2019-03-15 23:45 ` David P. Reed
2019-03-16 9:42 ` Michael Welzl
2019-03-16 10:08 ` Sebastian Moeller
2019-03-16 10:23 ` Nils Andreas Svee
2019-03-16 14:55 ` Jonathan Foulkes
2019-03-16 21:38 ` Holland, Jake
2019-03-16 21:57 ` Vint Cerf
2019-03-16 22:03 ` Dave Taht
2019-03-16 22:05 ` Holland, Jake
2019-03-17 18:07 ` David P. Reed
2019-03-17 18:05 ` Vint Cerf
2019-03-19 1:06 ` Bob Briscoe
2019-03-19 3:18 ` Dave Taht
2019-03-20 19:04 ` Holland, Jake
2019-03-20 19:58 ` Stephen Hemminger
2019-03-20 20:05 ` Holland, Jake
2019-03-20 21:48 ` Greg White
2019-03-20 21:56 ` Jonathan Morton
2019-03-20 22:38 ` Holland, Jake
2019-03-20 22:56 ` Greg White
2019-03-20 23:29 ` Bob Briscoe
2019-03-20 23:51 ` Jonathan Morton
2019-03-21 6:04 ` Bob Briscoe
2019-03-21 7:46 ` Jonathan Morton
2019-03-21 8:02 ` Bob Briscoe
2019-03-21 8:49 ` Bless, Roland (TM)
2019-03-21 13:24 ` Bob Briscoe
2019-03-22 12:53 ` Bless, Roland (TM)
2019-03-25 2:47 ` Bob Briscoe
2019-03-21 8:45 ` Sebastian Moeller
2019-03-24 20:15 ` alex.burr
2019-03-25 1:34 ` Bob Briscoe
2019-03-27 17:52 ` Alex Burr
2019-03-19 4:44 ` Greg White
2019-03-19 5:35 ` Jonathan Morton
2019-03-19 5:52 ` Greg White
2019-03-19 7:10 ` Jonathan Morton
2019-03-19 8:07 ` Sebastian Moeller
2019-03-19 8:50 ` Sebastian Moeller
2019-03-19 23:59 ` Dave Taht
2019-03-20 10:17 ` Sebastian Moeller
2019-03-16 22:03 ` Jonathan Morton
2019-03-16 22:09 ` Sebastian Moeller
2019-03-17 14:06 ` Mikael Abrahamsson
2019-03-17 17:37 ` Loganaden Velvindron
2019-03-17 17:40 ` Toke Høiland-Jørgensen
2019-03-17 17:44 ` Mikael Abrahamsson
2019-03-17 18:00 ` Dave Taht
2019-03-17 19:38 ` Rodney W. Grimes
2019-03-17 20:50 ` Luca Muscariello
2019-03-17 21:51 ` Toke Høiland-Jørgensen
2019-03-18 4:26 ` Mikael Abrahamsson
2019-03-16 4:04 ` Jonathan Morton
2019-03-16 4:51 ` Dave Taht
2019-03-15 18:07 ` Mikael Abrahamsson
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/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a7908bce-f747-b5bc-cb87-1e3e15fcfd8a@kit.edu \
--to=roland.bless@kit.edu \
--cc=bloat@lists.bufferbloat.net \
--cc=michawe@ifi.uio.no \
/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