Search RFCs

RFC Editor

File formats:

Status:

PROPOSED STANDARD

Updates:

RFC 4364

Authors:

E. Rosen
P. Psenak
P. Pillay-Esnault

Stream:

IETF

Source:

l3vpn (int)

Cite this RFC:TXT  | XML  |  BibTeX

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

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

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

Abstract

Many Service Providers offer Virtual Private Network (VPN) servicesto their customers, using a technique in which customer edge routers(CE routers) are routing peers of provider edge routers (PErouters). The Border Gateway Protocol (BGP) is used to distributethe customer's routes across the provider's IP backbone network, andMultiprotocol Label Switching (MPLS) is used to tunnel customerpackets across the provider's backbone. This is known as a "BGP/MPLSIP VPN". The base specification for BGP/MPLS IP VPNs presumes thatthe routing protocol on the interface between a PE router and a CErouter is BGP. This document extends that specification by allowingthe routing protocol on the PE/CE interface to be the Open ShortestPath First (OSPF) protocol.

This document updates RFC 4364. [STANDARDS-TRACK]

For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.