[tcpm] Some comments on rev -08 of draft-ietf-tcpm-tcp-ghost-acks

Gorry Fairhurst <gorry@erg.abdn.ac.uk> Tue, 28 July 2026 12:45 UTC

Return-Path: <gorry@erg.abdn.ac.uk>
X-Original-To: tcpm@mail2.ietf.org
Delivered-To: tcpm@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 7477211FCCF29; Tue, 28 Jul 2026 05:45:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1785242703; bh=6tY4PsPZ0HY+OQbl4Sx+qM53K9Uv1KFzi9JjYaIYdPg=; h=Date:To:Cc:From:Subject; b=bh34ZW6/fBdF4xtzwDA9lzfJmwggiPsn7ZmSsWyDeb71o33jfbD1JrY2Qlzy9OkqO 07v0o3GGbipWPucayLKUhESUWaHobkmvboumhlKS5UvXF8N4cX4oEK4Bj30caMv9Bv XE05Tm5Pc73hEPOX9hNbvdiXKWKWlZip6ysQ1CDQ=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=erg.abdn.ac.uk
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Zw1gzMGE19Se; Tue, 28 Jul 2026 05:45:02 -0700 (PDT)
Received: from pegasus.erg.abdn.ac.uk (pegasus.erg.abdn.ac.uk [137.50.19.135]) by mail2.ietf.org (Postfix) with ESMTP id 3406211FCCF24; Tue, 28 Jul 2026 05:45:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=erg.abdn.ac.uk; s=default; t=1785242700; bh=6tY4PsPZ0HY+OQbl4Sx+qM53K9Uv1KFzi9JjYaIYdPg=; h=Date:To:Cc:From:Subject:From; b=xQ/l4FEN815RR7yq9jvQ7bz7MvOuv6mk2jJI/FvoVxBnXhRyJJ+Snqsw/rhkvAa0z jKmrvifCosLXoNrvJOoNtOCG84CkSuwnZ5CXq0YVN/V104h78XksVPKA2FmXsPUzu6 HBubE04z1paIdS3FL87bXcbHq78qQ0Npst2bF3+hGTDwqPjp1mabZy3zT6gaArysZa GiYiw9Qb7ASP4V7VGOVCg1r/BgNBI7/HMmFORbGGLJsu4bismoQJKheNGzG0SNuQBU wDVKl9oDTyhUag8Ea5fqyhHIHTSwcmylVroojIdQOZIU3kRFdCzcHRn05vITeSkaQs IdgCo3torZaTQ==
Received: from [10.41.34.26] (unknown [77.241.232.4]) by pegasus.erg.abdn.ac.uk (Postfix) with ESMTPSA id 9E51F1B0076D; Tue, 28 Jul 2026 13:44:57 +0100 (BST)
Message-ID: <3342128b-6c22-492e-8d5f-006999f5be59@erg.abdn.ac.uk>
Date: Tue, 28 Jul 2026 14:44:57 +0200
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Content-Language: en-GB
To: tcpm IETF list <tcpm@ietf.org>, "tcpm-chairs@ietf.org" <tcpm-chairs@ietf.org>
From: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
Organization: UNIVERSITY OF ABERDEEN
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Message-ID-Hash: WICYS3S2NRGUMVGSM7X2SYUTAX2KJV7N
X-Message-ID-Hash: WICYS3S2NRGUMVGSM7X2SYUTAX2KJV7N
X-MailFrom: gorry@erg.abdn.ac.uk
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-tcpm.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [tcpm] Some comments on rev -08 of draft-ietf-tcpm-tcp-ghost-acks
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/tcpm/MEuYYkXkjvVyURBY4vuF7HgVe_M>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tcpm>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Owner: <mailto:tcpm-owner@ietf.org>
List-Post: <mailto:tcpm@ietf.org>
List-Subscribe: <mailto:tcpm-join@ietf.org>
List-Unsubscribe: <mailto:tcpm-leave@ietf.org>

I reviewed draft-ietf-tcpm-tcp-ghost-acks revision 08 as a part of an 
effort to provide input to the TCPM working group.

To me, teh current use of RFC 2119 language seems odd, because I read 
this as saying the specification will allow a conformant stack to use 
either approach described or no approach, and that seems like a poor 
choice for a standards-track document.  (e.g. “TCP stacks MAY implement 
one of the” - why “MAY”? )

Could the overall message be to say “ SHOULD implement the method in 
3.2. When RFC4948 is not supported, a receiver can alternatively 
implement the method in 3.1?

I also wonder about the use of SHOULD in section 3.1 and 3.2... Then the 
following comments could simply be fixed by a minor rephrasing to use 
different RFC2119 language, but I’d like to be sure that I have 
correctly understood!

* “At the beginning of the SEG.ACK validation, it SHOULD be determined”, 
I think this ought to be “MUST” when the receiver follows the method in 
3.1? (If it really is a “SHOULD”, then what are the allowed conditions 
this approach is followed bye the check is not performed?)
* I think the same need for “MUST”  applies to the next two “SHOULD” 
clauses in section 3.1 - I wonder could all of these be “MUST” when a 
receifollowing 3.1?

*  I also then wonder if “SHOULD ”,  ought to be “MUST” when following 
the approach in 3.2?

* In 3.2  “An implementation SHOULD handle tcpEStatsAppHCThruOctetsAcked 
overflow.” - is this a requirement, or is there a reason that complaint 
implementation will not check this — if so this needs to be explained, 
and if it remains a “SHOULD” is this a concern when not implemented?

Best wishes,
Gorry
(as a member of TCPM WG)


P.S. I have a few editorial comments:

1. is it true that “TCP as specified in [RFC0793] is widely deployed in 
today's Internet.”? Maybe an explanation or reference is needed to 
support this claim? (Although, I’m unsure if this claiming support for 
sept in RFC793, or just TCP support - is this perhaps what was intended: 
“TCP (as originally specified by [RFC0793] is widely supported…”
2. “This document aims to improve” … This seems like there is doubt, may 
be it could be “This document improves”.
3. “has never sent.” - is there an extra paragraph break or (I think) a 
missing space before the next paragraph?