From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <hannes@stressinduktion.org>
Received: from order.stressinduktion.org (order.stressinduktion.org
	[87.106.68.36])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(Client CN "order.stressinduktion.org",
	Issuer "order.stressinduktion.org" (not verified))
	by huchra.bufferbloat.net (Postfix) with ESMTPS id E446021F150
	for <bloat@lists.bufferbloat.net>; Wed, 26 Dec 2012 21:53:17 -0800 (PST)
Received: by order.stressinduktion.org (Postfix, from userid 500)
	id 1EBFF1A0CDA8; Thu, 27 Dec 2012 06:53:14 +0100 (CET)
Date: Thu, 27 Dec 2012 06:53:14 +0100
From: Hannes Frederic Sowa <hannes@stressinduktion.org>
To: Michael Richardson <mcr@sandelman.ca>
Message-ID: <20121227055314.GB20131@order.stressinduktion.org>
References: <20121227023728.GB19548@order.stressinduktion.org>
	<18172.1356584697@sandelman.ca>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <18172.1356584697@sandelman.ca>
Cc: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] enabling outgoing tcp-ecn by default for ipv6 links
X-BeenThere: bloat@lists.bufferbloat.net
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: General list for discussing Bufferbloat <bloat.lists.bufferbloat.net>
List-Unsubscribe: <https://lists.bufferbloat.net/options/bloat>,
	<mailto:bloat-request@lists.bufferbloat.net?subject=unsubscribe>
List-Archive: <https://lists.bufferbloat.net/pipermail/bloat>
List-Post: <mailto:bloat@lists.bufferbloat.net>
List-Help: <mailto:bloat-request@lists.bufferbloat.net?subject=help>
List-Subscribe: <https://lists.bufferbloat.net/listinfo/bloat>,
	<mailto:bloat-request@lists.bufferbloat.net?subject=subscribe>
X-List-Received-Date: Thu, 27 Dec 2012 05:53:18 -0000

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