Re: [quicwg/base-drafts] Editorial fixes to ECN text (#2189)

Martin Thomson <notifications@github.com> Mon, 17 December 2018 02:41 UTC

Return-Path: <noreply@github.com>
X-Original-To: quic-issues@ietfa.amsl.com
Delivered-To: quic-issues@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 267DA130DEB for <quic-issues@ietfa.amsl.com>; Sun, 16 Dec 2018 18:41:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.46
X-Spam-Level:
X-Spam-Status: No, score=-9.46 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-1.46, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com
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 2PjX1vUali3G for <quic-issues@ietfa.amsl.com>; Sun, 16 Dec 2018 18:41:26 -0800 (PST)
Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6D21A1294D7 for <quic-issues@ietf.org>; Sun, 16 Dec 2018 18:41:26 -0800 (PST)
Date: Sun, 16 Dec 2018 18:41:25 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1545014485; bh=tK9B5RO3eDOAK7Nfcz7fstCwZVbyG745iqjq8aZ0NZg=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=1gF6gp/Oj+dwQzLIvEX5UCu8fw2vrn1m0vDWU3a/pUJBNcAc1G9IQcTeUiF4YfjPJ 3VFE62VCTIeDeBQrn8zIV4nm65Py+vD3z0jW3PJW3g2UhUdWHZ70oGJ1xcJjiFA1sb QKHMFfkN3PcOhEt0zr3On5ldwM8qI//Moe0aiSrA=
From: Martin Thomson <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab9f6b05585e9ce92a88c5c0752d29ef8964d1c38792cf00000001182eced592a169ce17535656@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/2189/review/185423232@github.com>
In-Reply-To: <quicwg/base-drafts/pull/2189@github.com>
References: <quicwg/base-drafts/pull/2189@github.com>
Subject: Re: [quicwg/base-drafts] Editorial fixes to ECN text (#2189)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c170cd58da94_34d3f90414d45c0147989"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: martinthomson
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: quic-issues@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/c5B8NtE45ZhXSu_0wrtkCD0uEnc>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Notification list for GitHub issues related to the QUIC WG <quic-issues.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic-issues/>
List-Post: <mailto:quic-issues@ietf.org>
List-Help: <mailto:quic-issues-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Dec 2018 02:41:29 -0000

martinthomson approved this pull request.

Changes LGTM, though I have a new failure mode for ECN to add.

Also, this will rot my new patch, but I can look after that.

> @@ -3031,33 +3031,28 @@ an ACK frame without ECN feedback, the endpoint stops setting ECT codepoints in
 subsequent IP packets, with the expectation that either the network path or the
 peer no longer supports ECN.
 
-To reduce the risk of non-standard compliant ECN markings affecting the
-operation of an endpoint, an endpoint verifies the counts it receives when it
-receives new acknowledgements:
+Network devices that corrupt or apply non-standard ECN markings might result in
+reduced throughput or other undesirable side-effects.  To reduce this risk, an
+endpoint uses the following steps to verify the counts it receives in an ACK
+frame.  Note that the counts MUST NOT be verified if the ACK frame does not

```suggestion
frame.  Counts MUST NOT be verified if the ACK frame does not
```

Now we don't say why this is any more.  Is that OK?

There's a perverse situation in which this results in another problem with this logic.

That situation is where the largest acknowledged is lower on packet that is sent later.  AND that packet acknowledges more packets so that the counts are higher.  AND that packet is reordered ahead of packets with higher largest acknowledged.  This results in the verification failing on the second packet to arrive (counts are lower because it's an older ACK, but the largest acknowledged is higher).

A fix is to never decrease the largest acknowledged when sending an ACK frame.  Another is to disable validation if the packet containing the ACK is not higher-numbered than the last packet containing an ACK.  The question is whether we care enough to recommend either fix...

@gloinul, WDYT?

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/quicwg/base-drafts/pull/2189#pullrequestreview-185423232