Inverse Address Resolution Protocol (RFC1293)
Original Publication Date: 1992-Jan-01
Included in the Prior Art Database: 2019-Feb-11
Internet Society Requests For Comment (RFCs)
T. Bradley: AUTHOR [+1]
This memo describes additions to ARP that will allow a station to request a protocol address corresponding to a given hardware address. [STANDARDS-TRACK]
Network Working Group T. Bradley Request for Comments: 1293 C. Brown Wellfleet Communications, Inc. January 1992
Inverse Address Resolution Protocol
1. Status of this Memo
This RFC specifies an IAB standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "IAB Official Protocol Standards" for the standardization state and status of this protocol. Distribution of this memo is unlimited.
This memo describes additions to ARP that will allow a station to request a protocol address corresponding to a given hardware address. Specifically, this applies to Frame Relay stations that may have a Data Link Connection Identifier (DLCI), the Frame Relay equivalent of a hardware address, associated with an established Permanent Virtual Circuit (PVC), but do not know the protocol address of the station on the other side of this connection. It will also apply to other networks with similar circumstances.
The following language conventions are used in the items of specification in this document:
o Must, Will, Shall or Mandatory -- the item is an absolute requirement of the specification.
o Should or Recommended -- the item should generally be followed for all but exceptional circumstances.
o May or Optional -- the item is truly optional and may be followed or ignored according to the needs of the implementor.
This document will rely heavily on Frame Relay as an example of how the Inverse Address Resolution Protocol (InARP) can be useful. It is not, however, intended that InARP be used exclusively with Frame Relay. InARP may be used in any network that provides destination hardware addresses without indicating corresponding protocol
Bradley, Brown [Page 1]
RFC 1293 Inverse ARP January 1992
The motivation for the development of Inverse ARP is a result of the desire to make dynamic address resolution within Frame Relay both possible and efficient. Permanent virtual circuits (PVCs) and eventually switched virtual circuits (SVCs) are identified by a Data Link Connection Identifier (DLCI). These DLCIs define a single virtual connection through the wide area network (WAN) and are the Frame Relay equivalent to a hardware address. Periodically, through the exchange of signalling messages, a network may announce a new virtual circuit with its corresponding DLCI. Unfortunately, protocol addressing is not included in the announcement. The station receiving such an indication will learn of the new connection, but will not be able to address the other side. Without a new configuration or mechanism for discovering the protocol address of the other side, this new virtual circuit is unusable.
Other resolution methods were considered to solve the problems, but were rejected. Reverse ARP , for example, seemed like a good candidate, but the response to a request is the protocol address of the requesting station not...