From: Jeremy Austin <jeremy@aterlo.com>
To: "Network Neutrality is back! Let´s make the technical aspects
heard this time!" <nnagain@lists.bufferbloat.net>
Subject: Re: [NNagain] Small ISP Carve Out
Date: Tue, 17 Oct 2023 08:42:10 -0800 [thread overview]
Message-ID: <CACw=56LB4gH=DJnnbg6pbpXJKL16SPtkZXaPHkmjijxZOLRHeQ@mail.gmail.com> (raw)
In-Reply-To: <7FAB46F4-EA85-446F-BCC0-B79C03E0C11D@comcast.com>
[-- Attachment #1: Type: text/plain, Size: 2143 bytes --]
IMO the argument in seeking additional forbearance is that if all ISPs, no
matter the size, have a similar minimum burden of regulatory filing and
that burden is large, it acts as a barrier to entry. In a perfect world the
rules can apply to all sizes of ISPs *and* not be burdensome.
To keep this on topic, why is Title II (the burden WISPA rejects, not
necessarily the Net Neutrality goals TII espouses) the only way to achieve
NN?
On a related note, I observe that neither WISPA nor NTCA have weighed in on
neutrality per se. When I spoke to David Zumwalt last week in Vegas
(current WISPA President/CEO) he was surprised to hear that there are ISPs
and vendors active in the wireless and small fiber provider markets that
are actively advocating for, selling and deploying non-net-neutral traffic
management solutions. Perhaps WISPA is avoiding taking a stance on pure NN
ideals.
$boilerplate not necessarily the opinions of my employer and/or ancestors,
Jeremy
On Tue, Oct 17, 2023 at 6:45 AM Livingood, Jason via Nnagain <
nnagain@lists.bufferbloat.net> wrote:
> “Small Broadband Providers Urge FCC to Leave Them Out of Some Net
> Neutrality Rules” See
> https://broadbandbreakfast.com/2023/10/small-broadband-providers-urge-fcc-to-leave-them-out-of-some-net-neutrality-rules/.
> My personal opinion is any rules should apply to all providers. After all,
> my locally-owned small car mechanic does not get to opt out of EPA rules
> for used motor oil disposal since they are small and have 4 employees and
> small organic farms don’t get to opt out of food safety rules or labeling.
>
>
>
> JL
>
>
>
>
> _______________________________________________
> Nnagain mailing list
> Nnagain@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/nnagain
>
--
--
Jeremy Austin
Sr. Product Manager
Preseem | Aterlo Networks
preseem.com
Book a Call: https://app.hubspot.com/meetings/jeremy548
Phone: 1-833-733-7336 x718
Email: jeremy@preseem.com
Stay Connected with Newsletters & More:
*https://preseem.com/stay-connected/* <https://preseem.com/stay-connected/>
[-- Attachment #2: Type: text/html, Size: 4339 bytes --]
next prev parent reply other threads:[~2023-10-17 16:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-17 14:45 Livingood, Jason
2023-10-17 16:42 ` Jeremy Austin [this message]
2023-10-17 17:14 ` Spencer Sevilla
2023-10-18 7:08 ` le berger des photons
2023-10-18 8: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='CACw=56LB4gH=DJnnbg6pbpXJKL16SPtkZXaPHkmjijxZOLRHeQ@mail.gmail.com' \
--to=jeremy@aterlo.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