Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: Michael Richardson <mcr@sandelman.ca>
To: David Lang <david@lang.hm>, starlink@lists.bufferbloat.net
Subject: Re: [Starlink] APNIC56 last week
Date: Fri, 22 Sep 2023 14:52:04 -0400	[thread overview]
Message-ID: <25396.1695408724@localhost> (raw)
In-Reply-To: <o55p41n6-10n0-70p9-8880-nr55q4rp72sn@ynat.uz>

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


David Lang <david@lang.hm> wrote:
    > We don't know what their routing in space is. But we know that it isn't just
    > up to a single satellite and back down to a ground station.

If the "routing" was all based upon a connecting a circuit from a dishy
to a ground station, and they never look into the packets, then it sounds
like bent pipe to me.  Even though the specific physical path would change
every ~15 minutes.
One could do this with a variety of technologies, but I'd probably use MPLS.

OTH, if a dishy could be moved from one ground station to another, then
that's a different matter.

    > But I will say that since they NAT the connection at the ground station (or
    > Internet peering point), and not allowing dishy-to-dishy direct

I don't think that the l3 NAT44 is particularly relevant in this case.
One could easily allow for dishy-to-dishy "behind" the NAT, but it requires
an L3 decision point before the NAT44/Internet-Peering-Point.

I thought that there was many with working IPv6?
(but not all)




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

  reply	other threads:[~2023-09-22 18:52 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-19  4:39 Ulrich Speidel
2023-09-20  1:13 ` Dave Taht
2023-09-23  1:33   ` Noel Butler
2023-09-23  1:47     ` Vint Cerf
2023-09-23  4:22       ` Noel Butler
2023-09-23  6:41         ` Gert Doering
2023-09-23 10:53         ` Ulrich Speidel
2023-09-23 11:28           ` Sebastian Moeller
2023-09-23 12:56             ` Ulrich Speidel
2023-09-25  4:40           ` Noel Butler
2023-09-25  5:00             ` Ulrich Speidel
2023-09-25  5:10               ` Hayden Simon
2023-09-25  5:51               ` Noel Butler
2023-09-23 12:08     ` Hesham ElBakoury
2023-09-24 18:30     ` Michael Richardson
2023-09-25  4:04       ` Noel Butler
2023-09-21 13:20 ` Alexandre Petrescu
2023-09-21 19:05   ` Inemesit Affia
2023-09-21 19:08     ` Dave Taht
2023-09-22  8:26     ` Alexandre Petrescu
2023-09-22  8:41       ` David Lang
2023-09-22 17:12         ` Michael Richardson
2023-09-22 17:26           ` David Lang
2023-09-22 18:52             ` Michael Richardson [this message]
2023-09-23 21:55         ` Larry Press
2023-09-24  2:46           ` Dave Taht
2023-09-24 12:00           ` Hesham ElBakoury
2023-09-25  7:46             ` Alexandre Petrescu
2023-09-25  8:59               ` David Lang
2023-09-25 12:30                 ` Frantisek Borsik
2023-09-22 17:00 David Fernández

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=25396.1695408724@localhost \
    --to=mcr@sandelman.ca \
    --cc=david@lang.hm \
    --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