From: Eugene Y Chang <eugene.chang@ieee.org>
To: David Lang <david@lang.hm>
Cc: Eugene Chang <eugene.chang@ieee.org>,
Sebastian Moeller <moeller0@gmx.de>,
Dave Taht via Starlink <starlink@lists.bufferbloat.net>
Subject: Re: [Starlink] Starlink "Best Effort" offering
Date: Thu, 29 Sep 2022 09:38:30 -1000 [thread overview]
Message-ID: <14B0D432-15BA-42AE-9D8D-1DF7E7E50402@ieee.org> (raw)
In-Reply-To: <pso8oro2-qoqr-2os0-r262-2o347q71104@ynat.uz>
[-- Attachment #1.1: Type: text/plain, Size: 5694 bytes --]
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.
Gene
----------------------------------------------
Eugene Chang
IEEE Senior Life Member
eugene.chang@ieee.org
781-799-0233 (in Honolulu)
> On Sep 28, 2022, at 11:14 PM, David Lang <david@lang.hm> wrote:
>
> On Thu, 29 Sep 2022, Sebastian Moeller wrote:
>
>>> On Sep 29, 2022, at 09:50, Eugene Y Chang via Starlink <starlink@lists.bufferbloat.net> wrote:
>>>
>>> Good point… that sure makes matching new capacity to new subscribers really hard.
>>
>> [SM] Or easy: "just" add more satellites ;) some of the added capacity should also end up at new subscribers... SCNR
>
> yep, which is what they are doing. ;-)
>
> there is some that they can do in terms of the ground station positioning, density, and connectivity.
>
> David Lang
>
>> Regards
>> Sebastian
>>
>>
>>>
>>> Gene
>>> ----------------------------------------------
>>> Eugene Chang
>>> IEEE Senior Life Member
>>> eugene.chang@ieee.org
>>> 781-799-0233 (in Honolulu)
>>>
>>>
>>>
>>>> On Sep 28, 2022, at 6:29 PM, David Lang <david@lang.hm> wrote:
>>>>
>>>> that strip of land is different every orbit, a given satellite doesn't pass over the same land each orbit.
>>>>
>>>> David Lang
>>>>
>>>> On Wed, 28 Sep 2022, Eugene Y Chang wrote:
>>>>
>>>>> Date: Wed, 28 Sep 2022 14:40:35 -1000
>>>>> From: Eugene Y Chang <eugene.chang@ieee.org>
>>>>> To: David Lang <david@lang.hm>
>>>>> Cc: Eugene Chang <eugene.chang@ieee.org>, Dotzero <dotzero@gmail.com>,
>>>>> Dave Taht via Starlink <starlink@lists.bufferbloat.net>
>>>>> Subject: Re: [Starlink] Starlink "Best Effort" offering
>>>>> Yes and no.
>>>>>
>>>>> Yes they can beef up the constellation, one section at a time. (For a given launch, the are enhancing a particular orbit.)
>>>>>
>>>>> Depending on your definition of “one area” when you say “not in any one area”.
>>>>> Technically they would beef up an area in the shape of strips, where the strip is the ground under the orbit of the additional (new) satellites.
>>>>>
>>>>> Sorry, when I say “add service to an area”, it implies adding coverage to strips of land, the land under the new satellite orbit.
>>>>>
>>>>> https://satellitemap.space/?constellation=starlink <https://satellitemap.space/?constellation=starlink>
>>>>>
>>>>>
>>>>> Gene
>>>>> ----------------------------------------------
>>>>> Eugene Chang
>>>>> IEEE Senior Life Member
>>>>> eugene.chang@ieee.org
>>>>> 781-799-0233 (in Honolulu)
>>>>>
>>>>>
>>>>>
>>>>>> On Sep 28, 2022, at 1:35 PM, David Lang <david@lang.hm> wrote:
>>>>>>
>>>>>> The Starlink satellites are in low orbit (<90 min), so you beef up the contellation overall, not in any one area.
>>>>>>
>>>>>> David Lang
>>>>>>
>>>>>> On Wed, 28 Sep 2022, Eugene Y Chang via Starlink wrote:
>>>>>>
>>>>>>> Date: Wed, 28 Sep 2022 13:07:43 -1000
>>>>>>> From: Eugene Y Chang via Starlink <starlink@lists.bufferbloat.net>
>>>>>>> Reply-To: Eugene Y Chang <eugene.chang@ieee.org>
>>>>>>> To: Dotzero <dotzero@gmail.com>
>>>>>>> Cc: Dave Taht via Starlink <starlink@lists.bufferbloat.net>
>>>>>>> Subject: Re: [Starlink] Starlink "Best Effort" offering
>>>>>>> What is the definition and differences between regular and best effort service?
>>>>>>>
>>>>>>> Creating two bookings queue, wait list and best effort subscribers, the best effort subscribers are more “real”. With that, treating best effort subscribers as a (more) "real customer" backlog, it would be a good way to prioritize where to expand the constellation (i.e. where to add capacity).
>>>>>>>
>>>>>>> Gene
>>>>>>> ----------------------------------------------
>>>>>>> Eugene Chang
>>>>>>> IEEE Senior Life Member
>>>>>>> eugene.chang@ieee.org
>>>>>>> 781-799-0233 (in Honolulu)
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> On Sep 28, 2022, at 9:53 AM, Dotzero via Starlink <starlink@lists.bufferbloat.net> wrote:
>>>>>>>>
>>>>>>>> I've been on the wait list for almost 10 months and just received an email that I can sign up for a "best efforts" offering. Seeing as they also indicated the estimated time for regular service is mid-2023, I decided to go with it (You don't lose your place on the wait list). You can also "pause" the best effort service so I don't really have anything to lose.
>>>>>>>>
>>>>>>>> Has anyone had experience with this offering? Any input appreciated. If it makes a difference, location is Central East Ohio.
>>>>>>>>
>>>>>>>> According to https://www.starlink.com/legal/documents/DOC-1002-69942-69?regionCode=US <https://www.starlink.com/legal/documents/DOC-1002-69942-69?regionCode=US>, latency will be comparable to regular service, down will be 5-100mbs and up will be 1-10mps unless service is deprioritized due to congestion.
>>>>>>>>
>>>>>>>> Thanks in advance.
>>>>>>>>
>>>>>>>> Mike
>>>>>>>>
>>>>>>>> _______________________________________________
>>>>>>>> Starlink mailing list
>>>>>>>> Starlink@lists.bufferbloat.net
>>>>>>>> https://lists.bufferbloat.net/listinfo/starlink
>>>>>>>
>>>>>> _______________________________________________
>>>>>> Starlink mailing list
>>>>>> Starlink@lists.bufferbloat.net
>>>>>> https://lists.bufferbloat.net/listinfo/starlink
>>>>>
>>>
>>> _______________________________________________
>>> Starlink mailing list
>>> Starlink@lists.bufferbloat.net
>>> https://lists.bufferbloat.net/listinfo/starlink
>>
[-- Attachment #1.2: Type: text/html, Size: 8482 bytes --]
[-- Attachment #2: Message signed with OpenPGP --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-09-29 19:38 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 [this message]
2022-09-30 12:38 ` Michael Richardson
2022-09-30 12:43 ` Nathan Owens
2022-09-30 17:24 ` Eugene Chang
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=14B0D432-15BA-42AE-9D8D-1DF7E7E50402@ieee.org \
--to=eugene.chang@ieee.org \
--cc=david@lang.hm \
--cc=moeller0@gmx.de \
--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