From: Jeremy Austin <jeremy@aterlo.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: Dave Taht via Starlink <starlink@lists.bufferbloat.net>
Subject: Re: [Starlink] tarana strikes back
Date: Tue, 26 Sep 2023 11:14:08 -0800 [thread overview]
Message-ID: <CACw=56LLhA52n53aGjKUoDXMjiK3DAJvZtkspUFWMCFGpZJPow@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw56+8qi_F6325rQeB8Lr-GivvvCB0hkR2019FXdbHw7Uw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2224 bytes --]
I haven’t vetted their specific numbers; but the approach (regarding actual
households per square mile) is consistent with mine comparing StarLink with
other WISP bands.
https://preseem.com/2021/06/fixed-wireless-spectrum-bands/
The upshot is that you can consider the shared medium of RF in terms of
spectral density (compensating for modulation differences.) Back of the
envelope and using anecdotal analysis of Tarana that we see in the field, I
think it’s in the correct order of magnitude.
The comments about Starlink using spatial reuse are legitimate — nothing is
preventing it from happening eventually — but their current FCC licensing
does not provide for this. Theoretically, we have infinite bandwidth (see
Tony Kapela’s work on “FU-MIMO”), but in practice, we have constraints.
Starlink’s strength, as others have pointed out, is ubiquity. I suspect
that traditional WISP technologies are still justifiable somewhere above
five customers per square mile (reasonably high density, given that Alaska
is < 1 !), but where that line is precisely is the difference between a
viable business plan and a money sink.
Jeremy Austin
Sr Product Manager - Preseem
On Sat, Sep 23, 2023 at 6:34 PM Dave Taht via Starlink <
starlink@lists.bufferbloat.net> wrote:
> Tarana, which is indeed, delivering one of the most amazing NLOS WISP
> experiences I have ever seen,
> just put out this white paper:
>
>
> https://www.taranawireless.com/a-comparison-of-next-generation-fwa-vs-leo-satellite/
>
> Can anyone question these Starlink numbers for cell size, etc?
>
> --
> Oct 30:
> https://netdevconf.info/0x17/news/the-maestro-and-the-music-bof.html
> Dave Täht CSO, LibreQos
> _______________________________________________
> Starlink mailing list
> Starlink@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/starlink
>
--
--
Jeremy Austin
Sr. Product Manager
Preseem | Aterlo Networks
preseem.com
Book a Call: https://app.hubspot.com/meetings/jeremy548
Phone: 1-833-733-7336 x718
Email: jeremy@preseem.com
Stay Connected with Newsletters & More:
*https://preseem.com/stay-connected/* <https://preseem.com/stay-connected/>
[-- Attachment #2: Type: text/html, Size: 4256 bytes --]
prev parent reply other threads:[~2023-09-26 19:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-24 2:34 Dave Taht
2023-09-24 20:19 ` Luis A. Cornejo
2023-09-24 20:37 ` Dave Taht
2023-09-25 8:11 ` David Lang
2023-09-26 18:37 ` [Starlink] [LibreQoS] Starlink cell capacity (was; tarana strikes back) Jim Forster
2023-09-26 19:00 ` David Lang
2023-09-26 21:16 ` Ulrich Speidel
2023-09-26 21:32 ` David Lang
2023-09-27 9:01 ` Alexandre Petrescu
2023-09-26 23:05 ` dan
2023-09-26 19:14 ` Jeremy Austin [this message]
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='CACw=56LLhA52n53aGjKUoDXMjiK3DAJvZtkspUFWMCFGpZJPow@mail.gmail.com' \
--to=jeremy@aterlo.com \
--cc=dave.taht@gmail.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