From: Dave Taht <dave.taht@gmail.com>
To: Bruno George Moraes <brunogm0@gmail.com>
Cc: ecn-sane@lists.bufferbloat.net
Subject: Re: [Ecn-sane] ECN usable with UDP paper
Date: Mon, 24 Sep 2018 11:33:49 -0700 [thread overview]
Message-ID: <CAA93jw5JRaBs7bxQsba1TsYc9u+aR2Lp3GN=un3DMxpSCi3nAg@mail.gmail.com> (raw)
In-Reply-To: <CAJpr3FPQyAHLFB7cr9ZjvwDf2LFB3UKRiXmwu0HxiZH-gvAFZw@mail.gmail.com>
On Mon, Sep 24, 2018 at 11:18 AM Bruno George Moraes <brunogm0@gmail.com> wrote:
>
> https://csperkins.org/publications/2015/10/mcquistin2015ecn-udp.html
>
> Using measurements from the author’s homes, their workplace, and cloud servers in each of the nine EC2 regions worldwide, we test reachability of 2500 servers from the public NTP server pool, using ECT(0) and not-ECT marked UDP packets. We show that an average of 98.97% of the NTP servers that are reachable using not-ECT marked packets are also reachable using ECT(0) marked UDP packets, and that 98% of network hops pass ECT(0) marked packets without clearing the ECT bits. We compare reachability of the same hosts using ECN with TCP, finding that 82.0% of those reachable with TCP can successfully negotiate and use ECN. Our findings suggest that ECN is broadly usable with UDP traffic, and that support for use of ECN with TCP has increased.
> _______________________________________________
> Ecn-sane mailing list
> Ecn-sane@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/ecn-sane
Yep. So my follow-on questions are:
Would a NTP reflection attack be worse with ecn enabled?
Should ntp servers accept ect marked packets in the first place? If
so, what, if anything, should they do with a CE?
--
Dave Täht
CEO, TekLibre, LLC
http://www.teklibre.com
Tel: 1-669-226-2619
prev parent reply other threads:[~2018-09-24 18:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-24 17:27 Bruno George Moraes
2018-09-24 18:33 ` Dave Taht [this message]
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='CAA93jw5JRaBs7bxQsba1TsYc9u+aR2Lp3GN=un3DMxpSCi3nAg@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=brunogm0@gmail.com \
--cc=ecn-sane@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