From: Mark Steckel <mjs@phillywisper.net>
To: "\"Network Neutrality is back! Let´s make the technical aspects
heard this time!\"" <nnagain@lists.bufferbloat.net>
Subject: Re: [NNagain] On "Throttling" behaviors
Date: Mon, 02 Oct 2023 10:51:20 -0400 [thread overview]
Message-ID: <18af0df4e0b.edb34c95711106.5401229236188491451@phillywisper.net> (raw)
In-Reply-To: <6753C846-DD37-434B-9A07-8EFE4FEE7AF6@cable.comcast.com>
Adding to some of the points that Sebastian made that I largely agree with.
Some of the big ISPs own or are affiliated with content creation and/or distribution companies. AT&T owns Time-Warner, Comcast owns NBC and produces TV shows and movies. Some other large ISPs have done deals with content providers to provide the content over their network. These latter deals are a source of revenue of the ISPs and a way for the content owners to juice the distribution and audience for their content.
In both cases it is rational for the ISPs to favor this content over other content. This can be done by zero tier ratings, throttling, etc.
All this is nearly identical to the rail road industry during the 1800's (at least in the US). One example: A rail road company became involved with a coal mining organization. The Rail road company then decided to disfavor a competing coal mining company by charging more and slowing traffic. There are many examples of this from the rail roads in the 1800's. Everyone was against this except for the companies that profited from it. Laws and regulations were created to force the rails roads to be "common carriers" (as defined in the US). [Apparently the term "common carrier" has a different meaning in Europe.]
It is reasonable to expect that large corporate ISPs will act in their self interest, and in ways that harm the public.
While there are numerous issues around NN, the core of it starts with whether the public and companies that use the Internet are entitled to transparent, fair and and equal access to the Internet. It is not about whether things like VOIP traffic is prioritized, that is a distraction IMO. It's about whether an ISP can favor traffic to their benefit in ways that hurts consumers and other businesses.
The experience with the rail road industry (at least in the US) provides a clear example of the abuses that occur when a company owns a choke point and decides they will exploit it.
And finally, a few years before bittorrent brought a lot of these issues to the foreground Michael Powell (son of Colin Powell) was the chair of the FCC (appointed by pres Clinton). The cable companies had started providing Internet service over their cables during the 90's and had started looking at providing phone service. The Internet started with the traditional phone companies which were regulated under Title II. The cable companies did not want to be similarly regulated so Powell got the FCC to declare that Internet was an "informational service" which put it in a separate category which did not fall under Title II. The gist of this is Title II concerns about the Internet started well before bittorrent and bufferbloat entered the picture.
---- On Mon, 02 Oct 2023 09:43:40 -0400 Livingood, Jason via Nnagain wrote ---
> From: Nnagain nnagain-bounces@lists.bufferbloat.net> on behalf of Patrick Maupin via Nnagain nnagain@lists.bufferbloat.net>
>
> > If there are no would-be bad actors, no regulation is needed. But if there are would-be bad actors, then they will attempt to be instrumental in shaping any new regulations, and many of the presumed would-be
> bad actors have time, money, and histories of securing significant face time with regulatory agencies such as the FCC.
>
> Often the ‘bad actor’ is really just a ‘dumb actor’ that did something without thinking it through fully or understanding root causes, secondary effects of a network change, etc. In our industry (writ large)
> it seems like 99% of the negative stuff can be ascribed to mistakes/lack of foresight/incorrect root cause analysis/etc and 1% is due to some ‘evil genius plan’. ;-)
>
> _______________________________________________
> Nnagain mailing list
> Nnagain@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/nnagain
>
next prev parent reply other threads:[~2023-10-02 14:51 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-01 17:15 [NNagain] Some backstory on the nn-again mailing list Dave Taht
2023-10-01 18:56 ` Frantisek Borsik
2023-10-01 19:51 ` [NNagain] On "Throttling" behaviors Dave Taht
2023-10-01 20:50 ` Dave Cohen
2023-10-01 22:01 ` Patrick Maupin
2023-10-02 1:34 ` dan
2023-10-02 7:28 ` Sebastian Moeller
2023-10-02 16:29 ` dan
2023-10-04 7:30 ` Sebastian Moeller
2023-10-02 15:30 ` Andy Ringsmuth
2023-10-02 18:28 ` Nathan Loofbourrow
2023-10-02 20:34 ` Colin_Higbie
2023-10-02 21:04 ` Dave Cohen
2023-10-02 21:07 ` rjmcmahon
2023-10-02 21:43 ` Colin_Higbie
2023-10-02 21:55 ` rjmcmahon
2023-10-03 19:29 ` Colin_Higbie
2023-10-03 19:45 ` rjmcmahon
2023-10-04 0:57 ` David Lang
2023-10-03 7:50 ` Sebastian Moeller
2023-10-03 8:10 ` Karl Auerbach
2023-10-03 14:41 ` Sebastian Moeller
2023-10-03 15:34 ` dan
2023-10-03 16:54 ` rjmcmahon
2023-10-03 17:55 ` Sebastian Moeller
2023-10-03 18:09 ` Frantisek Borsik
2023-10-03 18:14 ` dan
2023-10-03 19:44 ` Dick Roy
2023-10-03 18:10 ` dan
2023-10-03 19:23 ` rjmcmahon
2023-10-04 1:05 ` David Lang
2023-10-04 0:39 ` David Lang
2023-10-03 20:26 ` Colin_Higbie
2023-10-03 21:40 ` dan
2023-10-04 15:56 ` Colin_Higbie
2023-10-04 17:45 ` David Lang
2023-10-05 20:24 ` Livingood, Jason
2023-10-05 22:17 ` Dick Roy
2023-10-05 22:47 ` Jeremy Austin
2023-10-05 22:53 ` Dave Cohen
2023-10-06 15:56 ` Dick Roy
2023-10-06 15:58 ` rjmcmahon
2023-10-04 17:59 ` rjmcmahon
2023-10-04 19:26 ` Dick Roy
[not found] ` <MN2PR16MB3391A66B0DC222C43664DAD6F1CBA@MN2PR16MB3391.namprd16.prod.outlook.com>
2023-10-05 8:44 ` Sebastian Moeller
2023-10-05 19:07 ` David Lang
2023-10-03 23:17 ` Mark Steckel
2023-10-04 7:51 ` Sebastian Moeller
2023-10-02 6:48 ` Sebastian Moeller
2023-10-02 13:43 ` Livingood, Jason
2023-10-02 14:51 ` Mark Steckel [this message]
2023-10-02 18:09 ` Livingood, Jason
2023-10-02 18:15 ` Patrick Maupin
2023-10-02 19:18 ` Dick Roy
2023-10-02 6:34 ` Sebastian Moeller
2023-10-02 13:27 ` Livingood, Jason
2023-10-02 6:06 ` [NNagain] Some backstory on the nn-again mailing list Sebastian Moeller
2023-10-02 12:36 ` Bless, Roland (TM)
2023-10-03 7:15 ` Sebastian Moeller
2023-10-02 20:18 [NNagain] On "Throttling" behaviors Livingood, Jason
2023-10-02 20:28 ` Dick Roy
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=18af0df4e0b.edb34c95711106.5401229236188491451@phillywisper.net \
--to=mjs@phillywisper.net \
--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