Which RFC Defines the UDP Standard?

The User Datagram Protocol (UDP) is officially defined by RFC 768. Published in August 1980 by David P. Reed, this brief yet foundational document establishes the operational specifications, header structure, and design principles of UDP within the Internet Protocol (IP) suite. This article covers the essential details of RFC 768, the core characteristics of UDP specified in the standard, and its role in modern computer networking.

Overview of RFC 768

RFC 768, titled simply User Datagram Protocol, is the definitive Internet Standard (STD 6) for UDP. Unlike the Transmission Control Protocol (TCP), which prioritizes reliable, ordered delivery through connection management, RFC 768 outlines a minimal, transaction-oriented protocol designed for low-overhead communications.

Key Specifications Defined in RFC 768

RFC 768 defines UDP as a connectionless transport layer protocol operating on top of IP. The key elements defined in the document include:

• 8-Byte Header: The UDP header is fixed at only 8 bytes (64 bits), significantly smaller than TCP’s 20-byte minimum header.
• Header Fields:
  1. Source Port (16 bits): Indicates the sending port, optional if no reply is expected.
  2. Destination Port (16 bits): Indicates the target port where the packet should be delivered.
  3. Length (16 bits): Specifies the total length in bytes of the UDP header and the payload combined (minimum value is 8).
  4. Checksum (16 bits): Provides optional error-checking for the header, payload, and a conceptual IP pseudo-header.
• No Connection Establishment: RFC 768 specifies that no handshake (such as TCP’s three-way handshake) is required before data transmission begins.
• Unreliable Delivery: The protocol does not guarantee packet delivery, ordering, or duplicate protection. Error recovery and flow control are left entirely to the application layer.

Practical Applications of UDP

Because RFC 768 provides a lightweight mechanism with minimal latency, UDP is the standard choice for time-sensitive applications and services where speed is favored over guaranteed delivery, including:

• Domain Name System (DNS) queries and responses.
• Real-time audio and video streaming (VoIP, video conferencing).
• Online multiplayer gaming.
• Network management protocols like SNMP and NTP.
• Modern transport protocols like QUIC (HTTP/3), which builds advanced reliability and encryption features on top of UDP.

Conclusion

RFC 768 remains the definitive standard that governs the User Datagram Protocol. Despite being only three pages long and published in 1980, its minimalist design continues to serve as a critical pillar of global internet infrastructure today.