From: David Lang <david@lang.hm>
To: "David Fernández" <davidfdzp@gmail.com>
Cc: starlink <starlink@lists.bufferbloat.net>
Subject: Re: [Starlink] IXPs in space
Date: Mon, 17 Apr 2023 11:55:46 -0700 (PDT) [thread overview]
Message-ID: <r779145s-n648-6o78-0q00-35o9pr0q365r@ynat.uz> (raw)
In-Reply-To: <CAC=tZ0q2gr-hV81Z=MFW9jd5qkiLoQLtomSyLtm1i9rM-8hPTw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2613 bytes --]
nobody else has had enough satellites in space to do real in space routing, so
take anything you read about it that's not specifically referring to starlink
as guesses/suggestions.
David Lang
On Mon, 17 Apr 2023, David Fernández via Starlink wrote:
> Date: Mon, 17 Apr 2023 16:22:33 +0200
> From: David Fernández via Starlink <starlink@lists.bufferbloat.net>
> Reply-To: David Fernández <davidfdzp@gmail.com>
> To: starlink <starlink@lists.bufferbloat.net>
> Subject: Re: [Starlink] IXPs in space
>
> Apologies in advance for any *profound* misunderstanding that could
> trigger any nerves, although I am grateful for all the info being
> shared. I will read this carefully:
> https://web.mit.edu/Saltzer/www/publications/endtoend/endtoend.pdf
>
> In the abstract, I read, at the end: "Low level mechanisms to support
> these functions are justified only as performance enhancements." So,
> every rule has its exceptions, like the PEPs for TCP performance
> acceleration.
>
> "Adding those anycast addresses to the satellites would be transparent
> to all users (assuming the satellites are operating at the IP layer,
> the old bent-pipe approach did not, but once you have routing in space
> via the laser links...)" Satellites being routers just because they
> have ISL does not follow. Is there any satellite nowadays doing
> routing in space? They do switching only (and not Ethernet switching).
> Because of this I proposed the idea of the so called L2 snooping. It
> is a hack, somehow similar to the PEPs to accelerate TCP, but in this
> case to accelerate DNS (not encrypted), without making satellites
> routers, keeping them transparent as they are now.
>
> If it has not been done before by anybody is for a good reason, maybe.
> Things like this did not have so much success, it seems:
> https://en.wikipedia.org/wiki/Internet_Routing_in_Space
>
> "DNS is an easy thing to start with compared to most others." Even in
> this case you are going to find a lot of issues to do it with
> transparent satellites, even with GEO satellites, where the gain could
> be bigger and things simpler than with fast moving LEO satellites.
>
> "bent pipe for normal operations doesn't mean that you can't watch for
> an anycast address to serve locally." This is what I was suggesting,
> you sniff packets in the satellite uplink and answer anycast DNS
> queries directly from satellite, if you see any, cutting RTT by a
> half.
>
> Regards,
>
> David
> _______________________________________________
> Starlink mailing list
> Starlink@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/starlink
next prev parent reply other threads:[~2023-04-17 18:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-17 14:22 David Fernández
2023-04-17 18:55 ` David Lang [this message]
[not found] <mailman.711.1681684935.1222.starlink@lists.bufferbloat.net>
2023-04-17 0:27 ` David P. Reed
2023-04-17 0:40 ` Hesham ElBakoury
2023-04-17 1:06 ` David Lang
2023-04-17 1:57 ` Ulrich Speidel
2023-04-17 2:03 ` Edwin Liava'a
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=r779145s-n648-6o78-0q00-35o9pr0q365r@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