From owner-freebsd-hackers@FreeBSD.ORG  Mon Jul 12 19:29:26 2010
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
Delivered-To: hackers@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 84B3B1065670
	for <hackers@freebsd.org>; Mon, 12 Jul 2010 19:29:26 +0000 (UTC)
	(envelope-from bruce@cran.org.uk)
Received: from muon.cran.org.uk (muon.cran.org.uk [204.109.60.94])
	by mx1.freebsd.org (Postfix) with ESMTP id 4B8288FC0A
	for <hackers@freebsd.org>; Mon, 12 Jul 2010 19:29:26 +0000 (UTC)
Received: from unknown (client-86-31-3-93.midd.adsl.virginmedia.com
	[86.31.3.93])
	(using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits))
	(No client certificate requested)
	by muon.cran.org.uk (Postfix) with ESMTPSA id ACB765F0C;
	Mon, 12 Jul 2010 19:29:11 +0000 (UTC)
Date: Mon, 12 Jul 2010 20:29:25 +0100
From: Bruce Cran <bruce@cran.org.uk>
To: Sergey Babkin <babkin@verizon.net>
Message-ID: <20100712202925.00002273@unknown>
In-Reply-To: <4C386208.291D2FB5@verizon.net>
References: <4C386208.291D2FB5@verizon.net>
X-Mailer: Claws Mail 3.7.4cvs1 (GTK+ 2.16.0; i586-pc-mingw32msvc)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Cc: hackers@freebsd.org
Subject: Re: TCP over UDP
X-BeenThere: freebsd-hackers@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Technical Discussions relating to FreeBSD
	<freebsd-hackers.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>, 
	<mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers>
List-Post: <mailto:freebsd-hackers@freebsd.org>
List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
	<mailto:freebsd-hackers-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Jul 2010 19:29:26 -0000

On Sat, 10 Jul 2010 08:05:29 -0400
Sergey Babkin <babkin@verizon.net> wrote:

> Basically, every time you use UDP, you've got to reinvent your
> own retransmission and reliability protocol. And these protocols
> are typically no good at all, as the story with NFS switching
> from UDP to TCP and improving the performance shows. At the same
> time TCP provides a very good transport control logic, so why not
> just reuse this logic in a library to solve the UDP issues once
> and for all?

Have you looked at SCTP? It may provide the features you've looking
for:
http://en.wikipedia.org/wiki/Stream_Control_Transmission_Protocol#Motivations

-- 
Bruce Cran