From: Michael Richardson <mcr@sandelman.ca>
To: =?UTF-8?Q?David_Fern=C3=A1ndez?= <davidfdzp@gmail.com>
Cc: starlink <starlink@lists.bufferbloat.net>
Subject: Re: [Starlink] fiber IXPs in space
Date: Thu, 13 Apr 2023 16:01:48 -0400 [thread overview]
Message-ID: <8151.1681416108@localhost> (raw)
In-Reply-To: <CAC=tZ0rE4pzoqUf53ptA1pvTHRdjsZYGX=GFS5XLCfdXje8mzw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 314 bytes --]
David Fernández via Starlink wrote:
> The delay up to GEO and back is slightly more than half a second.
exactly.
> I am not aware of any space situated systems making DNS queries, are
> there any, even proposed?
Someone has to move first before the other systems can think about it...
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 511 bytes --]
next prev parent reply other threads:[~2023-04-13 20:01 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2023-04-13 20:06 ` Tom Evslin
2023-04-19 23:34 ` [Starlink] DataCenters in Space (was Re: fiber IXPs in space) Michael Richardson
2023-04-20 1:12 ` tom
2023-04-20 1:16 ` Vint Cerf
[not found] ` <ZECsG+Ldro3V5+/4@faui48e.informatik.uni-erlangen.de>
2023-04-20 3:25 ` [Starlink] [E-impact] " Hesham ElBakoury
2023-04-20 5:43 ` Daniel Schien
2023-04-20 9:31 ` Chris Adams
2023-04-20 12:50 ` Hesham ElBakoury
2023-04-20 12:51 ` Hesham ElBakoury
2023-04-27 3:13 ` Eugene Y Chang
2023-04-20 11:10 ` Hesham ElBakoury
2023-04-20 11:23 ` Sebastian Moeller
2023-04-20 11:24 ` David Lang
2023-04-20 12:06 ` Dave Collier-Brown
2023-04-20 21:21 ` Ulrich Speidel
2023-04-20 12:14 ` tom
2023-04-20 14:36 ` Rodney W. Grimes
2023-04-20 14:18 ` Michael Richardson
2023-04-27 3:50 ` David Lang
2023-04-20 11:25 ` [Starlink] " Hesham ElBakoury
2023-04-20 11:27 ` Nathan Owens
2023-04-20 11:34 ` Mike Puchol
2023-04-20 14:21 ` Michael Richardson
2023-04-20 4:33 ` Ulrich Speidel
2023-04-20 14:12 ` Michael Richardson
-- strict thread matches above, loose matches on Subject: below --
2023-04-16 17:54 [Starlink] fiber IXPs in space 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
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=8151.1681416108@localhost \
--to=mcr@sandelman.ca \
--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