From owner-freebsd-net@FreeBSD.ORG Thu Nov 4 18:50:25 2004 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 88E0716A4CE for ; Thu, 4 Nov 2004 18:50:25 +0000 (GMT) Received: from c00l3r.networx.ch (c00l3r.networx.ch [62.48.2.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id BE07743D64 for ; Thu, 4 Nov 2004 18:50:24 +0000 (GMT) (envelope-from andre@freebsd.org) Received: (qmail 99617 invoked from network); 4 Nov 2004 18:46:28 -0000 Received: from unknown (HELO freebsd.org) ([62.48.0.53]) (envelope-sender ) by c00l3r.networx.ch (qmail-ldap-1.03) with SMTP for ; 4 Nov 2004 18:46:28 -0000 Message-ID: <418A79F7.15B7CDB9@freebsd.org> Date: Thu, 04 Nov 2004 19:50:31 +0100 From: Andre Oppermann X-Mailer: Mozilla 4.8 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Karim Fodil-Lemelin References: <20041022182430.31A2B1EF3BF@lawyers.icir.org> <418A6FDC.5010204@xiphos.ca> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsd-net@freebsd.org cc: freebsd-arch@freebsd.org cc: mallman@icir.org Subject: Re: Removing T/TCP and replacing it with something simpler X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Nov 2004 18:50:25 -0000 Karim Fodil-Lemelin wrote: > > Hi, > > I am jumping in here, was too busy to read the list for the last 2 > weeks, so please excuse my intrusion. We are using T/TCP in our product > line and are very happy with the performance gain. Could you tell me > what is the rational for removing T/TCP (security/performances/code > complexity, etc ..) from FreeBSD? Have a look at the rationale here (and the followup discussion): http://docs.freebsd.org/cgi/mid.cgi?4177C8AD.6060706 And also note that T/TCP was removed only from FreeBSD 6-current. It is still in 4.x and 5.x releases and will not be removed from them. A more secure and much less (code-) intrusive replacement for T/TCP is in the works by me. I'll have code ready soon and it'll be in FreeBSD 6-current probably before christmas along with a proper RFC draft submitted to the IETF TCPM WG. -- Andre