From: David Lang <david@lang.hm>
To: "David P. Reed" <dpreed@deepplum.com>
Cc: David Lang <david@lang.hm>, starlink@lists.bufferbloat.net
Subject: Re: [Starlink] Starlink "beam spread"
Date: Thu, 1 Sep 2022 01:09:03 -0700 (PDT) [thread overview]
Message-ID: <p75883s6-oo23-ps6-p4n2-1rs7or9p1s6@ynat.uz> (raw)
In-Reply-To: <1661980642.127124118@apps.rackspace.com>
On Wed, 31 Aug 2022, David P. Reed wrote:
> I'm not going to reason from "intersatellite" routing being operational until
> they offer it in operation. It's feasible, sort of. Laser beam aiming is quite
> different from phased array beam steering, and though they may have tested it
> between two satellites, that makes it a "link technology" not a network. (you
> can steer a laser beam by moving lightweight mirrors, I know. But tracking
> isn't so easy when both satellites are moving relative to each other - it
> seems like way beyond the technology base that Starlink has put in its
> satellites so far. But who knows.
They have been launching laser enabled satellites for a while now. I suspect
that the only way we will really know when they are enabled is when we see
coverage expand to the poles and mid-ocean (unless they make announcements about
it)
I doubt that they would be launching laser enabled satellites that could not
track each other.
David Lang
next prev parent reply other threads:[~2022-09-01 8:09 UTC|newest]
Thread overview: 71+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.800.1661972667.1281.starlink@lists.bufferbloat.net>
2022-08-31 19:51 ` David P. Reed
2022-08-31 20:28 ` David Lang
2022-08-31 21:17 ` David P. Reed
2022-08-31 21:33 ` David Lang
2022-09-01 7:05 ` Mike Puchol
2022-09-01 11:43 ` Ulrich Speidel
2022-09-01 8:09 ` David Lang [this message]
2022-08-31 20:24 ` [Starlink] CDNs in space! David P. Reed
2022-08-31 21:09 ` Mike Puchol
2022-08-31 22:19 ` Radostin Stoyanov
2022-08-31 22:46 ` Ulrich Speidel
2022-09-01 9:57 ` Brandon Butterworth
2022-09-01 15:19 [Starlink] Starlink "beam spread" David Fernández
2022-09-01 16:33 ` Darrell Budic
2022-09-02 9:32 ` David Fernández
2022-09-01 19:56 ` Michael Richardson
2022-09-02 12:27 ` Sebastian Moeller
2022-09-02 18:34 ` Michael Richardson
2022-09-02 20:11 ` Sebastian Moeller
-- strict thread matches above, loose matches on Subject: below --
2022-08-31 14:51 David Fernández
2022-08-31 18:09 ` Michael Richardson
2022-08-31 21:46 ` Ulrich Speidel
2022-08-31 23:44 ` Lin Han
2022-09-01 19:26 ` Dave Taht
2022-08-31 8:15 David Fernández
[not found] <mailman.3.1661875202.32670.starlink@lists.bufferbloat.net>
2022-08-30 16:53 ` David P. Reed
2022-08-30 17:32 ` Doc Searls
2022-08-30 20:09 ` Mike Puchol
2022-08-30 20:35 ` Daniel AJ Sokolov
2022-08-30 20:40 ` Mike Puchol
2022-08-30 21:09 ` David Lang
2022-08-30 21:01 ` David Lang
2022-08-30 22:07 ` Brandon Butterworth
2022-08-30 22:21 ` David Lang
2022-08-30 22:37 ` Brandon Butterworth
2022-08-30 23:07 ` David Lang
2022-08-30 23:45 ` Brandon Butterworth
2022-08-30 23:28 ` David P. Reed
2022-08-31 0:12 ` David Lang
2022-08-31 0:31 ` Dave Taht
2022-08-31 0:32 ` David P. Reed
2022-08-31 10:29 ` Dave Collier-Brown
2022-08-31 18:51 ` David Lang
2022-08-31 19:04 ` Dave Taht
2022-08-30 22:50 ` Ulrich Speidel
2022-08-30 23:13 ` David Lang
2022-08-31 0:46 ` tom
2022-08-31 0:58 ` Dave Taht
2022-08-31 7:36 ` Mike Puchol
2022-08-31 6:26 ` Sebastian Moeller
2022-08-31 7:25 ` Ulrich Speidel
2022-08-31 7:31 ` Hayden Simon
2022-08-31 7:33 ` David Lang
2022-08-31 9:59 ` Mike Puchol
2022-08-31 10:06 ` David Lang
2022-08-31 10:12 ` Mike Puchol
2022-08-31 17:52 ` Dick Roy
2022-08-31 13:41 ` Ulrich Speidel
2022-08-31 14:30 ` Mike Puchol
2022-08-31 21:44 ` Ulrich Speidel
2022-09-01 7:58 ` Sebastian Moeller
2022-09-01 11:38 ` Ulrich Speidel
2022-09-01 19:54 ` Michael Richardson
2022-09-01 21:08 ` tom
2022-09-02 7:52 ` Sebastian Moeller
2022-09-02 12:29 ` tom
2022-08-31 7:49 ` Sebastian Moeller
2022-08-31 9:25 ` Brandon Butterworth
2022-08-31 9:34 ` David Lang
2022-09-01 9:12 ` Brandon Butterworth
2022-08-31 14:52 ` Dave Taht
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=p75883s6-oo23-ps6-p4n2-1rs7or9p1s6@ynat.uz \
--to=david@lang.hm \
--cc=dpreed@deepplum.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