<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-idr-rfc2796bis" target="https://datatracker.ietf.org/doc/html/draft-ietf-idr-rfc2796bis-02">
   <front>
      <title>BGP Route Reflection: An Alternative to Full Mesh Internal BGP (IBGP)</title>
      <author initials="E." surname="Chen" fullname="Enke Chen">
         <organization>Cisco Systems</organization>
      </author>
      <author initials="T. J." surname="Bates" fullname="Tony J. Bates">
         <organization>Cisco Systems</organization>
      </author>
      <author initials="R." surname="Chandra" fullname="Ravi Chandra">
         <organization>Sonoa Systems</organization>
      </author>
      <date month="October" day="12" year="2005" />
      <abstract>
	 <t>The Border Gateway Protocol (BGP) is an inter-autonomous system routing protocol designed for TCP/IP internets. Typically, all BGP speakers within a single AS must be fully meshed so that any external routing information must be re-distributed to all other routers within that Autonomous System (AS). This represents a serious scaling problem that has been well documented with several alternatives proposed.

 This document describes the use and design of a method known as &quot;route reflection&quot; to alleviate the need for &quot;full mesh&quot; Internal BGP (IBGP).

 This document obsoletes RFC 2796 and RFC 1966. [STANDARDS-TRACK]
	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-idr-rfc2796bis-02" />
   
</reference>
