| 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
| ||
|
Message-ID: <20130106013117.GC28545@order.stressinduktion.org> Date: Sun, 6 Jan 2013 02:31:17 +0100 From: Hannes Frederic Sowa <hannes@...essinduktion.org> To: David Miller <davem@...emloft.net> Cc: 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 04:53:50AM -0800, David Miller wrote: > > 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. I wonder if we really should go down this route to turn on ecn by default or if I should try to come up with a patch which marks non working ecn paths in the destination cache and suppress ecn for those connections. Any advice? -- 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
Powered by blists - more mailing lists