Re: [tcpm] Question on draft-gomez-tcpm-ack-rate-request
Carles Gomez Montenegro <carlesgo@entel.upc.edu> Mon, 21 March 2022 18:02 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 F05983A11D5; Mon, 21 Mar 2022 11:02:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.907
X-Spam-Level:
X-Spam-Status: No, score=-6.907 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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 6N-svUWK14Aa; Mon, 21 Mar 2022 11:02:08 -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 A07D93A1143; Mon, 21 Mar 2022 11:02:07 -0700 (PDT)
Received: from entelserver.upc.edu (entelserver.upc.es [147.83.40.4]) by violet.upc.es (8.14.4/8.14.4/Debian-4.1ubuntu1.1) with ESMTP id 22LI22n0049368; Mon, 21 Mar 2022 19:02:02 +0100
Received: from webmail.entel.upc.edu (webmail.entel.upc.edu [147.83.40.6]) by entelserver.upc.edu (Postfix) with ESMTP id 769941D53C1; Mon, 21 Mar 2022 19:02:01 +0100 (CET)
Received: from 79.158.123.136 by webmail.entel.upc.edu with HTTP; Mon, 21 Mar 2022 19:03:07 +0100
Message-ID: <ced6d695031dc8d6c64b56bd094ae1af.squirrel@webmail.entel.upc.edu>
In-Reply-To: <CCE0E8B4-3553-4F2D-A26A-54038CA09A0A@gmail.com>
References: <7af3375e51f849c1ad934a758c30279e@hs-esslingen.de> <494ffff907b21034b43f3ca8151f79d1.squirrel@webmail.entel.upc.edu> <CCE0E8B4-3553-4F2D-A26A-54038CA09A0A@gmail.com>
Date: Mon, 21 Mar 2022 19:03:07 +0100
From: Carles Gomez Montenegro <carlesgo@entel.upc.edu>
To: Jonathan Morton <chromatix99@gmail.com>
Cc: "Scharf, Michael" <michael.scharf@hs-esslingen.de>, "draft-gomez-tcpm-ack-rate-request@ietf.org" <draft-gomez-tcpm-ack-rate-request@ietf.org>, tcpm IETF list <tcpm@ietf.org>
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.103.5 at violet
X-Virus-Status: Clean
X-Greylist: Delayed for 00:06:13 by milter-greylist-4.3.9 (violet.upc.es [147.83.2.51]); Mon, 21 Mar 2022 19:02:02 +0100 (CET)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tcpm/tfL8Mm3hWh6iUtdrK_1YiVBnJME>
Subject: Re: [tcpm] Question on draft-gomez-tcpm-ack-rate-request
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: Mon, 21 Mar 2022 18:02:13 -0000
Hi again, Jonathan, Please find below my inline response: >> On 12 Mar, 2021, at 12:00 pm, Carles Gomez Montenegro >> <carlesgo@entel.upc.edu> wrote: >> >>> Example: >>> >>> 0 1 2 3 >>> 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 >>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ >>> | Kind | Length | ExID | >>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ >>> |I|X|Value| >>> +-+-+-+-+-+-+ >>> >>> The bit "X"=0 would be equivalent to "R"=0, i.e., immediately request >>> ACKs. In that case, the 6 bit field "Value" could encode the value of >>> "N" >>> described in draft-gomez-tcpm-ack-rate-request-02. >>> >>> The bit "X"=1 would enable delayed ACKs ("R">0) and the 6 bit field >>> "Value" would encode the number that "R" defined in >>> draft-gomez-tcpm-ack-rate-request-02. >>> >>> The "I" bit would be defined as in >>> draft-gomez-tcpm-ack-rate-request-02. >>> (It may make sense to change the order and or naming of the fields, or >>> other details of the encoding - this is just an example.) >> >> Yes, your proposal above makes sense! >> >>> As far as I can see, there *is* a difference between this encoding and >>> the >>> one in draft-gomez-tcpm-ack-rate-request-02: There is one bit less to >>> encode the value of "R", and two bits less to encode the value of "N". >>> But >>> would that matter? Do we really expect values larger than 63 (or 63) >>> for >>> "R" and "N"? >> >> Yes, that is a good question, and it would be great to hear what the WG >> thinks about that. That is: are there use cases where R or N might need >> to >> be greater than 63? > > My gut feeling is that values up to 63 are sufficient in both cases. > > It might be possible to contemplate a different encoding which allocates > more range to one use of the field than the other, but this encoding is > simple enough to be hard to accidentally misinterpret, and that has to be > considered a Good Thing and weighed against the benefits of any > alternative. Many thanks for your feedback! At this moment, we are considering two possible approaches in Section 4 [1]: - OPTION 1, which corresponds to the straightforward encoding with a maximum supported value of R=63. - OPTION 2, suggested by Bob, which also captures the idea of better granularity for low R values, but allows encoding a maximum value of R equal to 1024. > - Jonathan Morton Cheers, Carles [1] https://datatracker.ietf.org/doc/html/draft-gomez-tcpm-ack-rate-request-03
- [tcpm] Question on draft-gomez-tcpm-ack-rate-requ… Scharf, Michael
- Re: [tcpm] Question on draft-gomez-tcpm-ack-rate-… Carles Gomez Montenegro
- Re: [tcpm] Question on draft-gomez-tcpm-ack-rate-… Jonathan Morton
- Re: [tcpm] Question on draft-gomez-tcpm-ack-rate-… Carles Gomez Montenegro
- Re: [tcpm] Question on draft-gomez-tcpm-ack-rate-… Bob Briscoe
- Re: [tcpm] Question on draft-gomez-tcpm-ack-rate-… Carles Gomez Montenegro
- Re: [tcpm] Question on draft-gomez-tcpm-ack-rate-… Carles Gomez Montenegro