Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: David Lang <david@lang.hm>
To: "David Fernández" <davidfdzp@gmail.com>
Cc: starlink@lists.bufferbloat.net
Subject: Re: [Starlink] fiber IXPs in space
Date: Mon, 17 Apr 2023 12:09:42 -0700 (PDT)	[thread overview]
Message-ID: <1n21p043-oqps-r637-p502-p51op49pqoss@ynat.uz> (raw)
In-Reply-To: <CAC=tZ0r++FTvJ2Q_vOgdwrs0sCLj4bTvJQ1rWLVm71KytDKmzQ@mail.gmail.com>

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

if Starlink can route via in-space-lasers and in a dishy-to-dishy way (both have 
been talked about, at least in future tenses) then they could also route to an 
on-satellite IP.

historically 'bent pipe' satellite support meant that the satellite just 
repeated the RF signal back down with no modifications. Starlink was designed to 
do routing of traffic, some to a ground station (possibly more than one), some 
to other satellites (including ones at different altitudes), and some to other 
dishys. It's initial deployment included no routing, just relaying between a 
dishy and a ground station, but we know that it's extended beyond that, at least 
when there are not ground stations in range

David Lang

On Mon, 17 Apr 2023, David Fernández via Starlink wrote:

> Well, I have some concerns about how you implement an anycast address
> in a transparent satellite.
>
> If the pre-requisite for this is that the satellite is a router, I
> don't see this happening anytime soon. I am not aware of any system,
> not deployed, even designed with satellites being routers, but IRIS2
> could be the first, maybe:
> https://defence-industry-space.ec.europa.eu/eu-space-policy/eu-space-programme/iriss_en
>
> Bufferbloat will be checked and prevented as much as possible in IRIS2.
>
> Regards,
>
> David
>
> 2023-04-17 16:38 GMT+02:00, Rodney W. Grimes <starlink@gndrsh.dnsmgr.net>:
>>> On Sun, 16 Apr 2023, David Fern?ndez via Starlink wrote:
>>>
>>> > The idea would be that the satellite inspects IP packets and when it
>>> > detects a DNS query, instead of forwarding the packet to ground
>>> > station, it just answers back to the sender of the query.
>>>
>>> This would be a bad way to implement it. You don't want to override
>>> queries to
>>> other DNS servers, but it would be very easy to create an anycast address
>>> that
>>> is served by the satellites.
>>
>> Yes, and the later is what I proposed, the idea of intercepting
>> someone ELSE'S anycast address and processing it would be
>> wrong in many ways, in effect a Man In the Middle attack
>> as stated else where.
>>
>>> David Lang
>> --
>> Rod Grimes
>> rgrimes@freebsd.org
>>
> _______________________________________________
> Starlink mailing list
> Starlink@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/starlink

  reply	other threads:[~2023-04-17 19:09 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-16 17:54 David Fernández
2023-04-16 21:22 ` Ulrich Speidel
2023-04-16 22:03   ` David Lang
2023-04-16 22:42     ` Ulrich Speidel
2023-04-16 23:22       ` David Lang
2023-04-17  0:51         ` Ulrich Speidel
2023-04-17  1:04           ` David Lang
2023-04-17  2:08             ` Ulrich Speidel
2023-04-17  2:34               ` David Lang
2023-04-17  3:21                 ` Ulrich Speidel
2023-04-17  5:01                   ` David Lang
2023-04-17  5:50                     ` Sebastian Moeller
2023-04-16 21:58 ` David Lang
2023-04-17 14:38   ` Rodney W. Grimes
2023-04-17 14:47     ` David Fernández
2023-04-17 19:09       ` David Lang [this message]
2023-04-17 20:09         ` Ulrich Speidel
2023-04-17 20:37           ` David Lang
2023-04-17 19:00     ` David Lang
2023-04-18  7:46       ` David Fernández
2023-04-18  8:34         ` Sebastian Moeller
2023-04-18 13:30           ` David Fernández
2023-04-18 17:55             ` David Lang
2023-04-18  5:59 ` Chris J. Ruschmann
2023-04-18 13:01   ` David Fernández
  -- strict thread matches above, loose matches on Subject: below --
2023-04-13 16:34 David Fernández
2023-04-13 17:22 ` Michael Richardson
2023-04-13 18:54   ` David Fernández
2023-04-13 20:01     ` Michael Richardson
2023-04-13 20:06       ` Tom Evslin
2023-04-13 15:57 Dave Taht
2023-04-14 14:47 ` Rodney W. Grimes
2023-04-14 19:36   ` David Lang
2023-04-14 19:50     ` Dave Taht
2023-04-15 23:56       ` Rodney W. Grimes
2023-04-16  7:03         ` Ulrich Speidel
2023-04-16 13:01           ` tom
2023-04-16 13:48             ` Ulrich Speidel

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=1n21p043-oqps-r637-p502-p51op49pqoss@ynat.uz \
    --to=david@lang.hm \
    --cc=davidfdzp@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