From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from bifrost.lang.hm (lang.hm [66.167.227.134]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id 474AE3B2A4 for ; Tue, 12 Dec 2017 17:21:43 -0500 (EST) Received: from asgard.lang.hm (asgard.lang.hm [10.0.0.100]) by bifrost.lang.hm (8.13.4/8.13.4/Debian-3) with ESMTP id vBCMLdLQ002482; Tue, 12 Dec 2017 14:21:39 -0800 Date: Tue, 12 Dec 2017 14:21:39 -0800 (PST) From: David Lang X-X-Sender: dlang@asgard.lang.hm To: Jonathan Morton cc: Benjamin Cronce , bloat In-Reply-To: Message-ID: References: <4D0E907C-E15D-437C-B6F7-FF348346D615@gmx.de> <019064B3-835C-4D59-BE52-9E86EE08CD02@gmx.de> User-Agent: Alpine 2.02 (DEB 1266 2009-07-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII Subject: Re: [Bloat] benefits of ack filtering X-BeenThere: bloat@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: General list for discussing Bufferbloat List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Dec 2017 22:21:43 -0000 On Wed, 13 Dec 2017, Jonathan Morton wrote: > The one "correct" argument against ack-filtering I've seen is that it > encourages (or rather validates) the use of extreme asymmetry ratios. I would sure rather have a extremely asymmetric ration than a 'proper' ratio with the same upstream bandwidth. I really doubt that choosing to badly support extreme ratios will stop or even slow down the deployment, and the technology continues to develop in ways that make such ratios more common (it's much easier to spend money on signal processing for a central box than for all the endpoint products) David Lang