From owner-freebsd-net@FreeBSD.ORG Thu Oct 21 18:51:39 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 1104716A4CE; Thu, 21 Oct 2004 18:51:39 +0000 (GMT) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id DF6AF43D41; Thu, 21 Oct 2004 18:51:38 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.13.1/8.13.1) with ESMTP id i9LIpcVc037579; Thu, 21 Oct 2004 11:51:38 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.13.1/8.13.1/Submit) id i9LIpcpO037578; Thu, 21 Oct 2004 11:51:38 -0700 (PDT) (envelope-from obrien) Date: Thu, 21 Oct 2004 11:51:37 -0700 From: "David O'Brien" To: Andre Oppermann Message-ID: <20041021185137.GA37500@dragon.nuxi.com> References: <4177C8AD.6060706@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4177C8AD.6060706@freebsd.org> User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD 6.0-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 cc: freebsd-net@freebsd.org cc: freebsd-arch@freebsd.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 Reply-To: freebsd-arch@freebsd.org, freebsd-net@freebsd.org List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Oct 2004 18:51:39 -0000 On Thu, Oct 21, 2004 at 04:33:17PM +0200, Andre Oppermann wrote: > I intend to remove T/TCP (transactional TCP) support from our TCP > implementation for the following reasons: .. Fine. > Thus after the removal of T/TCP for the reasons above I want to provide > a work-alike replacement for T/TCP's functionality: .. > This different implementation will be disabled by default and clearly > marked EXPERIMENTAL in a protocol sense. It will allow the only known > user of T/TCP to keep the same functionality with a very small change > to his application. It allows interesting new uses primarily in > Intranet environment where many short connections are openend in rapid > succession (LDAP servers, SQL servers, etc.). The modifications to > those programs to use the new option is minimal and requires only the > setting of the socket option, one setsockopt() call. I'm not so happy with a FreeBSD-only "proprietary" thing. Is there any proposed RFC work that provides the qualities you want? The advantage with T/TCP is that there was a published standard. -- -- David (obrien@FreeBSD.org)