Discussion of explicit congestion notification's impact on the Internet
 help / color / mirror / Atom feed
From: Sebastian Moeller <moeller0@gmx.de>
To: Jonathan Morton <chromatix99@gmail.com>
Cc: Mikael Abrahamsson <swmike@swm.pp.se>, ecn-sane@lists.bufferbloat.net
Subject: Re: [Ecn-sane] robustness against attack?
Date: Mon, 25 Mar 2019 10:40:42 +0100	[thread overview]
Message-ID: <9600DC6D-D545-404A-A7F7-63D345ECDACB@gmx.de> (raw)
In-Reply-To: <43D640E1-DF36-401A-A638-44D1AF6E1F47@gmail.com>

Hi Jonathan,


> On Mar 25, 2019, at 09:53, Jonathan Morton <chromatix99@gmail.com> wrote:
> 
>> On 25 Mar, 2019, at 9:34 am, Jonathan Morton <chromatix99@gmail.com> wrote:
>> 
>> If you'll recall, my initial workaround was simply to 
> 
> …not implement SCE on single-queue middleboxes, and rely on the known-good CE response in that case.  

	Which reduces the problem to get middle-boxes to use ECN at all ;)


> But if we can show that putting SCE there too is safe, that's even better.

	Given that the above might be harder than desired, it might be a good idea to immediately aim a bit higher than pure-CE ECN.

Best Regards
	Sebastian

> 
> - Jonathan Morton
> 


  reply	other threads:[~2019-03-25  9:40 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   ` [Ecn-sane] robustness against attack? Jonathan Morton
2019-03-25  8:53     ` Jonathan Morton
2019-03-25  9:40       ` Sebastian Moeller [this message]
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=9600DC6D-D545-404A-A7F7-63D345ECDACB@gmx.de \
    --to=moeller0@gmx.de \
    --cc=chromatix99@gmail.com \
    --cc=ecn-sane@lists.bufferbloat.net \
    --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