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

Demultiplex using ports

02

A destination port selects a receiving application in the context of the destination IP address.

Related RFCs and changes

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

DIAGRAMFields ↗
RFC 768 · FieldsEXAMPLE
3 / 3
Demultiplex using portsA destination port selects a receiving application in the context of the destination IP address.IP hostUDP destination port 53000port 53000port 5400053000 matchesdeliverPort selection is scoped to the destination IP address
03
Deliver it to the corresponding receive port, not every application.

Deliver it to the corresponding receive port, not every application.

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

UDP source and destination port fields are each 16 bits.

  • UDP source and destination port fields are each 16 bits.
  • The original source-port field may be zero when unused; a meaningful source port can guide replies.
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 ↗