Network Neutrality is back! Let´s make the technical aspects heard this time!
 help / color / mirror / Atom feed
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] The Verge: The quiet plan to make the internet feel faster
Date: Mon, 11 Dec 2023 15:13:06 +0000	[thread overview]
Message-ID: <BEAD21F3-2E57-4BF0-95C0-0BE73C3E64EA@comcast.com> (raw)
In-Reply-To: <826a0d77-b6b8-423d-a094-93d75840fa90@rjmcmahon.com>

> In general - a potential harm to innocent bystanders is a biggest L4S problem:

This likely belongs on the latency list, not NNAgain. But in this case, it seems low risk given that there's essentially no deployment of single-queue RFC3168 AQMs of which I am aware. 

JL


  parent reply	other threads:[~2023-12-11 15:13 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-10  4:48 Matt Mathis
2023-12-10  6:54 ` Frantisek Borsik
2023-12-10 11:12   ` Sauli Kiviranta
2023-12-10 18:21     ` Robert McMahon
2023-12-11  9:50       ` Frantisek Borsik
     [not found]         ` <4C2CA220-A7EF-4198-BE6C-A2FC979A1F8D@gmx.de>
2023-12-11 10:18           ` Frantisek Borsik
     [not found]             ` <E96CB707-1BDE-48F6-A09F-2229FDBA372A@gmx.de>
2023-12-11 19:33               ` Frantisek Borsik
2023-12-11 14:54         ` Livingood, Jason
2023-12-11 18:51           ` rjmcmahon
2023-12-11 19:25             ` Frantisek Borsik
2023-12-11 15:13       ` Livingood, Jason [this message]
2023-12-11 14:56 ` 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=BEAD21F3-2E57-4BF0-95C0-0BE73C3E64EA@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