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

Martin Thomson <> Wed, 22 May 2019 14:41 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id B9F5212006A for <>; Wed, 22 May 2019 07:41:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.464
X-Spam-Status: No, score=-6.464 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] 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 knUWcspHKLsH for <>; Wed, 22 May 2019 07:41:29 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 08D2312004F for <>; Wed, 22 May 2019 07:41:29 -0700 (PDT)
Date: Wed, 22 May 2019 07:41:27 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1558536087; bh=b6IZ8zZEkUII8TYW9G0ifUQ9VkbCa41B9DkjDW9/jGw=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=0YsTep2e7MI+kqC0aTEodAua3aYnteuLoxj/XxaMsfvaMhR7eNbU1uMpjPw72uYJH CqK1DXyYvMAQqS0IydUV8EkmaO1qOC2BN3Y9jDdFNwofzyuTrag1KfycZ9KooKKIz0 dj0BmAu/5NNGzQVA9Y+NIpVIfJrUzEde41LXYlhQ=
From: Martin Thomson <>
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_5ce55f97d760f_79d73fb00b6cd964208281"; 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
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: Wed, 22 May 2019 14:41:31 -0000

It seems reasonable to use a keep-alive.  If you have something you want to use the connection for and you aren't able to maintain activity on the connection, then either poke it or - more likely - give up.  I don't think that we need a design change for this, but if you want to write some text, I wouldn't be opposed to taking a look.

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