Return-Path: 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 7A6CC120111 for ; Wed, 8 May 2019 14:02:34 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.392 X-Spam-Level: X-Spam-Status: No, score=-6.392 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] 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 hd_HAZURDoyr for ; Wed, 8 May 2019 14:02:32 -0700 (PDT) Received: from out-1.smtp.github.com (out-1.smtp.github.com [192.30.252.192]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AC3F71200FB for ; Wed, 8 May 2019 14:02:32 -0700 (PDT) Date: Wed, 08 May 2019 14:02:31 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1557349351; bh=l8uSNSbXNxpiiYbkA/hnypek+Q4SYGo2cbLeK7zelpw=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=Md1MDyKTBYHrY17aJ/ZiLTIysVTQMgPANK153VgoOTr/5IQNRn/p3U2oyDzJ/+QSg 3VHF3euE/nPTqDjIDspvDye1Y83WL+08KIR2uaam89bn7BA3oqfFpBI0sXS4ElJZKU NLGBHL3LOxmEpvVs092WoTWTisBN2pxXEJW2lTCo= From: David Schinazi Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Output of the discard keys design team (#2673) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5cd343e78897a_3da93f8f812cd968236929"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: DavidSchinazi X-GitHub-Recipient: quic-issues X-GitHub-Reason: subscribed X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: quic-issues@ietf.org Archived-At: X-BeenThere: quic-issues@ietf.org 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, 08 May 2019 21:02:35 -0000 ----==_mimepart_5cd343e78897a_3da93f8f812cd968236929 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit DavidSchinazi commented on this pull request. > +previous handshake messages have not been modified. Note that the handshake +does not complete on both endpoints simultaneously, therefore any requirements +placed on endpoints based on the completion of the handshake are specific to +the handshake being complete from the perspective of the endpoint in question. + + +### Handshake Confirmed {#handshake-confirmed} + +In this document, the TLS handshake is considered confirmed when both of the +following two conditions are met: the handshake is complete and the endpoint +has received an acknowledgment for a packet sent with 1-RTT keys. This second +condition can be implemented by tracking the lowest packet number sent with +1-RTT keys, and the highest value of the Largest Acknowledged field in any +received 1-RTT ACK frame: once the latter is higher than the former, the +handshake is confirmed. + Good catch, fixed -- 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/2673#discussion_r282248353 ----==_mimepart_5cd343e78897a_3da93f8f812cd968236929 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@DavidSchinazi commented on this pull request.

In draft-ietf-quic-tls.md:

> +previous handshake messages have not been modified.  Note that the handshake
+does not complete on both endpoints simultaneously, therefore any requirements
+placed on endpoints based on the completion of the handshake are specific to
+the handshake being complete from the perspective of the endpoint in question.
+
+
+### Handshake Confirmed {#handshake-confirmed}
+
+In this document, the TLS handshake is considered confirmed when both of the
+following two conditions are met: the handshake is complete and the endpoint
+has received an acknowledgment for a packet sent with 1-RTT keys.  This second
+condition can be implemented by tracking the lowest packet number sent with
+1-RTT keys, and the highest value of the Largest Acknowledged field in any
+received 1-RTT ACK frame: once the latter is higher than the former, the
+handshake is confirmed.
+

Good catch, fixed

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

----==_mimepart_5cd343e78897a_3da93f8f812cd968236929--