From: Mike Conlow <mconlow@cloudflare.com>
To: "Network Neutrality is back! Let´s make the technical aspects
heard this time!" <nnagain@lists.bufferbloat.net>
Subject: Re: [NNagain] NN review in the UK
Date: Mon, 30 Oct 2023 11:12:21 -0400 [thread overview]
Message-ID: <CAMo6_mus83ZLukyVsTyLgqs9x8viSC95F9rX8xMV9r4kMsy=_A@mail.gmail.com> (raw)
In-Reply-To: <A5C936E2-BC75-4C89-BD32-80ADC2261977@comcast.com>
[-- Attachment #1.1: Type: text/plain, Size: 1374 bytes --]
+1. My understanding is the origins of this item in the NN review in the UK
is that ISPs requested it because of lack of clarity around whether
"premium quality service" offerings violated NN rules. See page 63-64 here
<https://www.ofcom.org.uk/__data/assets/pdf_file/0028/245926/net-neutrality-review.pdf>.
Screenshot below:
[image: Screenshot 2023-10-30 at 11.08.48 AM.png]
On Mon, Oct 30, 2023 at 10:26 AM Livingood, Jason via Nnagain <
nnagain@lists.bufferbloat.net> wrote:
> On 10/28/23, 06:01, "Nnagain on behalf of Sebastian Moeller via Nnagain"
> <nnagain-
> > For example, people who use high quality virtual reality applications
> may want to buy a premium quality service, while users who mainly stream
> and browse the internet can buy a cheaper package. Our updated guidance
> clarifies that ISPs can offer premium packages, for example offering low
> latency, as long as they are sufficiently clear to customers about what
> they can expect from the services they buy.
>
> Sigh. Wish more regulators knew about modern AQMs - we can have our cake
> and eat it too. The solution above seems to pre-suppose the need for QoS
> but this isn't a capacity problem.
>
> JL
>
> _______________________________________________
> Nnagain mailing list
> Nnagain@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/nnagain
>
[-- Attachment #1.2: Type: text/html, Size: 1933 bytes --]
[-- Attachment #2: Screenshot 2023-10-30 at 11.08.48 AM.png --]
[-- Type: image/png, Size: 230726 bytes --]
next prev parent reply other threads:[~2023-10-30 15:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-28 10:01 Sebastian Moeller
2023-10-30 14:26 ` Livingood, Jason
2023-10-30 15:12 ` Mike Conlow [this message]
2023-10-30 15:47 ` [NNagain] [EXTERNAL] " Livingood, Jason
2023-10-30 17:15 ` Mike Conlow
2023-10-30 15:55 ` [NNagain] " Sebastian Moeller
2023-10-31 16:33 ` Dave Taht
2023-10-31 17:37 ` Dave Taht
2023-10-31 18:00 ` Sebastian Moeller
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='CAMo6_mus83ZLukyVsTyLgqs9x8viSC95F9rX8xMV9r4kMsy=_A@mail.gmail.com' \
--to=mconlow@cloudflare.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