From: Hannes Frederic Sowa <hannes@stressinduktion.org>
To: Michael Richardson <mcr@sandelman.ca>
Cc: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] enabling outgoing tcp-ecn by default for ipv6 links
Date: Thu, 27 Dec 2012 06:53:14 +0100 [thread overview]
Message-ID: <20121227055314.GB20131@order.stressinduktion.org> (raw)
In-Reply-To: <18172.1356584697@sandelman.ca>
On Thu, Dec 27, 2012 at 12:04:57AM -0500, Michael Richardson wrote:
> >>>>> "Hannes" == Hannes Frederic Sowa <hannes@stressinduktion.org> writes:
> Hannes> I am thinking about advancing the ipv4/tcp_ecn knob in linux to
> Hannes> distinguish between ipv4 and ipv6 transport and enable ecn signaling
> Hannes> on outgoing ipv6 connections by default (for me, at least). I am
> Hannes> currently doing so with the help of iptables (echo 1 > tcp_ecn and -j
> Hannes> ECN --ecn-tcp-remove).
>
> I think it's definitely worth splitting the sysctl, so that we can at
> least learn if it can fly in v6 land. I'd turn it on.
>
> I suggest that doing this without a way to report on a path/IP/vendor
> that is screwing things up is a mistake.
>
> http://urchin.earth.li/ecn/
>
> went inactive again in 2011.
What data would be needed? Some website where one could copy&paste
traceroutes (with tcp/ecn enabled)? A reprobe mechanism? Some
correlation/dependence mechanisms?
Something like this could be a neat experiment for RIPE Atlas. It would
be nice to have such tests in the various implementations of looking
glass, too.
Greetings,
Hannes
next prev parent reply other threads:[~2012-12-27 5:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-27 2:37 Hannes Frederic Sowa
2012-12-27 5:04 ` Michael Richardson
2012-12-27 5:53 ` Hannes Frederic Sowa [this message]
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=20121227055314.GB20131@order.stressinduktion.org \
--to=hannes@stressinduktion.org \
--cc=bloat@lists.bufferbloat.net \
--cc=mcr@sandelman.ca \
/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