Re: [quicwg/base-drafts] Need to prevent amplification attack for any case where the server's response is big (#1309)
Martin Thomson <notifications@github.com> Thu, 02 August 2018 22:29 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 3244D1286E3 for <quic-issues@ietfa.amsl.com>; Thu, 2 Aug 2018 15:29:57 -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 5TCus57untMq for <quic-issues@ietfa.amsl.com>; Thu, 2 Aug 2018 15:29:55 -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 535A4130DD3 for <quic-issues@ietf.org>; Thu, 2 Aug 2018 15:29:55 -0700 (PDT)
Date: Thu, 02 Aug 2018 15:29:54 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1533248994; bh=UtscV+BfBK4qwDp7VBIJTE5zxaOTDBIrKg3/x36SjAo=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=K+NCmdrh5/ALaNwwdKkbf0C0VVSnVhmSEe1l/Qc2BUwQJatYCgI9H7Zkn3wfh2hyU RuO4nV5Rw51C9TGx36KOQMYoSRAMYf0KRba3kLc7mq1NnDWKTrZFu829GGrlVe2id7 ncmNlCRYvsrly4n9aOUXZo9Pnm0UoZMK8gEUIhls=
From: Martin Thomson <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab5b50f783ac5520c488980b00a1cd5e80ff29c03292cf00000001177b47e292a169ce12d73e29@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/1309/410087950@github.com>
In-Reply-To: <quicwg/base-drafts/issues/1309@github.com>
References: <quicwg/base-drafts/issues/1309@github.com>
Subject: Re: [quicwg/base-drafts] Need to prevent amplification attack for any case where the server's response is big (#1309)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5b6385e29bdf5_3d323fc1ee2d45c028139"; 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
X-GitHub-Recipient-Address: quic-issues@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/6_eRgj8cFQeD-h-LSv1uTjkeeV4>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.27
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: Thu, 02 Aug 2018 22:29:57 -0000
OK, as discussed on #1616: If there is no valid token we already have text that says that you can't send more than 3 datagrams. That covers 0-RTT as well has the handshake. If there is a valid token, limiting the amount of data sent to a valid peer is a job for a congestion controller. In this case, the initial congestion window is sufficient (or, as ekr put it: YOLO). With recommended settings, that moves from 3 packets to 10, which isn't a big enough increase to be problematic, especially considering the amount of processing involved in accepting and responding to 0-RTT. Servers won't want to do that without a reasonable assurance that the data is wanted, so the amplification attack surface is reduced. -- 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/1309#issuecomment-410087950
- [quicwg/base-drafts] Need to prevent amplificatio… ekr
- Re: [quicwg/base-drafts] Need to prevent amplific… Patrick McManus
- Re: [quicwg/base-drafts] Need to prevent amplific… Martin Thomson
- Re: [quicwg/base-drafts] Need to prevent amplific… janaiyengar
- Re: [quicwg/base-drafts] Need to prevent amplific… Martin Thomson
- Re: [quicwg/base-drafts] Need to prevent amplific… Martin Thomson
- Re: [quicwg/base-drafts] Need to prevent amplific… Martin Thomson
- Re: [quicwg/base-drafts] Need to prevent amplific… Martin Thomson
- Re: [quicwg/base-drafts] Need to prevent amplific… Martin Thomson
- Re: [quicwg/base-drafts] Need to prevent amplific… Martin Thomson
- Re: [quicwg/base-drafts] Need to prevent amplific… Martin Thomson