From: Dave Taht <dave.taht@gmail.com>
To: Sebastian Moeller <moeller0@gmx.de>
Cc: "Network Neutrality is back! Let´s make the technical aspects
heard this time!" <nnagain@lists.bufferbloat.net>,
"Livingood, Jason" <jason_livingood@comcast.com>
Subject: Re: [NNagain] nn back in the news
Date: Thu, 15 Aug 2024 10:05:55 -0700 [thread overview]
Message-ID: <CAA93jw5L=wdTBF21w3R8Frb4yD_WTOSa5q_HqKvHGVViP=bW-w@mail.gmail.com> (raw)
In-Reply-To: <47247967-DA81-4F5C-A471-767C4C721095@gmx.de>
[-- Attachment #1: Type: text/plain, Size: 4875 bytes --]
and in other news today:
https://www.theregister.com/2024/08/15/google_monopoly_fix/
I kind of wish would-be regulators to try and block google IPs and see how
good their web experience is - everything from fonts to css leads back to
goog. I am reminded of the bell telephone breakup where folk still didn't
have touchtone...
On Thu, Aug 15, 2024 at 8:58 AM Sebastian Moeller <moeller0@gmx.de> wrote:
> Hi Dave,
>
> On 15 August 2024 16:16:52 CEST, Dave Taht via Nnagain <
> nnagain@lists.bufferbloat.net> wrote:
> >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'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,
>
> [SM] So I believe/think that we need (or rather I need to convince my
> National Regulatory Agency that mandating a OWD to a national reference
> point <150ms, so an RTT <= 300ms) some clear study showing the effect of
> loaded latency/jitter on some measurable variable of obvious relevance.
> That is, I think we should make a scientifically backed claim that shitty
> latency causes shitty productivity. We as a group IMHO intuitively seem to
> accept that as a given (based on some evidence), but to convince regulators
> we need better examples then e.g. L4S' on-line switching between different
> live camera feeds, or showing that page completion time scales linearly
> with latency...
> Stuart's, remote desktop example might serve as good starting point, if we
> can show that productivity suffers significantly as a function of latency
> and jitter. I mention abstract productivity simply because I believe making
> remote work more efficient would be a case in the public's interest and
> hence might catch the regulator's attention.
> So if anybody on this list has an idea for an experiment or better yet an
> already existing paper describing such an experiment, that would be great.
>
>
>
> 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
> >
> >
> >On Thu, Aug 15, 2024 at 6:27 AM Livingood, Jason <
> >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> on behalf of
> Dave
> >> Taht via Nnagain <nnagain@lists.bufferbloat.net>
> >> *Reply-To: *Network Neutrality is back! Let´s make the technical aspects
> >> heard this time! <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>
> >> *Cc: *Dave Taht <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
> >>
> >
> >
>
> --
> Sent from my Android device with K-9 Mail. Please excuse my brevity.
>
--
Artists/Musician Campout Aug 9-11
https://www.eventbrite.com/e/healing-arts-event-tickets-928910826287
Dave Täht CSO, LibreQos
[-- Attachment #2: Type: text/html, Size: 7182 bytes --]
next prev parent reply other threads:[~2024-08-15 17: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 [this message]
2024-08-15 18:06 ` Jack Haverty
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='CAA93jw5L=wdTBF21w3R8Frb4yD_WTOSa5q_HqKvHGVViP=bW-w@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=jason_livingood@comcast.com \
--cc=moeller0@gmx.de \
--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