General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: "Livingood, Jason" <Jason_Livingood@comcast.com>
To: dan <dandenson@gmail.com>, Dave Taht <dave.taht@gmail.com>
Cc: Rpm <rpm@lists.bufferbloat.net>,
	libreqos <libreqos@lists.bufferbloat.net>,
	Jamal Hadi Salim <jhs@mojatatu.com>,
	Dave Taht via Starlink <starlink@lists.bufferbloat.net>,
	bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] [Starlink] [LibreQoS] [Rpm] net neutrality back in the news
Date: Thu, 28 Sep 2023 20:48:58 +0000	[thread overview]
Message-ID: <E267D7FF-E5A5-476B-AEE6-6CC73632480C@cable.comcast.com> (raw)
In-Reply-To: <CAA_JP8VqQkGxvPCSm-G=5Lx7p4rFLQmY1iepyV5-tMAFWMwLRg@mail.gmail.com>

> 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.  

Corporations are motivated to generate returns for investors. 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). So, IMO on a purely financial basis, public companies have significant motivation to retain customers and keep them happy. This typically follows through to staff members having part of their variable compensation based on things like NPS scores, contact rates, etc. And specifically in relation to Comcast, the company recently has 4 new wireless competitors: three 5G FWA and one LEO (more coming) - and those are posing significant competitive risks (and taking customers). 

> 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.

JL





  parent reply	other threads:[~2023-09-28 20:49 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           ` Livingood, Jason [this message]
2023-09-28 22:19             ` [Bloat] [Starlink] " 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
     [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 13:16 [Bloat] [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=E267D7FF-E5A5-476B-AEE6-6CC73632480C@cable.comcast.com \
    --to=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