<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.rosen-ospf-2547bis-dn" target="https://datatracker.ietf.org/doc/html/draft-rosen-ospf-2547bis-dn-00">
   <front>
      <title>OSPF as the PE/CE Protocol in BGP/MPLS VPNs</title>
      <author initials="E. C." surname="Rosen" fullname="Eric C. Rosen">
         </author>
      <date month="February" day="21" year="2003" />
      <abstract>
	 <t>[VPN] describes a method by which a Service Provider (SP) may provide
a VPN service to its customers.  In that method, BGP is used to carry
customer routes across the SP&#x27;s backbone.  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.  [VPN-OSPF] specifies additional procedures to be used when
the CE/PE router protocol is OSPF.  In these additional procedures,
customer OSPF routes from a CE router are translated into BGP routes
by a PE router.  Then they are sent via BGP to another PE router,
which translates them back into OSPF routes and distributes them to
another CE router.  This translation may lose some of the information
needed to prevent loops.   This document proposes that one of the
OSPF options bits be used to ensure that when a  VPN route is sent
from a PE to a CE, the route will be ignored by any PE which receives
it back from a CE.
	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-rosen-ospf-2547bis-dn-00" />
   
</reference>
