Re: [quicwg/base-drafts] Describe what happens if TLS breaks (#3587)

ianswett <> Tue, 21 April 2020 02:21 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 2A5583A15AF for <>; Mon, 20 Apr 2020 19:21:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: 0.082
X-Spam-Status: No, score=0.082 tagged_above=-999 required=5 tests=[DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_IMAGE_ONLY_24=1.282, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, 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 wRawUoV8XfMT for <>; Mon, 20 Apr 2020 19:21:25 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id A73F23A1593 for <>; Mon, 20 Apr 2020 19:21:25 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id C48D15206CC for <>; Mon, 20 Apr 2020 19:21:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1587435684; bh=9d8blNi1lRDocfq63x7zS9QO6t6rhrMUO6B2cQNWDf8=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=fcmnG9viC3Z5nexTE6/zhaOqSPoVcL8cUKEbRjY5SwUZfd5ytYDWwajKAAEHaaw6W vCaJiFzcCZcNGFrbG0CmdQjJByns7e+Zjwei0cHubCNESR9f1Ymeyymch7Bh8BrIMa yOax9n5+Dqf6FHOwrrqUJNKaxl4qcLURwCaDx3qs=
Date: Mon, 20 Apr 2020 19:21:24 -0700
From: ianswett <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/pull/3587/review/>
In-Reply-To: <quicwg/base-drafts/pull/>
References: <quicwg/base-drafts/pull/>
Subject: Re: [quicwg/base-drafts] Describe what happens if TLS breaks (#3587)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5e9e58a4b3dab_1bbc3f978bccd960243586"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: ianswett
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: Tue, 21 Apr 2020 02:21:36 -0000

@ianswett approved this pull request.

> @@ -6170,10 +6170,22 @@ considered separately.
 ### Handshake {#handshake-properties}
 The QUIC handshake incorporates the TLS 1.3 handshake and enjoys the

enjoys is an odd word to me, but I'm struggling to find a better one.

-In addition to those properties, the handshake is intended to provide some
-defense against DoS attacks on the handshake, as described below.
+Any attack on the TLS handshake that might compromise the secrecy or uniqueness

Any attack on the TLS handshake that compromises the secrecy or uniqueness

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