RFC 1735: NBMA Address Resolution Protocol (NARP)
In plain English — editorial summary, not part of the RFC
This document describes the NBMA Address Resolution Protocol (NARP). NARP can be used by a source terminal (host or router) connected to a Non-Broadcast, Multi-Access link layer (NBMA) network to find out the NBMA addresses of the a destination terminal provided that the destination terminal is connected to the same NBMA network. This memo defines an Experimental Protocol for the Internet community. This memo does not specify an Internet standard of any kind.
Document record
- Document ID
- RFC1735
- Published
- December 1994
- Authors
- J. Heinanen; R. Govindan
- Status
- EXPERIMENTAL
- Stream
- IETF
- Area
- rtg
- Pages
- 11
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 1577Classical IP and ARP over ATMObsoleted
January 1994
- RFC 1971IPv6 Stateless Address AutoconfigurationObsoleted
August 1996
- RFC 2225Classical IP and ARP over ATMUpdated
April 1998
- RFC 2269Using the MARS Model in non-ATM NBMA NetworksCurrent
January 1998
- RFC 1620Internet Architecture Extensions for Shared MediaCurrent
May 1994
- RFC 1868ARP Extension - UNARPCurrent
November 1995
- RFC 1931Dynamic RARP Extensions for Automatic Network Address AcquisitionCurrent
April 1996
- RFC 2469A Caution On The Canonical Ordering Of Link-Layer AddressesCurrent
December 1998
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?