netdev - Re: [PATCH v2] tcp: split tcp_ecn sysctl knob to distinguish between IPv4 and IPv6

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20130103165838.GA14323@order.stressinduktion.org>
Date:	Thu, 3 Jan 2013 17:58:38 +0100
From:	Hannes Frederic Sowa <hannes@...essinduktion.org>
To:	Stephen Hemminger <shemminger@...tta.com>
Cc:	David Miller <davem@...emloft.net>, netdev@...r.kernel.org
Subject: Re: [PATCH v2] tcp: split tcp_ecn sysctl knob to distinguish between IPv4 and IPv6

On Thu, Jan 03, 2013 at 08:22:54AM -0800, Stephen Hemminger wrote:
> On Thu, 3 Jan 2013 13:58:12 +0100
> Hannes Frederic Sowa <hannes@...essinduktion.org> wrote:
> 
> > On Thu, Jan 03, 2013 at 04:53:50AM -0800, David Miller wrote:
> > > From: Hannes Frederic Sowa <hannes@...essinduktion.org>
> > > Date: Thu, 3 Jan 2013 13:28:44 +0100
> > > 
> > > > On Thu, Jan 03, 2013 at 01:00:09AM +0100, Hannes Frederic Sowa wrote:
> > > >> ECN could be more reliable when used with IPv6 (I don't have proofs). For
> > > >> people who want to try ECN with IPv6 but still have problems connecting
> > > >> to destinations because of broken IPv4 routers this switch allows one
> > > >> to enable ECN just for IPv6.
> > > >> 
> > > >> Perhaps ECN could be enabled by default in future.
> > > >> 
> > > >> No code changes since initial submission, just added documentation.
> > > > 
> > > > May I ask what lead to the rejection of the patch?
> > > 
> > > I don't see any value in splitting up ipv4 and ipv6.
> > > 
> > > I think we should turn the existing knob on unliaterally
> > > by default.  That would be a much better patch.
> > 
> > Oh, I would be happy to do that. :)
> 
> Perhaps, ECN should be a property of the route.
> There is RTAX_FEATURE_ECN but it appears to have been lost
> as part of the removal of route cache.

I suggested something like this in the discussion on bufferbloat:
<http://thread.gmane.org/gmane.network.routing.bufferbloat/1086>

Especially if RFC5562 would be implemented one day, this could really be
helpful.

--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html