From: "Livingood, Jason" <jason_livingood@comcast.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: "Network Neutrality is back! Let´s make the technical aspects
heard this time!" <nnagain@lists.bufferbloat.net>
Subject: Re: [NNagain] nn back in the news
Date: Thu, 15 Aug 2024 19:08:25 +0000 [thread overview]
Message-ID: <97AF78A0-C4CE-456C-878A-D19D7A207736@comcast.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 4415 bytes --]
My personal theory (IANAL am guessing at this based on reading a lot on the subject).
We are here: Lawsuit to stop Title-I reclassification proceeds (on Loper Bright / Chevron and MQD issues) over the next months/years.
IF SCOTUS upholds the reclassification, THEN end of story.
IF SCOTUS overturns the reclassification, THEN existing or new state regs take precedence.
THEN, people on both sides decry the lack of national rules.
THEN, the will to create a legislative solution MAY develop (or MAY NOT).
IF SCOTUS overturns only part of the reclassification or returns it to the agency with some TBD direction, THEN who knows…
;-)
JL
From: Dave Taht <dave.taht@gmail.com>
Date: Thursday, August 15, 2024 at 10:17
To: Jason Livingood <jason_livingood@comcast.com>
Cc: Network Neutrality is back! Let´s make the technical aspects heard this time! <nnagain@lists.bufferbloat.net>
Subject: [EXTERNAL] Re: [NNagain] nn back in the news
Perhaps it would have been better to say that "one of the sites I read regularly just put out an update on it." :)
I like to think that bufferbloat.net<https://urldefense.com/v3/__http:/bufferbloat.net__;!!CQl3mcHX2A!GfEu5eBEYPiXujccckauGtSMMDXcKa6s7aNuJbEW7Cr2RBJVYShKwABi7oxqNgjeflOqydn-Z1L8Kd3KzneaYBl9$>'s NOI filing did a bit of good, getting cited 16 times, but not changing the top level conclusions one iota. Doing another one this year is on my mind in followup, but aside from harping on our latency points, pointing to progress, and the need for more IXPs, I don't know what top level items could be addressed, again? I'd have to buckle down and re-read what resonated, and what didn't.
Perhaps something might come out of the DNC?
I have been enjoying Carr's negative posts on BEAD, but there must be some bright news in that program somewhere by now?
I am perhaps reading too much into it, but with a potentially younger crowd moving into office, perhaps more technical clue is arriving? I'm very happy to see mudge make CIO at darpa. The white house got a cto yet? The FCC?
PS Ms Shotwell did a great fireside chat at Mountain Connect: https://www.broadband.io/c/broadband-community-events/shotwell<https://urldefense.com/v3/__https:/www.broadband.io/c/broadband-community-events/shotwell__;!!CQl3mcHX2A!GfEu5eBEYPiXujccckauGtSMMDXcKa6s7aNuJbEW7Cr2RBJVYShKwABi7oxqNgjeflOqydn-Z1L8Kd3KzmawuPvX$>
On Thu, Aug 15, 2024 at 6:27 AM Livingood, Jason <jason_livingood@comcast.com<mailto:jason_livingood@comcast.com>> wrote:
I would say it is not “back” in the news – it has continuously been in the news since the Loper Bright SCOTUS ruling that impacts “Chevron deference” as well the major questions doctrine issue raised in W VA vs EPA. As many people have long said, this will be tied up in the courts for several years.
Personal take – in the long-term it will be better to have legislation that codifies this (as well as a national cross-sector privacy law).
JL
From: Nnagain <nnagain-bounces@lists.bufferbloat.net<mailto:nnagain-bounces@lists.bufferbloat.net>> on behalf of Dave Taht via Nnagain <nnagain@lists.bufferbloat.net<mailto:nnagain@lists.bufferbloat.net>>
Reply-To: Network Neutrality is back! Let´s make the technical aspects heard this time! <nnagain@lists.bufferbloat.net<mailto:nnagain@lists.bufferbloat.net>>
Date: Thursday, August 15, 2024 at 07:41
To: Network Neutrality is back! Let´s make the technical aspects heard this time! <nnagain@lists.bufferbloat.net<mailto:nnagain@lists.bufferbloat.net>>
Cc: Dave Taht <dave.taht@gmail.com<mailto:dave.taht@gmail.com>>
Subject: [NNagain] nn back in the news
https://arstechnica.com/tech-policy/2024/08/isps-ask-supreme-court-to-kill-new-york-law-that-requires-15-broadband-plans/<https://urldefense.com/v3/__https:/arstechnica.com/tech-policy/2024/08/isps-ask-supreme-court-to-kill-new-york-law-that-requires-15-broadband-plans/__;!!CQl3mcHX2A!FPiUKVoVIIjDuEAjFeVX-ISnAeSb8gI7-H-8Pg5UvZVEuC6YaYS0X8k4cHM4F-i7JjIAMB_2uKpV5QLmf8MbXIx1fORtlGxN$>
--
Dave Täht CSO, LibreQos
--
Artists/Musician Campout Aug 9-11
https://www.eventbrite.com/e/healing-arts-event-tickets-928910826287<https://urldefense.com/v3/__https:/www.eventbrite.com/e/healing-arts-event-tickets-928910826287__;!!CQl3mcHX2A!GfEu5eBEYPiXujccckauGtSMMDXcKa6s7aNuJbEW7Cr2RBJVYShKwABi7oxqNgjeflOqydn-Z1L8Kd3Kzn4oY8V6$>
Dave Täht CSO, LibreQos
[-- Attachment #2: Type: text/html, Size: 12380 bytes --]
next reply other threads:[~2024-08-15 19:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-15 19:08 Livingood, Jason [this message]
-- strict thread matches above, loose matches on Subject: below --
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
2024-08-18 19:32 ` Frantisek Borsik
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=97AF78A0-C4CE-456C-878A-D19D7A207736@comcast.com \
--to=jason_livingood@comcast.com \
--cc=dave.taht@gmail.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