Reverse Address Resolution Protocol
| Internet protocol suite |
|---|
| Application layer |
| Transport layer |
| Internet layer |
| Link layer |
The Reverse Address Resolution Protocol (RARP) is an obsolete computer communication protocol used by a client computer to request its Internet Protocol (IPv4) address from a computer network, when all it has available is its link layer or hardware address, such as a MAC address.[1] The client broadcasts the request and does not need prior knowledge of the network topology or the identities of servers capable of fulfilling its request.
RARP has been rendered obsolete by the Bootstrap Protocol (BOOTP) and the modern Dynamic Host Configuration Protocol (DHCP), which both support a much greater feature set than RARP.
RARP requires one or more server hosts to maintain a database of mappings of link layer addresses to their respective protocol addresses. MAC addresses need to be individually configured on the servers by an administrator. RARP is limited to serving only IP addresses.
Reverse ARP differs from the Inverse Address Resolution Protocol (InARP), which is designed to obtain the IP address associated with a local Frame Relay data link connection identifier.[2] InARP is not used in Ethernet.
Modern Day Uses
[edit]Although the original uses for RARP have been superseded by different protocols, some modern-day protocols use RARP to handle MAC migration, particularly in virtual machines, using a technique originating in QEMU.
Examples include:
- Cisco's Overlay Transport Virtualization (OTV). RARP is used to update the layer 2 forwarding tables when a MAC address moves between data centers.
- VMware vSphere's vMotion.[3] RARP is used when a VM MAC moves between hosts.
See also
[edit]References
[edit]- ^ R. Finlayson; T. Mann; J. Mogul; M. Theimer (June 1984). A Reverse Address Resolution Protocol. Network Working Group. doi:10.17487/RFC0903. STD 38. RFC 903. Internet Standard 38.
- ^ T. Bradley; C. Brown; A. Malis (September 1998). Inverse Address Resolution Protocol. Network Working Group. doi:10.17487/RFC2390. RFC 2390. Draft Standard. Obsoletes RFC 1293.
- ^ Deshpande, Venky (22 July 2013). "VXLAN Series – How vMotion impacts the forwarding table – Part 6". vmware. Retrieved 15 March 2023.