RFC 4031: Service Requirements for Layer 3 Provider Provisioned Virtual Private Networks (PPVPNs)
In plain English — editorial summary, not part of the RFC
This document provides requirements for Layer 3 Virtual Private Networks (L3VPNs). It identifies requirements applicable to a number of individual approaches that a Service Provider may use to provision a Virtual Private Network (VPN) service. This document expresses a service provider perspective, based upon past experience with IP-based service offerings and the ever-evolving needs of the customers of such services. Toward this end, it first defines terminology and states general requirements. Detailed requirements are expressed from a customer perspective as well as that of a service provider. This memo provides information for the Internet community.
Document record
- Document ID
- RFC4031
- Published
- April 2005
- Authors
- M. Carugi; D. McDysan
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rtg
- Pages
- 50
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6517Mandatory Features in a Layer 3 Multicast BGP/MPLS VPN SolutionCurrent
February 2012
- RFC 6565OSPFv3 as a Provider Edge to Customer Edge (PE-CE) Routing ProtocolCurrent
June 2012
- RFC 7611BGP ACCEPT_OWN Community AttributeCurrent
August 2015
- RFC 4026Provider Provisioned Virtual Private Network (VPN) TerminologyCurrent
March 2005
- RFC 4364BGP/MPLS IP Virtual Private Networks (VPNs)Updated
February 2006
- RFC 4576Using a Link State Advertisement (LSA) Options Bit to Prevent Looping in BGP/MPLS IP Virtual Private Networks (VPNs)Current
June 2006
- RFC 4659BGP-MPLS IP Virtual Private Network (VPN) Extension for IPv6 VPNCurrent
September 2006
- RFC 4761Virtual Private LAN Service (VPLS) Using BGP for Auto-Discovery and SignalingUpdated
January 2007
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?