Re: [quicwg/base-drafts] ECN text disables ECN too aggressively (#2534)

Gorry Fairhurst <> Wed, 22 May 2019 09:41 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 72809120074 for <>; Wed, 22 May 2019 02:41:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.465
X-Spam-Status: No, score=-6.465 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_20=1.546, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 1JR9tTnO6Sln for <>; Wed, 22 May 2019 02:41:37 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id E35CA1200DE for <>; Wed, 22 May 2019 02:41:36 -0700 (PDT)
Date: Wed, 22 May 2019 02:41:35 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1558518095; bh=G81g31IJfh58QkBSzXpc721TO0YXHq+xmb7V8MD/a90=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=L/qE+Bqt6c7B2nN4QDFtP6MFP951jnm7iHrdL8uQ6R3spL8W33Mw/emQCmGQuSmlG Vah8xkJHoDvBDVaOXN+dDsGuZZY7qF7hI8Z3fbppN8zBMT/vszwXTzBX/JQNmEYFJi Vwiyoh79Ove/MznfjURD3l4hvViOZYlTl1M37Eb0=
From: Gorry Fairhurst <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/issues/2534/>
In-Reply-To: <quicwg/base-drafts/issues/>
References: <quicwg/base-drafts/issues/>
Subject: Re: [quicwg/base-drafts] ECN text disables ECN too aggressively (#2534)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5ce5194fd2c98_46e13fa273acd9601311b0"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: gorryfair
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
Archived-At: <>
X-Mailman-Version: 2.1.29
List-Id: Notification list for GitHub issues related to the QUIC WG <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 22 May 2019 09:41:38 -0000

There seems two things:

• What to do during handshake (maybe is described in transport)

• Disabling after handshake which I think is in the loss/recovery draft, rather than transport? - I thought I heard Jana argue that this reaction depends on the loss/marking observations on the path - which I would agree with.

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub: