From: Jonathan Morton <chromatix99@gmail.com>
To: Sebastian Moeller <moeller0@gmx.de>
Cc: ECN-Sane <ecn-sane@lists.bufferbloat.net>,
Cake List <cake@lists.bufferbloat.net>,
Jonathan Morton via Bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] [Cake] Anybody has contacts at Dropbox?
Date: Sun, 25 Jun 2023 02:04:00 +0300 [thread overview]
Message-ID: <46B3DF93-48F1-429C-B9E0-41683CBBE1E8@gmail.com> (raw)
In-Reply-To: <24D1A566-DFE9-4FDF-86A2-CFB30F20FCB2@gmx.de>
> On 25 Jun, 2023, at 12:00 am, Sebastian Moeller via Cake <cake@lists.bufferbloat.net> wrote:
>
> Is dropbox silently already using an L4S-style CC for their TCP?
It should be possible to distinguish this by looking at the three-way handshake at the start of the connection. This will show a different set of TCP flags and ECN field values depending on whether RFC-3168 or AccECN is being attempted. Without AccECN, you won't have functioning L4S on a TCP stream.
But I think it is more likely that it's a misapplied DSCP.
- Jonathan Morton
next prev parent reply other threads:[~2023-06-24 23:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-24 21:00 [Bloat] " Sebastian Moeller
2023-06-24 23:04 ` Jonathan Morton [this message]
2023-06-25 8:43 ` [Bloat] [Cake] " 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=46B3DF93-48F1-429C-B9E0-41683CBBE1E8@gmail.com \
--to=chromatix99@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=cake@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