From: Michael Richardson <mcr@sandelman.ca>
To: Mike Conlow <mconlow@cloudflare.com>,
Sebastian Moeller <moeller0@gmx.de>,
Rpm <rpm@lists.bufferbloat.net>, dan <dandenson@gmail.com>,
Frantisek Borsik <frantisek.borsik@gmail.com>,
libreqos <libreqos@lists.bufferbloat.net>,
Jamal Hadi Salim <jhs@mojatatu.com>,
Dave Taht via Starlink <starlink@lists.bufferbloat.net>,
bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Rpm] [Bloat] [Starlink] [LibreQoS] net neutrality back in the news
Date: Wed, 04 Oct 2023 18:19:06 -0400 [thread overview]
Message-ID: <4545.1696457946@localhost> (raw)
In-Reply-To: <CAMo6_mstw1tKjZfonQ=3Zc5TNqrffkEiUEXzCxLUf85o3kJs9A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2295 bytes --]
Mike Conlow via Bloat <bloat@lists.bufferbloat.net> wrote:
> As I read this thread and think about the coming debate in the U.S., two
> things come to mind:
> 1. Ofcom is considering
> <https://www.ofcom.org.uk/consultations-and-statements/category-1/net-neutrality-review>
> a net neutrality "clarification". The first topic in the consultation is
> whether ISPs should be allowed to offer "premium quality retail plans". It
> doesn't specify the technical implementation, but there would be different
> plans for "users who mainly stream" vs "people who use high quality
> virtual reality applications". Apparently ISPs feel the existing NN rules
> are not clear on whether this is allowed.
> The question I'm thinking about is do we want an Internet where end user
> plans are divided up this way? And if not, is a NN regulation the right
> place to put those rules?
Network Neutrality means that all senders are treated the same by the *ISP*
The ISP doesn't get to decide to prefer some peers over others.
It doesn't mean that the customer can't be given controls to determine what
traffic they want, and what priority they want to give it.
I think those two categories are totally bonkers. I would never want to
subscribe to either service plan, because clearly the ISP thinks they can
just offload bufferbloat. We've had protocols to classify traffic for
decades, but ISPs couldn't be bothered to figure out how to sell that.
> 2. To the point in the PS of the below email, I would agree things are
> mostly working in the EU, and in the US. But things
> <https://twitter.com/j0xaf/status/850081406277619712> are
What's twitter?
> Are NN rules the right place to address this and make sure it doesn't
> happen in the US? Or is one bad actor across the EU and US the cost of
> doing business and the Internet ecosystem and "market" are *mostly* solving
> the issue?
The EU bureaucrats are mostly lost in some fantasy land.
I don't think it will end well.
--
] Never tell me the odds! | ipv6 mesh networks [
] Michael Richardson, Sandelman Software Works | IoT architect [
] mcr@sandelman.ca http://www.sandelman.ca/ | ruby on rails [
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 511 bytes --]
next prev parent reply other threads:[~2023-10-05 18:53 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-27 18:21 [Rpm] " Dave Taht
2023-09-28 3:33 ` rjmcmahon
2023-09-28 6:06 ` Dave Taht
2023-10-01 17:08 ` [Rpm] [Starlink] " Sebastian Moeller
2023-10-05 19:22 ` Dave Taht
2023-09-28 6:25 ` [Rpm] " Sebastian Moeller
2023-09-28 6:36 ` [Rpm] [Starlink] " Gert Doering
2023-09-28 7:14 ` Sebastian Moeller
2023-09-28 7:33 ` Gert Doering
2023-09-28 7:38 ` Sebastian Moeller
2023-09-28 16:38 ` [Rpm] " Dave Taht
2023-09-28 16:52 ` [Rpm] [Starlink] " Livingood, Jason
2023-09-28 17:04 ` rjmcmahon
2023-09-28 19:31 ` [Rpm] " Sebastian Moeller
2023-09-28 19:39 ` Dave Taht
2023-09-28 20:08 ` [Rpm] [LibreQoS] " dan
2023-09-28 20:18 ` Dave Taht
2023-09-29 19:00 ` [Rpm] Getting Google to index. was:Re: [Starlink] " Rodney W. Grimes
2023-09-28 20:36 ` [Rpm] " Jeremy Austin
2023-09-28 20:54 ` [Rpm] [Bloat] " Livingood, Jason
2023-09-28 20:48 ` [Rpm] [Starlink] " Livingood, Jason
2023-09-28 22:19 ` [Rpm] [Bloat] " David Lang
2023-09-29 4:54 ` Jonathan Morton
2023-09-29 12:28 ` Rich Brown
2023-09-29 16:15 ` dan
2023-09-30 12:00 ` Frantisek Borsik
2023-09-30 12:19 ` Sebastian Moeller
2023-09-30 12:42 ` [Rpm] [Starlink] [Bloat] " Vint Cerf
2023-09-30 14:07 ` Sebastian Moeller
[not found] ` <CAMo6_mstw1tKjZfonQ=3Zc5TNqrffkEiUEXzCxLUf85o3kJs9A@mail.gmail.com>
2023-09-30 15:20 ` [Rpm] [Bloat] [Starlink] " Sebastian Moeller
2023-09-30 15:23 ` [Rpm] [LibreQoS] [Bloat] [Starlink] " Dave Taht
2023-09-30 17:35 ` Dave Taht
2023-09-30 21:57 ` [Rpm] New email list: NNagain for network neutrality Dave Taht
2023-10-04 22:19 ` Michael Richardson [this message]
2023-09-29 6:24 ` [Rpm] [Bloat] [Starlink] [LibreQoS] net neutrality back in the news Sebastian Moeller
2023-09-29 6:31 ` [Rpm] [Starlink] [Bloat] " Gert Doering
2023-09-29 7:07 ` Sebastian Moeller
2023-09-28 22:25 ` [Rpm] " David Lang
2023-09-28 17:10 ` [Rpm] [Bloat] " Livingood, Jason
2023-09-28 19:30 ` Dave Taht
2023-09-28 20:05 ` Sebastian Moeller
2023-09-28 21:07 ` [Rpm] [EXTERNAL] " Livingood, Jason
2023-09-28 21:08 ` Livingood, Jason
2023-09-29 8:56 ` [Rpm] [Bloat] [EXTERNAL] " Erik Auerswald
2023-09-29 13:16 [Rpm] [Bloat] [Starlink] [LibreQoS] " Livingood, Jason
2023-09-29 15:19 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/rpm.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4545.1696457946@localhost \
--to=mcr@sandelman.ca \
--cc=bloat@lists.bufferbloat.net \
--cc=dandenson@gmail.com \
--cc=frantisek.borsik@gmail.com \
--cc=jhs@mojatatu.com \
--cc=libreqos@lists.bufferbloat.net \
--cc=mconlow@cloudflare.com \
--cc=moeller0@gmx.de \
--cc=rpm@lists.bufferbloat.net \
--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