RFC 4110: A Framework for Layer 3 Provider-Provisioned Virtual Private Networks (PPVPNs)
In plain English — editorial summary, not part of the RFC
This document provides a framework for Layer 3 Provider-Provisioned Virtual Private Networks (PPVPNs). This framework is intended to aid in the standardization of protocols and mechanisms for support of layer 3 PPVPNs. It is the intent of this document to produce a coherent description of the significant technical issues that are important in the design of layer 3 PPVPN solutions. Selection of specific approaches, making choices regarding engineering tradeoffs, and detailed protocol specification, are outside of the scope of this framework document. This memo provides information for the Internet community.
Document record
- Document ID
- RFC4110
- Published
- July 2005
- Authors
- R. Callon; M. Suzuki
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rtg
- Pages
- 82
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4111Security Framework for Provider-Provisioned Virtual Private Networks (PPVPNs)Updated
July 2005
- RFC 4090Fast Reroute Extensions to RSVP-TE for LSP TunnelsUpdated
May 2005
- RFC 4136OSPF Refresh and Flooding Reduction in Stable TopologiesCurrent
July 2005
- RFC 4139Requirements for Generalized MPLS (GMPLS) Signaling Usage and Extensions for Automatically Switched Optical Network (ASON)Current
July 2005
- RFC 4167Graceful OSPF Restart Implementation ReportCurrent
October 2005
- RFC 4045Extensions to Support Efficient Carrying of Multicast Traffic in Layer-2 Tunneling Protocol (L2TP)Current
April 2005
- RFC 4176Framework for Layer 3 Virtual Private Networks (L3VPN) Operations and ManagementCurrent
October 2005
- RFC 4182Removing a Restriction on the use of MPLS Explicit NULLUpdated
September 2005
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?