[quicwg/base-drafts] 3x amplification limit for CONNECTION_CLOSE (#3864)
Martin Thomson <notifications@github.com> Wed, 08 July 2020 05:54 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 506933A0941 for <quic-issues@ietfa.amsl.com>; Tue, 7 Jul 2020 22:54:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.099
X-Spam-Level:
X-Spam-Status: No, score=-3.099 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_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 vJtT1sdwhy32 for <quic-issues@ietfa.amsl.com>; Tue, 7 Jul 2020 22:54:12 -0700 (PDT)
Received: from out-23.smtp.github.com (out-23.smtp.github.com [192.30.252.206]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DE6E43A093A for <quic-issues@ietf.org>; Tue, 7 Jul 2020 22:54:11 -0700 (PDT)
Received: from github-lowworker-5fb2734.va3-iad.github.net (github-lowworker-5fb2734.va3-iad.github.net [10.48.19.27]) by smtp.github.com (Postfix) with ESMTP id 19AD6661F3C for <quic-issues@ietf.org>; Tue, 7 Jul 2020 22:54:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1594187651; bh=8XzO0CP0a7wMnQDHcErpImBfqATwX4K72PCr5pOMJWY=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=ZvIzkLpqEEzX+l8K67BQNZKowFQ+vqm8rn77iKqAcD4DJyodom2wftFJkhQBXGhNg 5AjGEnMSrouEVOmZIA4Oj3WKfojc05zOhHc7EkdFtSygpiGN/kCFgpNTZl0vL9qSbs KFhiui1WC3wxf7O/9Ri/aNT7E5pnLoltwXSHfm1Y=
Date: Tue, 07 Jul 2020 22:54:11 -0700
From: Martin Thomson <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK6U6NJWLVEFUQQ7DVV5CFAIHEVBNHHCN26ZZI@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/3864@github.com>
Subject: [quicwg/base-drafts] 3x amplification limit for CONNECTION_CLOSE (#3864)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5f055f836ea9_52943f8e78ecd95c2806b9"; 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/mgg4a6AXHIMxJXGmnYP2pzahcao>
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: Wed, 08 Jul 2020 05:54:13 -0000
We weren't very concrete in saying how endpoints generate packets with CONNECTION_CLOSE, particularly those that throw away keys. We have a rather vague requirement. In short, follow the same rules we established for the handshake. Wording this as an aggregate number allows for stochastic reactions and larger CONNECTION_CLOSE frames. This way, if you get a 25-byte packet and respond with a 200-byte packet, you can do that, but you have to respond to 3 in 8 or fewer in that way. Note that this limit only applies if the endpoint throws away decryption keys. Endpoints with keys aren't blind amplifiers. Closes #3845. You can view, comment on, or merge this pull request online at: https://github.com/quicwg/base-drafts/pull/3864 -- Commit Summary -- * 3x amplification limit for CONNECTION_CLOSE -- File Changes -- M draft-ietf-quic-transport.md (9) -- Patch Links -- https://github.com/quicwg/base-drafts/pull/3864.patch https://github.com/quicwg/base-drafts/pull/3864.diff -- 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/3864
- [quicwg/base-drafts] 3x amplification limit for C… Martin Thomson
- Re: [quicwg/base-drafts] 3x amplification limit f… Mike Bishop
- Re: [quicwg/base-drafts] 3x amplification limit f… ianswett
- Re: [quicwg/base-drafts] 3x amplification limit f… Jana Iyengar
- Re: [quicwg/base-drafts] 3x amplification limit f… Martin Thomson