From: Michael Richardson <mcr@sandelman.ca>
To: David Lang <david@lang.hm>, Nathan Owens <nathan@nathan.io>,
"starlink@lists.bufferbloat.net" <starlink@lists.bufferbloat.net>,
"David P. Reed" <dpreed@deepplum.com>
Subject: Re: [Starlink] Starlink and bufferbloat status?
Date: Fri, 16 Jul 2021 16:51:00 -0400 [thread overview]
Message-ID: <15095.1626468660@localhost> (raw)
In-Reply-To: <nycvar.QRO.7.76.6.2107161020500.1440203@qynat-yncgbc>
David Lang <david@lang.hm> wrote:
> As there are more staellites, the up down time will get closer to 4-5ms
> rather then the ~7ms you list, and with laser relays in orbit, and terminal
> to terminal routing in orbit, there is the potential for the theoretical
> minimum to tend lower, giving some headroom for other overhead but still
> being in the 20ms range.
I really want this to happen, but how will this get managed?
We will don't know shit, and I'm not convinced SpaceX knows either.
I'm scared that these paths will centrally managed, and not based upon
longest prefix (IPv6) match.
--
] Never tell me the odds! | ipv6 mesh networks [
] Michael Richardson, Sandelman Software Works | IoT architect [
] mcr@sandelman.ca http://www.sandelman.ca/ | ruby on rails [
next prev parent reply other threads:[~2021-07-16 20:51 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.3.1625846401.13780.starlink@lists.bufferbloat.net>
2021-07-09 18:40 ` David P. Reed
2021-07-09 18:45 ` Nathan Owens
2021-07-09 19:08 ` Ben Greear
2021-07-09 20:08 ` Dick Roy
2021-07-09 22:58 ` David Lang
2021-07-09 23:07 ` Daniel AJ Sokolov
2021-07-10 15:58 ` Dave Taht
2021-07-16 10:21 ` Wheelock, Ian
2021-07-16 17:08 ` David Lang
2021-07-16 17:13 ` Nathan Owens
2021-07-16 17:24 ` David Lang
2021-07-16 17:29 ` Nathan Owens
2021-07-16 17:31 ` Mike Puchol
2021-07-16 17:35 ` Nathan Owens
2021-07-16 17:39 ` Jonathan Bennett
2021-07-19 1:05 ` Nick Buraglio
2021-07-19 1:20 ` David Lang
2021-07-19 1:34 ` Nick Buraglio
2021-07-17 18:36 ` David P. Reed
2021-07-17 18:42 ` David Lang
2021-07-18 19:05 ` David Lang
2021-07-16 17:38 ` David Lang
2021-07-16 17:42 ` Mike Puchol
2021-07-16 18:48 ` David Lang
2021-07-16 20:57 ` Mike Puchol
2021-07-16 21:30 ` David Lang
2021-07-16 21:40 ` Mike Puchol
2021-07-16 22:40 ` Jeremy Austin
2021-07-16 23:04 ` Nathan Owens
2021-07-17 10:02 ` [Starlink] Free Space Optics - was " Michiel Leenaars
2021-07-17 1:12 ` [Starlink] " David Lang
[not found] ` <d86d6590b6f24dfa8f9775ed3bb3206c@DM6PR05MB5915.namprd05.prod.outlook.com>
2021-07-17 15:55 ` Fabian E. Bustamante
2021-07-16 20:51 ` Michael Richardson [this message]
2021-07-18 19:17 ` David Lang
2021-07-18 22:29 ` Dave Taht
2021-07-19 1:30 ` David Lang
2021-07-19 12:14 ` Michael Richardson
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=15095.1626468660@localhost \
--to=mcr@sandelman.ca \
--cc=david@lang.hm \
--cc=dpreed@deepplum.com \
--cc=nathan@nathan.io \
--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