Re: [quicwg/base-drafts] 0-RTT can't use transport parameters or 1-RTT frames (#2461)

Kazuho Oku <> Wed, 13 February 2019 03:07 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id D76CE1295D8 for <>; Tue, 12 Feb 2019 19:07:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.597
X-Spam-Status: No, score=-1.597 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, HTML_IMAGE_ONLY_28=1.404, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_NONE=-0.0001, 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 6ZP_KgcKfPae for <>; Tue, 12 Feb 2019 19:07:52 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 1665D1277D2 for <>; Tue, 12 Feb 2019 19:07:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed;; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=ymbVWtzfcrkyyNxGDPs3Pn4LVck=; b=kt068FlWQ+hcae4M WBF7oEG23uyGtXKyvO9OO6H2WXFw0nQsxTYLZj9WSSLgQG6mr2wDvMJ0ifElJLEh zjbi3ybHAjbq8mq8o6zl1immSWDJqEfTuJ5I6nIVDBq0Cue5r+/17XSB/n9DHCT4 0jQ9T/Huh9inG6yoS68MkJKbCm8=
Received: by with SMTP id filter0999p1las1-12308-5C638A06-16 2019-02-13 03:07:50.875260101 +0000 UTC m=+356175.253909715
Received: from (unknown []) by (SG) with ESMTP id DNDeu5HPTUGgLAO3_OeK7A for <>; Wed, 13 Feb 2019 03:07:50.786 +0000 (UTC)
Received: from (localhost []) by (Postfix) with ESMTP id BBFFAA80242 for <>; Tue, 12 Feb 2019 19:07:50 -0800 (PST)
Date: Wed, 13 Feb 2019 03:07:51 +0000
From: Kazuho Oku <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/pull/2461/review/>
In-Reply-To: <quicwg/base-drafts/pull/>
References: <quicwg/base-drafts/pull/>
Subject: Re: [quicwg/base-drafts] 0-RTT can't use transport parameters or 1-RTT frames (#2461)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c638a06b193a_3acf3fe9cf6d45b81311aa"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: kazuho
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak1hP/wFL+CztJjGUj3YC4GlLfAQyaGkgjmV4v enDz8MIqAQrlrIEdWVlfkB2vMvk0z7BrlW5IsBwr+45aLJIzS43057SyPfvzAf5FdBBwm3lYRkdwih ybqVPQu601VmCJ8MPT+z75jvg6IKai5Gby9HLNx6wQPXJiwocMaykQpcotqqfK38d6/dODp/p7/FA7 Q=
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, 13 Feb 2019 03:07:54 -0000

kazuho approved this pull request.

LGTM modulo the very minor concern below.

 A client SHOULD instead generate a fresh cryptographic handshake message and
 start packet numbers from 0.  This ensures that new 0-RTT packets will not use
 the same keys, avoiding any risk of key and nonce reuse; this also prevents
 0-RTT packets from previous handshake attempts from being accepted as part of
 the connection.
+A client MUST NOT send 0-RTT packets once it starts processing 1-RTT packets
+from the server.  This means that 0-RTT packets can't contain any response to
+packets a server sends.  For instance, a client cannot send an ACK frame in a

Maybe it's worth clarifying that: "any response to _1-RTT_ packets"?

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