Discussion of explicit congestion notification's impact on the Internet
 help / color / mirror / Atom feed
From: Jonathan Morton <chromatix99@gmail.com>
To: Mikael Abrahamsson <swmike@swm.pp.se>
Cc: Sebastian Moeller <moeller0@gmx.de>, ecn-sane@lists.bufferbloat.net
Subject: Re: [Ecn-sane] robustness against attack?
Date: Mon, 25 Mar 2019 09:34:49 +0100	[thread overview]
Message-ID: <907D3152-4AD5-4551-AA6A-46FF9CA567DE@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1903250810490.3161@uplift.swm.pp.se>

> On 25 Mar, 2019, at 8:16 am, Mikael Abrahamsson <swmike@swm.pp.se> wrote:
> 
> Do people on this email list think we're trying to trick you when we're saying that FQ won't be available anytime soon on a lot of platforms that need this kind of AQM?

Well, I don't.  I recognise that most high-capacity links will end up with single-queue AQM, because that's what's already out there in hardware (though it's rarely turned on so far).  I'm still keen to see good FQ used where feasible, and in ways that make local sense.

That's why I've put some effort into making SCE play nicely with single-queue AQMs, since our initial conversation on that point where I was still assuming AIAD response to SCE.  That is, I now have non-AIAD SCE responses which should (theoretically) converge to an RTT-fair state over a single queue.  (One of them is the DCTCP response, which L4S folks should be intimately familiar with by now.)  If you'll recall, my initial workaround was simply to 

Experimentation will be needed to check whether my theorising actually works in practice, but I'm not exactly ignoring the problem.

 - Jonathan Morton


  parent reply	other threads:[~2019-03-25  8:34 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-24 22:50 Sebastian Moeller
2019-03-25  7:16 ` Mikael Abrahamsson
2019-03-25  7:54   ` [Ecn-sane] FQ in the core Dave Taht
2019-03-25  9:17     ` Luca Muscariello
2019-03-25  9:52       ` Sebastian Moeller
2019-03-25  9:23     ` Sebastian Moeller
2019-03-25 15:43     ` Mikael Abrahamsson
2019-03-25  8:34   ` Jonathan Morton [this message]
2019-03-25  8:53     ` [Ecn-sane] robustness against attack? Jonathan Morton
2019-03-25  9:40       ` Sebastian Moeller
2019-03-25 15:23     ` Mikael Abrahamsson
2019-03-25 22:53       ` David P. Reed
2019-03-25  8:46   ` Sebastian Moeller

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/ecn-sane.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=907D3152-4AD5-4551-AA6A-46FF9CA567DE@gmail.com \
    --to=chromatix99@gmail.com \
    --cc=ecn-sane@lists.bufferbloat.net \
    --cc=moeller0@gmx.de \
    --cc=swmike@swm.pp.se \
    /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