Re: [quicwg/base-drafts] Proposal for adding ECN support to QUIC. (#1372)

Kazuho Oku <notifications@github.com> Fri, 01 June 2018 14:39 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 5CD9312D88D for <quic-issues@ietfa.amsl.com>; Fri, 1 Jun 2018 07:39:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.01
X-Spam-Level:
X-Spam-Status: No, score=-8.01 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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, T_DKIMWL_WL_HIGH=-0.01] 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 1dKvRLYnzCO8 for <quic-issues@ietfa.amsl.com>; Fri, 1 Jun 2018 07:39:28 -0700 (PDT)
Received: from out-1.smtp.github.com (out-1.smtp.github.com [192.30.252.192]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6D89E12D883 for <quic-issues@ietf.org>; Fri, 1 Jun 2018 07:39:28 -0700 (PDT)
Date: Fri, 01 Jun 2018 07:39:27 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1527863967; bh=krZyfa6UKdkQtADhMGKj0EIfQKrVJlGHe4EkghXBj6E=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=loXxqtKNaaR6yjc27rrzJG/yh3SvFZ9TpoSgOkbK55h5wu/X2rvjO/OFRZV2hL2ev tORdCws6CiLmRjp9rFCzzbbkfZp9Vw96ozNMiRUvAcdmGAhfYeIg5XWwrtv4aZRE2L hjP3qlvH2WpTb8ZeJh8EQQWjmoJciMOjnwQpfD5w=
From: Kazuho Oku <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab76cf274165cd9843b03466228e5b39110afb721892cf0000000117291c9f92a169ce13656182@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/1372/review/125194246@github.com>
In-Reply-To: <quicwg/base-drafts/pull/1372@github.com>
References: <quicwg/base-drafts/pull/1372@github.com>
Subject: Re: [quicwg/base-drafts] Proposal for adding ECN support to QUIC. (#1372)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5b115a9f63728_78913f93d94d2f7c176179"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: kazuho
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/fC84fFqdZN8VH1tOPsu0w62dkwU>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.22
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: Fri, 01 Jun 2018 14:39:30 -0000

kazuho commented on this pull request.



> +
+The receiver side should implement three 64-bit counters that are copied to the
+ECN block when an ACK_ECN frame is generated:
+
+ECT_0:
+: Initial value = 0, incremented when a packet marked ECT(0) is received
+
+ECT_1:
+
+: Initial value = 0, incremented when a packet marked ECT(1) is received
+
+CE:
+
+: Initial value = 0, incremented when a packet marked CE is received
+
+Reception of duplicate packets SHOULD NOT increment the counters.

Can we count the packet (for all three counters) *before* detecting duplicates instead?

IMO, theoretically a receiver should send back all the information it has obtained. Ignoring the CE flag in duplicate packets goes against that principle. 

Counting packets after detecting duplicates makes sense only when we can assume that duplication happens near to the receiver than where ECN is applied. I do not think that we have such an assumption.

In practice, the recovery draft with the proposed changes only uses the CE counter to detect if _any_ congestion was reported by the ACK_ECN frame (it's essentially a binary flag). Considering that, I do not think that changing the moment of counting the packets causes any harm.

And lastly but importantly, by changing the rule as such, we can get rid of the requirement to detect duplicates.

See also: https://github.com/quicwg/base-drafts/issues/1405#issuecomment-393743048

-- 
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/1372#pullrequestreview-125194246