From: Kenneth Porter <shiva@sewingwitch.com>
To: bloat <bloat@lists.bufferbloat.net>
Subject: [Bloat] The Register; How TCP's congestion control saved the internet
Date: Mon, 25 Sep 2023 13:32:38 -0700 [thread overview]
Message-ID: <14070C4F89255E13B9D93B81@[10.96.7.39]> (raw)
<https://www.theregister.com/2023/09/24/tcp_congestion_control_internet/>
next reply other threads:[~2023-09-25 20:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-25 20:32 Kenneth Porter [this message]
[not found] <14070C4F89255E13B9D93B81@10.96.7.39>
2023-09-25 21:18 ` [Bloat] The Register; How TCP's congestion control saved the internet Dave Taht
2023-09-25 23:34 ` Dave Taht
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='14070C4F89255E13B9D93B81@[10.96.7.39]' \
--to=shiva@sewingwitch.com \
--cc=bloat@lists.bufferbloat.net \
/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