Re: [quicwg/base-drafts] Handshake loss recovery interacts poorly with amplification attack defense (#1764)
martinduke <notifications@github.com> Sat, 22 September 2018 03:20 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 CF80F130DD8 for <quic-issues@ietfa.amsl.com>; Fri, 21 Sep 2018 20:20:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.01
X-Spam-Level:
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: 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 rd3qOVlRfWXZ for <quic-issues@ietfa.amsl.com>; Fri, 21 Sep 2018 20:20:54 -0700 (PDT)
Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 852CA124D68 for <quic-issues@ietf.org>; 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; d=github.com; 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 <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab1b3ab365c9abcc72a11fd23443c8716d764a2c8592cf0000000117bd771592a169ce1589cd31@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/1764/423712859@github.com>
In-Reply-To: <quicwg/base-drafts/issues/1764@github.com>
References: <quicwg/base-drafts/issues/1764@github.com>
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
X-GitHub-Recipient-Address: quic-issues@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/Y7_Y2uxAZKHrmPUTeDxCHQJWZ4U>
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: 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: https://github.com/quicwg/base-drafts/issues/1764#issuecomment-423712859
- [quicwg/base-drafts] Handshake Flow Control can r… martinduke
- Re: [quicwg/base-drafts] Handshake Flow Control c… ianswett
- Re: [quicwg/base-drafts] Handshake loss recovery … martinduke
- Re: [quicwg/base-drafts] Handshake loss recovery … Martin Thomson
- Re: [quicwg/base-drafts] Handshake loss recovery … martinduke
- Re: [quicwg/base-drafts] Handshake loss recovery … martinduke
- Re: [quicwg/base-drafts] Handshake loss recovery … Martin Thomson
- Re: [quicwg/base-drafts] Handshake loss recovery … ianswett
- Re: [quicwg/base-drafts] Handshake loss recovery … martinduke
- Re: [quicwg/base-drafts] Handshake loss recovery … MikkelFJ
- Re: [quicwg/base-drafts] Handshake loss recovery … ianswett
- Re: [quicwg/base-drafts] Handshake loss recovery … Martin Thomson
- Re: [quicwg/base-drafts] Handshake loss recovery … janaiyengar