Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: Michael Richardson <mcr@sandelman.ca>
To: Starlink <Starlink@lists.bufferbloat.net>
Subject: Re: [Starlink] starlink IXP peering progress
Date: Tue, 27 Feb 2024 13:43:59 -0500	[thread overview]
Message-ID: <31252.1709059439@obiwan.sandelman.ca> (raw)
In-Reply-To: <CAA93jw6Tc26-6Gz7ukp16yxb3z92VzO9KEj6gGFjNjSCRzErmA@mail.gmail.com>

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


Dave Taht via Starlink <starlink@lists.bufferbloat.net> wrote:
    > One of the things I learned today was that starlink has published an
    > extensive guide as to how existing BGP AS holders can peer with them to
    > get better service. I am curious if there is a way to see how many have
    > peered already, how many they could actually peer with?, and progress
    > over time since inception.... is there a tool for that?

    > https://starlink-enterprise-guide.readme.io/docs/peering-with-starlink

    > This is increasingingly off topic and too technical for the nnagain
    > mailing list (aside from documenting its impact and importance for
    > network resilience), is there a better email list to discuss ixp stuff?

    > (I will send a copy of this separately to nanog)

As others have said, this is about peering with Starlink's wired/gateway side.
We certainly need this, a lot of this, but I'm skeptical that many smaller or
even middle sized communities are going to see Starlink at their local IXP.

Without the space lasers, my understanding is that the downlink stations need
to be within about 800km of the users.  While that's a lot of space over
urbanized places (and covers most of "Southern" Ontario where the people
live), it's really peanuts once you get up-north.  We need those downstations
to form hubs of new IXPs.

But, this will not help with what many of us would like to see: satellite as a key
part of a multi-link service to smaller and more remote communities.  It
might include short runs of fiber or terrestial microwave to nearby
communitiies.  The goal is for each area to be resillient to events
elsewhere.
That requires being able to use Starlink to form L2 tunnels from communities
to the nearer IXPs.

--
]               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-02-27 18:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-26 20:31 [Starlink] A Multifaceted Look at Starlink Performance the keyboard of geoff goodfellow
2024-02-27  7:51 ` [Starlink] starlink IXP peering progress Dave Taht
2024-02-27  8:02   ` [Starlink] [NNagain] " Fearghas Mckay
2024-02-27 18:43   ` Michael Richardson [this message]
2024-02-27 18:43 ` [Starlink] [NNagain] A Multifaceted Look at Starlink Performance rjmcmahon
     [not found] <CAA93jw5C-enhS1G4MZZ-js9RG5VQLmjEHg_r6uouQemuD8rP-A@mail.gmail.com>
2024-02-27 21:50 ` [Starlink] starlink ixp peering progress Bill Woodcock

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=31252.1709059439@obiwan.sandelman.ca \
    --to=mcr@sandelman.ca \
    --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