IETF Logo Mail Archive

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

MikkelFJ <notifications@github.com> Fri, 20 July 2018 19:09 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 913A8130E32 for <quic-issues@ietfa.amsl.com>; Fri, 20 Jul 2018 12:09:05 -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 d4Zy8GutPus1 for <quic-issues@ietfa.amsl.com>; Fri, 20 Jul 2018 12:09:03 -0700 (PDT)
Received: from out-6.smtp.github.com (out-6.smtp.github.com [192.30.252.197]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 10B11130DCE for <quic-issues@ietf.org>; Fri, 20 Jul 2018 12:09:03 -0700 (PDT)
Date: Fri, 20 Jul 2018 12:09:02 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1532113742; bh=QZ2q3vZAGCaMhuGhhoyOPOFdKrYLJogoLX0DPopjLCk=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=BVh67vtoJKKTNfWFJ3C/SK0YFD8RsASLqUGO/8EGn6CZE+7Fun3zQoK1a0RylLLuZ CfXycSKTpn4rsMcs9gg2mCR9YFTZrmyuXQyKYtl1O3eI+Dwqm5nHnR0e0GFQaUEC5F qFA+G+kfgpC5UobVubaylvy6Clj6ucVzPwJdcCsg=
From: MikkelFJ <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abbaa4ea5d586ba0ef3e6f83a86f565b9a137c76a992cf000000011769f54e92a169ce13c7a591@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/406699660@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_5b52334e2a935_3e93fbfdbed45c419074f"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: mikkelfj
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/UXk47dP1I5uwYxOx_sKvv6WVBZ4>
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 19:09:06 -0000

I was thinking through the ACK scenario earlier - there are two points:

1. ACKS eventually die because they are generated in response to traffic that does not arrive (unless routing is seriously messed up)
2. There can a backlog ACK's before they die out, and perhaps RESET need to act on these timely.

But there are also ping frames and small message updates like player status in games or IoT temperature measurements.


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

v2.23.0 | Report a Bug | By Email