[tcpm] [Fwd: New Version Notification for draft-gomez-tcpm-ack-rate-request-03.txt]

Carles Gomez Montenegro <carlesgo@entel.upc.edu> Wed, 09 March 2022 12:43 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 D484F3A0EE4 for <tcpm@ietfa.amsl.com>; Wed, 9 Mar 2022 04:43:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.904
X-Spam-Level:
X-Spam-Status: No, score=-1.904 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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 BExVq41f9WeI for <tcpm@ietfa.amsl.com>; Wed, 9 Mar 2022 04:43:00 -0800 (PST)
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 B81513A0F06 for <tcpm@ietf.org>; Wed, 9 Mar 2022 04:42:59 -0800 (PST)
Received: from entelserver.upc.edu (entelserver.upc.es [147.83.40.4]) by dash.upc.es (8.14.4/8.14.4/Debian-4.1ubuntu1) with ESMTP id 229CgtkK056537; Wed, 9 Mar 2022 13:42:55 +0100
Received: from webmail.entel.upc.edu (webmail.entel.upc.edu [147.83.40.6]) by entelserver.upc.edu (Postfix) with ESMTP id EE9DF1D53C1; Wed, 9 Mar 2022 13:42:54 +0100 (CET)
Received: from 79.159.85.235 by webmail.entel.upc.edu with HTTP; Wed, 9 Mar 2022 13:44:38 +0100
Message-ID: <b0e042449494fbcc55244ab2791b84a0.squirrel@webmail.entel.upc.edu>
Date: Wed, 09 Mar 2022 13:44:38 +0100
From: Carles Gomez Montenegro <carlesgo@entel.upc.edu>
To: tcpm@ietf.org
Cc: 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]); Wed, 09 Mar 2022 13:42:55 +0100 (CET)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tcpm/U9a6W3tiKhuOZzBzsarKY6A0vbM>
Subject: [tcpm] [Fwd: New Version Notification for draft-gomez-tcpm-ack-rate-request-03.txt]
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: Wed, 09 Mar 2022 12:43:05 -0000

Dear TCPM WG,

Please find below the main details of our recently updated version of the
"TCP ACK Rate Request Option" draft.

This version aims to incorporate the significant amount of feedback that
we received on the previous version (-02).

Main updates in -03:

- The TARR option format has been updated: the N field has been removed
(it appeared to be mostly redundant). The current size of the option is 5
bytes.

- There are two possible encodings for the R field (to be discussed).

- Several clarifications added/made.

- The requirement level for a TARR-capable receiver has changed from MUST
to SHOULD (the related reasons have been added).

- A new section (section 5) has been added to provide guidance on changing
the ACK rate during the lifetime of a TCP connection.

- The security considerations section has been extended.

Many thanks to Yoshifumi Nishida, Jonathan Morton, Michael Scharf, and Bob
Briscoe for providing feedback on -02. Such feedback has been extremely
helpful!

Comments on -03 are very much appreciated.

We would also like to collaborate with implementers. Should you be
interested, please do not hesitate to contact us!

Cheers,

Carles (on behalf of the authors)




---------------------------- Original Message ----------------------------
Subject: New Version Notification for
draft-gomez-tcpm-ack-rate-request-03.txt
From:    internet-drafts@ietf.org
Date:    Mon, March 7, 2022 7:17 am
To:      "Carles Gomez" <carlesgo@entel.upc.edu>
         "Jon Crowcroft" <jon.crowcroft@cl.cam.ac.uk>
--------------------------------------------------------------------------


A new version of I-D, draft-gomez-tcpm-ack-rate-request-03.txt
has been successfully submitted by Carles Gomez and posted to the
IETF repository.

Name:		draft-gomez-tcpm-ack-rate-request
Revision:	03
Title:		TCP ACK Rate Request Option
Document date:	2022-03-06
Group:		Individual Submission
Pages:		10
URL:           
https://www.ietf.org/archive/id/draft-gomez-tcpm-ack-rate-request-03.txt
Status:        
https://datatracker.ietf.org/doc/draft-gomez-tcpm-ack-rate-request/
Htmlized:      
https://datatracker.ietf.org/doc/html/draft-gomez-tcpm-ack-rate-request
Diff:          
https://www.ietf.org/rfcdiff?url2=draft-gomez-tcpm-ack-rate-request-03

Abstract:
   TCP Delayed Acknowledgments (ACKs) is a widely deployed mechanism
   that allows reducing protocol overhead in many scenarios.  However,
   Delayed ACKs may also contribute to suboptimal performance.  When a
   relatively large congestion window (cwnd) can be used, less frequent
   ACKs may be desirable.  On the other hand, in relatively small cwnd
   scenarios, eliciting an immediate ACK may avoid unnecessary delays
   that may be incurred by the Delayed ACKs mechanism.  This document
   specifies the TCP ACK Rate Request (TARR) option.  This option allows
   a sender to request the ACK rate to be used by a receiver, and it
   also allows to request immediate ACKs from a receiver.




The IETF Secretariat