From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.toke.dk (mail.toke.dk [52.28.52.200]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id D93AD3BA8E for ; Thu, 30 Nov 2017 03:52:58 -0500 (EST) From: Toke =?utf-8?Q?H=C3=B8iland-J=C3=B8rgensen?= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=toke.dk; s=20161023; t=1512031975; bh=DpxmzCaceu9vzomXeHaX54sAILp86WFP9gSr2esnKGk=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=jpMuBO1ny5QdmoLOf3CVMrJbEXlzIqv7SCzlgWk5GnWo+6EVGaq+RPo2Ra6qN53lr IbfTEjigV9n08+vzbozCD99mXB3R1Yaubi6i+P1cgHs9T0oqDPcNrM9VuMCLk24e9n V6RH3Fe/ohtTRkzO/6/UW9BlHCoAjqSmK05l2V1/C/GfBxvjNvxbr7v+K9vwiQkeKh qcpbWYfzLfZPdLiFCCSCsHIhLXnmj+Tu0CoUlS0NEjfR03k2opIOcNz24APkd55bb/ Cpa7gyXakoZLQxRJJMh+/jCqLOyI8tGpIygbLYDrXZKTxwEOdzE3iTDMrYTQ5WuDwP Q3zlCr9dW+rXA== To: Jonathan Morton , Dave Taht Cc: make-wifi-fast@lists.bufferbloat.net In-Reply-To: References: <87lgionrl5.fsf@toke.dk> Date: Thu, 30 Nov 2017 09:52:53 +0100 X-Clacks-Overhead: GNU Terry Pratchett Message-ID: <87po80407u.fsf@toke.dk> MIME-Version: 1.0 Content-Type: text/plain Subject: Re: [Make-wifi-fast] Fwd: Re: [iccrg] TCP behavior across WiFi pointers ? X-BeenThere: make-wifi-fast@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Nov 2017 08:52:59 -0000 Jonathan Morton writes: > A hint, but not a guarantee. If you generate a fake ack, you'd better be > prepared to retransmit the packet if, in fact, it gets lost deeper in the > network. I think their use case here is an AP that (they presume) is talking directly to the client. In which case it's probably a fair assumption... Most operating systems don't drop packets between the WiFi card and the TCP stack :) Of course, a client may be forwarding the packet somewhere, in which case this would probably break in interesting ways... -Toke