RFC 5405: Unicast UDP Usage Guidelines for Application Designers
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 8085.
Current version: RFC 8085 — UDP Usage Guidelines
In plain English — editorial summary, not part of the RFC
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 to establish some degree of fairness with concurrent traffic. This document provides guidelines on the use of UDP for the designers of unicast applications and upper-layer protocols. Congestion control guidelines are a primary focus, but the document also provides guidance on other topics, including message sizes, reliability, checksums, and middlebox traversal. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.
Document record
- Document ID
- RFC5405
- Published
- November 2008
- Authors
- L. Eggert; G. Fairhurst
- Status
- BEST CURRENT PRACTICE
- Stream
- IETF
- Area
- wit
- Pages
- 27
- Also known as
- —
- Obsoleted by:
- RFC 8085
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8084Network Transport Circuit BreakersCurrent
March 2017
- RFC 6582The NewReno Modification to TCP's Fast Recovery AlgorithmCurrent
April 2012
- RFC 6633Deprecation of ICMP Source Quench MessagesCurrent
May 2012
- RFC 6675A Conservative Loss Recovery Algorithm Based on Selective Acknowledgment (SACK) for TCPCurrent
August 2012
- RFC 6679Explicit Congestion Notification (ECN) for RTP over UDPUpdated
August 2012
- RFC 7141Byte and Packet Congestion NotificationCurrent
February 2014
- RFC 3517A Conservative Selective Acknowledgment (SACK)-based Loss Recovery Algorithm for TCPObsoleted
April 2003
- RFC 7560Problem Statement and Requirements for Increased Accuracy in Explicit Congestion Notification (ECN) FeedbackCurrent
August 2015
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?