UDP Usage Guidelines
draft-eggert-tsvwg-rfc5405bis-01
| Document | Type |
Replaced Internet-Draft
(tsvwg WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Lars Eggert , Gorry Fairhurst , Greg Shepherd | ||
| Last updated | 2015-10-14 (Latest revision 2014-06-17) | ||
| Replaced by | draft-ietf-tsvwg-rfc5405bis | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | Best Current Practice | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | Adopted by a WG | |
| Document shepherd | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-tsvwg-rfc5405bis | |
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
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
Gorry Fairhurst
Greg Shepherd
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)