Re: [quicwg/base-drafts] RESET_STREAM should be allowed in 0-RTT packets (#2344)

Martin Thomson <> Thu, 31 January 2019 01:14 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 4840F130E25 for <>; Wed, 30 Jan 2019 17:14:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -11.149
X-Spam-Status: No, score=-11.149 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-4.553, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_28=1.404, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001] 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 IjWPj5eh4uob for <>; Wed, 30 Jan 2019 17:14:23 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 372BD126CC7 for <>; Wed, 30 Jan 2019 17:14:23 -0800 (PST)
Date: Wed, 30 Jan 2019 17:14:22 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1548897262; bh=jCsWbKgm155AXKgtnIC943opm+t4+j74evSocIAnKh8=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=in6dBCqQjyGPUp3+eYJIrMgKQv/mh2OVTycPaQKwFk/n9NSa0r35nXXAB3Fc02DgW eA9n8A9xvp6j9vLxxsQF5ug40/bjsVobd5QHeHA0/33cCV2MEDYa+5oB1oiZIy+mfZ VkQ5swgnW0VcJhS8AX+Q+SpguFfdoGJpU6qGinOc=
From: Martin Thomson <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/issues/2344/>
In-Reply-To: <quicwg/base-drafts/issues/>
References: <quicwg/base-drafts/issues/>
Subject: Re: [quicwg/base-drafts] RESET_STREAM should be allowed in 0-RTT packets (#2344)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c524bee298f5_13103f9f7d0d45c4103250"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: martinthomson
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: Thu, 31 Jan 2019 01:14:25 -0000

Tokyo conclusion: limit this to stuff we know that we need.  This leaves CONNECTION_CLOSE, NEW_CONNECTION_ID, PATH_CHALLENGE, PATH_RESPONSE, and PING out for the moment, but if we identify a need, we would do the analysis regarding safety and make a decision.  This means that extensions would need to make their own assessment about safety.

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