From: Hannes Frederic Sowa <hannes@stressinduktion.org>
To: bloat@lists.bufferbloat.net
Subject: [Bloat] enabling outgoing tcp-ecn by default for ipv6 links
Date: Thu, 27 Dec 2012 03:37:28 +0100 [thread overview]
Message-ID: <20121227023728.GB19548@order.stressinduktion.org> (raw)
Hello!
I am thinking about advancing the ipv4/tcp_ecn knob in linux to
distinguish between ipv4 and ipv6 transport and enable ecn signaling
on outgoing ipv6 connections by default (for me, at least). I am
currently doing so with the help of iptables (echo 1 > tcp_ecn and -j
ECN --ecn-tcp-remove).
Currently linux does only respond to ecn signaling but does not actively
try to signal ecn capabilities by default because of the high(?) fail rate
of connections in ipv4 land. I wonder if this situation has improved in
ipv6 world because I assume most providers have upgraded their gear in
recent times to support this shiny new protocol.
Does someone know about recent data if such a change would be reasonable?
Btw, has someone looked at RFC5562 - Adding Explicit Congestion
Notification (ECN) Capability to TCP's SYN/ACK Packets;
experimental? Adam Langley has provided a patch for linux enabling ecn on
syn/ack packets some while ago[1]. This seems to be a nice addition but
I fear for new problems arising because of buggy routers. Perhaps after the
retransmit of the initial syn without the ecn-capable codepoint one could
mark this connection as non-ecn compatible in the destination cache to
reduce further latencies on follow-up syns (kind of path ecn discovery).
Greetings,
Hannes
[1] https://www.ietf.org/mail-archive/web/tcpm/current/msg03988.html
next reply other threads:[~2012-12-27 2:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-27 2:37 Hannes Frederic Sowa [this message]
2012-12-27 5:04 ` Michael Richardson
2012-12-27 5:53 ` Hannes Frederic Sowa
2012-12-31 17:37 ` Hannes Frederic Sowa
2015-02-27 15:52 ` Richard Scheffenegger
2012-12-27 20:10 ` Rick Jones
2012-12-27 21:25 ` Hannes Frederic Sowa
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=20121227023728.GB19548@order.stressinduktion.org \
--to=hannes@stressinduktion.org \
--cc=bloat@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