From: Daniel AJ Sokolov <daniel@falco.ca>
To: starlink@lists.bufferbloat.net
Subject: Re: [Starlink] Starlink Roaming
Date: Mon, 21 Feb 2022 15:02:29 -0700 [thread overview]
Message-ID: <be95f8e4-3d86-10eb-3395-d71f34a8bcaf@falco.ca> (raw)
In-Reply-To: <866405-s043-n12n-6pqs-46o38r189218@ynat.uz>
On 2022-02-21 at 13:52, David Lang wrote:
>
> They told me that I could try it, and it may work, may be degraded a
> bit, or may not work at all. They do plan to add roaming capabilities in
> the future (my guess is that the laser satellites will enable a lot more
> flexibility)
Isn't that a very optimistic assessment? :-)
Laser links are great for remote locations with very few users, but how
could they relieve overbooking of Starlink in areas with too many users?
The laser links can reduce the required density of ground stations, but
they don't add capacity to the network. Any ground station not built
thanks to laser links adds load to other ground stations - and, maybe
more importantly, adds load to the satellite that does eventually
connect to a ground station.
Can laser links really help on a large scale, or are they just a small
help here and there?
Cheers
Daniel
next prev parent reply other threads:[~2022-02-21 22:02 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-14 19:53 Jonathan Bennett
2022-02-14 20:29 ` David Lang
2022-02-14 21:43 ` Mike Puchol
2022-02-14 21:53 ` Jonathan Bennett
2022-02-14 21:59 ` Mike Puchol
2022-02-21 7:22 ` Larry Press
2022-02-21 7:29 ` David Lang
2022-02-21 20:31 ` Dick Roy
2022-02-21 20:43 ` Mike Puchol
2022-02-21 20:52 ` David Lang
2022-02-21 21:17 ` Dick Roy
2022-02-21 21:32 ` David Lang
2022-02-21 21:58 ` Nathan Owens
2022-02-21 22:26 ` Dick Roy
2022-02-21 23:08 ` Steve Golson
2022-02-21 23:15 ` Nathan Owens
2022-02-22 1:19 ` Dick Roy
2022-02-21 22:02 ` Daniel AJ Sokolov [this message]
2022-02-22 2:17 ` David Lang
2022-02-22 5:34 ` Mike Puchol
2022-02-22 7:20 ` Dick Roy
2022-02-22 7:42 ` Mike Puchol
2022-02-22 7:51 ` Dick Roy
2022-02-22 9:03 ` Sebastian Moeller
2022-02-22 9:40 ` Mike Puchol
2022-02-22 9:46 ` Sebastian Moeller
2022-02-22 10:01 ` Mike Puchol
2022-02-22 10:37 ` Vint Cerf
2022-02-22 11:14 ` Mike Puchol
2022-02-22 7:58 ` Ulrich Speidel
2022-02-22 8:51 ` David Lang
2022-02-22 7:47 ` Dick Roy
2022-02-22 8:55 ` David Lang
2022-02-22 23:14 ` Dick Roy
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=be95f8e4-3d86-10eb-3395-d71f34a8bcaf@falco.ca \
--to=daniel@falco.ca \
--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