Re: [quicwg/base-drafts] Anti-amplification limits should count junk too (#3340)

ianswett <notifications@github.com> Tue, 04 February 2020 11:34 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 D6E97120145 for <quic-issues@ietfa.amsl.com>; Tue, 4 Feb 2020 03:34:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.454
X-Spam-Level:
X-Spam-Status: No, score=-6.454 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, HTML_IMAGE_ONLY_20=1.546, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=unavailable 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 RjtiDWKh7chJ for <quic-issues@ietfa.amsl.com>; Tue, 4 Feb 2020 03:34:23 -0800 (PST)
Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 65905120144 for <quic-issues@ietf.org>; Tue, 4 Feb 2020 03:34:23 -0800 (PST)
Received: from github-lowworker-b19c547.va3-iad.github.net (github-lowworker-b19c547.va3-iad.github.net [10.48.17.66]) by smtp.github.com (Postfix) with ESMTP id 4E9ED2C0BD4 for <quic-issues@ietf.org>; Tue, 4 Feb 2020 03:34:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1580816062; bh=1moJL4KiS+SGEyqHilryLhXTEhZcfe0vepY1c+2uhoA=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=QshDy4qB9Pgv/ON/UQFra9NkpPLpnKnciROfqhq9C6rs3+KJXhBKo3l6MG3QrePyZ bepNneKHiw4iRamV4cb8bB460MTw7Fg2S/SXcIDUEoBr2iPO/NzcGs3H/M6UwfK+P8 FKs0UGz3sbh92Anu9ixh/Y0PkLfLpcAZtfKuGPqs=
Date: Tue, 04 Feb 2020 03:34:22 -0800
From: ianswett <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK6DP3PEWTMKINGBLFN4I2ET5EVBNHHCBQHUUM@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/3340/581866631@github.com>
In-Reply-To: <quicwg/base-drafts/issues/3340@github.com>
References: <quicwg/base-drafts/issues/3340@github.com>
Subject: Re: [quicwg/base-drafts] Anti-amplification limits should count junk too (#3340)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5e3956be3e19b_7f613fee4d4cd9683132f"; charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: ianswett
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/rRiIYkUcp3gbvbyK4OOEpVRb_cc>
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: Tue, 04 Feb 2020 11:34:33 -0000

All client Initial packets are in full-sized datagrams, based on my understanding, so a PING is fine in practice.

And the PTO is never armed for 0-RTT, so the probe packets would not be 0-RTT.  That being said, I'm a bit concerned those are SHOULDs and not MUSTs.


-- 
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/3340#issuecomment-581866631