From: Robert McMahon <rjmcmahon@rjmcmahon.com>
To: "Network Neutrality is back! Let´s make the technical aspects
heard this time!" <nnagain@lists.bufferbloat.net>
Subject: Re: [NNagain] FCC - delete, delete, delete
Date: Thu, 13 Mar 2025 09:33:30 -0700 [thread overview]
Message-ID: <CAEBrVk7WoBiq3PBqKtbefHMV1w72h=U_LEbpHU_b-LJm4Pv9-A@mail.gmail.com> (raw)
In-Reply-To: <IA0PR12MB7751F7EF224FEB158C74A0DE8AD32@IA0PR12MB7751.namprd12.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 1321 bytes --]
>
> As for "what the FCC can do", "dissolve itself" comes to mind. AFAIK, it's been over a decade since they have done anything helpful or useful for any American citizen who isn't the head of a major corporation. If you delete the entire organization, there will be no one around to enforce whatever regs are still on the books so who cares? ... and you'll save another few 10's of millions of dollars annually which will fit nicely in the pockets of the "good folks", aka FODT. 😊😊😊
>
I worked with a CA state regulator in a tech support role prior to
so-called broadband (actually, internet access beyond dial-up MODEMs)
This was post 1996 telco act, just prior to the dot com bubble. The
lobbyists at the time disliked having 50 States regulating things.
They pushed made it so the 5 commissioners on the FCC became the
primary regulators. Many call this regulatory capture.
Unfortunately, I don't think we can get rid of the FCC. Our utility
poles are mostly regulated by them as one example.
I also don't think the FCC can mandage any specific AQM algorithm.
That's a long term disaster in the making for sure. Let network
engineers and the market battle that out.
Bob
PS. Good to hear from you RR - i hope all is well. I've got a Fi-Wi
project you may be interested in - not sure.
[-- Attachment #2: who-regulates-telephone-and-power-poles-Google-Search-03-13-2025_09_22_AM.png --]
[-- Type: image/png, Size: 237619 bytes --]
[-- Attachment #3: image.png --]
[-- Type: image/png, Size: 692302 bytes --]
next prev parent reply other threads:[~2025-03-13 16:33 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-12 17:39 Dave Taht
2025-03-13 0:00 ` Richard Roy
2025-03-13 16:33 ` Robert McMahon [this message]
2025-03-13 17:00 ` Frantisek Borsik
2025-03-13 18:36 ` Robert McMahon
2025-03-13 23:59 ` David Lang
2025-03-14 1:12 ` Robert McMahon
2025-03-14 1:38 ` David Bray, PhD
2025-03-14 2:17 ` Robert McMahon
2025-03-14 2:20 ` Robert McMahon
2025-03-14 2:24 ` David Bray, PhD
2025-03-14 8:16 ` Tara Stella
2025-03-14 18:53 ` Robert McMahon
2025-03-14 19:05 ` Richard Roy
2025-03-14 21:09 ` David Lang
2025-03-14 21:20 ` Dick Roy
2025-03-14 21:48 ` David Lang
2025-03-15 18:16 ` Robert McMahon
2025-03-15 18:49 ` Daniel Ezell
2025-03-16 17:50 ` Robert McMahon
2025-03-15 18:50 ` Robert McMahon
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='CAEBrVk7WoBiq3PBqKtbefHMV1w72h=U_LEbpHU_b-LJm4Pv9-A@mail.gmail.com' \
--to=rjmcmahon@rjmcmahon.com \
--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