Re: [quicwg/base-drafts] Idle Timer Can Fire Even with Outstanding Data to Send (#2744)

Nick Banks <> Tue, 22 October 2019 23:01 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id E94D212012E for <>; Tue, 22 Oct 2019 16:01:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.454
X-Spam-Status: No, score=-6.454 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_20=1.546, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id WIVdi_QEyKME for <>; Tue, 22 Oct 2019 16:01:31 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 32C68120111 for <>; Tue, 22 Oct 2019 16:01:31 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 79C9CA0A6F for <>; Tue, 22 Oct 2019 16:01:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1571785290; bh=l/jRubBvx0MH8J5QjCArMrGK3bThb3XCsUi0PwysZmY=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=tx2I1MZwOK5FLvSpIIqqE1zIHJZF23kOJ+UL9yEGkNi1Tajf4HXxhnbrBt4woVBgE j56eBouy4iaLrBHpy9M2g+1mc31TTjAh7HKf2KnoU943rKLjmiObcGPfgPaFvlN+C+ ybWumUlu+9E/hgj32YwStprd+qpwgKrue3V1ZzvI=
Date: Tue, 22 Oct 2019 16:01:30 -0700
From: Nick Banks <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/issues/2744/>
In-Reply-To: <quicwg/base-drafts/issues/>
References: <quicwg/base-drafts/issues/>
Subject: Re: [quicwg/base-drafts] Idle Timer Can Fire Even with Outstanding Data to Send (#2744)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5daf8a4a6ad8d_64503fab2eacd96060643"; charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: nibanks
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
Archived-At: <>
X-Mailman-Version: 2.1.29
List-Id: Notification list for GitHub issues related to the QUIC WG <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 22 Oct 2019 23:01:33 -0000

I could definitely write a PR. We implement exactly this. I would argue though that it's not exponential. It's immediate and will go forever. The app has data to send. The connection is not idle, and should never idle out in this scenario. It's the app's responsibility to time out, if their protocol dictates as such (which it might not, if they expect to be blocked while a long running operation is processed).

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub: