RFC 2735: NHRP Support for Virtual Private Networks
In plain English — editorial summary, not part of the RFC
The NBMA Next Hop Resolution Protocol (NHRP) is used to determine the NBMA subnetwork addresses of the "NBMA next hop" towards a public internetworking layer address. This document describes the enhancements necessary to enable NHRP to perform the same function for private internetworking layer addresses available within the framework of a Virtual Private Network (VPN) service on a shared NBMA network. [STANDARDS-TRACK]
Document record
- Document ID
- RFC2735
- Published
- December 1999
- Authors
- B. Fox; B. Petri
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 12
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2603ILMI-Based Server Discovery for NHRPCurrent
June 1999
- RFC 2333NHRP Protocol Applicability StatementCurrent
April 1998
- RFC 2332NBMA Next Hop Resolution Protocol (NHRP)Current
April 1998
- RFC 2677Definitions of Managed Objects for the NBMA Next Hop Resolution Protocol (NHRP)Current
August 1999
- RFC 2583Guidelines for Next Hop Client (NHC) DevelopersCurrent
May 1999
- RFC 2529Transmission of IPv6 over IPv4 Domains without Explicit TunnelsCurrent
March 1999
- RFC 2520NHRP with Mobile NHCsCurrent
February 1999
- RFC 2470Transmission of IPv6 Packets over Token Ring NetworksUpdated
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?