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

Match an echo reply

02

An Echo Reply returns the request data along with its identifier and sequence number.

Related RFCs and changes

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

RFC 792 · Echo or Echo Reply MessageEXAMPLE
3 / 3
Match an echo replyAn Echo Reply returns the request data along with its identifier and sequence number.requesterpeertype 8 · id 7 · seq 2type 0 · id 7 · seq 2PINGIdentifier + sequence + returned data matchAn absent reply can mean loss or filtering
03
Match the reply to the request using the echoed fields.

Match the reply to the request using the echoed fields.

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

Echo Request is type 8; Echo Reply is type 0.

  • Echo Request is type 8; Echo Reply is type 0.
  • A missing reply can mean loss or filtering; it is not proof that the host does not exist.
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 ↗