Reverse Address Resolution Protocol
From Wikipedia, the free encyclopedia
| The TCP/IP model (RFC 1122) |
|---|
| Application Layer |
|
DHCP · DNS · FTP · Gopher · HTTP · IMAP4 · IRC · NNTP · XMPP · POP3 · RTP · SIP · SMTP · SNMP · SSH · TELNET · RPC · RTCP · RTSP · TLS (and SSL) · SDP · SOAP · GTP · STUN · NTP · BGP · RIP · (more) |
| Transport Layer |
| TCP · UDP · DCCP · SCTP · RSVP · ECN · (more) |
| Internet Layer |
| IP (IPv4 · IPv6) · ICMP · ICMPv6 · IGMP · IPsec · (more) |
| Link Layer |
| ARP · RARP · NDP · OSPF · IS-IS · Tunnels · Device Drivers · Media Access Control · (more) |
Reverse Address Resolution Protocol (RARP) is a Link layer protocol used to obtain an IP address for a given link-layer address (such as an Ethernet address). RARP is described in IETF publication RFC 903. It has been rendered obsolete by Bootstrap Protocol and the more modern Dynamic Host Configuration Protocol, which both support a much greater feature set than RARP.
The primary limitations of RARP are that each MAC address must be manually configured on a central server, and that the protocol only conveys an IP address. This leaves configuration of subnetting, gateways, and other information to other protocols or the user. Another limitation of RARP compared to BOOTP or DHCP is that it is a non-IP protocol. This means that like ARP it cannot be handled by the TCP/IP stack on the client, but is instead implemented separately.
Reverse ARP is the complement of the Address Resolution Protocol. RARP also differs from Inverse Address Resolution Protocol (InARP), which is designed to locate the IP address associated with another station's MAC address.
[edit] See also
- Dynamic Host Configuration Protocol (DHCP)
- Bootstrap protocol (BOOTP)
- Address Resolution Protocol (ARP)
- Maintenance Operations Protocol (MOP)
