From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-qt0-x22d.google.com (mail-qt0-x22d.google.com [IPv6:2607:f8b0:400d:c0d::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id D34DF3B29E; Fri, 1 Dec 2017 08:22:50 -0500 (EST) Received: by mail-qt0-x22d.google.com with SMTP id a16so12949241qtj.3; Fri, 01 Dec 2017 05:22:50 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=qckySeOdiRXNg9mgPPZa2wHE8/wLaqhV6NPKQAyfAoQ=; b=PHtKPcA6Wmea/NDCcjCmFwqYfjQvTBiomypTJbMaZQbnd4QBWn+LHIwhtrM9YSASak xHc7roQToTEvKe9Oovb1N72cQYWAgt9s2So2A0IRYtYGirCSf1RimtExu5BJO/WGk2We gt5xtUSXeDEyKogAZ8af3t/ZZPXSPkn1/3z7j92sfd7RdT1ryxpy/OMW54YNluATD1CL ljRaQM4PFR2cI/0j5BQ3bnv/ZNuyE6Cc4ZGvsTF/2ptbDkmFvpy1+QRnmO6KnQYnF4ny MbKWmnRwsTbJ41zZC+U4zcEjygApkbm0wSvU2tfrrpnD8OyyimFVJNbBeHEv5OWuV3CA NmyA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=qckySeOdiRXNg9mgPPZa2wHE8/wLaqhV6NPKQAyfAoQ=; b=ppBRJUVbuCZtYpixv1y0nKDWBtFKRJzxZqVJbS7cXfVSk1a+WEKVwpadbCOS767Hmn gyaJFuGitpSJmwFeHHCTYUFpZpat+nGqZ4AWehU+HGGLO30BfkjMLqkJJcJcFDenjJbk e8+PwYme9kKc9bn2B2nfoGtGdr8XhPP36jTKNdiTaA5eaUTdujxe0yhtzW2UsMaVZ4Qa zePbVTB3R9HW0GV6kHWyAeNng2AVNAxoIrNxZiF3Q7uUh1P9bZXw7pLEnOYBM5g/K2rw UjXNntEI2iz6cEgADwBz+OQlGvMZm21B4wzcVWmoL14LYPvKLGofDwcD7hFuQpz7ZCeU EB3w== X-Gm-Message-State: AKGB3mISNxZtdw/JAeu5w67k0UIsv3n7VhpLViJcXEs88a38Hwl/Ii80 txWFTwNSdjAvLTtsOdirqP5oLQo5cfolVzCsx5w= X-Google-Smtp-Source: AGs4zMZXMVm8CtLirO7nMBMBNFidoWO71fZgbz2TybVxYqY71G7hTb5aZm6VkwbAy/3Ygopimf9bvL5HZh3a7LyB6f0= X-Received: by 10.237.63.184 with SMTP id s53mr8811262qth.89.1512134570265; Fri, 01 Dec 2017 05:22:50 -0800 (PST) MIME-Version: 1.0 Received: by 10.12.191.227 with HTTP; Fri, 1 Dec 2017 05:22:49 -0800 (PST) In-Reply-To: References: <4D0E907C-E15D-437C-B6F7-FF348346D615@gmx.de> <7B92DF4D-B6B5-4A64-9E10-119DCA2D4A6F@ifi.uio.no> <1512037480.19682.10.camel@gmail.com> <6b494910-1373-afb0-5b93-99b725391fb3@gmail.com> <87wp2638yo.fsf@toke.dk> From: Luca Muscariello Date: Fri, 1 Dec 2017 14:22:49 +0100 Message-ID: To: =?UTF-8?B?0JrQuNGA0LjQu9C7INCb0YPQutC+0L3QuNC9?= Cc: =?UTF-8?B?VG9rZSBIw7hpbGFuZC1Kw7hyZ2Vuc2Vu?= , make-wifi-fast@lists.bufferbloat.net, Jan Ceuleers , bloat Content-Type: multipart/alternative; boundary="001a11472220e9d3bc055f474310" Subject: Re: [Make-wifi-fast] [Bloat] benefits of ack filtering 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: Fri, 01 Dec 2017 13:22:50 -0000 --001a11472220e9d3bc055f474310 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable I think only IPSEC would be a problem for fastACK but not TLS. On Fri, Dec 1, 2017 at 2:13 PM, =D0=9A=D0=B8=D1=80=D0=B8=D0=BB=D0=BB =D0=9B= =D1=83=D0=BA=D0=BE=D0=BD=D0=B8=D0=BD wrote: > As I noticed from the Meraki document: > > "FastACK also relies on packet inspection, and will not work when > payload is encrypted. However, in our networks, we do not currently > see an extensive use of encryption techniques like IPSec." > > But what about TLS ? > As for me, this technology will never work in most cases. > > > Best regards, > Lukonin Kirill. > > 2017-12-01 17:53 GMT+05:00 Toke H=C3=B8iland-J=C3=B8rgensen : > > Jan Ceuleers writes: > > > >> On 01/12/17 01:28, David Lang wrote: > >>> Stop thinking in terms of single-flow benchmarks and near idle > >>> 'upstream' paths. > >> > >> Nobody has said it so I will: on wifi-connected endpoints the upstream > >> acks also compete for airtime with the downstream flow. > > > > There's a related discussion going on over on the make-wifi-fast list > > related to the FastACK scheme proposed by Meraki at this year's IMC: > > > > https://conferences.sigcomm.org/imc/2017/papers/imc17-final203.pdf > > > > It basically turns link-layer ACKs into upstream TCP ACKs (and handles > > some of the corner cases resulting from this) and also seems to contain > > an ACK compression component. > > > > -Toke > > _______________________________________________ > > Make-wifi-fast mailing list > > Make-wifi-fast@lists.bufferbloat.net > > https://lists.bufferbloat.net/listinfo/make-wifi-fast > > > > -- > Best Regards, > Lukonin Kirill > _______________________________________________ > Make-wifi-fast mailing list > Make-wifi-fast@lists.bufferbloat.net > https://lists.bufferbloat.net/listinfo/make-wifi-fast --001a11472220e9d3bc055f474310 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
I think only IPSEC would be a problem for fastACK but not = TLS.

On Fri,= Dec 1, 2017 at 2:13 PM, =D0=9A=D0=B8=D1=80=D0=B8=D0=BB=D0=BB =D0=9B=D1=83= =D0=BA=D0=BE=D0=BD=D0=B8=D0=BD <klukonin@gmail.com> wrote:<= br>
As I noticed from the Meraki document:
"FastACK also relies on packet inspection, and will not work when
payload is encrypted. However, in our networks, we do not currently
see an extensive use of encryption techniques like IPSec."

But what about TLS ?
As for me, this technology will never work in most cases.


Best regards,
Lukonin Kirill.

2017-12-01 17:53 GMT+05:00 Toke H=C3=B8iland-J=C3=B8rgensen <toke@toke.dk>:
> Jan Ceuleers <jan.ceuleer= s@gmail.com> writes:
>
>> On 01/12/17 01:28, David Lang wrote:
>>> Stop thinking in terms of single-flow benchmarks and near idle=
>>> 'upstream' paths.
>>
>> Nobody has said it so I will: on wifi-connected endpoints the upst= ream
>> acks also compete for airtime with the downstream flow.
>
> There's a related discussion going on over on the make-wifi-fast l= ist
> related to the FastACK scheme proposed by Meraki at this year's IM= C:
>
> https://conferences.sigcomm.<= wbr>org/imc/2017/papers/imc17-final203.pdf
>
> It basically turns link-layer ACKs into upstream TCP ACKs (and handles=
> some of the corner cases resulting from this) and also seems to contai= n
> an ACK compression component.
>
> -Toke
> _______________________________________________
> Make-wifi-fast mailing list
> Make-wifi-fast= @lists.bufferbloat.net
> https://lists.bufferbloat.net/listin= fo/make-wifi-fast



--
Best Regards,
Lukonin Kirill
_______________________________________________
Make-wifi-fast mailing list
Make-wifi-fast@list= s.bufferbloat.net
https://lists.bufferbloat.net/listinfo/mak= e-wifi-fast

--001a11472220e9d3bc055f474310--