From: Jack Haverty <jack@3kitty.org>
To: nnagain@lists.bufferbloat.net
Subject: Re: [NNagain] nn back in the news
Date: Thu, 15 Aug 2024 11:06:04 -0700 [thread overview]
Message-ID: <28ebe36a-f586-42e9-917c-5c1f1cabaa6d@3kitty.org> (raw)
In-Reply-To: <CAA93jw5L=wdTBF21w3R8Frb4yD_WTOSa5q_HqKvHGVViP=bW-w@mail.gmail.com>
[-- Attachment #1.1.1.1: Type: text/plain, Size: 3081 bytes --]
IMHO, educating politicians and regulators is difficult but necessary.
Latency is an important and overlooked component of "broadband service",
not included in the definition of such "service". But there are others
that might also catch their attention.
I live in an area in California where wildfires are an issue. My
location officially has broadband service, according to the FCC
databases. I get IP through cable, provided by Comcast. The IP{
service is fast and latency hasn't been an issue for me.
The government (state, local, and federal) have all spent a lot of money
and effort to put technology in place to mitigate the risks of wildfire
and other such natural risks, to help keep the public safe. That's
their job. We have sensors and cameras that spot smoke columns or
seismic events. We have apps and communications channels that spread
the word fast, so that people can get out of harm's way. The Internet
has made quite a difference by providing the infrastructure to make such
safety mechanisms possible. (See app.watchduty.org for an example)
The local electric utility has also implemented mechanisms to avoid
causing wildfires. When it's dry and windy, and therefore the risks of
a falling tree limb starting a fire are high, they simply shut off the
power to the area. When the risk is over, they turn power back on. It
might be a day or two, but while the risks are high, a fire won't be
started by the electric grid. Many people have installed generators to
keep essential things going in their homes. The electric utility is
even offering subsidies for people to buy such equipment.
However...
Comcast relies on the electric grid for power. Some areas have
equipment with backup battery power, but that only works for an hour or
two. After that, communications shuts down - in my neighborhood that
means telephone, TV, and Internet all cease to work. All of the
information from those sensors, cameras, and emergency service agencies
doesn't get to us, the public it's supposed to help.
Despite that behavior, officially the database says we have broadband
service available. It of course is available, most of the time. It
turns off when you need it the most.
Thinking techologically for a bit, the problem is a lot like Latency.
Latency is not specified in the definition of "broadband service".
Neither is "Reliability".
I've filed a "challenge" to my own database entry, pointing out that we
don't actually have reliable broadband service. Even if, over a month
or so, the service is 99.xxx% "up", that's not much help if it's down
when you actually need it the most. The definition of "reliable" needs
to be revised.
I don't expect any action from my challenge as just a lone voice in the
crowd.
Perhaps educating the politicians and regulators about reliability would
grab some attention. It might be a bit easier to understand than just
"latency".
Jack Haverty
Nevada City, CA
[-- Attachment #1.1.1.2: Type: text/html, Size: 3554 bytes --]
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 2469 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 665 bytes --]
next prev parent reply other threads:[~2024-08-15 18:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-15 11:41 Dave Taht
2024-08-15 13:27 ` Livingood, Jason
2024-08-15 14:16 ` Dave Taht
2024-08-15 14:36 ` Dave Cohen
2024-08-15 15:58 ` Sebastian Moeller
2024-08-15 17:05 ` Dave Taht
2024-08-15 18:06 ` Jack Haverty [this message]
2024-08-18 19:32 ` Frantisek Borsik
2024-08-15 19:08 Livingood, Jason
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/nnagain.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=28ebe36a-f586-42e9-917c-5c1f1cabaa6d@3kitty.org \
--to=jack@3kitty.org \
--cc=nnagain@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