Re: [quicwg/base-drafts] Use of "supports ECN" is confusing (#1587)

janaiyengar <notifications@github.com> Tue, 07 August 2018 19:11 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 C3754130EA2 for <quic-issues@ietfa.amsl.com>; Tue, 7 Aug 2018 12:11:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.009
X-Spam-Level:
X-Spam-Status: No, score=-8.009 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, 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 JwcB0lcdYlD7 for <quic-issues@ietfa.amsl.com>; Tue, 7 Aug 2018 12:11:31 -0700 (PDT)
Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C697E130E0F for <quic-issues@ietf.org>; Tue, 7 Aug 2018 12:11:31 -0700 (PDT)
Date: Tue, 07 Aug 2018 12:11:30 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1533669090; bh=2L8rMS/IYpQMpWS+JTTpwC/Er6/a4VRb4QYcnKOAQbA=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=b6URD/K+LKZoW2yeJ5I3mYDaXevPj/PCFWQ7oysSewXsK3SEWp8IVYMFhpShWNEne Zkr7WnJ5NPQ2Fv+SRICX/ufbGml+0UhiDx5+N9c4GvfLv81kTOX0Oahw64z5BGKQ2M lbigXG5XK4tNdMgrXmeiSDxBdlxm8FQZkESCGqvg=
From: janaiyengar <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abca63db58a41ba8e756ecc5b9665894d83628d44192cf000000011781b0e292a169ce14701b1c@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/1587/411168016@github.com>
In-Reply-To: <quicwg/base-drafts/issues/1587@github.com>
References: <quicwg/base-drafts/issues/1587@github.com>
Subject: Re: [quicwg/base-drafts] Use of "supports ECN" is confusing (#1587)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5b69eee2ed3ab_53de3fea0fad45c4147924"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: janaiyengar
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/WRePi6glwEMhzENlzC7D-5hahB8>
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: Tue, 07 Aug 2018 19:11:35 -0000

I don't think this distinction is useful, and I don't understand it. An endpoint can choose to not support ECN, for whatever reason, one of them being that the ECN codepoints are not accessible. If it helps to clarify this, I'm happy to write something that clarifies what "endpoint support of ECN" means... I don't think we need more than a sentence to clarify this.

-- 
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/issues/1587#issuecomment-411168016