netdev - Re: time for TCP ECN defaulting to on?

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]

Date:	Fri, 07 Nov 2008 11:18:39 +0000
From:	Dave Hudson <linux-kernel@...eteddy.net>
To:	Ilpo Järvinen <ilpo.jarvinen@...sinki.fi>
CC:	Mikael Abrahamsson <swmike@....pp.se>,
	David Miller <davem@...emloft.net>, daniel.blueman@...il.com,
	LKML <linux-kernel@...r.kernel.org>,
	Netdev <netdev@...r.kernel.org>, linux-net@...r.kernel.org
Subject: Re: time for TCP ECN defaulting to on?

Ilpo Järvinen wrote:
> On Fri, 7 Nov 2008, Mikael Abrahamsson wrote:
> 
> And about somebody earlier claiming that they'll get an impressions that 
> Linux stack is broken (if such people even know that there's some network 
> stack in Linux :-))... I'm rather sure those isp supports etc. put a blaim 
> on us anyway even when loads of counterproof would exists because it's 
> just cheaper to do nothing and blaim linux instead. Also some claims 
> asserted by incompetent people easily start to live among random forums; 
> an example from the previous incident: "since disabling timestamps helps, 
> it must be that timestamps are broken" (and somebody even "more clueful" 
> added that they got enabled for 2.6.27?!?), needless to say, neither 
> holds.

Not all of the routers in question (the ones that crash, block packets 
or otherwise misbehave) are provided by ISPs - in fact a huge number of 
them are and have been sold retail.  Over time most of those boxes will 
get replaced with ones that don't have the problem because most 
(probably all major) SOHO router suppliers now test that they don't 
break with ECN so eventually there will be a point where enabling ECN by 
default will make a lot of sense (there will be too few broken routers 
to care about).

What I do believe (having spent a lot of years writing embedded device 
and router code - and no, not the ones that crash ;-)) is that if you 
enable a feature that causes just 1% of users to have an out-of-the-box 
problem you'll see a seriously disproportionate response from end users. 
  Most people (and engineers are not "most people" :-)) will blame the 
new thing that they've just added or changed, not the old thing that was 
broken to begin with (it's human nature not to truly understand cause 
and effect).

Whether we like it or not there's currently a known problem deploying 
ECN on a wide scale - it has been sufficient to stop pretty-much 
everyone from enabling it by default so far.

Regards,
Dave

--
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