[tcpm] Question on draft-gomez-tcpm-ack-rate-request

"Scharf, Michael" <Michael.Scharf@hs-esslingen.de> Thu, 11 March 2021 14:30 UTC

Return-Path: <Michael.Scharf@hs-esslingen.de>
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 B627C3A0E83; Thu, 11 Mar 2021 06:30:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.097
X-Spam-Level:
X-Spam-Status: No, score=-7.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=hs-esslingen.de
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 K7Ws4iHZ5De2; Thu, 11 Mar 2021 06:30:24 -0800 (PST)
Received: from mail.hs-esslingen.de (mail.hs-esslingen.de [134.108.32.78]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BC6E63A0E79; Thu, 11 Mar 2021 06:30:20 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by mail.hs-esslingen.de (Postfix) with ESMTP id 19B0E25A17; Thu, 11 Mar 2021 15:30:16 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=hs-esslingen.de; s=mail; t=1615473016; bh=vobrlhL2JKfQSE92M5nbcOKCfPkara/JY9UNCJr1jlQ=; h=From:To:CC:Subject:Date:From; b=wvE4dDv5RtYatra07AkE0t2BcTO6/eS0bTTcGYGSWD41EkTEF/zCl/AoVUxg5UJvu uwNIJbdbtGYmXMxWEIswrZkjQBLN3rP66y2a4PBd+Tuc6yKZyZMn8CAK6OuuWCEuEx Aqn2S97+K37tAk9Dn9Ht2yHTEiTTo1mZheV128j0=
X-Virus-Scanned: by amavisd-new-2.7.1 (20120429) (Debian) at hs-esslingen.de
Received: from mail.hs-esslingen.de ([127.0.0.1]) by localhost (hs-esslingen.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1aatc_t4ySNm; Thu, 11 Mar 2021 15:30:15 +0100 (CET)
Received: from rznt8202.rznt.rzdir.fht-esslingen.de (rznt8202.hs-esslingen.de [134.108.48.165]) (using TLSv1.2 with cipher AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.hs-esslingen.de (Postfix) with ESMTPS; Thu, 11 Mar 2021 15:30:15 +0100 (CET)
Received: from rznt8202.rznt.rzdir.fht-esslingen.de (134.108.48.165) by rznt8202.rznt.rzdir.fht-esslingen.de (134.108.48.165) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2176.2; Thu, 11 Mar 2021 15:30:15 +0100
Received: from rznt8202.rznt.rzdir.fht-esslingen.de ([fe80::aca4:171a:3ee1:57e0]) by rznt8202.rznt.rzdir.fht-esslingen.de ([fe80::aca4:171a:3ee1:57e0%3]) with mapi id 15.01.2176.009; Thu, 11 Mar 2021 15:30:15 +0100
From: "Scharf, Michael" <Michael.Scharf@hs-esslingen.de>
To: "draft-gomez-tcpm-ack-rate-request@ietf.org" <draft-gomez-tcpm-ack-rate-request@ietf.org>
CC: tcpm IETF list <tcpm@ietf.org>
Thread-Topic: Question on draft-gomez-tcpm-ack-rate-request
Thread-Index: AdcWf1FSmuOq9VMPR0mzgOrQuE5n4g==
Date: Thu, 11 Mar 2021 14:30:15 +0000
Message-ID: <7af3375e51f849c1ad934a758c30279e@hs-esslingen.de>
Accept-Language: de-DE, en-US
Content-Language: de-DE
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [134.108.140.248]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/tcpm/K8_dlkzXYCa6Xi0HxbCpgyPyCT8>
Subject: [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: Thu, 11 Mar 2021 14:30:26 -0000

Hi Carles,

I wonder if it is possible to save one byte of space in the option proposed in draft-gomez-tcpm-ack-rate-request-02.

As far as I understand the proposal, the "N" field is only used if the "R" field is 0. So, no matter whether R is set to 0 or >0, almost one byte of the TCP option just consists of zero bits. If that was true, it might be inefficient to transfer a large number of zero bits in the TCP header. TCP option space is rather scarce and should not be wasted.

Wouldn't be one byte less be sufficient?

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.)

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"?

(And, if significantly large values were needed for "R" and "N", one could use another encoding instead of a raw binary number, such as encoding an exponent - then 6 bit would be a lot).

Or do I just miss something basic and need more coffee?

Thanks

Michael