Re: [quicwg/base-drafts] Clarify use of the term "supports ECN" (#1631)

mirjak <notifications@github.com> Thu, 02 August 2018 14:28 UTC

Return-Path: <bounces+848413-a050-quic-issues=ietf.org@sgmail.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 3A3A2130E77 for <quic-issues@ietfa.amsl.com>; Thu, 2 Aug 2018 07:28:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.01
X-Spam-Level:
X-Spam-Status: No, score=-3.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_NONE=-0.0001, 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 ixQ9Df3u_iEq for <quic-issues@ietfa.amsl.com>; Thu, 2 Aug 2018 07:28:57 -0700 (PDT)
Received: from o9.sgmail.github.com (o9.sgmail.github.com [167.89.101.2]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 46A29130E78 for <quic-issues@ietf.org>; Thu, 2 Aug 2018 07:28:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=H/Kmj//DN8BoFLN0pcSDSYgvoYM=; b=ixfeVQ93Eefp0gqd tw1QmBZ4jhYgTb7OOVELfPS1ZsFWb8aTn31NjvQYuHRAKShYth8hzwOcGCRDVwec 5HL3kBNW8RgKiplwVeSdwH7I26rcdOx74GaySam1vws0QWcpZI/1plNtPCPDqMeN NEBi+gQf2OJXUL/N/ONBlV3tqrw=
Received: by filter0795p1las1.sendgrid.net with SMTP id filter0795p1las1-26577-5B631527-42 2018-08-02 14:28:55.828014455 +0000 UTC m=+662409.553008866
Received: from github-lowworker-56a5eb2.cp1-iad.github.net (unknown [192.30.252.33]) by ismtpd0021p1iad2.sendgrid.net (SG) with ESMTP id HWGZegpLSdmWqPgm-KtIPg for <quic-issues@ietf.org>; Thu, 02 Aug 2018 14:28:55.682 +0000 (UTC)
Received: from github.com (localhost [127.0.0.1]) by github-lowworker-56a5eb2.cp1-iad.github.net (Postfix) with ESMTP id 9CFE5C151F for <quic-issues@ietf.org>; Thu, 2 Aug 2018 07:28:55 -0700 (PDT)
Date: Thu, 02 Aug 2018 14:28:56 +0000
From: mirjak <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab9a20239bd1ea0f5e5882d70753f36579a165127992cf00000001177ad72792a169ce14a9568b@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/1631/review/142819639@github.com>
In-Reply-To: <quicwg/base-drafts/pull/1631@github.com>
References: <quicwg/base-drafts/pull/1631@github.com>
Subject: Re: [quicwg/base-drafts] Clarify use of the term "supports ECN" (#1631)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5b6315279b2a3_4efc3f84a84d45c4164654"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: mirjak
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: quic-issues@ietf.org
X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak2f6sdorxaaXsqmdUwM2F6I4QSoJnvq9yT6I1 S8PfVtvOgcsurJtOWiBRsGTY91RB69eHlfedd79EHkuKjhjpsrdfujIZp0VG9+dAtTdybgrdmQmU/L TBjjrOcGHUx5pkifuqXjalsskGZlgqqwxPtm0Iptw2VM0uAuZQw73KFHEg==
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/I839_4HjlrwNGUy8PN1-9dpiCfA>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.27
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: Thu, 02 Aug 2018 14:28:59 -0000

mirjak commented on this pull request.



> -
-To verify that both a path and the peer support ECN, an endpoint MUST set one of
-the ECN Capable Transport (ECT) codepoints -- ECT(0) or ECT(1) -- in the IP
-header {{!RFC8311}} of all outgoing packets.
+To use ECN, QUIC endpoints first determine whether a path supports ECN
+marking and the peer is able to access the ECN codepoint in the IP header. 
+A network path regarded as not supporting ECN if ECN marked packets get dropped
+or ECN marking are rewritten on the path.
+An endpoint verifies the path, both during connection establishment 
+and when migrating to a new path (see {{migration}}).
+
+Each endpoint independently verifies and enables use of ECN by setting the IP
+header ECN codepoint to ECN Capable Transport (ECT) for the path from it to the
+other peer. Even if ECN is not used on the path to the peer, the endpoint MUST
+provide ECN feedback information if the receive of a non-zero ECN IP codepoint
+is observed.

Maybe just "the endpoint MUST provide feedback about ECN markings received (if accessible)." Is that better?

-- 
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/1631#discussion_r207247316