IETF Logo Mail Archive

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

MikkelFJ <notifications@github.com> Wed, 13 February 2019 15:34 UTC

Return-Path: <bounces+848413-a050-quic-issues=ietf.org@sgmail.github.com>
X-Original-To: quic-issues@ietfa.amsl.com
Delivered-To: quic-issues@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D691F126C7E for <quic-issues@ietfa.amsl.com>; Wed, 13 Feb 2019 07:34:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.597
X-Spam-Level:
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: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uqzoGh6R-7kf for <quic-issues@ietfa.amsl.com>; Wed, 13 Feb 2019 07:34:19 -0800 (PST)
Received: from o6.sgmail.github.com (o6.sgmail.github.com [192.254.113.101]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0B49912D826 for <quic-issues@ietf.org>; Wed, 13 Feb 2019 07:34:18 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; 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=IQcMcLZz5rpYYf+uqYn1wRyz1iM=; b=E/9SKSiDF/zBF8+s 2UMd6znXNoJNKRFziPgLwbmqfTaPdbPQXgHbqGJaeN9Ae+c494xfJ03qv2c9HfpU B8WGSig7/Vmw9k9Bax74giPi904JJeR2eyNVaDx1IQ/9agz/fkKHfWT5SP9szewd YCMKOgjqNBUNQTChnZVv5CLgxEc=
Received: by filter1106p1las1.sendgrid.net with SMTP id filter1106p1las1-31427-5C6438F9-2A 2019-02-13 15:34:17.756041182 +0000 UTC m=+126204.871987820
Received: from github-lowworker-b40b5a4.cp1-iad.github.net (unknown [192.30.252.36]) by ismtpd0001p1iad1.sendgrid.net (SG) with ESMTP id VvVUQ4RvTKWvaVqOT02ibQ for <quic-issues@ietf.org>; Wed, 13 Feb 2019 15:34:17.656 +0000 (UTC)
Received: from github.com (localhost [127.0.0.1]) by github-lowworker-b40b5a4.cp1-iad.github.net (Postfix) with ESMTP id 984343E0EEE for <quic-issues@ietf.org>; Wed, 13 Feb 2019 07:34:17 -0800 (PST)
Date: Wed, 13 Feb 2019 15:34:18 +0000
From: MikkelFJ <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab325bdd9b280f368f238d87e56ec6f37cd73cf85692cf00000001187bfaf992a169ce1869fe88@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/2461/review/203277589@github.com>
In-Reply-To: <quicwg/base-drafts/pull/2461@github.com>
References: <quicwg/base-drafts/pull/2461@github.com>
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_5c6438f996237_625b3f8d590d45b4236432"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: mikkelfj
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: quic-issues@ietf.org
X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak2aDt2jv1AuQhL/Ue1zqG2TbSySd5Lp+TbejL TOZO7++P7KrZivVTPkzxCha3wjO7TWtvA16c2P+tq7UF8XorK7QfSGipWPmojGTbzC2MJYRNrYD921 lKbRAa3tCxltQQCYiolMto8fgRuHR7bSCSLDnoInfauXWeXelTcOl3QlvlFkAkm4/joeU2d5v27eCI w=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/-GeHet90LNICMiDhMYr-2RInC9A>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Notification list for GitHub issues related to the QUIC WG <quic-issues.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic-issues/>
List-Post: <mailto:quic-issues@ietf.org>
List-Help: <mailto:quic-issues-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Feb 2019 15:34:21 -0000

mikkelfj commented on this pull request.



>  
 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

```suggestion
from the server.  This means that 0-RTT packets cannot contain any response to
```

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/quicwg/base-drafts/pull/2461#pullrequestreview-203277589

v2.23.0 | Report a Bug | By Email