<div dir="ltr">If I understand the text right, FastACK runs in the AP and generates an ACK on behalf (or despite) of the TCP client end.<div>Then, it decimates dupACKs. </div><div><br></div><div>This means that there is a stateful connection tracker in the AP. Not so simple.</div><div>It's almost, not entirely though, a TCP proxy doing Split TCP.</div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Dec 1, 2017 at 1:53 PM, Toke Høiland-Jørgensen <span dir="ltr"><<a href="mailto:toke@toke.dk" target="_blank">toke@toke.dk</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">Jan Ceuleers <<a href="mailto:jan.ceuleers@gmail.com">jan.ceuleers@gmail.com</a>> writes:<br>
<br>
> On 01/12/17 01:28, David Lang wrote:<br>
>> Stop thinking in terms of single-flow benchmarks and near idle<br>
>> 'upstream' paths.<br>
><br>
> Nobody has said it so I will: on wifi-connected endpoints the upstream<br>
> acks also compete for airtime with the downstream flow.<br>
<br>
</span>There's a related discussion going on over on the make-wifi-fast list<br>
related to the FastACK scheme proposed by Meraki at this year's IMC:<br>
<br>
<a href="https://conferences.sigcomm.org/imc/2017/papers/imc17-final203.pdf" rel="noreferrer" target="_blank">https://conferences.sigcomm.<wbr>org/imc/2017/papers/imc17-<wbr>final203.pdf</a><br>
<br>
It basically turns link-layer ACKs into upstream TCP ACKs (and handles<br>
some of the corner cases resulting from this) and also seems to contain<br>
an ACK compression component.<br>
<span class="HOEnZb"><font color="#888888"><br>
-Toke<br>
</font></span><div class="HOEnZb"><div class="h5">______________________________<wbr>_________________<br>
Bloat mailing list<br>
<a href="mailto:Bloat@lists.bufferbloat.net">Bloat@lists.bufferbloat.net</a><br>
<a href="https://lists.bufferbloat.net/listinfo/bloat" rel="noreferrer" target="_blank">https://lists.bufferbloat.net/<wbr>listinfo/bloat</a><br>
</div></div></blockquote></div><br></div>