General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: "Livingood, Jason" <jason_livingood@comcast.com>
To: Sebastian Moeller <moeller0@gmx.de>
Cc: Jonathan Morton <chromatix99@gmail.com>,
	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:27:47 +0000	[thread overview]
Message-ID: <1B7AD485-9CEA-4F79-B6F0-F2C1B0A9355D@comcast.com> (raw)
In-Reply-To: <C7D64E36-1A7D-449D-9708-D8B4E8CF3B39@gmx.de>

[-- Attachment #1: Type: text/plain, Size: 363 bytes --]

[SM] Here is Pete's data showing that, the middle two bars show what happens when the bottleneck is not treating TCP Prague to the expected signalling... That is not really fit for use over the open internet...

[JL] That graph is not anything like what we’ve seen in lab or field testing. I suspect you may have made some bad assumptions in the simulation.

[-- Attachment #2: Type: text/html, Size: 1709 bytes --]

  parent reply	other threads:[~2024-05-22 12:27 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         ` [Bloat] [EXTERNAL] " Livingood, Jason
2024-05-22 12:27       ` Livingood, Jason [this message]
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=1B7AD485-9CEA-4F79-B6F0-F2C1B0A9355D@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