General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: "Livingood, Jason" <jason_livingood@comcast.com>
To: Jonathan Morton <chromatix99@gmail.com>,
	Sebastian Moeller <moeller0@gmx.de>
Cc: Frantisek Borsik <frantisek.borsik@gmail.com>,
	bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] [EXTERNAL] Re: "Very interesting L4S presentation from Nokia Bell Labs on tap for RIPE 88 in Krakow this week! "
Date: Wed, 22 May 2024 12:30:12 +0000	[thread overview]
Message-ID: <591DB4E8-581D-4614-A812-0F48DC8C173D@comcast.com> (raw)
In-Reply-To: <11E74650-2844-42A7-96D1-3372324A9B91@gmail.com>

> I don't dispute that, at least insofar as the metrics you prefer for such comparisons, under the network conditions you also prefer. But by omitting the conventional AQM results from the performance charts, the comparison presented to readers is not between L4S and the current state of the art, and the expected benefit is therefore exaggerated in a misleading way.

[JL] That is good feedback for you to send to Nokia. But as I mentioned, all our comparisons in lab and field testing are of AQM vs L4S - so we have that covered (and lots of other tests cases I won't cover here). 





  reply	other threads:[~2024-05-22 12:30 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-21 15:31 [Bloat] " Frantisek Borsik
2024-05-21 16:18 ` Jonathan Morton
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         ` Livingood, Jason [this message]
2024-05-22 12:27       ` [Bloat] [EXTERNAL] " Livingood, Jason
2024-05-22 12:54         ` [Bloat] [EXTERNAL] " Sebastian Moeller
2024-05-22 17:37           ` 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=591DB4E8-581D-4614-A812-0F48DC8C173D@comcast.com \
    --to=jason_livingood@comcast.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=chromatix99@gmail.com \
    --cc=frantisek.borsik@gmail.com \
    --cc=moeller0@gmx.de \
    /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