UDP Usage Guidelines for Application Designers
draft-eggert-tsvwg-udp-guidelines-02
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Lars Eggert | ||
| Last updated | 2007-05-29 (Latest revision 2007-04-09) | ||
| Replaced by | draft-ietf-tsvwg-udp-guidelines | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-tsvwg-udp-guidelines | |
| 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 upper-layer protocols that choose to use UDP as an Internet 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 that cover congestion-control and other topics, including message sizes and reliability.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)