From: Nathan Owens <nathan@nathan.io>
To: Mike Puchol <mike@starlink.sx>
Cc: Dave Taht <davet@teklibre.net>,
Michael Richardson <mcr@sandelman.ca>,
starlink@lists.bufferbloat.net
Subject: Re: [Starlink] Microstate Accounting and the Nyquist problem
Date: Sat, 12 Jun 2021 09:42:51 -0700 [thread overview]
Message-ID: <CALjsLJvy-fki-Lp6BdGbN6GsKX0LZptpr09ECGOsFeXW5Nb18A@mail.gmail.com> (raw)
In-Reply-To: <c75357e6-d3f8-4f82-ae8d-d81009ca84d6@Spark>
[-- Attachment #1: Type: text/plain, Size: 1091 bytes --]
You can buy a coin sized chip-scale atomic clock, so it wouldn’t surprise
me.
On Sat, Jun 12, 2021 at 9:15 AM Mike Puchol <mike@starlink.sx> wrote:
> The basis for the GPS time sync is an atomic clock on board each
> satellite. I very much doubt Starlink is placing one of those in their
> birds :-)
>
> Best,
>
> Mike
> On Jun 12, 2021, 16:00 +0200, Michael Richardson <mcr@sandelman.ca>,
> wrote:
>
>
> Dave Taht <davet@teklibre.net> wrote:
>
> It’s ironic that the device has to have gps in it, and thus should be
> able to provide perfect time to clients directly behind it, isn’t.
>
>
> Couldn't starlink satellites *also* provide a GPS reference?
> They are lower and way more of them...
>
> --
> ] Never tell me the odds! | ipv6 mesh networks [
> ] Michael Richardson, Sandelman Software Works | network architect [
> ] mcr@sandelman.ca http://www.sandelman.ca/ | ruby on rails [
>
> _______________________________________________
> Starlink mailing list
> Starlink@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/starlink
>
[-- Attachment #2: Type: text/html, Size: 2201 bytes --]
next prev parent reply other threads:[~2021-06-12 16:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <baa8ff7a-0bde-9d6e-5984-ef5fcbae5ccd@rogers.com>
2021-06-09 13:15 ` [Starlink] Fwd: " Dave Taht
2021-06-11 22:14 ` David Collier-Brown
2021-06-11 22:34 ` Mike Puchol
2021-06-11 22:39 ` [Starlink] " Dave Taht
2021-06-11 22:59 ` Nathan Owens
2021-06-11 23:00 ` Dave Taht
2021-06-11 23:09 ` Mike Puchol
2021-06-18 18:17 ` [Starlink] NTP implementations [was: Microstate Accounting and the Nyquist problem] Juliusz Chroboczek
2021-06-12 14:00 ` [Starlink] Microstate Accounting and the Nyquist problem Michael Richardson
2021-06-12 16:13 ` Mike Puchol
2021-06-12 16:42 ` Nathan Owens [this message]
2021-06-12 19:05 ` Mike Puchol
2021-06-12 19:20 ` Gary E. Miller
2021-06-12 1:40 ` [Starlink] Fwd: " Karl Auerbach
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=CALjsLJvy-fki-Lp6BdGbN6GsKX0LZptpr09ECGOsFeXW5Nb18A@mail.gmail.com \
--to=nathan@nathan.io \
--cc=davet@teklibre.net \
--cc=mcr@sandelman.ca \
--cc=mike@starlink.sx \
--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