From: Sebastian Moeller <moeller0@gmx.de>
To: thejoff@mail.com,
"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: Wed, 18 Oct 2023 10:00:33 +0200 [thread overview]
Message-ID: <30B37F02-FF93-4551-B9A7-096F1727B81C@gmx.de> (raw)
In-Reply-To: <CAO-LeMw4oZ=2MQWH6tLKzexhR2cG-6946g4B7AsFcsUMB7CqWA@mail.gmail.com>
Hi Mr. Photons
> On Oct 18, 2023, at 09:08, le berger des photons via Nnagain <nnagain@lists.bufferbloat.net> wrote:
>
> but an ISP and its clients should be able to agree together on anything which they feel works for them. The only rule that I see that should apply is that there should be proper disclosure. This rule already exists. It is contract law. All of this regulation would make it impossible for an Isp and its customers to do something that they all WANT to do.
[SM] At the heart of the NN dispute is, that some ISPs clearly did something only they wanted to do and which their customers disagreed with. This does not apply to all ISPs and all customers, but there clearly was abuse and hence reactive regulation... if the market players do not behave well enough by themselves, they risk the referee stepping in, so business as usual.
>
> That would be like them deciding to dump their waste oil all over the ground IF they had their own planet. Though that would be perhaps stupid, all of the affected people agree to it, they should be able to do it. It's THEIR planet!
[SM] This approach might work for agreements between equal partners, but history/experience shows that if one side has considerably more leverage it is likely to abuse that leverage. There is a reason why most human societies implement some "fairness" rules and try to enforce those. (Often "fairness" is restricted to small subsets of the population, but still the principle itself seems universal or terran).
Regards
Sebastian
>
> On Tue, Oct 17, 2023 at 4:45 PM 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
> _______________________________________________
> Nnagain mailing list
> Nnagain@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/nnagain
prev parent reply other threads:[~2023-10-18 8:00 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
2023-10-17 17:14 ` Spencer Sevilla
2023-10-18 7:08 ` le berger des photons
2023-10-18 8:00 ` Sebastian Moeller [this message]
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=30B37F02-FF93-4551-B9A7-096F1727B81C@gmx.de \
--to=moeller0@gmx.de \
--cc=nnagain@lists.bufferbloat.net \
--cc=thejoff@mail.com \
/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