<?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="Bufferbloat - Page 11 - Wikipedia">
<p>
<a accesskey="1" href="page.php?w=Bufferbloat&amp;p=10">1.Previous</a><br />
<a accesskey="3" href="page.php?w=Bufferbloat&amp;p=12">3.Next</a>
</p>
<p>the buffer is fully saturated. Once this happens, TCP may even decide that the path of the connection has changed, and again go into the more aggressive search for a new operating point.</p>

<p>Packets are queued within a network buffer before being transmitted; in problematic situations, packets are dropped only if the buffer is full.  On older routers, buffers were fairly small, so they filled quickly, and therefore packets began to drop shortly after the link became saturated, so the TCP protocol could adjust, and the issue would not become</p><p>
<a accesskey="1" href="page.php?w=Bufferbloat&amp;p=10">1.Previous</a><br />
<a accesskey="3" href="page.php?w=Bufferbloat&amp;p=12">3.Next</a>
</p>

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

</card>
</wml>
