RFC 4111: Security Framework for Provider-Provisioned Virtual Private Networks (PPVPNs)
In plain English — editorial summary, not part of the RFC
This document addresses security aspects pertaining to Provider-Provisioned Virtual Private Networks (PPVPNs). First, it describes the security threats in the context of PPVPNs and defensive techniques to combat those threats. It considers security issues deriving both from malicious behavior of anyone and from negligent or incorrect behavior of the providers. It also describes how these security attacks should be detected and reported. It then discusses possible user requirements for security of a PPVPN service. These user requirements translate into corresponding provider requirements. In addition, the provider may have additional requirements to make its network infrastructure secure to a level that can meet the PPVPN customer's expectations. Finally, this document defines a template that may be used to describe and analyze the security characteristics of a specific PPVPN technology. This memo provides information for the Internet community.
Document record
- Document ID
- RFC4111
- Published
- July 2005
- Authors
- L. Fang
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rtg
- Pages
- 45
- Also known as
- —
- Updated by:
- RFC 8996
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4110A Framework for Layer 3 Provider-Provisioned Virtual Private Networks (PPVPNs)Current
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 4176Framework for Layer 3 Virtual Private Networks (L3VPN) Operations and ManagementCurrent
October 2005
- RFC 4045Extensions to Support Efficient Carrying of Multicast Traffic in Layer-2 Tunneling Protocol (L2TP)Current
April 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?