IETF Logo Mail Archive

Re: [tcpm] More motivating scenarios for tcpm-ack-pull

Gorry Fairhurst <gorry@erg.abdn.ac.uk> Sat, 07 December 2019 13:08 UTC

Return-Path: <gorry@erg.abdn.ac.uk>
X-Original-To: tcpm@ietfa.amsl.com
Delivered-To: tcpm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 711DF1200EC for <tcpm@ietfa.amsl.com>; Sat, 7 Dec 2019 05:08:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dZBNL9E1DLPZ for <tcpm@ietfa.amsl.com>; Sat, 7 Dec 2019 05:08:46 -0800 (PST)
Received: from pegasus.erg.abdn.ac.uk (pegasus.erg.abdn.ac.uk [137.50.19.135]) by ietfa.amsl.com (Postfix) with ESMTP id 95B93120024 for <tcpm@ietf.org>; Sat, 7 Dec 2019 05:08:46 -0800 (PST)
Received: from Gs-MacBook-Pro.local (fgrpf.plus.com [212.159.18.54]) by pegasus.erg.abdn.ac.uk (Postfix) with ESMTPSA id 262D91B00193; Sat, 7 Dec 2019 13:08:43 +0000 (GMT)
Message-ID: <5DEBA45A.2060504@erg.abdn.ac.uk>
Date: Sat, 07 Dec 2019 13:08:42 +0000
From: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
Reply-To: gorry@erg.abdn.ac.uk
Organization: University of Aberdeen
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: Jeremy Harris <jgh@wizmail.org>
CC: tcpm@ietf.org
References: <3326ed99-b077-592b-7913-aeb2286912c4@bobbriscoe.net> <13486113479ebcb344247daedda10467.squirrel@webmail.entel.upc.edu> <CAEeTejJC4KLbjLNWmVxPXwDtrC=rjrcOsVnwjEym2uEhJZq7cw@mail.gmail.com> <3f4d3d94-24a8-4ed8-a752-ae5242907d43@gmx.at> <ef6c55535a860b37056cd014ad178416.squirrel@webmail.entel.upc.edu> <56fe444b-87a2-8004-a178-98e8da1e28ea@wizmail.org>
In-Reply-To: <56fe444b-87a2-8004-a178-98e8da1e28ea@wizmail.org>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/tcpm/-x1pLux_xknjoxB1U1ht5SZPOlU>
Subject: Re: [tcpm] More motivating scenarios for tcpm-ack-pull
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcpm>, <mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tcpm/>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>, <mailto:tcpm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 07 Dec 2019 13:08:48 -0000

On 07/12/2019, 13:01, Jeremy Harris wrote:
> On 07/12/2019 11:30, Carles Gomez Montenegro wrote:
>> Summarizing, there may be two approaches to enable ACK Pull:
>>
>> 1.- Overloading semantics of existing TCP header fields.
>> 2.- Dedicating a resource.
> Dedicating a resource, specifically a new TCP option type,
> if enabling this feature produces performance benefits,
> would have the useful effect of inducing the removal of
> middleboxes that filter unknown options.
Personally, I suspect, that's not going to be a likely outcome in any 
reasonable time frame - and we should focus on understanding whether 
paths that do permit this will gain useful benefit.

Gorry

v2.23.0 | Report a Bug | By Email