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

Read the variable-address packet

03

ARP identifies hardware and protocol spaces, address lengths, opcode, and sender and target address pairs.

Related RFCs and changes

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

RFC 826 · Packet formatEXAMPLE
3 / 3
Read the variable-address packetARP identifies hardware and protocol spaces, address lengths, opcode, and sender and target address pairs.hardware typeprotocol typehlen 6plen 4opcodesender MAC · 6 octetssender IPv4 · 4 octetstarget MAC · 6 octetstarget IPv4 · 4 octetsVariable lengths determine each address boundaryEthernet/IPv4 worked example; schematic field widths
03
The opcode determines request or reply, not the shape of an IP header.

The opcode determines request or reply, not the shape of an IP header.

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

For Ethernet/IPv4, hardware and protocol address lengths are six and four octets.

  • For Ethernet/IPv4, hardware and protocol address lengths are six and four octets.
  • Multibyte values use the specified network transmission order.
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. Resolve the next hop on a link
  2. Broadcast a question and receive a reply
  3. Read the variable-address packet
  4. Learn from the sender mapping
  5. Probe before claiming an IPv4 address

Drawing view

Scroll the drawing to see every part. Playback controls stay above it.

RFC 9700 / CHAPTERS

Chapters

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

RFC status and corrections ↗