From: David Lang <david@lang.hm>
To: "Livingood, Jason" <Jason_Livingood@comcast.com>
Cc: dan <dandenson@gmail.com>, Dave Taht <dave.taht@gmail.com>,
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: [Starlink] [Bloat] [LibreQoS] [Rpm] net neutrality back in the news
Date: Thu, 28 Sep 2023 15:19:28 -0700 (PDT) [thread overview]
Message-ID: <5so3r00n-31pn-14s7-7775-08731s3s551r@ynat.uz> (raw)
In-Reply-To: <E267D7FF-E5A5-476B-AEE6-6CC73632480C@cable.comcast.com>
[-- Attachment #1: Type: text/plain, Size: 3155 bytes --]
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.
David Lang
next prev parent reply other threads:[~2023-09-28 22:19 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-27 18:21 [Starlink] " Dave Taht
2023-09-28 3:33 ` [Starlink] [Rpm] " rjmcmahon
2023-09-28 6:06 ` Dave Taht
2023-10-01 17:08 ` Sebastian Moeller
2023-10-05 19:22 ` Dave Taht
2023-09-28 6:25 ` Sebastian Moeller
2023-09-28 6:36 ` Gert Doering
2023-09-28 7:14 ` Sebastian Moeller
2023-09-28 7:33 ` Gert Doering
2023-09-28 7:38 ` Sebastian Moeller
2023-09-28 16:38 ` Dave Taht
2023-09-28 16:52 ` Livingood, Jason
2023-09-28 17:04 ` rjmcmahon
2023-09-28 19:31 ` Sebastian Moeller
2023-09-28 19:39 ` Dave Taht
2023-09-28 20:08 ` [Starlink] [LibreQoS] " dan
2023-09-28 20:18 ` Dave Taht
2023-09-29 19:00 ` [Starlink] Getting Google to index. was:Re: " Rodney W. Grimes
2023-09-28 20:36 ` [Starlink] " Jeremy Austin
2023-09-28 20:54 ` [Starlink] [Bloat] " Livingood, Jason
2023-09-28 20:48 ` [Starlink] " Livingood, Jason
2023-09-28 22:19 ` David Lang [this message]
2023-09-29 4:54 ` [Starlink] [Bloat] " Jonathan Morton
2023-09-29 12:28 ` [Starlink] [Rpm] [Bloat] [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 ` Vint Cerf
2023-09-30 14:07 ` Sebastian Moeller
2023-09-30 14:41 ` Mike Conlow
[not found] ` <4129491C-FFC7-4E5E-A5A4-8CBE9B5C5255@gmx.de>
2023-09-30 15:23 ` [Starlink] [LibreQoS] [Rpm] [Bloat] " Dave Taht
2023-09-30 17:35 ` Dave Taht
2023-09-30 21:57 ` [Starlink] New email list: NNagain for network neutrality Dave Taht
2023-10-04 22:19 ` [Starlink] [Bloat] [Rpm] [LibreQoS] net neutrality back in the news Michael Richardson
2023-09-29 6:24 ` [Starlink] [Rpm] [Bloat] " Sebastian Moeller
2023-09-29 6:31 ` Gert Doering
2023-09-29 7:07 ` Sebastian Moeller
2023-09-28 22:25 ` [Starlink] [Bloat] [LibreQoS] [Rpm] " David Lang
2023-09-28 17:10 ` [Starlink] [Bloat] " Livingood, Jason
2023-09-28 19:30 ` Dave Taht
2023-09-28 20:05 ` Sebastian Moeller
2023-09-28 21:07 ` [Starlink] [EXTERNAL] " Livingood, Jason
2023-09-28 21:08 ` Livingood, Jason
2023-09-29 8:56 ` [Starlink] [Bloat] [EXTERNAL] " Erik Auerswald
2023-09-29 13:16 [Starlink] [Bloat] [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/starlink.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5so3r00n-31pn-14s7-7775-08731s3s551r@ynat.uz \
--to=david@lang.hm \
--cc=Jason_Livingood@comcast.com \
--cc=bloat@lists.bufferbloat.net \
--cc=dandenson@gmail.com \
--cc=dave.taht@gmail.com \
--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