From: Colin_Higbie <CHigbie1@Higbie.name>
To: David Lang <david@lang.hm>
Cc: "starlink@lists.bufferbloat.net" <starlink@lists.bufferbloat.net>
Subject: Re: [Starlink] Itʼs the Latency, FCC
Date: Wed, 1 May 2024 03:38:50 +0000 [thread overview]
Message-ID: <MN2PR16MB33910D073C31647133F12807F1192@MN2PR16MB3391.namprd16.prod.outlook.com> (raw)
In-Reply-To: <1on0ppr4-os7r-7pp4-r802-65r795862p38@ynat.uz>
David,
You wrote, "I in no way advocate for the elimination of 25Mb connectivity. What I am arguing against is defining that as the minimum acceptable connectivity. i.e. pretending that anything less than that may as well not exist (ot at the very least should not be defined as 'broadband')"
If you're simply talking about approaching an existing ISP with existing services and telling them, "Please implement cake and codel to reduce latency problems at load," then I'm with you. That's a clear win because you're fixing a latency problem without creating any new problems. Good.
The importance of the 25Mbps minimum arises with NEW services, new construction. Specifically, where an ISP is looking to expand their geographic footprint or seeking funding to provide improvements or a new ISP is looking to enter a market, it is DESTRUCTIVE for them to roll out a new service that can't support at least 25Mbps service. This is because a new service rollout will generally not be upgraded in terms of bandwidth capacity for a period of years following the initial deployment. As stated before, it's fine if they also OFFER plans with lower top speeds because not everyone needs 25Mbps, but they must at least OFFER a minimum of a 25Mbps plan. You do more harm to Internet infrastructure and further the Internet divide if you encourage good latency for new constructions at sub-25Mbps bandwidth.
If members of this group are touting themselves as experts and advising ISPs, then you must include the 25Mbps bandwidth as the floor for at least the top tier of service.
I don't mean to suggest 25Mbps at 1,000ms latency is better than 20Mbps at 30ms latency, but rather that assuming a reasonable latency, getting to AT LEAST 25Mbps bandwidth is important. I yield to the wisdom of this group on an equivalent max reasonable latency. In my experience anything sub 100ms would be an acceptable max latency, but I would accept if you told me the upper limit on new rollout should require nothing above 50ms or 60ms.
-----Original Message-----
From: David Lang <david@lang.hm>
Sent: Tuesday, April 30, 2024 11:19 PM
To: Colin_Higbie <CHigbie1@Higbie.name>
Cc: David Lang <david@lang.hm>; starlink@lists.bufferbloat.net
Subject: RE: [Starlink] Itʼs the Latency, FCC
On Wed, 1 May 2024, Colin_Higbie wrote:
> This is a largely black and white issue: there are a significant # of
> users who need 4K streaming support. Period. This is a market
> standard, like 91 octane gas, 802.11ax Wi-Fi, skim (0%) milk, 50 SPF sunblock, and 5G phones.
> The fact that not everyone uses one of those market-established
> standards does not mean that each is not an important standard with a
> sizable market cohort that merits support. 25Mbps for 4K HDR streaming
> is one such standard. That's not my opinion. That's a
> market-established fact and the only reason I posted here – to ensure
> this group has that information so that you can be more effective in presenting your latency arguments and solutions to the ISPs.
But just because many people want those things doesn't mean that 87 octane gas, SPF 20 sunblock, 2% milk, 4G phones, etc should be eliminated.
I in no way advocate for the elimination of 25Mb connectivity. What I am arguing against is defining that as the minimum acceptable connectivity. i.e. pretending that anything less than that may as well not exist (ot at the very least should not be defined as 'broadband')
David Lang
next prev parent reply other threads:[~2024-05-01 3:38 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 [this message]
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
[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=MN2PR16MB33910D073C31647133F12807F1192@MN2PR16MB3391.namprd16.prod.outlook.com \
--to=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