Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: Michael Richardson <mcr@sandelman.ca>
To: J Pan <Pan@uvic.ca>,
	Frantisek Borsik <frantisek.borsik@gmail.com>,
	Dave Taht via Starlink <starlink@lists.bufferbloat.net>
Subject: [Starlink] Re: Lost in Space: The Limits of Geolocation in a Satellite-Connected World (new article from Geoff Huston)
Date: Wed, 01 Oct 2025 12:46:30 -0400	[thread overview]
Message-ID: <23116.1759337190@obiwan.sandelman.ca> (raw)
In-Reply-To: <CAHn=e4h-_1scJAvbqr3zChH+nHQkWf_PGmCkb=eiAtCMth7JLQ@mail.gmail.com>

Dr. Pan, I am still confused by the presences/need of the CGNAT layer in
Starlink, vs your slides saying that it's "one big IPv4 hop"

Is that the IPv4 100.x on the outside of the customer's access point?
Are they unique within Starlink, or unique to each Landing Station?
Gosh, I wish they had just done one of the v4-over-v6 mechanisms.

--
]               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    [


  reply	other threads:[~2025-10-01 16:46 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-01  5:34 [Starlink] " Frantisek Borsik
2025-10-01  5:56 ` [Starlink] " J Pan
2025-10-01 16:46   ` Michael Richardson [this message]
2025-10-01 17:40     ` J Pan
2025-10-01 21:08       ` Michael Richardson
2025-10-01 22:50         ` J Pan
2025-10-01 13:18 ` Livingood, Jason
2025-10-01 21:22   ` David Lang
2025-10-01 21:51     ` Spencer Sevilla
2025-10-01 22:48       ` J Pan
2025-10-01 23:05       ` David Lang
2025-10-02  4:34         ` J Pan
     [not found] ` <22339.1759337017@obiwan.sandelman.ca>
2025-10-01 16:47   ` Michael Richardson
2025-10-01 21:13 ` 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=23116.1759337190@obiwan.sandelman.ca \
    --to=mcr@sandelman.ca \
    --cc=Pan@uvic.ca \
    --cc=frantisek.borsik@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