IETF Logo Mail Archive

Re: [quicwg/base-drafts] Allowing QUIC to suspend ECN usage (#4028)

mirjak <notifications@github.com> Thu, 20 August 2020 11: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 9EA283A091B for <quic-issues@ietfa.amsl.com>; Thu, 20 Aug 2020 04:11:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.009
X-Spam-Level:
X-Spam-Status: No, score=-2.009 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_16=1.092, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_MSPIKE_H2=-0.001, 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 7n-IMbPFju5Y for <quic-issues@ietfa.amsl.com>; Thu, 20 Aug 2020 04:11:44 -0700 (PDT)
Received: from out-20.smtp.github.com (out-20.smtp.github.com [192.30.252.203]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1102D3A08FE for <quic-issues@ietf.org>; Thu, 20 Aug 2020 04:11:44 -0700 (PDT)
Received: from github-lowworker-a6a2749.va3-iad.github.net (github-lowworker-a6a2749.va3-iad.github.net [10.48.16.62]) by smtp.github.com (Postfix) with ESMTP id 5F8A6E0C1C for <quic-issues@ietf.org>; Thu, 20 Aug 2020 04:11:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1597921903; bh=ZhGI/sBskWxDhmwVl2mV2DCtmEvxuNmYb56RLbUmkYM=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=CThqb4FDBDkIqPKwaxPQDo914us+U7xujNMkJ4knIbgvSowpmxNOU7ZQU4vQ2IRrH O5YxbOjBEiOJ7A0ksfbX5f2r+Ej9o+4TnVoW8AAqg2VD18bLt61EOxCj/vfby3VGrc kR8LTQyzW2NRJVUhifIhiZbo024OmBo5LjS1YVcU=
Date: Thu, 20 Aug 2020 04:11:43 -0700
From: mirjak <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJKZOTOIT234MJJSP6DF5JI5W7EVBNHHCRJHLKQ@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/4028/677536353@github.com>
In-Reply-To: <quicwg/base-drafts/issues/4028@github.com>
References: <quicwg/base-drafts/issues/4028@github.com>
Subject: Re: [quicwg/base-drafts] Allowing QUIC to suspend ECN usage (#4028)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5f3e5a6f50bae_3fb519641944d"; 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/usJJKucTp1BKqT3d3ZilGPOrRZk>
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: Thu, 20 Aug 2020 11:11:46 -0000

I think the point is if a path changes happens without the sender noticing and suddenly because of misconfiguration alll packets get CE marked you want to detect that and disable ECN. However, if that is something we want to recommend I think we further need to specify this. Another case that is easier to detect would be you only set ECT(0) packets but suddenly get feedback for ECT(1) marks. For that case to detect you basically would need to "run" the validation continuously.

-- 
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/4028#issuecomment-677536353

v2.31.3 | Report a Bug | By Email | System Status