Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: Michael Richardson <mcr@sandelman.ca>
To: Dave Taht <dave.taht@gmail.com>,
	Dave Taht via Starlink <starlink@lists.bufferbloat.net>
Subject: Re: [Starlink] Starship's 4th flight test was magnificent
Date: Sun, 09 Jun 2024 22:22:29 -0400	[thread overview]
Message-ID: <10447.1717986149@obiwan.sandelman.ca> (raw)
In-Reply-To: <CAA93jw6A4TNBL5zBFsrJwi3AOjbjun2B98fjyAc3NY0BJsLUPA@mail.gmail.com>

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


Dave Taht via Starlink <starlink@lists.bufferbloat.net> wrote:
    > When they kicked into the Blue Danube, during Starship's coast phase, I
    > started dancing around the boat. The landing phase was a real
    > nailbiter, but seeing starlink maintain connectivity through nearly it
    > all of that plasma was amazing, too. To be massively cheered up about

Silly legal/technical question:

When starship is in a suborbital, ~140km apogee (coast phase) over Atlantic
Ocean or Africa, whose jurisdiction are the power limits set by?

If at 140km altitude, that's 20% to 30% closer to the satellites than on
land.  OTH, it's moving really fast, and does the hand-off really work?
Are they just using TCP (or maybe QUIC) for data, or something else?

Also, during the entire Tonga situation, Ulrich provided lots of really good
explanation of how hard it was to do a downlink.  That was before the space
lasers.  I would guess that this data link required inter-satellite lasers,
since downlink over oceans (and probably Africa) would be difficult.

    > Lastly, I couldn't help but imagine small repair robots deploying once
    > in orbit to get a full view of every tile on starship, and perhaps
    > effect repairs. Call 'em Hewey, Duey and Louie....

Naw. R2-xx are Astro *MECHS*. https://www.youtube.com/watch?v=gfMoXBOjWBM

--
]               Never tell me the odds!                 | ipv6 mesh networks [
]   Michael Richardson, Sandelman Software Works        |    IoT architect   [
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 511 bytes --]

  parent reply	other threads:[~2024-06-10  2:22 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-09 23:50 Dave Taht
2024-06-10  0:15 ` Ulrich Speidel
2024-06-10  2:22 ` Michael Richardson [this message]
2024-06-10 10:51   ` Ulrich Speidel
2024-06-10 12:04     ` David Lang
2024-06-10 12:15       ` Ulrich Speidel
2024-06-10  2:38 ` David Lang
2024-06-10 11:04   ` Ulrich Speidel
2024-06-10 12:06     ` David Lang
2024-06-10 12:21       ` Ulrich Speidel
2024-06-10  8:57 ` Alexandre Petrescu
2024-06-10  9:49   ` David Lang
2024-06-10 13:22     ` Alexandre Petrescu
2024-06-10 13:37       ` David Lang

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=10447.1717986149@obiwan.sandelman.ca \
    --to=mcr@sandelman.ca \
    --cc=dave.taht@gmail.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