From: Ryan Mounce <ryan@mounce.com.au>
To: Sebastian Moeller <moeller0@gmx.de>
Cc: bloat <bloat@lists.bufferbloat.net>,
Jonathan Foulkes <jfoulkes@evenroute.com>
Subject: Re: [Bloat] number of home routers with ingress AQM
Date: Tue, 2 Apr 2019 23:45:57 +1030 [thread overview]
Message-ID: <CAN+fvRYF2TkQxP-rC0F0d=AAHbkFvWjpeLMxhuQwxTjRHY8QEA@mail.gmail.com> (raw)
In-Reply-To: <ED9289F4-B466-432F-ABD3-C5F14EC5DAA3@gmx.de>
On Tue, 2 Apr 2019 at 22:08, Sebastian Moeller <moeller0@gmx.de> wrote:
>
> I just wondered if anybody has any reasonable estimate how many end-users actually employ fair-queueing AQMs with active ECN-marking for ingress traffic @home? I am trying to understand whether L4S approach to simply declare these as insignificant in number is justifiable?
L4S people are concerned by RFC 3168 / "classic" ECN bottlenecks
*without* fq. I don't think there would be any such ingress shapers
configured on home gateways. Certainly not by anyone on this list...
anyone running non-fq codel or flowblind cake for ingress shaping?
-Ryan
next prev parent reply other threads:[~2019-04-02 13:16 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-02 11:38 Sebastian Moeller
2019-04-02 12:10 ` Mikael Abrahamsson
2019-04-02 12:35 ` Sebastian Moeller
2019-04-02 13:04 ` Mikael Abrahamsson
2019-04-02 13:28 ` Sebastian Moeller
2019-04-02 13:33 ` Ryan Mounce
2019-04-02 14:11 ` Jonathan Foulkes
2019-04-02 21:10 ` Ryan Mounce
2019-04-02 14:14 ` Jonathan Foulkes
2019-04-02 14:58 ` Sebastian Moeller
2019-04-02 13:51 ` Jonathan Foulkes
2019-04-02 14:14 ` Jonathan Foulkes
2019-04-02 16:20 ` Jonathan Morton
2019-04-02 16:38 ` Sebastian Moeller
2019-04-02 13:15 ` Ryan Mounce [this message]
2019-04-02 13:34 ` Mikael Abrahamsson
2019-04-02 13:38 ` Ryan Mounce
2019-04-02 14:02 ` Mikael Abrahamsson
2019-04-02 13:34 ` Sebastian Moeller
2019-04-02 23:23 ` Ryan Mounce
2019-04-03 8:16 ` Sebastian Moeller
2019-04-03 10:09 ` Jonathan Morton
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='CAN+fvRYF2TkQxP-rC0F0d=AAHbkFvWjpeLMxhuQwxTjRHY8QEA@mail.gmail.com' \
--to=ryan@mounce.com.au \
--cc=bloat@lists.bufferbloat.net \
--cc=jfoulkes@evenroute.com \
--cc=moeller0@gmx.de \
/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