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

Nick Banks <> Thu, 23 May 2019 10:10 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 68D651201CC for <>; Thu, 23 May 2019 03:10:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.392
X-Spam-Status: No, score=-6.392 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_24=1.618, 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 y3AeyKdicmQz for <>; Thu, 23 May 2019 03:10:52 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id B89E7120184 for <>; Thu, 23 May 2019 03:10:52 -0700 (PDT)
Date: Thu, 23 May 2019 03:10:51 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1558606252; bh=RPH/zUhjVet6mjTVlH7ePPnu3S3HXxw3TsiNht+LkXk=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=qPowdr6o9CIiT3sqgKZvVdf+FgWYwJxmxVCGNgmtWVkciNcTkCjombb1SFYG0t/Pk 2MMs4zAisosgkzgCB6j2L1uNkCfSIa1/eQpSsZHetAQS/GZiyHmy2mRQpblh7AFPch 63CaE44Ku0KyMO4QcATZKSLM707lpyel3CMsCZxI=
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_5ce671abca642_6e2e3fe39d2cd95c13743c"; 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: Thu, 23 May 2019 10:11:05 -0000

Thinking about this, another solution would be to continue to send a *blocked frame, while in the blocked state. Even if the peer acknowledged the first blocked frame, if you're still blocked, you send it again. Personally, for my implementation, this would be the easiest thing to implement.

I don't think the spec should make any requirements in this area, but I do think it should call this problem out and possibly make a recommendation.

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