From: "Rodney W. Grimes" <starlink@gndrsh.dnsmgr.net>
To: Dave Taht <dave.taht@gmail.com>
Cc: Dave Taht via Starlink <starlink@lists.bufferbloat.net>
Subject: Re: [Starlink] fiber IXPs in space
Date: Fri, 14 Apr 2023 07:47:42 -0700 (PDT) [thread overview]
Message-ID: <202304141447.33EElgvA043555@gndrsh.dnsmgr.net> (raw)
In-Reply-To: <CAA93jw6ES-b_9h0K+wZJ64fB+1T2T8or+WNi9kXjp8w0c248Aw@mail.gmail.com>
> "The Kepler Network will streamline on-orbit communications with a
> network infrastructure designed to act as Internet exchange points
> (IXP) for space-to-space data relay. The Internet-ready constellation
> will deliver data to and from spacecraft in real time, enabling
> high-speed data relay through SDA-standard optical terminals."
>
> https://kepler.space/2023/04/13/kepler-raises-92-million-usd-series-c-to-complete-internet-ready-optical-constellation/
>
> I keep wondering when or if Nasa will find a way to move their DNS
> root server "up there" . DNS data is not all that much... it is the
> original distributed database...
As others have pointed out a "root server" may not be very advantages,
but what I think would be far better is to put up a couple of anycast
recursive caching resolvers, aka 8.8.8.8/8.8.4.4 and almost anyone
can do that, including starlink itself.
--
Rod Grimes rgrimes@freebsd.org
next prev parent reply other threads:[~2023-04-14 14:47 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-13 15:57 Dave Taht
2023-04-14 14:47 ` Rodney W. Grimes [this message]
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
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-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
2023-04-18 13:01 ` 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=202304141447.33EElgvA043555@gndrsh.dnsmgr.net \
--to=starlink@gndrsh.dnsmgr.net \
--cc=dave.taht@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