Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: Sebastian Moeller <moeller0@gmx.de>
To: Gert Doering <gert@space.net>
Cc: David Lang <david@lang.hm>,
	David Lang via Starlink <starlink@lists.bufferbloat.net>,
	Ulrich Speidel <u.speidel@auckland.ac.nz>
Subject: Re: [Starlink] Jamaican Starlink Outages and a hint of shared infrastructure
Date: Tue, 25 Jun 2024 09:26:05 +0200	[thread overview]
Message-ID: <2BF2613D-BDB4-4309-A1DF-43544AF5CD4A@gmx.de> (raw)
In-Reply-To: <ZnppolZb159bQzlI@Space.Net>

Hi Gert,


> On 25. Jun 2024, at 08:54, Gert Doering <gert@space.net> wrote:
> 
> Hi,
> 
> On Tue, Jun 25, 2024 at 07:37:40AM +0200, Sebastian Moeller via Starlink wrote:
>> My understanding is routing mostly follows the path of least cost... and is more complex then BGP makes it look, if two ASs have multiple handover points one still needs to pick one for each flow... and even for a simple route between two AS the forward and reverse path might use different hand-over points... think hot-potato routing.
> 
> This is true, but BGP offers sufficient knobs to help in situations
> where the "naive" algorithms would fail to find the actual best path
> (for some definition of "best" - bandwidth, latency, monetary cost, ...).
> 
> It gets more problematic when money or politics get in the way of 
> "build good networks" - like, two major transit ISPs refusing to peer
> with each other, because both assert the other one should buy from
> them...  and customers of both suffer.

Indeed, however these customers are part of the problem in a sense, as if customers would simply drop these two like a hot potato for exactly that reason, I am sure these two might be willing to come together over a cake perhaps ( h++ps://eu-images.contentstack.com/v3/assets/blt8eb3cdfc1fce5194/blt87f5367a512efb22/664b33f657aac63927f84866/Hurricane-Cake.jpg?width=700&auto=webp&quality=80&disable=upscale )?




Sorry for fudging the URL, but my mail service helpfully marks outgoing posts with (too many?) URLs as spam and the list server will reject my posts...

> 
> Gert Doering
>        -- NetMaster
> -- 
> have you enabled IPv6 on something today...?
> 
> SpaceNet AG                      Vorstand: Sebastian v. Bomhard, Ingo Lalla,
>                                           Karin Schuler, Sebastian Cler
> Joseph-Dollinger-Bogen 14        Aufsichtsratsvors.: A. Grundner-Culemann
> D-80807 Muenchen                 HRB: 136055 (AG Muenchen)
> Tel: +49 (0)89/32356-444         USt-IdNr.: DE813185279


  reply	other threads:[~2024-06-25  7:26 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-19 17:31 [Starlink] I still dream of an tiny on-orbit repair and inspection robot Dave Taht
2024-06-19 18:44 ` Kenneth Porter
2024-06-24 10:39 ` [Starlink] Jamaican Starlink Outages and a hint of shared infrastructure Inemesit Affia
2024-06-24 14:42   ` J Pan
2024-06-24 22:19     ` Ulrich Speidel
2024-06-25  3:42       ` David Lang
2024-06-25  4:34         ` Ulrich Speidel
2024-06-25  5:37         ` Sebastian Moeller
2024-06-25  6:54           ` Gert Doering
2024-06-25  7:26             ` Sebastian Moeller [this message]
2024-06-25 19:07       ` J Pan

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=2BF2613D-BDB4-4309-A1DF-43544AF5CD4A@gmx.de \
    --to=moeller0@gmx.de \
    --cc=david@lang.hm \
    --cc=gert@space.net \
    --cc=starlink@lists.bufferbloat.net \
    --cc=u.speidel@auckland.ac.nz \
    /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