[tsvwg] Fwd: New Version Notification for draft-eggert-tsvwg-rfc5405bis-00.txt

["Eggert, Lars" <[e-mail]>]

Hi,

Gorry and me have started to put together an update to RFC5405 in light of the recent discussions. Comments welcome.

Lars


Begin forwarded message:

> From: <[e-mail]>
> Subject: New Version Notification for draft-eggert-tsvwg-rfc5405bis-00.txt
> Date: June 14, 2014 at 12:14:42 GMT+2
> To: Lars Eggert <[e-mail]>, Godred Fairhurst <[e-mail]>, Gorry Fairhurst <[e-mail]>, Lars Eggert <[e-mail]>
> 
> 
> A new version of I-D, draft-eggert-tsvwg-rfc5405bis-00.txt
> has been successfully submitted by Lars Eggert and posted to the
> IETF repository.
> 
> Name:		draft-eggert-tsvwg-rfc5405bis
> Revision:	00
> Title:		UDP Usage Guidelines
> Document date:	2014-06-14
> Group:		Individual Submission
> Pages:		36
> URL:            http://www.ietf.org/internet-drafts/draft-eggert-tsvwg-rfc5405bis-00.txt
> Status:         https://datatracker.ietf.org/doc/draft-eggert-tsvwg-rfc5405bis/
> Htmlized:       http://tools.ietf.org/html/draft-eggert-tsvwg-rfc5405bis-00
> 
> 
> Abstract:
>   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 other protocols that choose to use UDP as
>   an Internet transport must employ mechanisms to prevent congestion
>   collapse and to establish some degree of fairness with concurrent
>   traffic.  They may also need to implement additional mechanisms,
>   depending on how they use UDP.
> 
>   This document provides guidelines on the use of UDP for the designers
>   of applications, tunnels and other protocols that use UDP.
>   Congestion control guidelines are a primary focus, but the document
>   also provides guidance on other topics, including message sizes,
>   reliability, checksums, and middlebox traversal.
> 
>   If published as an RFC, this document will obsolete RFC5405.
> 
> 
> 
> 
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
> 
> The IETF Secretariat
>