From owner-freebsd-net@FreeBSD.ORG Sat Oct 23 13:17:24 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 D0BDB16A4CE; Sat, 23 Oct 2004 13:17:24 +0000 (GMT) Received: from stewart.chicago.il.us (dpc674425142.direcpc.com [67.44.25.142]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9D68943D53; Sat, 23 Oct 2004 13:17:22 +0000 (GMT) (envelope-from randall@stewart.chicago.il.us) Received: from stewart.chicago.il.us (localhost [127.0.0.1]) i9NDHJtr031503; Sat, 23 Oct 2004 09:17:20 -0400 (EDT) (envelope-from randall@stewart.chicago.il.us) Message-ID: <417A5994.7020306@stewart.chicago.il.us> Date: Sat, 23 Oct 2004 09:16:04 -0400 From: Randall Stewart User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.6) Gecko/20040429 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Marco Molteni References: <4177C8AD.6060706@freebsd.org> <20041021153933.GK13756@empiric.icir.org> <4177E25E.804639E@freebsd.org> <20041021213248.223cab2c.molter@tin.it> In-Reply-To: <20041021213248.223cab2c.molter@tin.it> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-net@freebsd.org cc: Andre Oppermann 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: Sat, 23 Oct 2004 13:17:25 -0000 Marco Molteni wrote: > On Thu, 21 Oct 2004 Andre Oppermann wrote: > > >>Bruce M Simpson wrote: >> >>>On Thu, Oct 21, 2004 at 04:33:17PM +0200, Andre Oppermann wrote: >>> >>>>Thus after the removal of T/TCP for the reasons above I want to >>>>provide a work-alike replacement for T/TCP's functionality: >>> >>>I disagree. I think the time spent here would be better spent on >>>working on an import of SCTP into the kernel, perhaps the KAME code >>>base would be a good starting point. >> >>Is the SCTP in KAME complete and stable? Are there any other (open >>source) implementations of it? > > > SCTP in KAME is complete, stable and fully supported. > It is mainly developed by the SCTP RFC author, Randall Stewart. > > A T/TCP alternative as you are describing sounds very > similar to PR-SCTP (Partial Reliability SCTP). (Don't let the > name fool you, please read the internet draft). RFC3758 (its a proposed standard now.. not a draft.) :-> R > There is at least another kernel-level open source implementation, > for Linux, plus other user-level implementations. > > marco -- Randall Stewart 803-345-0369 815-342-5222(cell)