<?xml version="1.0" encoding='utf-8'?>
<!DOCTYPE wml PUBLIC "-//WAPFORUM//DTD WML 1.1//EN" "http://www.wapforum.org/DTD/wml_1.1.xml">
<wml>
<card id="card1" title="Border Gateway Protocol - Page 19 - Wikipedia">
<p>
<a accesskey="1" href="page.php?w=Border_Gateway_Protocol&amp;p=18">1.Previous</a><br />
<a accesskey="3" href="page.php?w=Border_Gateway_Protocol&amp;p=20">3.Next</a>
</p>
<p>In the simplest arrangement, all routers within a single AS and participating in BGP routing must be configured in a full mesh: each router must be configured as a peer to every other router. This causes scaling problems, since the number of required connections <a href="page.php?w=quadratic_growth">grows quadratically</a> with the number of routers involved. To alleviate the problem, BGP implements two options: <a href="page.php?w=route_reflector">route reflector</a>s (RFC 4456) and <a href="page.php?w=BGP_confederation">BGP confederation</a>s</p><p>
<a accesskey="1" href="page.php?w=Border_Gateway_Protocol&amp;p=18">1.Previous</a><br />
<a accesskey="3" href="page.php?w=Border_Gateway_Protocol&amp;p=20">3.Next</a>
</p>

<do type="prev" label="Search">
        <go href="search.wml"/>
</do>

</card>
</wml>
