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

Marten Seemann <> Sat, 26 January 2019 08:08 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 0442713117B for <>; Sat, 26 Jan 2019 00:08:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -11.148
X-Spam-Status: No, score=-11.148 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, URIBL_BLOCKED=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 XWdLOBj42Ugw for <>; Sat, 26 Jan 2019 00:08:52 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 40545131177 for <>; Sat, 26 Jan 2019 00:08:52 -0800 (PST)
Date: Sat, 26 Jan 2019 00:08:50 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1548490130; bh=8qhyj/+3NMP2DehqLe4cnFmm9O4aWiQHSiQijOAQJzU=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=oWu7TifjVpM4KfKBvzhwlUjRRM2SMlu1hHsItozn46pMSrCQyaN+uZ9auG/oscYvw 31GJ+7GbvIwY2XL5GFAU4Hx9um4rIWgxk6WLbgECsyJ3M/fxNG5e6RRauFgVJlnWDf uib1TkPQ2rVsW83NbjDWH7v9dmSvLip1IKwqtLdo=
From: Marten Seemann <>
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_5c4c1592bdd4d_35ce3f8a86ad45bc241729"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: marten-seemann
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: Sat, 26 Jan 2019 08:08:54 -0000

If I understand our [rules for dropping keys]( correctly, this attack is only possible for a limited amount of time, namely 3 PTO after the server received the Client Initial:
> For 0-RTT keys, which do not carry CRYPTO frames, this timer starts when the first packets protected with 1-RTT are sent or received.

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