Discussion of explicit congestion notification's impact on the Internet
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: ecn-sane@lists.bufferbloat.net
Subject: [Ecn-sane] straw men
Date: Wed, 19 Sep 2018 08:13:20 -0700	[thread overview]
Message-ID: <CAA93jw7nH_f-1+pjRDwVe9obYfyjotdAcqKJaatHSA3pay7Wbw@mail.gmail.com> (raw)

At one level, my hope in starting this project is that once enough
researchers realize that ECN is now ubiquitous in apple's products,
all kinds of new ideas and research will emerge and we won't have to
do any more work. :)

In my case, though, I rather wanted to promote a skeptical look at the
edge cases. A quick look at things like /etc/services or the long list
of ethertypes https://www.iana.org/assignments/ieee-802-numbers/ieee-802-numbers.xhtml#ieee-802-numbers-1
is sufficient cause to worry.

I'm pretty good with short, ringing phrases, and hereby give away most
of these potential paper titles away to whoever wants to use them.

I'm going to talk to two or three of these in the coming weeks, but to
at least get the list out of my system:

Where ECN is unfair
When ECN is evil
ECN along the edge
ECN as an attack vector
DCTCP along asymmetric paths
Towards making ecn generally deployable
Fair queuing failures
ack-filtering in practice
ECN has mass!
ecn over wifi
syn/ack limiting as rate control
self congestion as aqm
ecn on alternative protocols
sch_cake and blue
ECN should be an earlier congestion signal than loss?
Mosh's reaction to ecn
ECN outbound on residential links
GSO considered harmful
Making tcp go slower makes it faster
Damage from an ecn enabled DDOS
FQ is not enough
ECN on meshy protocols
ECN vs ISIS

-- 

Dave Täht
CEO, TekLibre, LLC
http://www.teklibre.com
Tel: 1-669-226-2619

                 reply	other threads:[~2018-09-19 15:13 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=CAA93jw7nH_f-1+pjRDwVe9obYfyjotdAcqKJaatHSA3pay7Wbw@mail.gmail.com \
    --to=dave.taht@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