From: Sebastian Moeller <moeller0@gmx.de>
To: David Lang <david@lang.hm>
Cc: "Livingood, Jason" <Jason_Livingood@comcast.com>,
Dave Taht via Starlink <starlink@lists.bufferbloat.net>,
dan <dandenson@gmail.com>, Jamal Hadi Salim <jhs@mojatatu.com>,
libreqos <libreqos@lists.bufferbloat.net>,
Rpm <rpm@lists.bufferbloat.net>,
bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] [Rpm] [Starlink] [LibreQoS] net neutrality back in the news
Date: Fri, 29 Sep 2023 08:24:13 +0200 [thread overview]
Message-ID: <E0D21168-2016-4A96-A56A-199EF8BE054A@gmx.de> (raw)
In-Reply-To: <5so3r00n-31pn-14s7-7775-08731s3s551r@ynat.uz>
Hi David,
> On Sep 29, 2023, at 00:19, David Lang via Rpm <rpm@lists.bufferbloat.net> wrote:
>
> On Thu, 28 Sep 2023, Livingood, Jason via Bloat wrote:
>
>> Date: Thu, 28 Sep 2023 20:48:58 +0000
>> From: "Livingood, Jason via Bloat" <bloat@lists.bufferbloat.net>
>> Reply-To: "Livingood, Jason" <Jason_Livingood@comcast.com>
>> To: dan <dandenson@gmail.com>, Dave Taht <dave.taht@gmail.com>
>> Cc: Rpm <rpm@lists.bufferbloat.net>,
>> Dave Taht via Starlink <starlink@lists.bufferbloat.net>,
>> bloat <bloat@lists.bufferbloat.net>,
>> libreqos <libreqos@lists.bufferbloat.net>,
>> Jamal Hadi Salim <jhs@mojatatu.com>
>> Subject: Re: [Bloat] [Starlink] [LibreQoS] [Rpm] net neutrality back in the
>> news
>>> dan <dandenson@gmail.com> wrote:
>>
>>> "(I assume most ISPs want happy customers)."
>
>>> made me laugh a little. 'Most' by quantity of businesses maybe, but 'most' in terms of customers being served by puts the Spectrums and Comcasts in the mix (in the US) and they don't care about happy customers they care about defacto monopolies in markets so that they don't have to care about happy customers.
>>
>> In that context, happy customers stay longer (less churn) and spend more (upgrades, multiple services). And unhappy customers generate costs via disconnects (loss of revenue, costs to replace them with a new customer to just stay at the same subscriber levels), and costs via customer contacts (call center staff).
>
> Except when you have a monopoly in an area, at which point the ability of customers to leave is minimal, and years of bad customer service means that people don't bother complaining, so the call center staffing costs are lower than they should be.
>
>>> For the last mile, I'm actually less concerned with pure NN and more concerned with no-blocking or 'brand' prioritization and required/label transparency...
>>
>> The two thoughts your comments (thanks for the response BTW!) trigger are:
>
>> 1 - Often regulation looks to the past - in this case maybe an era of bandwidth scarcity where prioritization may have mattered. I think we're in the midst of a shift into bandwidth abundance where priority does not matter. What will is latency/responsiveness, content/compute localization, reliability, consistency, security, etc.
>
>> 2 - If an ISP blocked YouTube or Netflix, they'd incur huge customer care (contact) costs and would see people start to immediately shift to competitors (5G FWA, FTTP or DOCSIS, WISP, Starlink/LEO, etc.). It just does not seem like something that could realistically happen any longer in the US.
>
> Dave T called out earlier that the rise of bittorrent was a large part of the inital NN discussion here in the US. But a second large portion was a money grab from ISPs thinking that they could hold up large paid websites (netflix for example) for additional fees by threatening to make their service less useful to their users (viewing their users as an asset to be marketed to the websites rather than customers to be satisfied by providing them access to the websites)
>
> I don't know if a new round of "it's not fair that Netflix doesn't pay us for the bandwidth to service them" would fall flat at this point or not.
[SM] In the EU we have this as a continuous lobbying effort by big incumbent ISPs (a move to have the large content providers (CAPs) shoulder their "fair" share of the cost of modernizing the networks*), why this flys with at least some EU politicians is that the intended payees of this scheme are all located outside the EU and hence will have little support by the EU citizenry... (The latter is IMHO not fully undeserved either, the days of "do no evil" are long behind us and big tech often forgets that we are all in this together, but I digress). In the EU one of these days such an effort might actually succeed, as much as I dislike this.
*) This argument about fairness is indeed made by the same ISPs that already charge their eye-ball customers for the same capacity they say they need to built with particpatoin of the CAPs
>
> David Lang_______________________________________________
> Rpm mailing list
> Rpm@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/rpm
next prev parent reply other threads:[~2023-09-29 6:27 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-27 18:21 [Bloat] " Dave Taht
2023-09-28 3:33 ` [Bloat] [Rpm] " rjmcmahon
2023-09-28 6:06 ` Dave Taht
2023-10-01 17:08 ` [Bloat] [Starlink] " Sebastian Moeller
2023-10-05 19:22 ` Dave Taht
2023-09-28 6:25 ` [Bloat] " Sebastian Moeller
[not found] ` <ZRUe_5uiRJyDxb9Z@Space.Net>
2023-09-28 7:14 ` [Bloat] [Starlink] " Sebastian Moeller
[not found] ` <ZRUsLalRicJpQoXH@Space.Net>
2023-09-28 7:38 ` Sebastian Moeller
2023-09-28 16:38 ` [Bloat] " Dave Taht
2023-09-28 16:52 ` [Bloat] [Starlink] " Livingood, Jason
2023-09-28 17:04 ` [Bloat] [Rpm] [Starlink] " rjmcmahon
2023-09-28 19:31 ` [Bloat] [Rpm] " Sebastian Moeller
2023-09-28 19:39 ` Dave Taht
2023-09-28 20:08 ` [Bloat] [LibreQoS] " dan
2023-09-28 20:18 ` Dave Taht
2023-09-29 19:00 ` [Bloat] Getting Google to index. was:Re: [Starlink] " Rodney W. Grimes
2023-09-28 20:36 ` [Bloat] " Jeremy Austin
2023-09-28 20:54 ` Livingood, Jason
2023-09-28 20:48 ` [Bloat] [Starlink] " Livingood, Jason
2023-09-28 22:19 ` David Lang
2023-09-29 4:54 ` Jonathan Morton
2023-09-29 12:28 ` [Bloat] [Rpm] [Starlink] [LibreQoS] " Rich Brown
2023-09-29 16:15 ` dan
2023-09-30 12:00 ` Frantisek Borsik
2023-09-30 12:19 ` Sebastian Moeller
2023-09-30 12:42 ` [Bloat] [Starlink] [Rpm] " Vint Cerf
2023-09-30 14:07 ` Sebastian Moeller
2023-09-30 14:28 ` [Bloat] [Rpm] [Starlink] " Jan Ceuleers
2023-09-30 14:35 ` Sebastian Moeller
2023-09-30 14:41 ` Mike Conlow
2023-09-30 15:20 ` Sebastian Moeller
2023-09-30 15:23 ` [Bloat] [LibreQoS] [Rpm] [Starlink] " Dave Taht
2023-09-30 17:35 ` Dave Taht
2023-09-30 21:57 ` [Bloat] New email list: NNagain for network neutrality Dave Taht
2023-10-04 22:19 ` [Bloat] [Rpm] [Starlink] [LibreQoS] net neutrality back in the news Michael Richardson
2023-09-29 6:24 ` Sebastian Moeller [this message]
[not found] ` <ZRZvMLtKhkd6-16m@Space.Net>
2023-09-29 7:07 ` [Bloat] [Starlink] [Rpm] " Sebastian Moeller
2023-09-28 22:25 ` [Bloat] [LibreQoS] [Rpm] " David Lang
2023-09-28 17:10 ` [Bloat] " Livingood, Jason
2023-09-28 19:30 ` Dave Taht
2023-09-28 20:05 ` Sebastian Moeller
2023-09-28 21:07 ` [Bloat] [EXTERNAL] " Livingood, Jason
2023-09-28 21:08 ` Livingood, Jason
2023-09-29 8:56 ` Erik Auerswald
2023-09-29 15:19 [Bloat] [Rpm] [Starlink] [LibreQoS] " Livingood, Jason
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/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E0D21168-2016-4A96-A56A-199EF8BE054A@gmx.de \
--to=moeller0@gmx.de \
--cc=Jason_Livingood@comcast.com \
--cc=bloat@lists.bufferbloat.net \
--cc=dandenson@gmail.com \
--cc=david@lang.hm \
--cc=jhs@mojatatu.com \
--cc=libreqos@lists.bufferbloat.net \
--cc=rpm@lists.bufferbloat.net \
--cc=starlink@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