Skip to main content

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

Revision differences

Document history

Date By Action
2020-01-21
(System) Received changes through RFC Editor sync (added Verified Errata tag)
2018-12-20
(System)
Received changes through RFC Editor sync (changed abstract to 'Many Service Providers offer Virtual Private Network (VPN) services to their customers, using a technique in …
Received changes through RFC Editor sync (changed abstract to '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. [STANDARDS-TRACK]')
2015-10-14
(System) Notify list changed from rick@rhwilder.net, rcallon@juniper.net, rbonica@juniper.net, erosen@cisco.com, ppsenak@cisco.com, padma@juniper.net to rbonica@juniper.net, rcallon@juniper.net, rick@rhwilder.net
2006-06-27
Amy Vezza State Changes to RFC Published from RFC Ed Queue by Amy Vezza
2006-06-27
Amy Vezza [Note]: 'RFC 4577' added by Amy Vezza
2006-06-26
(System) RFC published