Re: [quicwg/base-drafts] In an unlikely event of emergency.... set ECN marks (#3454)

mirjak <notifications@github.com> Wed, 26 February 2020 10:50 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 142903A0418 for <quic-issues@ietfa.amsl.com>; Wed, 26 Feb 2020 02:50:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.554
X-Spam-Level:
X-Spam-Status: No, score=-1.554 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_IMAGE_ONLY_20=1.546, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, SPF_HELO_NONE=0.001, 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 o-Ceco2lb5h6 for <quic-issues@ietfa.amsl.com>; Wed, 26 Feb 2020 02:50:56 -0800 (PST)
Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DB9063A0415 for <quic-issues@ietf.org>; Wed, 26 Feb 2020 02:50:55 -0800 (PST)
Received: from github-lowworker-ca5950c.va3-iad.github.net (github-lowworker-ca5950c.va3-iad.github.net [10.48.17.57]) by smtp.github.com (Postfix) with ESMTP id D1709C6172B for <quic-issues@ietf.org>; Wed, 26 Feb 2020 02:50:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1582714254; bh=HnTvZkvqBWQtLViuBq3VVJpjNCW/dxFTq92ycUjE/8s=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=YCp1hqq0/T+nVQbIBKP6Cc6R/biEc6UgJCA+6VEQaBgDQciW16fBJUXOVjVJBUOND 7a/PVpAJIh35qGeSG4hzP7GTjbHEomfYP0RphQ1F/VZAWmpBYaserymWk8RYyFXqFc ZqsIhDyeuD+cKSciZmj9udVQsAHlAXcnlPXQdPNg=
Date: Wed, 26 Feb 2020 02:50:54 -0800
From: mirjak <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK4ZM6YVAJUWNPOK5DV4MOAA5EVBNHHCDKKNEA@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/3454/c591364026@github.com>
In-Reply-To: <quicwg/base-drafts/pull/3454@github.com>
References: <quicwg/base-drafts/pull/3454@github.com>
Subject: Re: [quicwg/base-drafts] In an unlikely event of emergency.... set ECN marks (#3454)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5e564d8ec25be_6cd13ff199acd968184188"; 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
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/qmrVFwtS1LoG1bYXYdAFbrxFxqE>
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: Wed, 26 Feb 2020 10:50:57 -0000

I think that is not strong enough. I think "unlikely" is a bit stronger but I also think you need to provide some reasoning why this case is discussed as all (if it is unlikely). I would really like people to understand the situation rather than indicate to implement something complicated that is probably not needed which might cause some people not implement ECN support at all.

-- 
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/3454#issuecomment-591364026