Re: [quicwg/base-drafts] Text on ECN probing (#3585)

Lars Eggert <notifications@github.com> Fri, 29 May 2020 08:40 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 47F4E3A0CFB for <quic-issues@ietfa.amsl.com>; Fri, 29 May 2020 01:40:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.555
X-Spam-Level:
X-Spam-Status: No, score=-1.555 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, 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 Kg3T4SdIb3Qn for <quic-issues@ietfa.amsl.com>; Fri, 29 May 2020 01:40:05 -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 156013A0CFA for <quic-issues@ietf.org>; Fri, 29 May 2020 01:40:05 -0700 (PDT)
Received: from github-lowworker-e8b54ca.ac4-iad.github.net (github-lowworker-e8b54ca.ac4-iad.github.net [10.52.23.39]) by smtp.github.com (Postfix) with ESMTP id 5A9CE960415 for <quic-issues@ietf.org>; Fri, 29 May 2020 01:40:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1590741604; bh=FL27iE/cceQjWlFFLNNTsyazQd5A/VhkSS+4NXJ84tA=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=QVt9r4k059IAG7WR8xQnysxMxr4Ul4KP/bPMqdI5jWpzgqoVFG73Xwrsujf6sREsB FIbG1jwKya/606yWtVDuKM257yTRW4BNKUtL739FTxnm489IWumbjQMWqbUFvWGwTJ qDYMzJ1CTYk6iqufPixXru0CzpHCUSV4U1vwS6Vo=
Date: Fri, 29 May 2020 01:40:04 -0700
From: Lars Eggert <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJKYMGYUYAICQECPMPZF43SVWJEVBNHHCHVTIIM@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/3585/635850154@github.com>
In-Reply-To: <quicwg/base-drafts/issues/3585@github.com>
References: <quicwg/base-drafts/issues/3585@github.com>
Subject: Re: [quicwg/base-drafts] Text on ECN probing (#3585)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5ed0ca644bf37_35f13ff16e8cd9682656bf"; charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: larseggert
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/HmOYAL0-IGJL9mekOBFHG0fOWLk>
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: Fri, 29 May 2020 08:40:06 -0000

So last I counted there were only four stacks that even implemented the ACK-ECN frame type to _report_ ECN marks. So even very basic support for ECN is (still) missing in most stacks, esp. the ones that are likely going to see the largest deployments.

I don't think any text tweaks we could make here are going to move the needle on ECN support in QUIC. 

What will make a difference if a major stack implements it and reports a benefit. That will likely make other stacks follow.

-- 
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/3585#issuecomment-635850154