IETF Logo Mail Archive

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

Mike Bishop <notifications@github.com> Thu, 21 June 2018 21:25 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 9E64F130E21 for <quic-issues@ietfa.amsl.com>; Thu, 21 Jun 2018 14:25:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.009
X-Spam-Level:
X-Spam-Status: No, score=-8.009 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, 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 8fj2GgWeMVPQ for <quic-issues@ietfa.amsl.com>; Thu, 21 Jun 2018 14:25:41 -0700 (PDT)
Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A3BF5131125 for <quic-issues@ietf.org>; Thu, 21 Jun 2018 14:25:41 -0700 (PDT)
Date: Thu, 21 Jun 2018 14:25:40 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529616340; bh=ROyKcoNwnPWtFvgUqE3WiRTQoA2veRhZ7b7Ik24F9ZY=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=zNnOFCU93zbEjS1vws0XkKBiyT4/ga8bwRn40PMHGNxSfYP6Ez6dDjiwugdjuTLli o4LGkxsOJSGztyHSAlbV9aAT0wLh8FkJHWRmV+m+etwN9cZlfxJIRlDhY8YSbbJcKb pGFCy1KYBOWE8EpdJe5rQOGLkDAOVHVwz0jihwPo=
From: Mike Bishop <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab116af9e128a8ad17f6dee0bc2adb4d19f07daa5092cf000000011743d9d492a169ce13c7a591@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/399248516@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_5b2c17d49385f_1c0c2ade4ce70f5415665a"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: MikeBishop
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/R3ERDJ4QyT-uJgyg8u5qtJXrIok>
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: Thu, 21 Jun 2018 21:25:52 -0000

Honestly, I'm inclined toward both/and.  @mikkelfj, nothing says it needs to be dramatically smaller.  SR currently has to be at least 37 octets long; with a requirement that it also be smaller than the triggering packet, it's guaranteed to die eventually.

An implementation can choose the size of SR it sends back based on how concerned it is; if it usually selects a size that's 60-80% the size of the packet that triggered it, the ping-pong will die out after ~6 round trips.  Select smaller, and it dies even more quickly.  Couple that with permission (not a requirement) for an implementation to keep a little state to short-circuit these and I think it's sufficient.

-- 
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-399248516

v2.23.0 | Report a Bug | By Email