Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: "David P. Reed" <dpreed@deepplum.com>, starlink@lists.bufferbloat.net
Subject: Re: [Starlink] Starlink deplyment in Ukraine
Date: Sat, 05 Mar 2022 22:01:28 -0500	[thread overview]
Message-ID: <9915.1646535688@localhost> (raw)
In-Reply-To: <1646527180.51036626@apps.rackspace.com>

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


David P. Reed <dpreed@deepplum.com> wrote:
    > 1. I'm really curious how well Starlink's bent-pipe architecture
    > actually works in a context like Ukraine where fiber and copper
    > infrastructure are vulnerable and less redundant than in a place like
    > the UK. I'm not so worried about the dishy's working or being
    > targeted. They can be moved and disguised. What is not being discussed
    > here (or anywhere) is where the ground stations that the traffic must
    > *all* traverse are, and the fact that they are Single Points of
    > Failure, and must be nailed down in places which are close enough to
    > the dishy they serve, and also fiber-backhauled into the Internet. This
    > is a serious technical issue that interests me, mostly because Starlink
    > doesn't publish its technical specs.

Given the discussion abotu Tonga, I wondered this as well.

Could one have grond stations that just acted as relays... more bent pipes
essentially on the ground.  Some kind of super-dual-dishy.
As I write this, the snake version of the NASA comes to mind as a shape :-)

    > Now Poland and Moldova are potential sites that might cover part of
    > Ukraine, but certainly not that far into the country.

Agreed.
This is where the laser stuff would actually be super valuable.

(Former co-chair of IETF ROLL WG.  I think RFC6550 might do well in space,
but I suspect an SDN approach using a PCE would be better)

--
Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 IøT consulting )
           Sandelman Software Works Inc, Ottawa and Worldwide





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

  parent reply	other threads:[~2022-03-06  3:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.1959.1646493913.1267.starlink@lists.bufferbloat.net>
2022-03-06  0:39 ` David P. Reed
2022-03-06  1:02   ` David Lang
2022-03-06  5:58     ` Larry Press
     [not found]     ` <BYAPR03MB38636126A57966F48EFA05BEC2079@BYAPR03MB3863.namprd03.prod.outloo k.com>
     [not found]       ` <BYAPR03MB38636126A57966F48EFA05BEC2079@BYAPR03MB3863.namprd03.prod.outlook. com>
2022-03-06 21:10         ` David P. Reed
2022-03-06 21:17           ` David Lang
2022-03-07 17:34           ` Ben Greear
2022-03-07 17:49             ` Sebastian Moeller
2022-03-06  3:01   ` Michael Richardson [this message]
2022-03-08  6:01   ` Inemesit Affia

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=9915.1646535688@localhost \
    --to=mcr+ietf@sandelman.ca \
    --cc=dpreed@deepplum.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