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

Carles Gomez Montenegro <carlesgo@entel.upc.edu> Thu, 26 March 2020 14:23 UTC

Return-Path: <carlesgo@entel.upc.edu>
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 BC9D93A0905 for <tcpm@ietfa.amsl.com>; Thu, 26 Mar 2020 07:23:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=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 RKKajSBVLtmr for <tcpm@ietfa.amsl.com>; Thu, 26 Mar 2020 07:23:54 -0700 (PDT)
Received: from violet.upc.es (violet.upc.es [147.83.2.51]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0A4B83A0902 for <tcpm@ietf.org>; Thu, 26 Mar 2020 07:23:53 -0700 (PDT)
Received: from entelserver.upc.edu (entelserver.upc.es [147.83.39.4]) by violet.upc.es (8.14.4/8.14.4/Debian-4.1ubuntu1) with ESMTP id 02QENbv0032137; Thu, 26 Mar 2020 15:23:37 +0100
Received: from webmail.entel.upc.edu (webmail.entel.upc.edu [147.83.39.6]) by entelserver.upc.edu (Postfix) with ESMTP id 397811D53C1; Thu, 26 Mar 2020 15:23:36 +0100 (CET)
Received: from 83.53.67.51 by webmail.entel.upc.edu with HTTP; Thu, 26 Mar 2020 15:23:37 +0100
Message-ID: <f6b93a18b2c9ab76d71873c850394448.squirrel@webmail.entel.upc.edu>
In-Reply-To: <32CE26D6-DB33-4F50-A960-23E1E6BAB978@gmail.com>
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> <2BA84671-AF1A-40B0-A195-B64059B780CD@gmail.com> <21b7e16ea8b42772ecc296a325b53ad6.squirrel@webmail.entel.upc.edu> <32CE26D6-DB33-4F50-A960-23E1E6BAB978@gmail.com>
Date: Thu, 26 Mar 2020 15:23:37 +0100
From: Carles Gomez Montenegro <carlesgo@entel.upc.edu>
To: Jonathan Morton <chromatix99@gmail.com>
Cc: tcpm IETF list <tcpm@ietf.org>, Jon Crowcroft <jon.crowcroft@cl.cam.ac.uk>
User-Agent: SquirrelMail/1.4.21-1.fc14
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
X-Virus-Scanned: clamav-milter 0.100.3 at violet
X-Virus-Status: Clean
X-Greylist: IP, sender and recipient auto-whitelisted, not delayed by milter-greylist-4.3.9 (violet.upc.es [147.83.2.51]); Thu, 26 Mar 2020 15:23:37 +0100 (CET)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tcpm/nrcRRTEKFv0OICbXuxgXfjwsBDI>
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: Thu, 26 Mar 2020 14:23:56 -0000

Hi Jonathan,

First of all, sorry for the late reply.

Thanks a lot for your comments. Please find below our inline responses:

>> On 15 Mar, 2020, at 11:38 am, Carles Gomez Montenegro
>> <carlesgo@entel.upc.edu> wrote:
>>
>> Thanks a lot for your detailed response, which helped shape our latest
>> draft [1] in several ways.
>>
>> While we focus on analyzing the problem space and its requirements, it
>> will be good to keep an eye on potential solutions as well, including
>> the
>> one you describe below. In particular, I found the idea of spacing AKP
>> flags (or something similar) in order to control the desired ACK ratio
>> to
>> be very interesting!
>
> I'm glad you found my comment useful.
>
> I think one of the big takeaways from draft-gomez-tcpm-delack-suppr-reqs
> is that the sender has the most information about when, and to what
> extent, Delayed Acks are helpful, but the receiver is the point at which
> they must be implemented. So some means to convey this information from
> sender to receiver is desirable.  The precise form of that is still open
> to debate.

Thanks for your conclusions and assessment.

We agree that the form to convey this information from sender to receiver
is open to debate. We hope that section 5 of our document can contribute
to the discussion!

> And there are well-known circumstances where the receiver already has to
> interrupt or suspend Delayed Ack processing - when it notices a packet
> loss, or receives an ECN mark, for example.  I assume these would not
> change materially on a transport supporting Ack Pull or similar.

In fact, there is a new subsection (4.10), suggested by Bob, that mentions
that the receiver might sometimes be unable to honour the ACK ratio or ACK
behavior desired by the sender (this relates also to your first paragraph
above). In a subsequent revision, we'll be more specific about
circumstances such as the ones you mention above.

Once again, thanks a lot for your comments!

Cheers,

Carles


>  - Jonathan Morton
>
>