[Tsvwg] comments wanted: draft-eggert-tsvwg-udp-guidelines

Lars Eggert <lars.eggert@nokia.com> Wed, 28 February 2007 10:39 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HMME1-0007ZZ-0t; Wed, 28 Feb 2007 05:39:57 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HMMDz-0007VN-FP for tsvwg@ietf.org; Wed, 28 Feb 2007 05:39:55 -0500
Received: from smtp.nokia.com ([131.228.20.170] helo=mgw-ext11.nokia.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HMMDw-0007cr-Q9 for tsvwg@ietf.org; Wed, 28 Feb 2007 05:39:55 -0500
Received: from esebh105.NOE.Nokia.com (esebh105.ntc.nokia.com [172.21.138.211]) by mgw-ext11.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id l1SAZPXQ024416 for <tsvwg@ietf.org>; Wed, 28 Feb 2007 12:35:57 +0200
Received: from esebh104.NOE.Nokia.com ([172.21.143.34]) by esebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 28 Feb 2007 12:39:25 +0200
Received: from esebh102.NOE.Nokia.com ([172.21.138.183]) by esebh104.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 28 Feb 2007 12:39:24 +0200
Received: from mgw-int01.ntc.nokia.com ([172.21.143.96]) by esebh102.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.1830); Wed, 28 Feb 2007 12:39:24 +0200
Received: from [172.21.34.191] (esdhcp034191.research.nokia.com [172.21.34.191]) by mgw-int01.ntc.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id l1SAZTp4007580 for <tsvwg@ietf.org>; Wed, 28 Feb 2007 12:35:29 +0200
Mime-Version: 1.0 (Apple Message framework v752.3)
To: tsvwg WG <tsvwg@ietf.org>
Message-Id: <21B62EB2-7A61-44EA-A346-3C86BCAADD76@nokia.com>
Content-Type: multipart/signed; micalg="sha1"; boundary="Apple-Mail-38--1069050903"; protocol="application/pkcs7-signature"
References: <E1HM9Gt-0001fP-8L@stiedprstage1.ietf.org>
From: Lars Eggert <lars.eggert@nokia.com>
Date: Wed, 28 Feb 2007 12:39:20 +0200
X-Mailer: Apple Mail (2.752.3)
X-OriginalArrivalTime: 28 Feb 2007 10:39:24.0995 (UTC) FILETIME=[B6F72930:01C75B24]
X-Nokia-AV: Clean
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8de5f93cb2b4e3bee75302e9eacc33db
Subject: [Tsvwg] comments wanted: draft-eggert-tsvwg-udp-guidelines
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

Hi,

Magnus and have recently had a number of discussions with application  
and application-layer-procotol designers on the use of UDP as a  
transport protocol. I've tried to write up a pretty short document  
that intends to give some guidelines to that community on the use of  
UDP as a transport protocol.

I'd be very interested in feedback from the transport community on  
whether this document is (1) useful and (2) has the correct guidelines.

Begin forwarded message:
> 	Title		: UDP Usage Guidelines for Application Designers
> 	Author(s)	: L. Eggert
> 	Filename	: draft-eggert-tsvwg-udp-guidelines-00.txt
> 	Pages		: 10
> 	Date		: 2007-2-27
> 	
>    The User Datagram Protocol (UDP) provides a minimal, message- 
> passing
>    transport that has no inherent congestion control mechanisms.
>    Because congestion control is critical to the stable operation  
> of the
>    Internet, applications and upper-layer protocols that choose to use
>    UDP as a transport must employ mechanisms to prevent congestion
>    collapse and establish some degree of fairness with concurrent
>    traffic.  This document provides guidelines on the use of UDP  
> for the
>    designers of such applications and upper-layer protocols.
>
> http://www.ietf.org/internet-drafts/draft-eggert-tsvwg-udp- 
> guidelines-00.txt

Lars