File formats:

Status:

PROPOSED STANDARD

Obsoletes:

RFC 2547

Updated by:

RFC 4577, RFC 4684, RFC 5462

Authors:

E. Rosen
Y. Rekhter

Stream:

IETF

Source:

l3vpn (int)

Cite this RFC: TXT  |  XML  |   BibTeX

DOI:  https://doi.org/10.17487/RFC4364

Discuss this RFC: Send questions or comments to the mailing list l3vpn@ietf.org

Other actions: View Errata  |  Submit Errata  |  Find IPR Disclosures from the IETF  |  View History of RFC 4364

Abstract

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]

For the definition of Status, see RFC 2026.

For the definition of Stream, see RFC 8729.