From: "Livingood, Jason" <Jason_Livingood@comcast.com>
To: "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:27:14 +0000 [thread overview]
Message-ID: <6FFD0DE5-B728-42AF-99C4-F3AA90F9F5EE@cable.comcast.com> (raw)
In-Reply-To: <CAA93jw7cRjb_c8JnzFQCzJ7ZS-v4nFw0t4Y0LzH4W3NdqhFD=Q@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 468 bytes --]
On 10/1/23, 15:55, "Nnagain on behalf of Dave Taht via Nnagain" <nnagain-bounces@lists.bufferbloat.net <mailto:nnagain-bounces@lists.bufferbloat.net> on behalf of nnagain@lists.bufferbloat.net <mailto:nnagain@lists.bufferbloat.net>> wrote:
> Throttling, using DPI or other methods, is indeed feasible.
Via https://alissacooperdotcom.files.wordpress.com/2017/12/thesis.pdf
[A white text on a white background Description automatically generated]
[-- Attachment #1.2: Type: text/html, Size: 2753 bytes --]
[-- Attachment #2: image001.png --]
[-- Type: image/png, Size: 37991 bytes --]
next prev parent reply other threads:[~2023-10-02 13:27 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2023-10-02 6:06 ` [NNagain] Some backstory on the nn-again mailing list Sebastian Moeller
2023-10-02 12:36 ` Bless, Roland (TM)
2023-10-03 7:15 ` Sebastian Moeller
2023-10-02 20:18 [NNagain] On "Throttling" behaviors Livingood, Jason
2023-10-02 20:28 ` Dick Roy
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=6FFD0DE5-B728-42AF-99C4-F3AA90F9F5EE@cable.comcast.com \
--to=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