<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-l3vpn-ospf-2547" target="https://datatracker.ietf.org/doc/html/draft-ietf-l3vpn-ospf-2547-06">
   <front>
      <title>OSPF as the Provider/Customer Edge Protocol for BGP/MPLS IP Virtual Private Networks (VPNs)</title>
      <author initials="P." surname="Pillay-Esnault" fullname="Padma Pillay-Esnault">
         <organization>Cisco Systems</organization>
      </author>
      <author initials="E. C." surname="Rosen" fullname="Eric C. Rosen">
         <organization>Cisco Systems</organization>
      </author>
      <author initials="P." surname="Psenak" fullname="Peter Psenak">
         <organization>Cisco Systems</organization>
      </author>
      <date month="February" day="17" year="2006" />
      <abstract>
	 <t>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&#x27;s routes across the provider&#x27;s IP backbone network, and Multiprotocol Label Switching (MPLS) is used to tunnel customer packets across the provider&#x27;s backbone. This is known as a &quot;BGP/MPLS IP VPN&quot;. 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]
	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-l3vpn-ospf-2547-06" />
   
</reference>
