From: James Forster <jim@connectivitycap.com>
To: Colin_Higbie <CHigbie1@higbie.name>
Cc: David Lang <david@lang.hm>, starlink@lists.bufferbloat.net
Subject: Re: [Starlink] Itʼs the Latency, FCC
Date: Tue, 30 Apr 2024 23:54:33 -0400 [thread overview]
Message-ID: <E13E9C92-6107-4BEC-8D28-4AC327B4FF81@connectivitycap.com> (raw)
In-Reply-To: <MN2PR16MB3391F6412E3176FC9F3BC25BF1192@MN2PR16MB3391.namprd16.prod.outlook.com>
I agree.
> There is no conflict between the need to support 25Mbps Internet and this group's goal of reducing latency at load. On the other hand, you lose credibility and won't be taken seriously by your target audience if you disregard the importance of the need for every ISP rolling out a new plan to at least offer a 25Mbps bandwidth level of support.
next prev parent reply other threads:[~2024-05-01 3:54 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.2785.1714507537.1074.starlink@lists.bufferbloat.net>
2024-04-30 20:48 ` [Starlink] It’s " Colin Higbie
2024-04-30 20:49 ` Colin_Higbie
2024-05-01 0:51 ` David Lang
2024-05-01 2:46 ` [Starlink] Itʼs " Colin_Higbie
2024-05-01 3:18 ` David Lang
2024-05-01 3:38 ` Colin_Higbie
2024-05-01 3:51 ` David Lang
2024-05-01 4:16 ` Colin_Higbie
2024-05-01 7:40 ` David Lang
2024-05-01 15:13 ` Colin_Higbie
2024-05-01 3:54 ` James Forster [this message]
[not found] <mailman.2773.1714488060.1074.starlink@lists.bufferbloat.net>
2024-04-30 18:05 ` [Starlink] It’s " Colin_Higbie
2024-04-30 19:04 ` Eugene Y Chang
2024-05-01 0:36 ` David Lang
2024-05-01 1:30 ` [Starlink] Itʼs " Eugene Y Chang
2024-05-01 1:52 ` Jim Forster
2024-05-01 3:59 ` Eugene Y Chang
2024-05-01 4:12 ` David Lang
2024-05-01 10:15 ` Frantisek Borsik
2024-05-01 18:51 ` Eugene Y Chang
2024-05-01 19:18 ` David Lang
2024-05-01 21:11 ` Frantisek Borsik
2024-05-01 22:10 ` Eugene Y Chang
2024-05-01 21:12 ` Eugene Y Chang
2024-05-01 21:27 ` Sebastian Moeller
2024-05-01 22:19 ` Eugene Y Chang
2024-05-02 19:17 ` Michael Richardson
[not found] <mailman.11.1710518402.17089.starlink@lists.bufferbloat.net>
2024-03-15 18:32 ` [Starlink] It’s " Colin Higbie
2024-03-15 18:41 ` Colin_Higbie
2024-03-15 19:53 ` Spencer Sevilla
2024-03-15 23:07 ` David Lang
2024-03-16 18:45 ` [Starlink] Itʼs " Colin_Higbie
2024-03-16 19:09 ` Sebastian Moeller
2024-03-16 19:26 ` Colin_Higbie
2024-03-16 19:45 ` Sebastian Moeller
2024-03-16 23:05 ` David Lang
2024-04-30 0:39 ` [Starlink] It’s " David Lang
2024-04-30 1:30 ` [Starlink] Itʼs " Colin_Higbie
2024-04-30 2:16 ` David Lang
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=E13E9C92-6107-4BEC-8D28-4AC327B4FF81@connectivitycap.com \
--to=jim@connectivitycap.com \
--cc=CHigbie1@higbie.name \
--cc=david@lang.hm \
--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