From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.toke.dk (mail.toke.dk [45.145.95.4]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id 91C633CB43; Wed, 20 Oct 2021 05:45:11 -0400 (EDT) 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=1634723101; bh=Q7x9mkK4zcFuYN3u98lXn5DHk4S0YpaSuUna35q5deU=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=R562PbP2C/dRrBDrqmjZcCof/a2ulg2ao8VzYhYPygfkLoyjxSi2c7lOSq5hy6wC3 kkJuIVkhkXFPRLmmwMHkOQuQWEvQVhKQoK2S81Wmw5UWQqr8bFl8e0NnxKeELtcL1Q BWvR63kPOsFExXOPCiq3/AZocox7RHMP7tyMsHJXuJL9dAnoGeo552ESPWvaveqwOk UvJwYRvM/m++/SSRxW+jMhRo6P0COMxT1K7/QLqXH0o4qDQC3nybTr+a+FHZhP5CVL YwmuVeAb6zZ33+NzzCbSntSmRiMe1EbvfIf6krkGOqUSGgOUwLBpCJ/a5u84z+Es4A pdEJ0pGKNeobA== To: Michael Welzl , Dave Taht Cc: Rpm , Make-Wifi-fast , Keith Winstein In-Reply-To: <4BD0AC02-62FB-4AE4-B83B-BAF5CCEA2B24@ifi.uio.no> References: <4BD0AC02-62FB-4AE4-B83B-BAF5CCEA2B24@ifi.uio.no> Date: Wed, 20 Oct 2021 11:44:58 +0200 X-Clacks-Overhead: GNU Terry Pratchett Message-ID: <87lf2of2sl.fsf@toke.dk> MIME-Version: 1.0 Content-Type: text/plain Subject: Re: [Rpm] [Make-wifi-fast] tack - reducing acks on wlans X-BeenThere: rpm@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: revolutions per minute - a new metric for measuring responsiveness List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Oct 2021 09:45:11 -0000 Michael Welzl writes: > Am I being naive? Why can't such an ARQ proxy be deployed? Is it just > because standardizing this negotiation is too difficult, or would it > also be too computationally heavy for an AP perhaps, at high speeds? Immediate thought: this won't work for QUIC or other encrypted transports (like VPNs). -Toke