RFC 826: An Ethernet Address Resolution Protocol: Or Converting Network Protocol Addresses to 48.bit Ethernet Address for Transmission on Ethernet Hardware

The purpose of this RFC is to present a method of Converting Protocol Addresses (e.g., IP addresses) to Local Network Addresses (e.g., Ethernet addresses).…

Read RFC 826 on the RFC Editor

Incoming relationships (68 related RFCs)

Showing 50 of 68 related RFCs.

Updated by — RFC 5227: IPv4 Address Conflict Detection
Updated by, Normatively referenced by — RFC 5494: IANA Allocation Guidelines for the Address Resolution Protocol (ARP)
Normatively referenced by — RFC 3927: Dynamic Configuration of IPv4 Link-Local Addresses
Normatively referenced by — RFC 6740: Identifier-Locator Network Protocol (ILNP) Architectural Description
Normatively referenced by — RFC 6747: Address Resolution Protocol (ARP) for the Identifier-Locator Network Protocol for IPv4 (ILNPv4)
Normatively referenced by — RFC 4436: Detecting Network Attachment in IPv4 (DNAv4)
Normatively referenced by — RFC 7513: Source Address Validation Improvement (SAVI) Solution for DHCP
Normatively referenced by — RFC 9161: Operational Aspects of Proxy ARP/ND in Ethernet Virtual Private Networks
Normatively referenced by — RFC 6939: Client Link-Layer Address Option in DHCPv6
Normatively referenced by — RFC 4562: MAC-Forced Forwarding: A Method for Subscriber Separation on an Ethernet Access Network
Normatively referenced by — RFC 5692: Transmission of IP over Ethernet over IEEE 802.16 Networks
Normatively referenced by — RFC 6575: Address Resolution Protocol (ARP) Mediation for IP Interworking of Layer 2 VPNs
Normatively referenced by — RFC 7342: Practices for Scaling ARP and Neighbor Discovery (ND) in Large Data Centers
Normatively referenced by — RFC 7586: The Scalable Address Resolution Protocol (SARP) for Large Data Centers
Normatively referenced by — RFC 8171: Transparent Interconnection of Lots of Links (TRILL): Edge Directory Assistance Mechanisms
Normatively referenced by — RFC 8302: Transparent Interconnection of Lots of Links (TRILL): ARP and Neighbor Discovery (ND) Optimization
Normatively referenced by — RFC 6018: IPv4 and IPv6 Greynets
Normatively referenced by — RFC 7436: IP-Only LAN Service (IPLS)
Normatively referenced by — RFC 9721: Extended Mobility Procedures for Ethernet VPN Integrated Routing and Bridging (EVPN-IRB)
Informatively referenced by — RFC 4861: Neighbor Discovery for IP version 6 (IPv6)
Informatively referenced by — RFC 1122: Requirements for Internet Hosts - Communication Layers
Informatively referenced by — RFC 2002: IP Mobility Support
Informatively referenced by — RFC 3819: Advice for Internet Subnetwork Designers
Informatively referenced by — RFC 1042: Standard for the transmission of IP datagrams over IEEE 802 networks
Informatively referenced by — RFC 1209: The Transmission of IP Datagrams over the SMDS Service
Informatively referenced by — RFC 894: A Standard for the Transmission of IP Datagrams over Ethernet Networks
Informatively referenced by — RFC 6741: Identifier-Locator Network Protocol (ILNP) Engineering Considerations
Informatively referenced by — RFC 1970: Neighbor Discovery for IP Version 6 (IPv6)
Informatively referenced by — RFC 5218: What Makes for a Successful Protocol?
Informatively referenced by — RFC 7426: Software-Defined Networking (SDN): Layers and Architecture Terminology
Informatively referenced by — RFC 1293: Inverse Address Resolution Protocol
Informatively referenced by — RFC 4388: Dynamic Host Configuration Protocol (DHCP) Leasequery
Informatively referenced by — RFC 1027: Using ARP to implement transparent subnet gateways
Informatively referenced by — RFC 8344: A YANG Data Model for IP Management
Informatively referenced by — RFC 9099: Operational Security Considerations for IPv6 Networks
Informatively referenced by — RFC 1294: Multiprotocol Interconnect over Frame Relay
Informatively referenced by — RFC 6820: Address Resolution Problems in Large Data Center Networks
Informatively referenced by — RFC 1011: Official Internet protocols
Informatively referenced by — RFC 5556: Transparent Interconnection of Lots of Links (TRILL): Problem and Applicability Statement
Informatively referenced by — RFC 7067: Directory Assistance Problem and High-Level Design Proposal
Informatively referenced by — RFC 9834: YANG Data Models for Bearers and Attachment Circuits as a Service (ACaaS)
Informatively referenced by — RFC 948: Two methods for the transmission of IP datagrams over IEEE 802.3 networks
Informatively referenced by — RFC 1188: Proposed Standard for the Transmission of IP Datagrams over FDDI Networks
Informatively referenced by — RFC 1390: Transmission of IP and ARP over FDDI Networks
Informatively referenced by — RFC 1433: Directed ARP
Informatively referenced by — RFC 1931: Dynamic RARP Extensions for Automatic Network Address Acquisition
Informatively referenced by — RFC 2896: Remote Network Monitoring MIB Protocol Identifier Macros
Informatively referenced by — RFC 3077: A Link-Layer Tunneling Mechanism for Unidirectional Links
Informatively referenced by — RFC 4058: Protocol for Carrying Authentication for Network Access (PANA) Requirements
Informatively referenced by — RFC 7212: MPLS Generic Associated Channel (G-ACh) Advertisement Protocol