<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.rosen-vpns-ospf-bgp-mpls" target="https://datatracker.ietf.org/doc/html/draft-rosen-vpns-ospf-bgp-mpls-06">
   <front>
      <title>OSPF as the PE/CE Protocol in BGP/MPLS VPNs</title>
      <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>
      <author initials="P." surname="Pillay-Esnault" fullname="Padma Pillay-Esnault">
         <organization>Juniper Networks</organization>
      </author>
      <date month="February" day="6" year="2003" />
      <abstract>
	 <t>[VPN] describes a method of providing a VPN service.  That method
allows a variety of different protocols to be used as the routing
protocol between the Customer Edge (CE) router and the Provider Edge
(PE) router.  However, it does not fully specify the procedures which
must be implemented within the Provider&#x27;s network when OSPF is used
as the PE/CE routing protocol.  This document provides that
specification.
	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-rosen-vpns-ospf-bgp-mpls-06" />
   
</reference>
