Re: [quicwg/base-drafts] Prevent Idle Timeout while Blocked (#3266)

Martin Thomson <> Mon, 25 November 2019 06:35 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 9818E120801 for <>; Sun, 24 Nov 2019 22:35:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.596
X-Spam-Status: No, score=-6.596 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_28=1.404, 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 fgkC56jE69ln for <>; Sun, 24 Nov 2019 22:35:03 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 697BE1207FE for <>; Sun, 24 Nov 2019 22:35:03 -0800 (PST)
Date: Sun, 24 Nov 2019 22:35:02 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1574663702; bh=meCk/K0RmjIIqsyD/ybWj2LEXV+hiiCcJxC1oqbGcZc=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=EbhEGIZ8lneZHxLZOGpKLRrURmDWzY/71rglSZ6tbLtbUq8QKs6ameWKP4rm0O3q6 Imm84yZ+NKUAs0A2OuE81W05kXbi60Xi0Gjz+XkkDdls545PUAKHPmZA8pZHU4IuiA TuI7ZGu+TmNu/DzwEH58+uXPzgvn8MVRQD5aCqcI=
From: Martin Thomson <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/pull/3266/review/>
In-Reply-To: <quicwg/base-drafts/pull/>
References: <quicwg/base-drafts/pull/>
Subject: Re: [quicwg/base-drafts] Prevent Idle Timeout while Blocked (#3266)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5ddb7616b924e_2f2d3fca342cd95c8656f"; 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: Mon, 25 Nov 2019 06:35:06 -0000

martinthomson approved this pull request.

> @@ -2353,7 +2351,8 @@ processed successfully.  The timer is also restarted when sending an
 ack-eliciting packet (see {{QUIC-RECOVERY}}), but only if no other ack-eliciting
 packets have been sent since last receiving a packet.  Restarting when sending
 packets ensures that connections do not prematurely time out when initiating new
+activity.  An endpoint should be careful to avoid an idle timeout if it is idle

You use "should", which is a little sketchy.

> An endpoint might need to send packets to avoid an idle timeout if it is unable to send application data due to being blocked on flow control limits (see {{data-flow-control}}).

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