IETF Logo Mail Archive

Re: [quicwg/base-drafts] No reading of 1-RTT before the handshake is complete (#3224)

Jana Iyengar <notifications@github.com> Tue, 19 November 2019 02:39 UTC

Return-Path: <noreply@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 2F582120BA9 for <quic-issues@ietfa.amsl.com>; Mon, 18 Nov 2019 18:39:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.383
X-Spam-Level:
X-Spam-Status: No, score=-6.383 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_24=1.618, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, 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 vIKW2tWkYYmE for <quic-issues@ietfa.amsl.com>; Mon, 18 Nov 2019 18:39:04 -0800 (PST)
Received: from out-19.smtp.github.com (out-19.smtp.github.com [192.30.252.202]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5546C120255 for <quic-issues@ietf.org>; Mon, 18 Nov 2019 18:39:04 -0800 (PST)
Received: from github-lowworker-f144ac1.va3-iad.github.net (github-lowworker-f144ac1.va3-iad.github.net [10.48.16.59]) by smtp.github.com (Postfix) with ESMTP id AFEA5520782 for <quic-issues@ietf.org>; Mon, 18 Nov 2019 18:39:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1574131143; bh=AHUjRvQgFyOBXj5CQN0mkSA90qZILIpl2/cu+JJuzOY=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=SoLMNnM08KLJ1jdSuS2FYICrXi8uXwfpoIAUNJ3+JT5o3+ls4UDn3lMk7dq1vkuHX 7NCPhI1PWOlxEf8ukZELyWzbPqnaqWe+UbutQ/t5Vpw4r1fNv7v9mIGreS/Hq+SGrv 8tZ8csiTj4n5T0XVJ0vD9JtDLxVzpknQtfCNz86A=
Date: Mon, 18 Nov 2019 18:39:03 -0800
From: Jana Iyengar <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK2AH5H7IRIVVYLIQX534CEEPEVBNHHB6ES7L4@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/3224/review/318753830@github.com>
In-Reply-To: <quicwg/base-drafts/pull/3224@github.com>
References: <quicwg/base-drafts/pull/3224@github.com>
Subject: Re: [quicwg/base-drafts] No reading of 1-RTT before the handshake is complete (#3224)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5dd355c79f8a1_3e13fa8cb0cd95c2505"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: janaiyengar
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: quic-issues@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/g1xggptnU-NkUDcomNHk_P5yiQk>
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: Tue, 19 Nov 2019 02:39:09 -0000

janaiyengar commented on this pull request.



> @@ -1171,27 +1171,34 @@ Note:
 ## Receiving Out-of-Order Protected Frames {#pre-hs-protected}
 
 Due to reordering and loss, protected packets might be received by an endpoint
-before the final TLS handshake messages are received.  A client will be unable
-to decrypt 1-RTT packets from the server, whereas a server will be able to
-decrypt 1-RTT packets from the client.
+before the final TLS handshake messages are received.  Each endpoint MUST NOT
+decrypt 1-RTT packets from its peer prior to completing the handshake.

Meh. Both/Each, they're both sucky here.

-- 
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/3224#discussion_r347707369

v2.23.0 | Report a Bug | By Email