Skip to content

Address Resolution Protocol

A local-link protocol that discovers the link-layer address associated with a network-layer address, most commonly mapping an IPv4 address to a MAC address.

Core Idea

ARP uses broadcast requests, unicast or broadcast replies and a time-limited neighbor cache; it assumes a local broadcast domain and lacks authentication, enabling spoofing unless networks add controls. A host checks its cache, broadcasts a query naming the target protocol address, the matching node replies with its hardware address, and the mapping is cached for subsequent frame delivery. The abstraction is therefore identified by a declared carrier, a transformation or constraint over that carrier, and an invariant that tells an analyst whether the named structure is genuinely present.

How would you explain it like I'm…

Who Has This Address?

On a home network, computers know each other by one kind of name but need a different, hardware name to actually deliver a message. So a computer shouts to everyone nearby, "Who has this name?" and the right computer answers, "That's me, here is my hardware name." The first computer writes it down for a while so it does not have to ask again. That asking game is the Address Resolution Protocol.

Finding a Neighbor's Hardware Address

The Address Resolution Protocol, or ARP, helps computers on the same local network find each other. Each computer has an internet-style address (an IP address) and a hardware address built into its network card. To send data, a computer needs the hardware address, so it first checks its memory list. If it's not there, it broadcasts a question to everyone nearby: "Who has this IP address?" The matching computer replies with its hardware address, and the asker saves the answer for a limited time. ARP doesn't check whether answers are honest, so an attacker can fake replies unless the network adds protections.

Local Address Lookup Protocol

The Address Resolution Protocol (ARP) maps a network-layer address, typically an IPv4 address, to a link-layer hardware address, such as an Ethernet MAC address, within a local broadcast domain. When a host needs to send a frame to another host on the same local network, it first checks its ARP cache. If there is no entry, it broadcasts an ARP request naming the target IP address; the host that owns that address replies with its hardware address, usually directly (unicast) but sometimes by broadcast. The requester stores the mapping in its cache for a limited time and uses it to address frames. There are variants: gratuitous ARP announces a host's own mapping, which also helps detect duplicate addresses, and proxy ARP lets one device answer on behalf of another. ARP has no authentication, so attackers can send fake replies (ARP spoofing) unless the network adds controls. It only works within a local broadcast domain, and IPv6 uses a different mechanism instead.

 

The Address Resolution Protocol resolves network-layer protocol addresses to link-layer hardware addresses within a single local broadcast domain. A host consults its neighbor cache; on a miss it broadcasts a request carrying the target protocol address, and the owning node returns its hardware address in a reply that may be unicast or broadcast. The resulting mapping is cached with a limited lifetime and used for subsequent frame delivery. Request and reply packets carry fields specifying the hardware and protocol types and address lengths along with sender and target addresses, so the protocol is not tied to one address family. Variants include gratuitous ARP, used for announcements and duplicate-address detection, and proxy ARP, where a node answers for addresses it does not own. ARP assumes a trusted local broadcast domain and lacks authentication, so forged replies can poison caches and enable interception unless networks add filtering or inspection controls. Failure handling, cache behavior, and security assumptions are part of its specification, and in IPv6 its role is taken over by a different neighbor-discovery mechanism.

Scope of Application

Address Resolution Protocol belongs to internet and link layer networking and is useful where the analyst can specify the typed internet and link layer networking carrier, defining objects and relations, parameters, conventions, evidence, boundary cases, and comparison targets, then evaluate the network and link-layer protocols, local broadcast domain, requester and target, protocol and hardware address lengths, request and reply fields, cache state and lifetime, duplicate-address behavior, proxy and gratuitous variants, failure handling, security assumptions, filtering and IPv6 replacement are explicit.

Clarity

The abstraction clarifies a crowded vocabulary by making the network and link-layer protocols, local broadcast domain, requester and target, protocol and hardware address lengths, request and reply fields, cache state and lifetime, duplicate-address behavior, proxy and gratuitous variants, failure handling, security assumptions, filtering and IPv6 replacement are explicit the center of the account. A claim should name the carrier, the governing operation or relation, the applicable assumptions, and the recognition test.

Manages Complexity

Without the abstraction, an analyst must reason directly over many local details: the carrier roles, admissibility assumptions, competing conventions, derived invariants, boundary cases, and proof or validation obligations specific to Address Resolution Protocol. Address Resolution Protocol compresses them into the roles in the structural signature. That compression permits comparison across instances without erasing the variables that determine validity. It also exposes which details may be varied safely and which are constitutive.

Abstract Reasoning

  1. Identify the carrier. State what the elements, states, objects, or observations are: the typed internet and link layer networking carrier, defining objects and relations, parameters, conventions, evidence, boundary cases, and comparison targets. Reject examples whose alleged carrier belongs to a different problem. 2.

Knowledge Transfer

Knowledge transfers strongly among subfields of internet and link layer networking because they reuse the typed internet and link layer networking carrier, defining objects and relations, parameters, conventions, evidence, boundary cases, and comparison targets, A host checks its cache, broadcasts a query naming the target protocol address, the matching node replies with its hardware address, and the mapping is cached for subsequent frame delivery., and type the carrier, state every parameter and convention in the definition, test that the network and link-layer protocols, local broadcast domain, requester and target, protocol and hardware address lengths, request and reply fields, cache state and lifetime, duplicate-address behavior, proxy and gratuitous variants, failure handling, security assumptions, filtering and IPv6 replacement are explicit, compare the nearest accepted identity, and report counterexamples, uncertainty, and limiting cases.

Relationships to Other Abstractions

Local relationship map for Address Resolution ProtocolParents appear above the current abstraction, mutual partners to the right, and children below. Node labels state whether each abstraction is prime or domain-specific; colors identify relation types.Address ResolutionProtocolDOMAINPrime abstraction: Search and Retrieval — is a kind ofSearch andRetrievalPRIME

Current abstraction Address Resolution Protocol Domain-specific

Parents (1) — outgoing typed relations

  • Address Resolution Protocol is a kind of Search and Retrieval Prime

    It remains its own entry because its identity is fixed by the network and link-layer protocols, local broadcast domain, requester and target, protocol and hardware address lengths, request and reply fields, cache state and lifetime, duplicate-address behavior, proxy and gratuitous variants, failure handling, security assumptions, filtering and IPv6 replacement.

Hierarchy paths (4) — routes to 3 parentless roots

Neighborhood in Abstraction Space

Address Resolution Protocol sits in a crowded region of the domain-specific corpus (12th percentile for distinctiveness): several abstractions share nearly its structure, so a description that fits it tends to fit its neighbors too.

Family — Network Architecture & Transport Protocols (26 abstractions)

Nearest neighbors

Computed from structural-signature embeddings · 2026-10-25