Re: [quicwg/base-drafts] Explain asymmetric confirmation condition (#2881)

Martin Thomson <> Sun, 14 July 2019 22:38 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id AEBD1120121 for <>; Sun, 14 Jul 2019 15:38:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.596
X-Spam-Status: No, score=-6.596 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_HI=-5, SPF_HELO_NONE=0.001, 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 9MZeDHJIwpTu for <>; Sun, 14 Jul 2019 15:38:01 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 1B4B212006B for <>; Sun, 14 Jul 2019 15:38:01 -0700 (PDT)
Date: Sun, 14 Jul 2019 15:38:00 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1563143880; bh=ctrgxHz5XDtxQ2SmzpnC8Zc/WpYl7BO8Smns3XqMwl0=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=2H/GfWXFBd0+X+Xdgz3vMaBTd02eqFmZ3neG4qegSazk7Skeh2bEM/GLsLNnuL8zX +89v9R+un1MaL9Py9DdR0Wzt3lRQ5lnT21H1BkSk+oRV2XMvmKcFGA+afhraDjDalB 7MlL8CTeWVE869vFMJO6X4mWPO2GJoG+ltgBa8co=
From: Martin Thomson <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/pull/2881/review/>
In-Reply-To: <quicwg/base-drafts/pull/>
References: <quicwg/base-drafts/pull/>
Subject: Re: [quicwg/base-drafts] Explain asymmetric confirmation condition (#2881)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5d2baec8f615_297e3fcf454cd96c208655"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: martinthomson
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
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: Sun, 14 Jul 2019 22:38:03 -0000

martinthomson commented on this pull request.

> @@ -391,6 +391,15 @@ 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 or equal to the
 former, the handshake is confirmed.
+: Unless ack-eliciting packets protected by 1-RTT keys are sent by an endpoint,
+  the handshake might never be confirmed by an endpoint.  If the peer does
+  confirm the handshake, this could result in perpetual retransmission of
+  Handshake packets, which cannot be acknowledged.  To avoid this problem, in

It's definitely packets in this case.  The content isn't relevant to the point, it's that they won't/can't be acknowledged.

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