[tcpm] Duplicate or ghost ACK
Michael Tuexen <tuexen@fh-muenster.de> Wed, 18 November 2026 00:42 UTC
Received: from mx-out-02.fh-muenster.de (mx-out-02.fh-muenster.de [212.201.120.206]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange x25519 server-signature ECDSA (prime256v1) server-digest SHA256) (No client certificate requested) by mx.ietf.org (Postfix) with ESMTPS id E75D646 for <tcpm@ietf.org>; Wed, 18 Nov 2026 00:42:27 +0000 (UTC)
Authentication-Results: mx.ietf.org; dkim=none; spf=pass (mx.ietf.org: domain of tuexen@fh-muenster.de designates 212.201.120.206 as permitted sender) smtp.mailfrom=tuexen@fh-muenster.de; dmarc=none
Received: from mail-director-01.fh-muenster.de (mail-director-01.fh-muenster.de [185.149.215.227]) by mx-out-02.fh-muenster.de (Postfix) with ESMTPS id A7C35E260A for <tcpm@ietf.org>; Wed, 18 Nov 2026 01:42:20 +0100 (CET)
Received: from smtpclient.apple (dhcp-860e.users.meeting.ietf.org [31.133.134.14]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: tuexen) by mail-director-01.fh-muenster.de (Postfix) with ESMTPSA id 4363F1A00EC for <tcpm@ietf.org>; Wed, 18 Nov 2026 01:42:19 +0100 (CET)
From: Michael Tuexen <tuexen@fh-muenster.de>
Content-Type: multipart/signed; boundary="Apple-Mail=_EA46B4F8-1347-483C-9695-E63209E4423F"; protocol="application/pkcs7-signature"; micalg="sha-256"
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3901.200.71.1.16\))
Message-Id: <F065AEFB-7716-4D46-BAE9-FD04913C86A2@fh-muenster.de>
Date: Tue, 17 Nov 2026 16:42:18 -0800
To: tcpm <tcpm@ietf.org>
X-Mailer: Apple Mail (2.3901.200.71.1.16)
X-Spamd-Bar: ----------------
Message-ID-Hash: GDPDVQVINQUW4BL2XJ4VIY2TUJYIDLB4
X-Message-ID-Hash: GDPDVQVINQUW4BL2XJ4VIY2TUJYIDLB4
X-MailFrom: tuexen@fh-muenster.de
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; header-match-tcpm.ietf.org-0; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.10
Precedence: list
Subject: [tcpm] Duplicate or ghost ACK
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/tcpm/ZbjDTFQSHeKSVHAToyAnKBr3TpU>
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>
Dear all, as mentioned in the TCPM meeting on Monday, I would like to bring up a question, which will resolve one of the WGLC comments we got back for draft-ietf-tcpm-tcp-ghost-acks-09. Using the notation of RFC 9293, assume we have a TCP handshake completed: Send: <SEQ=ISS><CTL=SYN> Recv: <SEQ=IRS><ACK=ISS+1><CTL=SYN,ACK> Send: <SEQ=ISS+1><ACK=IRS+1><CTL=ACK> Now the endpoint receives the following ACK segment: Recv: <SEQ=IRS+1><ACK=ISS><CTL=ACK> The question is: Is this a duplicate ACK or a ghost ACK? A ghostACK is defined as an ACK segment acknowledging a sequence number, for which data never was sent. In my view, the above ACK is a ghost ACK, since it acknowledges all sequence number smaller than ISS, none of which has been sent. Does anyone agree with this analysis or does anyone objects? Best regards Michael
- [tcpm] Duplicate or ghost ACK Michael Tuexen
- [tcpm] Re: Duplicate or ghost ACK Flavius-Romeo MAZILU (123666)