From: Jonathan Morton <chromatix99@gmail.com>
To: Frantisek Borsik <frantisek.borsik@gmail.com>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] "Very interesting L4S presentation from Nokia Bell Labs on tap for RIPE 88 in Krakow this week! "
Date: Tue, 21 May 2024 19:18:41 +0300 [thread overview]
Message-ID: <28C0EFA5-8681-41DB-AF49-E551D1AA2A0A@gmail.com> (raw)
In-Reply-To: <CAJUtOOhzp3p6DEdSTuHrczk7AM5uFcDUgE6mc+A_BM5G+O5JHw@mail.gmail.com>
> On 21 May, 2024, at 6:31 pm, Frantisek Borsik via Bloat <bloat@lists.bufferbloat.net> wrote:
>
> Just "fresh from the oven", shared by Jason on social media:
>
> https://ripe88.ripe.net/wp-content/uploads/presentations/67-20240521_RIPE88_L4S_introduction_Werner_Coomans_upload.pdf
The usual set of half-truths, with a fresh coat of paint. Notice in particular that the only *performance* comparisons they make are between L4S and no AQM at all, not between L4S and conventional AQM - even though they now mention that the latter *exists*. There's also no mention whatsoever of what happens when L4S traffic meets a conventional AQM.
- Jonathan Morton
next prev parent reply other threads:[~2024-05-21 16:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-21 15:31 Frantisek Borsik
2024-05-21 16:18 ` Jonathan Morton [this message]
2024-05-21 17:13 ` Livingood, Jason
2024-05-21 17:32 ` Sebastian Moeller
2024-05-22 5:40 ` [Bloat] Fwd: " Sebastian Moeller
2024-05-22 8:47 ` Frantisek Borsik
2024-05-22 12:48 ` Livingood, Jason
2024-05-22 13:10 ` [Bloat] " Sebastian Moeller
2024-05-22 9:37 ` Jonathan Morton
2024-05-22 12:30 ` [Bloat] [EXTERNAL] " Livingood, Jason
2024-05-22 12:27 ` Livingood, Jason
2024-05-22 12:54 ` [Bloat] [EXTERNAL] " Sebastian Moeller
2024-05-22 17:37 ` Sebastian Moeller
2024-05-23 0:06 [Bloat] " Livingood, Jason
2024-05-23 6:16 ` Sebastian Moeller
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=28C0EFA5-8681-41DB-AF49-E551D1AA2A0A@gmail.com \
--to=chromatix99@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=frantisek.borsik@gmail.com \
/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