From owner-freebsd-net@FreeBSD.ORG Fri Oct 22 11:58:26 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 2E4BB16A4D0; Fri, 22 Oct 2004 11:58:26 +0000 (GMT) Received: from smtp.des.no (flood.des.no [217.116.83.31]) by mx1.FreeBSD.org (Postfix) with ESMTP id 861E743D41; Fri, 22 Oct 2004 11:58:25 +0000 (GMT) (envelope-from des@des.no) Received: by smtp.des.no (Pony Express, from userid 666) id 384EB5311; Fri, 22 Oct 2004 13:58:24 +0200 (CEST) Received: from dwp.des.no (des.no [80.203.228.37]) by smtp.des.no (Pony Express) with ESMTP id EEB745310; Fri, 22 Oct 2004 13:58:16 +0200 (CEST) Received: by dwp.des.no (Postfix, from userid 2602) id 77F7AB861; Fri, 22 Oct 2004 13:58:16 +0200 (CEST) To: Andre Oppermann References: <4177C8AD.6060706@freebsd.org> From: des@des.no (=?iso-8859-1?q?Dag-Erling_Sm=F8rgrav?=) Date: Fri, 22 Oct 2004 13:58:16 +0200 In-Reply-To: <4177C8AD.6060706@freebsd.org> (Andre Oppermann's message of "Thu, 21 Oct 2004 16:33:17 +0200") Message-ID: User-Agent: Gnus/5.1006 (Gnus v5.10.6) Emacs/21.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Spam-Checker-Version: SpamAssassin 2.64 (2004-01-11) on flood.des.no X-Spam-Level: X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.64 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 List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Oct 2004 11:58:26 -0000 Andre Oppermann writes: > o T/TCP only available on FreeBSD. No other Operating System or TCP/IP > stack implements it to my knowledge. Certainly no OS that is common. AFAIK, both Linux and Windows support it, at least on the server side (i.e. they can receive T/TCP connections even if they can't initiate them). > o T/TCP requires different API calls than TCP to use it (UDP like). Only on the client side, I believe. > o T/TCP is not supported by any common network application. Prior to libfetch, fetch(1) used it by default. > Thus after the removal of T/TCP for the reasons above I want to provide > a work-alike replacement for T/TCP's functionality: Unlike your proposal, T/TCP is described in Internet RFCs (1379 and 1644) and well-known by the Internet community. > If you haven't read and/or unstood the link above or TCP/IP Illustrated > Volume 3 then please refrain from participating in this discussion! Nice. DES --=20 Dag-Erling Sm=F8rgrav - des@des.no