From mboxrd@z Thu Jan 1 00:00:00 1970 From: Rick Jones Subject: Re: [PATCH net-next] tcp: be more strict before accepting ECN negociation Date: Fri, 04 May 2012 11:09:31 -0700 Message-ID: <4FA41B5B.5080103@hp.com> References: <1336144442.3752.348.camel@edumazet-glaptop> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: David Miller , netdev , Perry Lorier , Matt Mathis , Yuchung Cheng , Neal Cardwell , Tom Herbert , Wilmer van der Gaast , =?UTF-8?B?RGF2ZSBUw6RodA==?= , Ankur Jain To: Eric Dumazet Return-path: Received: from g1t0028.austin.hp.com ([15.216.28.35]:9694 "EHLO g1t0028.austin.hp.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752517Ab2EDSJe (ORCPT ); Fri, 4 May 2012 14:09:34 -0400 In-Reply-To: <1336144442.3752.348.camel@edumazet-glaptop> Sender: netdev-owner@vger.kernel.org List-ID: On 05/04/2012 08:14 AM, Eric Dumazet wrote: > From: Eric Dumazet > > It appears some networks play bad games with the two bits reserved for > ECN. This can trigger false congestion notifications and very slow > transferts. > > Since RFC 3168 (6.1.1) forbids SYN packets to carry CT bits, we can > disable TCP ECN negociation if it happens we receive mangled CT bits in > the SYN packet. What sort of networks were these? Any chance it was some sort of attempt to add ECN to FastOpen? rick jones