RFC 2583: Guidelines for Next Hop Client (NHC) Developers
In plain English — editorial summary, not part of the RFC
This document provides guidelines for developers of the Next Hop Resolution Protocol Clients (NHC). The intent is to define the interaction between the NHC code and the TCP/IP protocol stack of the local host operating system. This memo provides information for the Internet community.
Document record
- Document ID
- RFC2583
- Published
- May 1999
- Authors
- R. Carlson; L. Winkler
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- int
- Pages
- 9
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2269Using the MARS Model in non-ATM NBMA NetworksCurrent
January 1998
- RFC 2225Classical IP and ARP over ATMUpdated
April 1998
- RFC 2121Issues affecting MARS Cluster SizeCurrent
March 1997
- RFC 1577Classical IP and ARP over ATMObsoleted
January 1994
- RFC 1561Use of ISO CLNP in TUBA EnvironmentsCurrent
December 1993
- RFC 4293Management Information Base for the Internet Protocol (IP)Current
April 2006
- RFC 2519A Framework for Inter-Domain Route AggregationCurrent
February 1999
- RFC 2338Virtual Router Redundancy ProtocolObsoleted
April 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?