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

Preserve a datagram boundary

01

UDP sends discrete application messages with very little transport mechanism.

Related RFCs and changes

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

RFC 768 · IntroductionEXAMPLE
3 / 3
Preserve a datagram boundaryUDP sends discrete application messages with very little transport mechanism.sendermessage Amessage Blostmessage Areceiverintact boundaryUDP does not restore the missing message B
03
The surviving datagram remains a message; UDP does not reconstruct the missing one.

The surviving datagram remains a message; UDP does not reconstruct the missing one.

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

UDP does not guarantee arrival, ordering, or duplicate protection.

  • UDP does not guarantee arrival, ordering, or duplicate protection.
  • Applications needing reliable ordered streams require another mechanism.
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 ↗