Re: [quicwg/base-drafts] Handshake loss recovery interacts poorly with amplification attack defense (#1764)

martinduke <> Sat, 22 September 2018 03:20 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id CF80F130DD8 for <>; Fri, 21 Sep 2018 20:20:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -8.01
X-Spam-Status: No, score=-8.01 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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, T_DKIMWL_WL_HIGH=-0.01] 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 rd3qOVlRfWXZ for <>; Fri, 21 Sep 2018 20:20:54 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 852CA124D68 for <>; Fri, 21 Sep 2018 20:20:54 -0700 (PDT)
Date: Fri, 21 Sep 2018 20:20:53 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1537586453; bh=4Xm5/Yr34hMwmHVb4zVHYdxzwu6nM9huHgBYVQDQ1H0=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=k7xD4Jjgq5Dcp+0lGrqnq+GzWlJmbp8U6TmGe/1w7S7FY3va2jxFbiTe/w7r3U2TN 4b46Nt73spAEiuigqHi5jJTjYoBk72mZO3oJDcsJpXuuDl1AwwZAc6huwLZrk19KQe GbGS79jnX7Gwdk7S/bZ2wb+ewYQgrYlV9nw8vV1Y=
From: martinduke <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/issues/1764/>
In-Reply-To: <quicwg/base-drafts/issues/>
References: <quicwg/base-drafts/issues/>
Subject: Re: [quicwg/base-drafts] Handshake loss recovery interacts poorly with amplification attack defense (#1764)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5ba5b5156449c_7edc3fb205ad45c04524db"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: martinduke
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: Sat, 22 Sep 2018 03:20:56 -0000

I was under the impression we'd agreed to that.

It can certainly work with just PADDING, but that's more complicated. If the client simply sends a PING right when it gets the Handshake Keys, it is able to use the normal retransmission logic without any odd special cases around handshake timers.

(Setting aside the multiple server-hello case)

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