Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: Kenneth Porter <shiva@sewingwitch.com>
To: Starlink mailing list <starlink@lists.bufferbloat.net>
Subject: [Starlink] A transport protocol’s view of Starlink (APNIC blog article from May 2024)
Date: Sat, 7 Dec 2024 23:14:13 -0800	[thread overview]
Message-ID: <628c4862-d0e1-4423-81b5-b940da350bdd@sewingwitch.com> (raw)

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


  A transport protocol’s view of Starlink

By Geoff Huston <https://blog.apnic.net/author/geoff-huston/> on 17 May 
2024

https://blog.apnic.net/2024/05/17/a-transport-protocols-view-of-starlink/

> Digital communications systems always represent a collection of design 
> tradeoffs. Maximizing one characteristic of a system may impair 
> others, and various communications services may choose to optimize 
> different performance parameters based on the intersection of these 
> design decisions with the physical characteristics of the 
> communications medium.
>
> In this article, I’ll look at how TCP, the workhorse transport 
> protocol of the Internet, interacts with the characteristics of the 
> Starlink service <https://www.starlink.com/>.
>
Nice analysis of the satellite handoff's effects on Reno, CUBIC, and 
BBR. Lots of graphs.

[Apologies if this was already discussed here. I checked the May 
archives and didn't see the link or author's name.]


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

                 reply	other threads:[~2024-12-08  7:17 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=628c4862-d0e1-4423-81b5-b940da350bdd@sewingwitch.com \
    --to=shiva@sewingwitch.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