From: "Dick Roy" <dickroy@alum.mit.edu>
To: "'Livingood, Jason'" <Jason_Livingood@comcast.com>,
"'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, 2 Oct 2023 13:28:00 -0700 [thread overview]
Message-ID: <C1C33948733B44FB85C398D84ADD0BAC@SRA6> (raw)
In-Reply-To: <9C609026-5907-4A90-857A-AE096E767521@cable.comcast.com>
-----Original Message-----
From: Livingood, Jason [mailto:Jason_Livingood@comcast.com]
Sent: Monday, October 2, 2023 1:18 PM
To: dickroy@alum.mit.edu; 'Network Neutrality is back! Let´s make the
technical aspects heard this time!'
Subject: RE: [NNagain] On "Throttling" behaviors
From: Dick Roy <dickroy@alum.mit.edu> on behalf of Dick Roy
<dickroy@alum.mit.edu>
>> To take the example of throttling - all that would do is (1) prompt
customer contacts
> [RR] Did you mean “contracts”?
No, I meant contacts. In an ISP support context, that means a telephone call
or chat with a customer care agent. Those activities are closely monitored
for quality/cost/time and so at scale a phone contact will cost $X, chat $Y,
social media interaction like Reddit or Twitter $Z, etc.
[RR] Exactly what I was wondering :) Thanks for the clarification!
RR
Jason
next prev parent reply other threads:[~2023-10-02 20:28 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-02 20:18 Livingood, Jason
2023-10-02 20:28 ` Dick Roy [this message]
-- strict thread matches above, loose matches on Subject: below --
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
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
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=C1C33948733B44FB85C398D84ADD0BAC@SRA6 \
--to=dickroy@alum.mit.edu \
--cc=Jason_Livingood@comcast.com \
--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