UDP Usage Guidelines
draft-tsvwg-rfc5405bis-00

Document Type Replaced Internet-Draft (individual)
Last updated 2014-12-09
Replaced by draft-ietf-tsvwg-rfc5405bis
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-ietf-tsvwg-rfc5405bis
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-tsvwg-rfc5405bis-00.txt

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.

Authors

Lars Eggert (lars@netapp.com)
Gorry Fairhurst (gorry@erg.abdn.ac.uk)
Greg Shepherd (gjshep@gmail.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)