RFC 1293: Inverse Address Resolution Protocol
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 2390.
Current version: RFC 2390 — Inverse Address Resolution Protocol
In plain English — editorial summary, not part of the RFC
This memo describes additions to ARP that will allow a station to request a protocol address corresponding to a given hardware address. [STANDARDS-TRACK]
Document record
- Document ID
- RFC1293
- Published
- January 1992
- Authors
- T. Bradley; C. Brown
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 6
- Also known as
- —
- Obsoleted by:
- RFC 2390
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 1294Multiprotocol Interconnect over Frame RelayObsoleted
January 1992
- RFC 1490Multiprotocol Interconnect over Frame RelayObsoleted
July 1993
- RFC 1289DECnet Phase IV MIB ExtensionsObsoleted
December 1991
- RFC 1286Definitions of Managed Objects for BridgesObsoleted
December 1991
- RFC 1285FDDI Management Information BaseUpdated
January 1992
- RFC 1493Definitions of Managed Objects for BridgesObsoleted
July 1993
- RFC 4188Definitions of Managed Objects for BridgesCurrent
September 2005
- RFC 7067Directory Assistance Problem and High-Level Design ProposalCurrent
November 2013
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?