From: "Chris J. Ruschmann" <chris@scsalaska.net>
To: "David Fernández" <davidfdzp@gmail.com>,
"starlink@lists.bufferbloat.net" <starlink@lists.bufferbloat.net>
Subject: Re: [Starlink] fiber IXPs in space
Date: Tue, 18 Apr 2023 05:59:45 +0000 [thread overview]
Message-ID: <CO6PR11MB5617F896F98C688F17BB254CBE9D9@CO6PR11MB5617.namprd11.prod.outlook.com> (raw)
In-Reply-To: <CAC=tZ0qrB4Eqj-7nwXirB-2x0oya0Kmgfi1_8QptmOP904D=nQ@mail.gmail.com>
What makes you think each Starlink satellite doesn't have a router on board? Just Curious...
I think they are more complex than most people or you think.
-----Original Message-----
From: Starlink <starlink-bounces@lists.bufferbloat.net> On Behalf Of David Fernández via Starlink
Sent: Sunday, April 16, 2023 9:54 AM
To: starlink@lists.bufferbloat.net
Subject: Re: [Starlink] fiber IXPs in space
CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.
In case you put a DNS server in the satellite, so that it replies instead of a DNS server on ground, the RTT is reduced by half.
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.
Nowadays, satellites (starlink included) are still transparent and are signal repeaters, not routers processing IP packets, so doing this is not immediate at all, but it could bring some benefits.
CDNs or even datacenters (Cloud) in GEO or LEO is even more complex.
Regards,
David
_______________________________________________
Starlink mailing list
Starlink@lists.bufferbloat.net
https://lists.bufferbloat.net/listinfo/starlink
next prev parent reply other threads:[~2023-04-18 5:59 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
2023-04-18 13:30 ` David Fernández
2023-04-18 17:55 ` David Lang
2023-04-18 5:59 ` Chris J. Ruschmann [this message]
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=CO6PR11MB5617F896F98C688F17BB254CBE9D9@CO6PR11MB5617.namprd11.prod.outlook.com \
--to=chris@scsalaska.net \
--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