Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: Sebastian Moeller <moeller0@gmx.de>
To: "David Fernández" <davidfdzp@gmail.com>,
	"David Fernández via Starlink" <starlink@lists.bufferbloat.net>
Subject: Re: [Starlink] fiber IXPs in space
Date: Tue, 18 Apr 2023 10:34:18 +0200	[thread overview]
Message-ID: <E54FADDE-616E-4756-A5C4-A0892314B020@gmx.de> (raw)
In-Reply-To: <CAC=tZ0qyT_OkwdAmZUCAgeq+cEiMWdXFz0NX6+96L1-aWhjShw@mail.gmail.com>

Hi David,


> On Apr 18, 2023, at 09:46, David Fernández via Starlink <starlink@lists.bufferbloat.net> wrote:
> 
> PEPs have been mentioned as an example of so called stealth optimization.
> 
> Another example, I think it is IGMP snooping:
> https://en.wikipedia.org/wiki/IGMP_snooping

	I think this is different from "PEPs" (I really dislike the marketing naming... IGMP snooping arguably deals to deal with the fact that IGMP has a different idea of unicast/multicast scoping than is optimal for switched L2 network domains... it is also as far as I can tell opt-in in that one needs to activate it in once's L2.5 devices first. I am not sure whether norrmal geo-stationary internet users can opt-out of the TCP shenanigans played by PEPs?

> So, well, maybe this so called DNS stealth optimization is not so bad,
> if it really is easy to implement and it brings benefits (RTT by
> half), but pros and cons should be carefully evaluated.

	I heartily disagree, stealth DNS "optimization" is not something an ISP should be caught doing behind their users backs. I remember when my former ISPs insisted upon capturing DNS queries to non-existent domains to an advertisement page of their own, I was neither impressed nor happy (even though they did offer an opt-out).
Now, if a hypothetical starlink offer would do that DNS snooping only for DNS queries directed against starlink's own DNS server IP addresses that would be palatable from a who handles the query perspective (starlink in both cases), but from a layering violation perspective this still seems rather vile. If the want to offer DNS forwarders in space, they should simply do so overtly and not high-jack packets directed to a different server.

At least that is my subjective take on this issue.
Regards
	Sebastian

> 
> Regards,
> 
> David
> 
> 2023-04-17 21:00 GMT+02:00, David Lang <david@lang.hm>:
>> On Mon, 17 Apr 2023, Rodney W. Grimes wrote:
>> 
>>>> 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.
>> 
>> I was assuming that it would be done in coordination with the existing user,
>> not
>> as a stealth optimization. I should have made that clear.
>> 
>> David Lang
>> 
> _______________________________________________
> Starlink mailing list
> Starlink@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/starlink


  reply	other threads:[~2023-04-18  8:34 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
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 [this message]
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=E54FADDE-616E-4756-A5C4-A0892314B020@gmx.de \
    --to=moeller0@gmx.de \
    --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