[tcpm] Possible error in accurate-ecn

Bob Briscoe <research@bobbriscoe.net> Tue, 10 November 2020 00:31 UTC

Return-Path: <research@bobbriscoe.net>
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 9B32B3A1533 for <tcpm@ietfa.amsl.com>; Mon, 9 Nov 2020 16:31:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 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, HTML_MESSAGE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=bobbriscoe.net
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 ZgiRcJ0GgKcC for <tcpm@ietfa.amsl.com>; Mon, 9 Nov 2020 16:31:17 -0800 (PST)
Received: from cl3.bcs-hosting.net (cl3.bcs-hosting.net [3.11.37.202]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C79133A1263 for <tcpm@ietf.org>; Mon, 9 Nov 2020 16:31:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=bobbriscoe.net; s=default; h=Content-Type:MIME-Version:Date:Message-ID: Subject:From:To:Sender:Reply-To:Cc:Content-Transfer-Encoding:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:In-Reply-To:References:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=K9lk4Z3tTAvGgaQb2uA8rGNLF3aZjw+lrs6t8yUaSN8=; b=BvqTtfYmyPzy84A89QGY2QYJRx 0HapFn1L/+8fhguPIgj/+IUvUbVtZ6X7dppImxRrmaauRLl3IrvExoe3qRrhE+iTji4FeKR9wuWE4 IfBvb8bM52/3d1lTISqQHCRJRydQyyv1QsLJo1fhTwtV6ipKJvXj/dUmdb8PTCgfJWJxGr3ZCrt2M 5xqEQlaKcwtZtX0yb+zp/WY4CNVeAmT4gWXfvuv7mjQusrBkhes+iR7qe6QgyHObE1YFs92iiEjGp wfIjS0HrDuX+1S4n5Mz4/DrsM81Q3j9qXaX+0K1McQsaGcJsqXkbdeoKKVuawFIqZkdEIP1CPlFjO jeij5d5Q==;
Received: from 67.153.238.178.in-addr.arpa ([178.238.153.67]:45658 helo=[192.168.1.11]) by cl3.bcs-hosting.net with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.93) (envelope-from <research@bobbriscoe.net>) id 1kcHZ4-004LF9-Gf; Tue, 10 Nov 2020 00:31:16 +0000
To: Richard Scheffenegger <rscheff@gmx.at>, Mirja Kuehlewind <ietf@kuehlewind.net>, =?UTF-8?Q?Ilpo_J=c3=a4rvinen?= <ilpo.jarvinen@helsinki.fi>, tcpm IETF list <tcpm@ietf.org>
From: Bob Briscoe <research@bobbriscoe.net>
Message-ID: <47df9b8b-515e-d40d-3473-599b0a3e3876@bobbriscoe.net>
Date: Tue, 10 Nov 2020 00:31:13 +0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="------------59B0390BB3B319789DFBF248"
Content-Language: en-GB
X-OutGoing-Spam-Status: No, score=-1.0
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - cl3.bcs-hosting.net
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - bobbriscoe.net
X-Get-Message-Sender-Via: cl3.bcs-hosting.net: authenticated_id: in@bobbriscoe.net
X-Authenticated-Sender: cl3.bcs-hosting.net: in@bobbriscoe.net
X-Source:
X-Source-Args:
X-Source-Dir:
Archived-At: <https://mailarchive.ietf.org/arch/msg/tcpm/JrIlJa8_JdsRp7FaqthidiaWw3E>
Subject: [tcpm] Possible error in accurate-ecn
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: Tue, 10 Nov 2020 00:31:20 -0000

Mirja, Richard, Ilpo, tcpm list,

I've just been reading through the accurate-ecn draft to double-check. I 
think there's a problem with the following text...

3.2.2.5.1.  Data Receiver Safety Procedures

    An AccECN Data Receiver:

    o  SHOULD immediately send an ACK whenever a data packet marked CE
       arrives after the previous [data] packet was not CE.

    o  MUST immediately send an ACK once 'n' CE marks have arrived since
       the previous ACK, where 'n' SHOULD be 2 and MUST be no greater
       than 6.

...
    For the avoidance of doubt, the change-triggered ACK mechanism is
    deliberately worded to solely apply to data packets, and to ignore
    the arrival of a control packet with no payload, because it is
    important that TCP does not acknowledge pure ACKs.


In the first bullet, I think it doesn't matter whether the previous 
packet marked CE was a data packet or a pure ACK (i.e we should remove 
the second occurrence of 'data' that I have put in [square brackets].

The second bullet doesn't consider the possibility that the 'n'th CE 
mark might arrive on a pure ACK. Then, the wording as it stands says the 
Data Receiver MUST immediately ACK a pure ACK. I know TCP never ACKs a 
pure ACK, but I'm not actually sure it does any harm to do so in this 
case (it cannot cause an infinite loop of ACKs). However, given it would 
be unorthodox, we maybe ought to rule it out by rewording anyway?

Thoughts anyone?


Bob

--
________________________________________________________________
Bob Briscoe                               http://bobbriscoe.net/