Re: [quicwg/base-drafts] Make the ECN requirements match the the discussion in #2156. Fixes #2156 (#2201)

ekr <notifications@github.com> Tue, 18 December 2018 11:42 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 9B0C2130EC0 for <quic-issues@ietfa.amsl.com>; Tue, 18 Dec 2018 03:42:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.459
X-Spam-Level:
X-Spam-Status: No, score=-9.459 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, URIBL_BLOCKED=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 Bf3qCK6c-Wn2 for <quic-issues@ietfa.amsl.com>; Tue, 18 Dec 2018 03:42:02 -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 5B39E130EBE for <quic-issues@ietf.org>; Tue, 18 Dec 2018 03:42:02 -0800 (PST)
Date: Tue, 18 Dec 2018 03:42:00 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1545133320; bh=AwgoSAzRkKnU8n3/6Xkb0PDnzphEJgbdDgbKjglJAJc=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=rRyYRT0sh7o9+SKd7F2feXX3qiiIln/cG0KQwYFgEDHGc1aKwCMiZep3wy5Bu1myD hmdBqmvcdeQjTqMoDQ6hJHrExYpftp7CLeQMCU1LsThRFzzyUcYsdhTRX/FGNwuqzR p+vNLZ1yEv6G2V2nYN6D/9+QedoYnDxRLxeexR6g=
From: ekr <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abc28e840059fe4f5bd13ece039125d9a9fa46a8b392cf0000000118309f0892a169ce175ab940@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/2201/c448192650@github.com>
In-Reply-To: <quicwg/base-drafts/pull/2201@github.com>
References: <quicwg/base-drafts/pull/2201@github.com>
Subject: Re: [quicwg/base-drafts] Make the ECN requirements match the the discussion in #2156. Fixes #2156 (#2201)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c18dd08c2eb4_33853fb62e0d45c079886"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: ekr
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/bLwb_EKrGRT8EO7lHBZtn0cdUmk>
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: Tue, 18 Dec 2018 11:42:05 -0000

I took the discussion to be "MAY" but obviously this is easily changed if
the chairs judge consensus otherwise.



On Mon, Dec 17, 2018 at 8:19 PM Martin Thomson <notifications@github.com>
wrote:

> *@martinthomson* approved this pull request.
> ------------------------------
>
> In draft-ietf-quic-transport.md
> <https://github.com/quicwg/base-drafts/pull/2201#discussion_r242402632>:
>
> > @@ -3014,11 +3016,11 @@ the 1-RTT packet number space will be increased by two.
>
>  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 feedback about ECN markings received (if accessible).
> +other peer. Even if not setting ECN codepoints on packets it transmits, the
> +endpoint MAY provide feedback about ECN markings received (if accessible).
>
> SHOULD?
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub
> <https://github.com/quicwg/base-drafts/pull/2201#pullrequestreview-185901814>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/ABD1oRt2EbSqbfKSyUhZ6ug38oB5aX__ks5u6Gy7gaJpZM4ZW1UG>
> .
>


-- 
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/2201#issuecomment-448192650