Re: [quicwg/base-drafts] Stateless Reset Eternal Ping Pong (#1443)

Martin Thomson <notifications@github.com> Fri, 29 June 2018 07:36 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 EBCAE130E09 for <quic-issues@ietfa.amsl.com>; Fri, 29 Jun 2018 00:36:22 -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 CuCShtO-KwMR for <quic-issues@ietfa.amsl.com>; Fri, 29 Jun 2018 00:36:21 -0700 (PDT)
Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0CCFF127AC2 for <quic-issues@ietf.org>; Fri, 29 Jun 2018 00:36:21 -0700 (PDT)
Date: Fri, 29 Jun 2018 00:36:20 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530257780; bh=erBgTFWPEQoTPUL2F91gBjGPppk9r1qBd+ObDaIQt7U=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=pZjKSvw/5W6+hmNU22GQQeLBWtZDfHOrjwq0Wgc0gqrFUOpXBW4nv235t+sLNjrkA cdP07Zo7Q/FeU3in8QZoq0YKqAvu5j5x8n6hTW+vN0CrK38VDinjaDbhpBdWoJFvy8 +Txgtj3SR4ziuyYHXx3kv1S0rMjzdlGBsVWE4nNs=
From: Martin Thomson <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abfcc73e18202dffb1ee85105da6697d06fb13ff2292cf00000001174da37492a169ce13c7a591@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/1443/401273965@github.com>
In-Reply-To: <quicwg/base-drafts/issues/1443@github.com>
References: <quicwg/base-drafts/issues/1443@github.com>
Subject: Re: [quicwg/base-drafts] Stateless Reset Eternal Ping Pong (#1443)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5b35e17427d6c_48872b1fe4d8ef58698a2"; 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/0iB8foaDEd1TKAP0Kh_ODj50tPI>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.26
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: Fri, 29 Jun 2018 07:36:23 -0000

I think that I'm with @MikeBishop here.  37 octets is quite a bit bigger than the smallest packet that might be sent, and if there is at least a chance of getting a reset back, then connections will die more quickly, though it might only be in the aggregate.  Advising reduced probability when the reset is not smaller than the packet it responds to seems right.

If you consider that we want to have resets of varying size, that's probably good, because you don't end up clamping resets to the size of the incoming packet.  I'm sure that you can devise a simple scheme that randomizes probability as a function of the increase in packet length over the incoming packet.

-- 
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/1443#issuecomment-401273965