---

User Datagram Protocol (UDP)

---

1. Overview and Core Philosophy

The User Datagram Protocol (UDP) (RFC 768) is a lightweight, connectionless Transport Layer protocol in the TCP/IP protocol suite.

While TCP provides guaranteed, highly regulated delivery, UDP is designed with a minimalist philosophy: it provides the absolute minimum transport service required—process-to-process multiplexing via port numbers and basic optional error detection—without adding connection handshakes, retransmissions, or flow throttling.

---

2. Key Characteristics of UDP

1. Connectionless:
   • Transmits data immediately without performing a handshake (zero round-trip setup delay).
2. Unreliable (Best-Effort Delivery):
   • Does not acknowledge receipt of packets (No ACKs).
   • Packets may be dropped, duplicated, delayed, or arrive out of order. If reliability is needed, the application layer itself must implement sequence tracking.
3. No Flow Control or Congestion Control:
   • The UDP sender transmits datagrams at whatever rate the application generates them. It never slows down in response to network congestion or receiver buffer exhaustion.
4. Message-Oriented (Preserves Message Boundaries):
   • Unlike TCP's byte-stream model, UDP packages each write call into an independent datagram. If an application writes 500 bytes, UDP sends a 500-byte datagram; the receiver reads exactly 500 bytes in a single read operation.
5. Supports Multicast and Broadcast:
   • Because UDP is connectionless, a single packet can be addressed to a broadcast or multicast group (TCP only supports 1-to-1 unicast connections).

---

3. UDP Datagram Format

The UDP header is exceptionally compact, consisting of only 8 bytes (64 bits) divided into four 16-bit fields:

Field Breakdown:

1. Source Port (16 bits): Port of the sending process on the client or server. Optional (set to 0 if no reply is expected).
2. Destination Port (16 bits): Port of the target process on the destination machine (mandatory for demultiplexing).
3. Length (16 bits): Total length of the UDP segment in bytes (Header + Data). Minimum value is 8 (a datagram with zero payload bytes).
4. Checksum (16 bits): One's complement checksum covering the UDP header, UDP payload, and an imaginary IP Pseudo-Header. (Optional in IPv4, but mandatory in IPv6).

---

4. The UDP Pseudo-Header

To verify that the packet was not delivered to the wrong IP destination due to a corrupted IP header, UDP computes its checksum over an imaginary Pseudo-Header prepended to the segment during calculation:

• If the computed checksum does not match at the receiver, the damaged UDP datagram is silently discarded.

---

5. When is UDP Preferred over TCP?

Application Category	Why UDP is Ideal	Examples
Real-Time Multimedia	Retransmitting a dropped audio/video frame $200\text{ ms}$ late is useless; humans prefer minor glitching over freezing audio.	VoIP (SIP/RTP), Zoom, Live Gaming, Video Streaming
Simple Request-Response	Completes in a single round-trip without connection setup/teardown overhead.	DNS (Port 53), DHCP (Port 67), NTP (Port 123)
Network Management	Works even on unstable, highly congested links.	SNMP (Port 161), TFTP (Port 69)
Multicast / Broadcast	TCP cannot maintain synchronized connection states with multiple recipients.	IPTV, mDNS, Routing updates (RIP)

---