Network Neutrality is back! Let´s make the technical aspects heard this time!
 help / color / mirror / Atom feed
From: "Ronan Pigott" <ronan@rjp.ie>
To: nnagain@lists.bufferbloat.net
Subject: [NNagain] Net neutrality and Bufferbloat?
Date: Mon, 11 Dec 2023 23:55:24 +0000	[thread overview]
Message-ID: <b25de682b71af4b429324a19ce4ae2ead10c8e06@rjp.ie> (raw)

Hi,

I read the recent NOI response and it sparked my interest in the relationship
between Net Neutrality and bufferbloat. I also found [1] which makes it seem
Net Neutrality is an obstacle to solving bufferbloat in the US, at least. I'm
just curious about the legal obstacles to bufferbloat solutions in the US. I
tried reading the FCC rules which I understand changed in 2010, 2014, and 2017
but theye're kinda vague I think and I am no lawyer nor industry veteran and
don't think I really understand the implications.

In particular, [1] claims:

> Misapplied concepts of network neutrality is one of the things that killed
> fq codel for DOCSIS 3.1

Does anyone know more about this?

When looking around, I found more similar claims [2]:

> Finally, some jurisdictions impose regulations that limit the ability of
> networks to provide differentiation of services, in large part this seems to
> be based on the belief that doing so necessarily involves prioritization or
> privileged access to bandwidth, and thus a benefit to one class of traffic
> always comes at the expense of another.

Anyone know what regulations the authors mean here?

I personally run openwrt+sqm/cake in my home router and have found it to be
effective, so I am convinced of the value of sqm. Is Net Neutrality regulation
an obstacle to wider deployment?

[1] https://blog.cerowrt.org/post/net_neutrality_customers/
[2] https://datatracker.ietf.org/doc/draft-ietf-tsvwg-nqb/

Thanks,

Ronan

             reply	other threads:[~2023-12-11 23:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-11 23:55 Ronan Pigott [this message]
2023-12-15 23:31 ` Dave Taht
2023-12-17  1:00 ` Ronan Pigott
2023-12-18 15:10 ` Livingood, Jason
2023-12-18 15:23   ` Sebastian Moeller
2023-12-18 20:51     ` Dick Roy
2023-12-18 21:55       ` 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=b25de682b71af4b429324a19ce4ae2ead10c8e06@rjp.ie \
    --to=ronan@rjp.ie \
    --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