Re: [quicwg/base-drafts] Backoff on CONNECTION_CLOSE (#3157)

MikkelFJ <notifications@github.com> Sat, 22 February 2020 17:54 UTC

Return-Path: <bounces+848413-a050-quic-issues=ietf.org@sgmail.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 4B8E23A047F for <quic-issues@ietfa.amsl.com>; Sat, 22 Feb 2020 09:54:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.555
X-Spam-Level:
X-Spam-Status: No, score=-1.555 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, DKIM_VALID_EF=-0.1, HTML_IMAGE_ONLY_20=1.546, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] 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 xwPCa1uV4jfE for <quic-issues@ietfa.amsl.com>; Sat, 22 Feb 2020 09:54:46 -0800 (PST)
Received: from o8.sgmail.github.com (o8.sgmail.github.com [167.89.101.199]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4B6DB3A0484 for <quic-issues@ietf.org>; Sat, 22 Feb 2020 09:54:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=RVF2ebXMSBqpQwbmU3F3jWW0qyP1PIbMG0ktkMIOUpQ=; b= k8cAI59d1RwOBpEyJ2c/Xp3CEEOqoE/a+z1QYwq+QeTM97FCa96i+Wx2+/Ps0lkY 8kCnvhCsDiS1We0FyFXwA1UFf7TyEhRhxe6JE3nDrwvDuECK9Q2bp3ecHAtaKIyt d0iqKx5Mjiadk6XsEvdaEJzse4RYp9v3ksFmbJTXdRI=
Received: by filter0419p1iad2.sendgrid.net with SMTP id filter0419p1iad2-18778-5E516348-29 2020-02-22 17:22:16.897205936 +0000 UTC m=+1371251.336801620
Received: from out-24.smtp.github.com (out-24.smtp.github.com [192.30.252.207]) by ismtpd0033p1mdw1.sendgrid.net (SG) with ESMTP id sEbYogSnRMW6UXDs3J2wgQ for <quic-issues@ietf.org>; Sat, 22 Feb 2020 17:22:16.661 +0000 (UTC)
Date: Sat, 22 Feb 2020 17:22:16 +0000 (UTC)
From: MikkelFJ <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK355DA3FQHSZIT6AFF4L2K4REVBNHHB5FPVAE@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/3157/c589978273@github.com>
In-Reply-To: <quicwg/base-drafts/pull/3157@github.com>
References: <quicwg/base-drafts/pull/3157@github.com>
Subject: Re: [quicwg/base-drafts] Backoff on CONNECTION_CLOSE (#3157)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5e5163482477a_5ea13fa11fccd9682352c7"; charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: mikkelfj
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: quic-issues@ietf.org
X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak1tnm4IZ4BAbMfSwK+o26INHlfIQfNNo9oQDZ dy7qt2VnCrOkxFCbJJo+OtSSKS5vyulQVoM8OBjzORnqAwOwqryj14X1flf+KBsAhmxrvO2Kh5jTwr H6t37fefCgjkR3Y4dHnUelP2EC/ABD/xw6YqVxaoesM/ReRiJH1smxmX4R3q7A1m5oHGiVRAaaX/nq o=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/8m4nzdT37YfWsOGk81tyV4ja-6A>
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 Feb 2020 17:54:48 -0000

Is there a risk of amplification attacks if an attacker sends bad packets during handshake that triggers a connection close, possible to a spoofed address. Sorry, not really up to speed on handshake details, just want to make sure this isn't overlooked. I think it should be OK, since it would be below a factor 3.

-- 
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/pull/3157#issuecomment-589978273