From owner-freebsd-net Mon Oct 25 9:43:36 1999 Delivered-To: freebsd-net@freebsd.org Received: from bomber.avantgo.com (ws1.avantgo.com [207.214.200.194]) by hub.freebsd.org (Postfix) with ESMTP id 6D2AB14D90 for ; Mon, 25 Oct 1999 09:43:19 -0700 (PDT) (envelope-from scott@avantgo.com) Received: from river ([10.0.128.30]) by bomber.avantgo.com (Netscape Messaging Server 3.5) with SMTP id 304 for ; Mon, 25 Oct 1999 09:37:50 -0700 Message-ID: <048d01bf1f07$e85749d0$1e80000a@avantgo.com> From: "Scott Hess" To: Subject: RFC 2140. Date: Mon, 25 Oct 1999 09:42:21 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Does FreeBSD, 3.3 or 4.0, contain anything like the optimizations discussed in RFC 2140? Basically, this RFC describes treating certain TCP control block information as host-pair shared rather than only used on a per-connection basis. Things like congestion control and suggested window size. I'm looking at it as a way to gain many of the positives of multiplexing things over long-running sockets, without having to build the application intelligence to multiplex over long-running sockets. Thanks, scott To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message