IETF Logo Mail Archive

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

Martin Thomson <notifications@github.com> Fri, 20 July 2018 20:49 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 A5EF9130DFD for <quic-issues@ietfa.amsl.com>; Fri, 20 Jul 2018 13:49:24 -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 a_j_s-kDYTPl for <quic-issues@ietfa.amsl.com>; Fri, 20 Jul 2018 13:49:22 -0700 (PDT)
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 8B19B130DEE for <quic-issues@ietf.org>; Fri, 20 Jul 2018 13:49:22 -0700 (PDT)
Date: Fri, 20 Jul 2018 13:49:21 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1532119761; bh=4pFcg38ut1wyaYO+uiFYmmD6mzZwK+NQIm1K8SvMTwI=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=brEZtf29bZvpuO/sPUNlucdt/SreFd5v0l+41b8uj2jb43x7U38Eb2N2kxMKRKgxf sHF5WuFqKd6KoHK5xH6TG8PyDWKCOSYN8gcIcLWdHTZ6QiDapbagKuEijCQ7zSKYJ0 6Vy+Rrb09nAdIWJAdOlqL8010x4IDc3KU6EqOicI=
From: Martin Thomson <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab808b2196545a3779c81cde64fcb8d070bff3bc5f92cf00000001176a0cd192a169ce13c7a591@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/406722859@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_5b524ad191701_62f73f8d39ed45bc11473d"; 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/oQTVqdbp5czYHGPVxZexqOUeiDA>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.27
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, 20 Jul 2018 20:49:25 -0000

An ACK- only packets seem like they are less critical to reset. The sender of an ACK- only packet is unlikely to send again shortly. That cuts two ways though. Either it would be a huge optimization to get the reset, because it would otherwise be a fair while until the next packet would be sent; or it would be wasteful, because the endpoint isn't planning to use the connection any time soon.

To me that suggests that ACK-only packets aren't worth paying special attention to in the design, even if they are super common. 

Either way, guessing the size of the peer's connection ID doesn't seem right to me. 

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

v2.46.0 | Report a Bug | By Email | System Status