RFC 4026: Provider Provisioned Virtual Private Network (VPN) Terminology
In plain English — editorial summary, not part of the RFC
The widespread interest in provider-provisioned Virtual Private Network (VPN) solutions lead to memos proposing different and overlapping solutions. The IETF working groups (first Provider Provisioned VPNs and later Layer 2 VPNs and Layer 3 VPNs) have discussed these proposals and documented specifications. This has lead to the development of a partially new set of concepts used to describe the set of VPN services. To a certain extent, more than one term covers the same concept, and sometimes the same term covers more than one concept. This document seeks to make the terminology in the area clearer and more intuitive. This memo provides information for the Internet community.
Document record
- Document ID
- RFC4026
- Published
- March 2005
- Authors
- L. Andersson; T. Madsen
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rtg
- Pages
- 20
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7439Gap Analysis for Operating IPv6-Only MPLS NetworksCurrent
January 2015
- RFC 9889A Realization of Network Slices for 5G Networks Using Current IP/MPLS TechnologiesCurrent
November 2025
- RFC 9833A Common YANG Data Model for Attachment CircuitsCurrent
September 2025
- RFC 9834YANG Data Models for Bearers and Attachment Circuits as a Service (ACaaS)Current
September 2025
- RFC 9835A Network YANG Data Model for Attachment CircuitsCurrent
September 2025
- RFC 9836A YANG Data Model for Augmenting VPN Service and Network Models with Attachment CircuitsCurrent
September 2025
- RFC 4031Service Requirements for Layer 3 Provider Provisioned Virtual Private Networks (PPVPNs)Current
April 2005
- RFC 4665Service Requirements for Layer 2 Provider-Provisioned Virtual Private NetworksCurrent
September 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?