RFC 1029: More fault tolerant approach to address resolution for a Multi-LAN system of Ethernets
In plain English — editorial summary, not part of the RFC
This memo discusses an extension to a Bridge Protocol to detect and disclose changes in heighbouring host address parameters in a Multi-Lan system of Ethernets. The problem is one which is appearing more and more regularly as the interconnected systems grow larger on Campuses and in Commercial Institutions. This RFC suggests a protocol enhancement for the Internet community, and requests discussion and suggestions for improvements.
Document record
- Document ID
- RFC1029
- Published
- May 1988
- Authors
- G. Parr
- Status
- UNKNOWN
- Stream
- Legacy
- Area
- —
- Pages
- 17
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 826An Ethernet Address Resolution Protocol: Or Converting Network Protocol Addresses to 48.bit Ethernet Address for Transmission on Ethernet HardwareUpdated
November 1982
- RFC 1620Internet Architecture Extensions for Shared MediaCurrent
May 1994
- RFC 2835IP and ARP over HIPPI-6400 (GSN)Updated
May 2000
- RFC 1293Inverse Address Resolution ProtocolObsoleted
January 1992
- RFC 2625IP and ARP over Fibre ChannelObsoleted
June 1999
- RFC 2734IPv4 over IEEE 1394Current
December 1999
- RFC 2834ARP and IP Broadcast over HIPPI-800Updated
May 2000
- RFC 4391Transmission of IP over InfiniBand (IPoIB)Updated
April 2006
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?