Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: Ulrich Speidel <ulrich@cs.auckland.ac.nz>
To: Nathan Owens <nathan@nathan.io>
Cc: starlink@lists.bufferbloat.net
Subject: Re: [Starlink] Starlink tidbits from NANOG
Date: Sat, 6 Nov 2021 11:12:49 +1300	[thread overview]
Message-ID: <53decc41-74ee-1785-6d1a-4bbf9e71f050@cs.auckland.ac.nz> (raw)
In-Reply-To: <CALjsLJu8YiC0sKRX6VjOyoiHd4URDRLd_P6OW4nvtX5vBjuGmA@mail.gmail.com>

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

On 5/11/2021 2:05 pm, Nathan Owens wrote:
> > They are using waves back to regional DCs now, but will be moving to
> > dark fiber over the next year or two
> If that means "radio" waves, then this goes a long way to explaining why
> there's already limited capacity even near the US-Canada border.
>
> Waves in this case generally refers to 10G/100G leased optical circuit 
> capacity.
>
Thanks for clearing this up, that makes sense now!

Now I note that a single Starlink ground station is generally within 
sight of and set up to handle multiple satellite links (all known images 
show 6 or more radomes). As each bird has ~20 Gb/s capacity, I guess 
we'll probably be talking 100G circuits here (where they can get them). 
And the move to dark fibre is a logical step then.

-- 

****************************************************************
Dr. Ulrich Speidel

School of Computer Science

Room 303S.594 (City Campus)
Ph: (+64-9)-373-7599 ext. 85282

The University of Auckland
ulrich@cs.auckland.ac.nz  
http://www.cs.auckland.ac.nz/~ulrich/
****************************************************************



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

  parent reply	other threads:[~2021-11-05 22:13 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-04 15:26 Darrell Budic
2021-11-04 16:21 ` Dave Taht
2021-11-04 16:46 ` Dave Taht
2021-11-04 17:11   ` Dave Taht
2021-11-05  1:30     ` Darrell Budic
2021-11-05  1:41   ` Darrell Budic
2021-11-05  1:46   ` Darrell Budic
2021-11-04 18:16 ` Michael Richardson
2021-11-04 18:25   ` Inemesit Affia
2021-11-04 18:29   ` Dave Taht
2021-11-04 19:10     ` Michael Richardson
2021-11-05  0:34 ` Ulrich Speidel
2021-11-05  1:05   ` Nathan Owens
2021-11-05  1:18     ` Darrell Budic
2021-11-05 22:24       ` Ulrich Speidel
2021-11-05 15:00     ` [Starlink] data sovereignty Michael Richardson
2021-11-05 15:07       ` Spencer Sevilla
2021-11-05 17:36       ` Daniel AJ Sokolov
2021-11-05 18:01       ` Daniel AJ Sokolov
2021-11-05 22:12     ` Ulrich Speidel [this message]
2021-11-05  1:27   ` [Starlink] Starlink tidbits from NANOG Darrell Budic
2021-11-05 15:03     ` Michael Richardson

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=53decc41-74ee-1785-6d1a-4bbf9e71f050@cs.auckland.ac.nz \
    --to=ulrich@cs.auckland.ac.nz \
    --cc=nathan@nathan.io \
    --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