A Large UDP Message May Depend on Every IP Fragment

A voice application batches a few encoded audio frames into one large UDP message to reduce per-message overhead. On a path whose maximum transmission unit is smaller than the resulting IP packet, the packet may be fragmented. The receiver needs every fragment before it can reassemble and deliver the datagram. One lost fragment therefore discards the whole audio batch, including the frames whose fragments arrived.

That all-or-nothing dependency is the central warning in RFC 8085’s message-size guidance. Fragmentation affects both IPv4 and IPv6, and some network address translators or firewalls drop fragments outright. A large datagram can pass on one route and fail when a tunnel or a different route reduces the available packet size. Testing only on a local network gives weak evidence for an Internet-facing voice service.

The path maximum transmission unit, or PMTU, is the largest IP packet a route can carry without fragmentation. The usable UDP payload is smaller: subtract the IP header, including any options or extension headers, and the eight-byte UDP header. Tunnels can reduce the effective PMTU further. RFC 8085 recommends using PMTU information from the IP layer or discovering it. Ordinary discovery can be impaired when intermediate devices filter the control messages it needs. Packetization-layer discovery uses probes and success or loss feedback instead, which adds protocol work that UDP itself does not provide.

When a voice protocol splits a larger application message across UDP datagrams, design each datagram to be useful independently where possible. Put sequence or timestamp information in the application framing so the receiver can identify gaps and decide whether a late frame still matters. If the application offers reliability, it can retransmit an individual missing datagram; an IP fragment cannot be recovered that way by the application. A codec or envelope that requires every piece before playback can recreate the same all-or-nothing failure above the transport layer, so choose boundaries around independently decodable units when the format permits.

Smaller datagrams add headers and may be inefficient on a path with a generous PMTU. They also do not excuse unlimited send rates: RFC 8085 asks UDP applications to control congestion. For a real-time voice path, determine a payload ceiling from the path, include encapsulation overhead, and measure loss and delay as the route changes. Keep frames small enough for that ceiling while preserving a rate the network can carry.