From: Dave Taht <dave.taht@gmail.com>
To: starlink@lists.bufferbloat.net
Subject: [Starlink] My NTAI broadband filing
Date: Sun, 6 Feb 2022 09:23:14 -0800 [thread overview]
Message-ID: <CAA93jw6uioyEDHyXXz-ZCSBw-m53Xep7tX8-2P9ZtFkjmLUHzw@mail.gmail.com> (raw)
The NTIA put out an RFC asking for how to spend $70B properly, so I
wrote up a brief submission, submitted yesterday, to try and broaden
the debate to have metrics more than average "speed".
Starlink fans will be thrilled at how much better than a tethered cell
phone starlink presently is, under load.
https://docs.google.com/document/d/1FjRo9MNnVOLh733SNPNyqaR1IFee7Q5qbMrmW1PlPr8/edit#
It could still be so much better. I do often wish that instead of
focusing on bandwidth, starlink optimizing to provide consistently low
latency 50Mbits per subscriber instead might let them increase
subscriber density, with the only disappointed ones being speedtest
freaks.
--
I tried to build a better future, a few times:
https://wayforward.archive.org/?site=https%3A%2F%2Fwww.icei.org
Dave Täht CEO, TekLibre, LLC
reply other threads:[~2022-02-06 17:23 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CAA93jw6uioyEDHyXXz-ZCSBw-m53Xep7tX8-2P9ZtFkjmLUHzw@mail.gmail.com \
--to=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