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

Report an IPv4 delivery problem

01

ICMP returns control information to the source of an IPv4 datagram.

Related RFCs and changes

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

RFC 792 · IntroductionEXAMPLE
3 / 3
Report an IPv4 delivery problemICMP returns control information to the source of an IPv4 datagram.sourcerouteroriginal IP trafficICMP errorquoted original bytesfeedbackICMP feedback does not complete the original delivery
03
Send feedback toward the original source, not onward as payload delivery.

Send feedback toward the original source, not onward as payload delivery.

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

ICMP uses IP protocol number 1 and is carried inside an IP datagram.

  • ICMP uses IP protocol number 1 and is carried inside an IP datagram.
  • Feedback does not make IP reliable; ICMP errors are not sent in response to ICMP errors.
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 ↗