RFC 4381: Analysis of the Security of BGP/MPLS IP Virtual Private Networks (VPNs)

In plain English — editorial summary, not part of the RFC

This document analyses the security of the BGP/MPLS IP virtual private network (VPN) architecture that is described in RFC 4364, for the benefit of service providers and VPN users. The analysis shows that BGP/MPLS IP VPN networks can be as secure as traditional layer-2 VPN services using Asynchronous Transfer Mode (ATM) or Frame Relay. This memo provides information for the Internet community.

Document record

Document ID

RFC4381

Published

February 2006

Authors

M. Behringer

Status

INFORMATIONAL

Stream

INDEPENDENT

Area

—

Pages

22

Also known as

—

• Read the full RFC text →
• Plain text version
• IETF Datatracker history
• DOI: 10.17487/RFC4381

Topics

• service provider
• atm
• asynchronous transfer mode
• frame relay

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

• RFC 3606Definitions of Supplemental Managed Objects for ATM InterfaceCurrent

  November 2003

• RFC 3532Requirements for the Dynamic Partitioning of Switching ElementsCurrent

  May 2003

• RFC 3355Layer Two Tunnelling Protocol (L2TP) Over ATM Adaptation Layer 5 (AAL5)Current

  September 2002

• RFC 3336PPP Over Asynchronous Transfer Mode Adaptation Layer 2 (AAL2)Current

  December 2002

• RFC 3293General Switch Management Protocol (GSMP) Packet Encapsulations for Asynchronous Transfer Mode (ATM), Ethernet and Transmission Control Protocol (TCP)Current

  June 2002

• RFC 3175Aggregation of RSVP for IPv4 and IPv6 ReservationsUpdated

  September 2001

• RFC 3108Conventions for the use of the Session Description Protocol (SDP) for ATM Bearer ConnectionsCurrent

  May 2001

• RFC 3107Carrying Label Information in BGP-4Obsoleted

  May 2001

Also filed under

• INFORMATIONAL
• 2006
• INDEPENDENT stream