RFC - 4577

OSPF as the Provider/Customer Edge Protocol for BGP/MPLS IP Virtual Private Networks (VPNs)

Original:	ftp://ftp.isi.edu/in-notes/rfc4577.txt
Authors:	E. Rosen [Cisco Systems, Inc.], P. Psenak [Cisco Systems, Inc.], P. Pillay-Esnault [Cisco Systems, Inc.]
Date:	June 2006
Category:	Informational

---

Updates:
RFC-4364prop	BGP/MPLS IP Virtual Private Networks (VPNs) (Updated by RFC-4577, RFC-4684prop)

Referred by:	1 RFC
Refers to:	9 RFC

---

Status

This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited.

Copyright Notice

Copyright (C) The Internet Society (2006).

Abstract

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

This document updates RFC 4364.

---