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

Explain an unreachable destination

03

Type 3 reports reasons such as unreachable networks, hosts, protocols, or ports.

Related RFCs and changes

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

RFC 792 · Destination Unreachable MessageEXAMPLE
3 / 3
Explain an unreachable destinationType 3 reports reasons such as unreachable networks, hosts, protocols, or ports.sourcedestinationUDP to closed portICMP type 3 · code 3Original IP header + 64 data bitsThe quotation identifies traffic; it is not peer authentication
03
Quote the original header and data prefix so the sender can identify the traffic.

Quote the original header and data prefix so the sender can identify the traffic.

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

The code qualifies the failure; not all unreachable conditions have the same meaning.

  • The code qualifies the failure; not all unreachable conditions have the same meaning.
  • The original error includes the IP header and at least the first 64 data bits of the triggering datagram.
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. Report an IPv4 delivery problem
  2. Match an echo reply
  3. Explain an unreachable destination
  4. Observe a lifetime expiry
  5. Recognize retired Source Quench behavior
RFC 9700 / CHAPTERS

Chapters

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

RFC status and corrections ↗