Network Neutrality is back! Let´s make the technical aspects heard this time!
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: "Network Neutrality is back! Let´s make the technical aspects
	heard this time!" <nnagain@lists.bufferbloat.net>
Cc: Ronan Pigott <ronan@rjp.ie>
Subject: Re: [NNagain] Net neutrality and Bufferbloat?
Date: Fri, 15 Dec 2023 15:31:49 -0800	[thread overview]
Message-ID: <CAA93jw5iqGydNvn1hvztVwoegazA+Y07vmbu2LtuYq58E6GyaQ@mail.gmail.com> (raw)
In-Reply-To: <b25de682b71af4b429324a19ce4ae2ead10c8e06@rjp.ie>

On Fri, Dec 15, 2023 at 3:12 PM Ronan Pigott via Nnagain
<nnagain@lists.bufferbloat.net> wrote:
>
> 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?

I quoted from a cable industry insider on that (2013) and at the time,
I too thought that the technology was so new that any number of
objections could be raised to it. Queuing remains ill-industood in
general, the pain points and misunderstandings that fueled the
bitorrent vs voip debacle, still present.

We've since cracked a few billion instances of fq_codel, so... tI long
ago stopped worrying a regulator would take an interest (except
perhaps in helping further deployment!), and even the pro-NN side,
places like public knowledge, have acknowledged the benefit, but it
has taken a huge educational and deployment process to get to where we
are today.

At the time I could hardly imagine the technology to be as successful
as it has been either (apple and linux defaults), and yet I keep
hoping to see deployments where it is needed most, on our wireless
technologies. fq_codel on 5G or starlink would be nice to see next
year!

>
> 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?

We have done extensive surveys of US and some european law here, and
the consensus appears to be that so long as it is an application
class, not a specific service from a specific provider being boosted
or not, "reasonable network management" suffices.

> 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
> _______________________________________________
> Nnagain mailing list
> Nnagain@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/nnagain



-- 
:( My old R&D campus is up for sale: https://tinyurl.com/yurtlab
Dave Täht CSO, LibreQos

  reply	other threads:[~2023-12-15 23:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-11 23:55 Ronan Pigott
2023-12-15 23:31 ` Dave Taht [this message]
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=CAA93jw5iqGydNvn1hvztVwoegazA+Y07vmbu2LtuYq58E6GyaQ@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=nnagain@lists.bufferbloat.net \
    --cc=ronan@rjp.ie \
    /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