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

Martin Thomson <> Tue, 22 January 2019 01:27 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id CE99C130E79 for <>; Mon, 21 Jan 2019 17:27:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -12.553
X-Spam-Status: No, score=-12.553 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_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 ajd7DAF2fwxJ for <>; Mon, 21 Jan 2019 17:27:53 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 38101130E71 for <>; Mon, 21 Jan 2019 17:27:53 -0800 (PST)
Date: Mon, 21 Jan 2019 17:27:51 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1548120471; bh=p9/h7TsR7WfJbsyNxMvp1uLembwH+Pp3nvbtonnB7yY=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=fmkpXZyQG5OLYrwea6xJAMydhHY4IBIEePG2dV5uc1zEcGV0M1jyGUzy1AThBzl/3 HsCLcHa/slcWHvMlJEnHY2GLkVmNuZPZWWCZkHQ0biUH5au4smpVTL7i5Rw9p8x+Zr fa0XfGEpPVZW8VKLj34Wupj1PB4MLQIxx3muK6oo=
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_5c467197e9dec_390f3fe5574d45b4660392"; 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: Tue, 22 Jan 2019 01:27:55 -0000


> The problem with 0-RTT in QUIC is that, unlike TLS 1.3 (that has max_early_data_size), there is no limit in the amount of data that the client can send using the 0-RTT key. IIUC, currently, it's entirely up to the client to decide when it switches from 0-RTT to 1-RTT keys.

QUIC uses `initial_max_data` for that purpose.  You can't receive a flow control update, so whatever value you have for that determines how much 0-RTT you can send.

In thinking through this, I realized that the client can't send 0-RTT after receiving 1-RTT from the server.  A client won't have the keys until it has the entire handshake flight from the server, at which point it has to switch to 1-RTT keys.  So this all comes down to the same calculus we have in TLS/TCP, after you have spent a little bit of time on the question of RESET_STREAM and its effect on long-term application state.

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