From: Eugene Chang <eugene.chang@alum.mit.edu>
To: Michael Richardson <mcr@sandelman.ca>
Cc: Eugene Chang <eugene.chang@alum.mit.edu>,
"starlink@lists.bufferbloat.net" <starlink@lists.bufferbloat.net>
Subject: Re: [Starlink] Starlink "Best Effort" offering
Date: Fri, 30 Sep 2022 17:24:15 +0000 [thread overview]
Message-ID: <63D0EE5D-9CCE-479C-8BDD-B7A8DCB80925@alum.mit.edu> (raw)
In-Reply-To: <760833.1664541518@dooku>
[-- Attachment #1.1: Type: text/plain, Size: 1254 bytes --]
Ow… the implications on no satellite to satellite routing is all traffic is one-hop. That puts limits on big patches of the Pacific Basin. (And not a solution for trans-pacific aircraft.)
Any clues how far apart are the ground stations? That is a lot of ground stations. This makes me reconsider (terrestrial) fixed-wireless as an alternative.
Gene
-----------------------------------
Eugene Chang
eugene.chang@alum.mit.edu
+1-781-799-0233 (in Honolulu)
> On Sep 30, 2022, at 2:38 AM, Michael Richardson via Starlink <starlink@lists.bufferbloat.net> wrote:
>
> Signed PGP part
>
> Eugene Y Chang via Starlink <starlink@lists.bufferbloat.net> wrote:
>> Hmmmm….. is ground station positioning more about geographic topology
>> or managing subscriber density? I suspect it is easier to manage
>> subscriber density (and aggregate traffic) by building higher capacity
>> ground stations than by distributing ground stations.
>
> Until they have satellite to satellite routing, the ground stations have to
> be "near" the users that they serve.
>
> My understanding from this list is that's why they couldn't easily help Tongo: it
> was all just ocean "nearby" (and why they can help Ukraine)
>
>
>
>
>
[-- Attachment #1.2: Type: text/html, Size: 13182 bytes --]
[-- Attachment #2: Message signed with OpenPGP --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-09-30 17:24 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-28 19:53 Dotzero
2022-09-28 20:01 ` Dave Taht
2022-09-28 20:58 ` Dotzero
2022-09-28 21:02 ` David Lang
2022-09-28 21:04 ` Dave Taht
2022-09-28 23:07 ` Eugene Y Chang
2022-09-28 23:35 ` David Lang
2022-09-29 0:40 ` Eugene Y Chang
2022-09-29 4:29 ` David Lang
2022-09-29 7:50 ` Eugene Y Chang
2022-09-29 9:10 ` Sebastian Moeller
2022-09-29 9:14 ` David Lang
2022-09-29 19:38 ` Eugene Y Chang
2022-09-30 12:38 ` Michael Richardson
2022-09-30 12:43 ` Nathan Owens
2022-09-30 17:24 ` Eugene Chang [this message]
2022-09-30 17:26 ` Nathan Owens
2022-09-30 18:03 ` Mike Puchol
2022-09-30 21:39 rob currie
2022-09-30 23:56 ` Eugene Chang
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=63D0EE5D-9CCE-479C-8BDD-B7A8DCB80925@alum.mit.edu \
--to=eugene.chang@alum.mit.edu \
--cc=mcr@sandelman.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