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

Carles Gomez Montenegro <carlesgo@entel.upc.edu> Sun, 15 March 2020 09:47 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 3527C3A1342 for <tcpm@ietfa.amsl.com>; Sun, 15 Mar 2020 02:47:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.895
X-Spam-Level:
X-Spam-Status: No, score=-1.895 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, 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 aTrvth6TvI7k for <tcpm@ietfa.amsl.com>; Sun, 15 Mar 2020 02:47:32 -0700 (PDT)
Received: from dash.upc.es (dash.upc.es [147.83.2.50]) (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 0BD923A1340 for <tcpm@ietf.org>; Sun, 15 Mar 2020 02:47:26 -0700 (PDT)
Received: from entelserver.upc.edu (entelserver.upc.es [147.83.39.4]) by dash.upc.es (8.14.4/8.14.4/Debian-4.1ubuntu1) with ESMTP id 02F9lLgH028863; Sun, 15 Mar 2020 10:47:21 +0100
Received: from webmail.entel.upc.edu (webmail.entel.upc.edu [147.83.39.6]) by entelserver.upc.edu (Postfix) with ESMTP id 2D3091D53C1; Sun, 15 Mar 2020 10:47:21 +0100 (CET)
Received: from 83.53.67.51 by webmail.entel.upc.edu with HTTP; Sun, 15 Mar 2020 10:47:21 +0100
Message-ID: <391035ee6f57baa407f9be225db8dfbc.squirrel@webmail.entel.upc.edu>
In-Reply-To: <fde0262a-0206-92bf-b529-4043cacc8030@bobbriscoe.net>
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> <db2a849d-a26f-d741-a039-1622c478ee50@gmx.at> <fde0262a-0206-92bf-b529-4043cacc8030@bobbriscoe.net>
Date: Sun, 15 Mar 2020 10:47:21 +0100
From: Carles Gomez Montenegro <carlesgo@entel.upc.edu>
To: Bob Briscoe <in@bobbriscoe.net>
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 dash
X-Virus-Status: Clean
X-Greylist: IP, sender and recipient auto-whitelisted, not delayed by milter-greylist-4.3.9 (dash.upc.es [147.83.2.50]); Sun, 15 Mar 2020 10:47:21 +0100 (CET)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tcpm/5RYaQSQ0kMwinDVLdpq4snue7yc>
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: Sun, 15 Mar 2020 09:47:34 -0000

Hi Bob,

Thanks, once again, for your kind suggestions!

We agreed with your proposal below, and we published the initial version
of a new I-D [1] that has the aim that you described below (i.e.
requirements analysis plus discussion of suggested solutions).

We hope the document can be useful to analyze the problem space in a more
comprehensive approach.

Should you have further comments, please do not hesitate to let us know!

Cheers,

Carles

[1] https://tools.ietf.org/html/draft-gomez-tcpm-delack-suppr-reqs-00


> Carles,
>
> It strikes me that there is a lot of interest in doing something like
> ACK-pull, but also a lot of disagreement in where to draw the line
> between what to do and what not to do.
>
> Can I suggest that a way to resolve this would be to start with an
> informational requirements draft, that I am sure would be adopted as WG
> business immediately given the interest. Whereas any particular choice
> of mechanism at this stage would probably not get the necessary
> consensus to be adopted.
>
> The requirements draft could discuss solutions, not as a "on this we all
> agree" protocol, but in terms of their pros and cons, e.g. which
> mechanisms could satisfy which requirements, so they can be judged
> relative to each mechanism's complexity / traversibility / usage of bits
> / etc.
>
> I will warn you that a requirements draft could itself add years to the
> process (the accurate ECN requirements did [RFC7560]). But not if we
> agree to allow a solution draft to start in parallel once the
> requirements are starting to converge, rather than waiting for the
> requirements to go thru the full RFC process.
>
>
> You might prefer to continue evangelising ack-pull as a sufficient
> solution, so I don't want to say a requirements draft is the only way
> forward. But you saw my comment earlier - that once you've been through
> all the years of effort of getting anything changed in TCP, you
> sometimes feel that you wish you'd been more ambitious than just one bit
> at the start.
>
>
> Bob