From owner-freebsd-net@FreeBSD.ORG Sun Feb 10 08:18:02 2013 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id B695F456 for ; Sun, 10 Feb 2013 08:18:02 +0000 (UTC) (envelope-from garmitage@swin.edu.au) Received: from gpo1.cc.swin.edu.au (gpo1.cc.swin.edu.au [136.186.1.30]) by mx1.freebsd.org (Postfix) with ESMTP id 32A37E90 for ; Sun, 10 Feb 2013 08:18:01 +0000 (UTC) Received: from [136.186.229.37] (garmitage.caia.swin.edu.au [136.186.229.37]) by gpo1.cc.swin.edu.au (8.14.3/8.14.3) with ESMTP id r1A8I07Y002449 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 10 Feb 2013 19:18:00 +1100 Message-ID: <511757B8.3080407@swin.edu.au> Date: Sun, 10 Feb 2013 19:18:00 +1100 From: grenville armitage User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:16.0) Gecko/20121107 Thunderbird/16.0.2 MIME-Version: 1.0 To: freebsd-net@freebsd.org Subject: Re: [PATCH] Add a new TCP_IGNOREIDLE socket option References: <201301221511.02496.jhb@freebsd.org> <50FF06AD.402@networx.ch> <061B4EA5-6A93-48A0-A269-C2C3A3C7E77C@lakerest.net> <201302060746.43736.jhb@freebsd.org> <511292C9.4040307@mu.org> <51166019.9040104@mu.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Feb 2013 08:18:02 -0000 On 02/10/2013 18:30, Eggert, Lars wrote: > On Feb 10, 2013, at 6:05, Kevin Oberman wrote: >> One idea that popped into my head (and may be completely ridiculous, >> is to make its availability dependent on a kernel option and have >> warning in NOTES about it contravening normal and accepted practice >> and that it can cause serious problems both for yourself and for >> others using the network. > > Also, if it gets merged, don't call it TCP_IGNOREIDLE. Call it TCP_BLAST_DANGEROUSLY_AFTER_IDLE. TCP_AVALANCHE cheers, gja