Visual RFC.
ALL RFCs / RFC 768
Read the RFC ↗
RFC 768 / PROTOCOL MECHANISMS

Count the header and data

03

The UDP header is eight octets; the Length field includes both that header and the payload.

Related RFCs and changes

“Updates” changes part of an earlier RFC. “Obsoletes” replaces it. This list shows selected related documents.

DIAGRAMFormat ↗
RFC 768 · FormatEXAMPLE
3 / 3
Count the header and dataThe UDP header is eight octets; the Length field includes both that header and the payload.UDP HEADER · 8 OCTETSSource portDestination portLengthChecksumExample payload: 12 octets8 + 12 = 20 octetsLength includes the header, not just application data
03
The example UDP Length is twenty octets.

The example UDP Length is twenty octets.

Protocol participantThreat or exceptionProtocol controlSimplified drawings · precise section references
KEY POINT

The minimum UDP Length is eight.

  • The minimum UDP Length is eight.
  • The original 16-bit field bounds the ordinary UDP datagram length; IPv6 jumbograms are a separate extension.
DETAILS

The drawing is a simplified worked example. Follow the linked RFC and its updates for implementation requirements.

Read the RFC section ↗

Diagrams simplify the RFC. Read the linked sections for complete requirements.

Privacy
All chapters in this RFC
  1. Preserve a datagram boundary
  2. Demultiplex using ports
  3. Count the header and data
  4. Check a datagram’s integrity
  5. Separate UDP from application reliability
RFC 9700 / CHAPTERS

Chapters

For full details, tables, algorithms, and exceptions, read the original RFC.

RFC status and corrections ↗