Browse Prior Art Database

UDP Usage Guidelines (RFC8085) Disclosure Number: IPCOM000249615D
Original Publication Date: 2017-Mar-01
Included in the Prior Art Database: 2017-Mar-08

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

L. Eggert: AUTHOR [+3]


The User Datagram Protocol (UDP) [RFC768] provides a minimal, unreliable, best-effort, message-passing transport to applications and other protocols (such as tunnels) that wish to operate over IP. Both are simply called "applications" in the remainder of this document.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 2% of the total text.

Internet Engineering Task Force (IETF)                         L. Eggert Request for Comments: 8085                                        NetApp BCP: 145                                                    G. Fairhurst Obsoletes: 5405                                   University of Aberdeen Category: Best Current Practice                              G. Shepherd ISSN: 2070-1721                                            Cisco Systems                                                               March 2017

                           UDP Usage Guidelines


   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 Explicit    Congestion Notification (ECN), Differentiated Services Code Points    (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.

   This document obsoletes RFC 5405 and adds guidelines for multicast    UDP usage.

 Eggert, et al.            Best Current Practice                 [Page 1]
 RFC 8085                  UDP Usage Guidelines                March 2017

 Status of This Memo

   This memo documents an Internet Best Current Practice.

   This document is a product of the Internet Engineering Task Force    (IETF).  It represents the consensus of the IETF community.  It has    received public review and has been approved for publication by the    Internet Engineering Steering Group (IESG).  Further information on    BCPs is available in Section 2 of RFC 7841.

   Information about the current status of this document, any errata,    and how to provide feedback on it may be obtained at    http://www.rfc-edi...