<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.marques-idr-best-external" target="https://datatracker.ietf.org/doc/html/draft-marques-idr-best-external-01">
   <front>
      <title>Advertisement of the best external route in BGP</title>
      <author initials="P. R." surname="Marques" fullname="Pedro R. Marques">
         <organization>Juniper Networks</organization>
      </author>
      <author initials="R." surname="Fernando" fullname="Rex Fernando">
         <organization>Juniper Networks</organization>
      </author>
      <author initials="E." surname="Chen" fullname="Enke Chen">
         <organization>Cisco Systems</organization>
      </author>
      <author initials="P." surname="Mohapatra" fullname="Prodosh Mohapatra">
         <organization>Cisco Systems</organization>
      </author>
      <date month="March" day="26" year="2009" />
      <abstract>
	 <t>The base BGP specifications prevent a BGP speaker from advertising
any route that is not the best route for a BGP destination.  This
document specifies a modification of this rule.  Routes are divided
into two categories, &quot;external&quot; and &quot;internal&quot;.  A specification is
provided for choosing a &quot;best external route&quot; (for a particular value
of the Network Layer Reachability Information).  A BGP speaker is
then allowed to advertise its &quot;best external route&quot; to its internal
BGP peers, even if that is not the best route for the destination.
The document explains why advertising the best external route can
improve convergence time without causing routing loops.  Additional
benefits include reduction of inter-domain churn and avoidance of
permanent route oscillation.  The document also generalizes the
notions of &quot;internal&quot; and &quot;external&quot; so that they can be applied to
Route Reflector Clusters and Autonomous System Confederations.
	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-marques-idr-best-external-01" />
   
</reference>
