Re: [quicwg/base-drafts] What resets idle timeout? (#2149)

Martin Thomson <notifications@github.com> Thu, 13 December 2018 23:51 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 19347130EC8 for <quic-issues@ietfa.amsl.com>; Thu, 13 Dec 2018 15:51:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.056
X-Spam-Level:
X-Spam-Status: No, score=-8.056 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-1.46, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_28=1.404, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-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 f8NOz7VGuWTn for <quic-issues@ietfa.amsl.com>; Thu, 13 Dec 2018 15:51:32 -0800 (PST)
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 05286130EC2 for <quic-issues@ietf.org>; Thu, 13 Dec 2018 15:51:32 -0800 (PST)
Date: Thu, 13 Dec 2018 15:51:30 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1544745090; bh=PqI7XpqUgiESYGsvXCOnaNezvwA1MdPdzxXDMIldvKY=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=kR9MF44DtI6lPWJClPfmHa07qPHdtkF77XED7xGjlS7rN1BT8jmKeX20QmYg+LeJ2 rvLecNWZRXJMu6Lj8O2pry9+/aBF/gaAwl8/GoGlbeRMuFBZ9A1lb0X/2Z13ZVCln8 0oxyDcJiSGHZClcSDh6QT23xlacC5pHATZTjWCXU=
From: Martin Thomson <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab7d2d14e6542d39731734867bb503ef5fa603f49792cf00000001182ab28292a169ce174b8a33@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2149/447163343@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2149@github.com>
References: <quicwg/base-drafts/issues/2149@github.com>
Subject: Re: [quicwg/base-drafts] What resets idle timeout? (#2149)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c12f082c27b3_21b23ff4942d45c4181559"; 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/aDZTNc4dNNU4s2jbWg4r8kqy_NA>
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: Thu, 13 Dec 2018 23:51:34 -0000

Yeah, this is opaque.

I think that the logic is something like:

* when receiving a packet, restart the idle timer
* when sending an ACK-eliciting packet. if you haven't sent other ACK-eliciting packets since the idle timer was started, restart the idle timer

That is, if you send 10 packets, only the first of those restarts the timer.

This clearly needs to be reworded.

-- 
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/2149#issuecomment-447163343