IETF Logo Mail Archive

Re: [quicwg/base-drafts] Clarify crypto context for Connection Close (#1818)

Kazuho Oku <notifications@github.com> Tue, 02 October 2018 02:21 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 B4C04127B92 for <quic-issues@ietfa.amsl.com>; Mon, 1 Oct 2018 19:21:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.456
X-Spam-Level:
X-Spam-Status: No, score=-8.456 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.456, 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: 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 M1zoWFx9dvyW for <quic-issues@ietfa.amsl.com>; Mon, 1 Oct 2018 19:21:00 -0700 (PDT)
Received: from out-7.smtp.github.com (out-7.smtp.github.com [192.30.252.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B06001286D9 for <quic-issues@ietf.org>; Mon, 1 Oct 2018 19:21:00 -0700 (PDT)
Date: Mon, 01 Oct 2018 19:20:58 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1538446858; bh=KYM7HiJw4tYizelEBQ6BEzGQcWRgb/IpF5A08MPNPaM=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=knRnkmxj6b7WJPgnGpHUE4IRGWI+YZZufzL6OvZaLradmyuyoKB2LnnatqGLH7CW0 mUvnrKorHVnoZFbdCD4vyTXRjT6SwfLJexjtKIKn2ZwXgEx2HhLIA7zOvAUjQFe9k3 TeGS1QEVLP7xBNYQvjtEBxrOMGHaNsB26lR1UJcA=
From: Kazuho Oku <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab4b1dd3dcc3d69cd6a05a279722475a8672b41e9f92cf0000000117ca980a92a169ce15cb9be3@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/1818/review/160548756@github.com>
In-Reply-To: <quicwg/base-drafts/pull/1818@github.com>
References: <quicwg/base-drafts/pull/1818@github.com>
Subject: Re: [quicwg/base-drafts] Clarify crypto context for Connection Close (#1818)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5bb2d60a3adb4_58653f84bfad45c013841e"; 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-GitHub-Recipient-Address: quic-issues@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/QdkD8oOusdQarqp8FG3Az9MbufE>
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, 02 Oct 2018 02:21:03 -0000

kazuho commented on this pull request.



> @@ -2606,6 +2606,16 @@ An endpoint sends a closing frame (CONNECTION_CLOSE or APPLICATION_CLOSE) to
 terminate the connection immediately.  Any closing frame causes all streams to
 immediately become closed; open streams can be assumed to be implicitly reset.
 
+If the endpoint has successfully decrypted a 1-RTT packet from its peer, it
+SHOULD send CONNECTION_CLOSE in a 1-RTT packet. If not, and it has received a

FWIW, a client "knows that the peer can decrypt a 1-RTT packet" when it receives the first ACK for a 1-RTT packet it has sent. A server knows that when it obtains the 1-RTT read key from the TLS stack (i.e. when a ClientFinished received from the client is processed without an error).

We might want to clarify that.

-- 
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/1818#discussion_r221810280

v2.23.0 | Report a Bug | By Email