UDP Usage Guidelines
draft-ietf-tsvwg-rfc5405bis-06

The information below is for an old version of the document
Document Type None Internet-Draft (tsvwg WG)
Last updated 2015-09-21 (latest revision 2015-09-18)
Replaces draft-tsvwg-rfc5405bis, draft-eggert-tsvwg-rfc5405bis
Stream IETF
Intended RFC status Best Current Practice
Formats
Expired & archived
pdf htmlized bibtex
Reviews
Additional URLs
- Mailing list discussion
Stream WG state (None)
Document shepherd No shepherd assigned
IESG IESG state Unknown state
Consensus Boilerplate Unknown
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-ietf-tsvwg-rfc5405bis-06.txt

Abstract

The User Datagram Protocol (UDP) provides a minimal message-passing transport that has no inherent congestion control mechanisms. 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, middlebox traversal, the use of ECN, DSCPs, and ports. 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. Some guidance is also applicable to the design of other protocols (e.g., protocols layered directly on IP or via IP-based tunnels), especially when these protocols do not themselves provide congestion control. 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.)