From: Jonathan Morton <chromatix99@gmail.com>
To: Sebastian Moeller <moeller0@gmx.de>
Cc: bloat <bloat@lists.bufferbloat.net>,
ECN-Sane <ecn-sane@lists.bufferbloat.net>
Subject: Re: [Bloat] [Ecn-sane] The curious case of "cursed-ECN" steam downloads
Date: Mon, 4 Sep 2023 01:36:03 +0300 [thread overview]
Message-ID: <49DF744B-E60F-47CA-AF57-F2C5D42B9244@gmail.com> (raw)
In-Reply-To: <758B6681-14B5-473E-9706-45B7E2927505@gmx.de>
> On 3 Sep, 2023, at 9:54 pm, Sebastian Moeller via Ecn-sane <ecn-sane@lists.bufferbloat.net> wrote:
>
> B) Excessive ECT(1) marking (this happened with a multi-GB download)
This *could* be a badly configured middlebox attempting to apply a DSCP, but clobbering the entire TOS byte instead of the (left justified) DSCP field. Apparently Comcast just found a whole raft of these in their own network as part of rolling out L4S support. Funny how they didn't notice them previously.
- Jonathan Morton
next prev parent reply other threads:[~2023-09-03 22:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-03 18:54 [Bloat] " Sebastian Moeller
2023-09-03 22:36 ` Jonathan Morton [this message]
2023-09-04 7:14 ` [Bloat] [Ecn-sane] " 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=49DF744B-E60F-47CA-AF57-F2C5D42B9244@gmail.com \
--to=chromatix99@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=ecn-sane@lists.bufferbloat.net \
--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