[NNagain] On "Throttling" behaviors

[Patrick Maupin]

> That is likely why I think industry writ large agrees with the notion of
no blocking/throttling/prioritization.

In that case, there should be no problems with getting agreement with
properly worded transparency and behavioral regulations.  It will be
interesting to see how this plays out in the real world.

On Mon, Oct 2, 2023 at 1:10 PM Livingood, Jason via Nnagain <
nnagain at lists.bufferbloat.net> wrote:

> On 10/2/23, 10:51, "Nnagain on behalf of Mark Steckel via Nnagain" <
> nnagain-bounces at lists.bufferbloat.net <mailto:
> nnagain-bounces at lists.bufferbloat.net> on behalf of
> nnagain at lists.bufferbloat.net <mailto:nnagain at lists.bufferbloat.net>>
> wrote:
>
> > 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.
>
> What I have observed in practice is the businesses of connectivity and
> content are separately run & tend to act with a very high degree of
> independence. To take the example of throttling - all that would do is (1)
> prompt customer contacts - driving cost to the ISP, or (2) prompt churn -
> also driving cost + reducing revenue. My personal view is that the whole
> notion of throttling streaming video (or whatever) is a non-issue to any
> large ISP. That is why I think there is consensus support for 'no
> throttling or blocking' in the ISP community.
>
> > 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.
>
> That is likely why I think industry writ large agrees with the notion of
> no blocking/throttling/prioritization.
>
> JL
>
> _______________________________________________
> Nnagain mailing list
> Nnagain at lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/nnagain
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.bufferbloat.net/pipermail/nnagain/attachments/20231002/d48e1194/attachment.html>