RFC 4365: Applicability Statement for BGP/MPLS IP Virtual Private Networks (VPNs)
In plain English — editorial summary, not part of the RFC
This document provides an Applicability Statement for the Virtual Private Network (VPN) solution described in RFC 4364 and other documents listed in the References section. This memo provides information for the Internet community.
Document record
- Document ID
- RFC4365
- Published
- February 2006
- Authors
- E. Rosen
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rtg
- Pages
- 32
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4364BGP/MPLS IP Virtual Private Networks (VPNs)Updated
February 2006
- RFC 4368Multiprotocol Label Switching (MPLS) Label-Controlled Asynchronous Transfer Mode (ATM) and Frame-Relay Management Interface DefinitionCurrent
January 2006
- RFC 4360BGP Extended Communities AttributeUpdated
February 2006
- RFC 4377Operations and Management (OAM) Requirements for Multi-Protocol Label Switched (MPLS) NetworksCurrent
February 2006
- RFC 4378A Framework for Multi-Protocol Label Switching (MPLS) Operations and Management (OAM)Current
February 2006
- RFC 4379Detecting Multi-Protocol Label Switched (MPLS) Data Plane FailuresObsoleted
February 2006
- RFC 4349High-Level Data Link Control (HDLC) Frames over Layer 2 Tunneling Protocol, Version 3 (L2TPv3)Updated
February 2006
- RFC 4382MPLS/BGP Layer 3 Virtual Private Network (VPN) Management Information BaseCurrent
February 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?