Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
* [Starlink] A transport protocol’s view of Starlink (APNIC blog article from May 2024)
@ 2024-12-08  7:14 Kenneth Porter
  0 siblings, 0 replies; only message in thread
From: Kenneth Porter @ 2024-12-08  7:14 UTC (permalink / raw)
  To: Starlink mailing list

[-- 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 --]

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2024-12-08  7:17 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2024-12-08  7:14 [Starlink] A transport protocol’s view of Starlink (APNIC blog article from May 2024) Kenneth Porter

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox