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

RFC 792 / START HERE

ICMPv4, before the details

ICMP: Internet Control Message Protocol

ICMP carries control and error information about IPv4 traffic. It helps devices report problems that ordinary application data cannot explain.

The idea in one picture

  1. A packet encounters a problem

  2. ICMP reports information

  3. The sender can react

A simplified picture of the idea; the chapters explain the actual mechanisms.

Why it exists

A sender needs feedback when a destination cannot be reached or a packet cannot proceed.

A familiar example

The ping utility uses ICMP echo messages to check whether another device responds.

Helpful background

You can start here without reading another RFC. If these ideas are unfamiliar, these short introductions may help.

What you’ll learn next

Begin with chapter one, or choose a topic.

  1. Report an IPv4 delivery problemICMP returns control information to the source of an IPv4 datagram.
  2. Match an echo replyAn Echo Reply returns the request data along with its identifier and sequence number.
  3. Explain an unreachable destinationType 3 reports reasons such as unreachable networks, hosts, protocols, or ports.
  4. Observe a lifetime expiryTime Exceeded distinguishes transit TTL expiry from fragment-reassembly timeout.
  5. Recognize retired Source Quench behaviorSource Quench was an early congestion signal and is now deprecated.
Start with chapter one →

This introduction explains RFC 792 (1981). Read the original RFC ↗