Separate UDP from application reliability
05UDP’s interface supplies addresses, ports, and datagrams; delivery policy belongs above this minimal service.
Related RFCs and changes
“Updates” changes part of an earlier RFC. “Obsoletes” replaces it. This list shows selected related documents.
DIAGRAMUser Interface ↗
RFC 768 · User InterfaceEXAMPLE
3 / 3
03
An application-defined reply can supply evidence that UDP itself does not.
An application-defined reply can supply evidence that UDP itself does not.
Protocol participantThreat or exceptionProtocol controlSimplified drawings · precise section references
Read the updated RFC section ↗
A successful local send does not prove the remote application received the message.
- A successful local send does not prove the remote application received the message.
- This RFC supplies no handshake, retransmission timer, congestion controller, or cryptographic peer authentication.
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