metasystema.org
UpdatedPROPOSED STANDARDIETF stream

RFC 4364: BGP/MPLS IP Virtual Private Networks (VPNs)

Still current, but amended. Parts of this document are changed or extended by RFC 4577, RFC 4684, RFC 5462. Read both.

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

This document describes a method by which a Service Provider may use an IP backbone to provide IP Virtual Private Networks (VPNs) for its customers. This method uses a "peer model", in which the customers' edge routers (CE routers) send their routes to the Service Provider's edge routers (PE routers); there is no "overlay" visible to the customer's routing algorithm, and CE routers at different sites do not peer with each other. Data packets are tunneled through the backbone, so that the core routers do not need to know the VPN routes. [STANDARDS-TRACK]

Document record

Document ID
RFC4364
Published
February 2006
Authors
E. Rosen; Y. Rekhter
Status
PROPOSED STANDARD
Stream
IETF
Area
rtg
Pages
47
Also known as
—
Obsoletes:
RFC 2547
Updated by:
RFC 4577, RFC 4684, RFC 5462

Topics

Referenced by

3 later RFCs formally update or obsolete part of this document.

Related documents

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

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?

canonical URL: /rfc/4364-bgp-mpls-ip-virtual-private-networks-vpns