From: Jim Forster <jim@connectivitycap.com>
To: starlink@lists.bufferbloat.net
Subject: Re: [Starlink] Geoff Huston on StarLink TCP Performance
Date: Sat, 11 May 2024 11:10:53 -0700 [thread overview]
Message-ID: <7A7D0225-FE7D-4FE8-943A-F3DFCE6952E1@connectivitycap.com> (raw)
In-Reply-To: <AC4ADEA5-A083-4AE6-A188-5A6A6F2D1A8F@connectivitycap.com>
[-- Attachment #1: Type: text/plain, Size: 200 bytes --]
Quite Interesting! Geoff notes the effects of StarLink’s delay variations on TCP variants..
https://podcasts.apple.com/us/podcast/ping/id1591549361?i=1000654196603
— Jim
[-- Attachment #2: Type: text/html, Size: 3451 bytes --]
prev parent reply other threads:[~2024-05-11 18:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-09 20:26 Jim Forster
2024-05-11 18:10 ` Jim Forster [this message]
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/starlink.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7A7D0225-FE7D-4FE8-943A-F3DFCE6952E1@connectivitycap.com \
--to=jim@connectivitycap.com \
--cc=starlink@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