Network Neutrality is back! Let´s make the technical aspects heard this time!
 help / color / mirror / Atom feed
From: Mike Conlow <mconlow@cloudflare.com>
To: "Livingood, Jason" <jason_livingood@comcast.com>
Cc: "Network Neutrality is back! Let´s make the technical aspects
	heard this time!" <nnagain@lists.bufferbloat.net>
Subject: Re: [NNagain] [EXTERNAL] Re:  NN review in the UK
Date: Mon, 30 Oct 2023 13:15:18 -0400	[thread overview]
Message-ID: <CAMo6_mvuDK-MJ+c_bewCCCUstxo-FGFHsd6a_xhytiwT-RHVCQ@mail.gmail.com> (raw)
In-Reply-To: <ACBB2608-162A-4923-86BD-488AE4ADE8EB@comcast.com>


[-- Attachment #1.1: Type: text/plain, Size: 3591 bytes --]

I'm not aware of any regularly occurring congestion issues in the UK, and
the consultation didn't suggest there are such issues.

I agree it comes across as legacy thinking. "Because packages offering
different quality of service would require some traffic prioritisation
where there is network congestion" kind of says it all.

This is speculation, but perhaps what the ISPs had in mind when discussing
this with Ofcom were newer AQMs, but it was translated into the
consultation this way? Regardless, to my reading, they asked for, and were
granted, a clarification that says they could offer one service with known
congestion issues and another service (which costs more to the end user)
that routes around the congestion.




On Mon, Oct 30, 2023 at 11:47 AM Livingood, Jason <
jason_livingood@comcast.com> wrote:

> Thx for the pointer to that section. Seems like some legacy thinking in
> that the view is the network rather than edge needs to do the heavy lifting
> on congestion control. But maybe with UK leased access there’s routine
> daily congestion (not enough capacity)?
>
>
>
> Looking at 6.28 I don’t see why an ISP could not charge more for a low
> latency service if that service was delivered at the same best effort QoS
> as the baseline service – which is possible with current AQMs. Not knowing
> as much about UK regs – maybe that is the issue? That it is unclear whether
> there can be any price/feature differentiation for broadband services even
> at the same level of best effort QoS?
>
>
>
> JL
>
>
>
> *From: *Mike Conlow <mconlow@cloudflare.com>
> *Date: *Monday, October 30, 2023 at 11:14
> *To: *Network Neutrality is back! Let´s make the technical aspects heard
> this time! <nnagain@lists.bufferbloat.net>
> *Cc: *Jason Livingood <jason_livingood@comcast.com>
> *Subject: *[EXTERNAL] Re: [NNagain] NN review in the UK
>
>
>
> +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://urldefense.com/v3/__https:/www.ofcom.org.uk/__data/assets/pdf_file/0028/245926/net-neutrality-review.pdf__;!!CQl3mcHX2A!ErUN6Nq2hd-S88MFqYrqwFhfFKN93rTuYy_MrrQMvwrAUBC8kQ1ZpHnPt6_zuqhoVQJ1uK6IxZPFbU5BkJwTwLYDDg$>.
> Screenshot below:
>
>
>
>
>
> 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
> <https://urldefense.com/v3/__https:/lists.bufferbloat.net/listinfo/nnagain__;!!CQl3mcHX2A!ErUN6Nq2hd-S88MFqYrqwFhfFKN93rTuYy_MrrQMvwrAUBC8kQ1ZpHnPt6_zuqhoVQJ1uK6IxZPFbU5BkJwtGoJWVg$>
>
>

[-- Attachment #1.2: Type: text/html, Size: 5974 bytes --]

[-- Attachment #2: image001.png --]
[-- Type: image/png, Size: 230727 bytes --]

  reply	other threads:[~2023-10-30 17:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-28 10:01 [NNagain] " Sebastian Moeller
2023-10-30 14:26 ` Livingood, Jason
2023-10-30 15:12   ` Mike Conlow
2023-10-30 15:47     ` [NNagain] [EXTERNAL] " Livingood, Jason
2023-10-30 17:15       ` Mike Conlow [this message]
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_mvuDK-MJ+c_bewCCCUstxo-FGFHsd6a_xhytiwT-RHVCQ@mail.gmail.com \
    --to=mconlow@cloudflare.com \
    --cc=jason_livingood@comcast.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