Re: [quicwg/base-drafts] Idle timeout indicates you will timeout (#3099)

Martin Thomson <> Wed, 16 October 2019 20:53 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id B8FA812012A for <>; Wed, 16 Oct 2019 13:53:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -8
X-Spam-Status: No, score=-8 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_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 KP9OSNjq1E_r for <>; Wed, 16 Oct 2019 13:53:32 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 824A0120122 for <>; Wed, 16 Oct 2019 13:53:32 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id C0081960615 for <>; Wed, 16 Oct 2019 13:53:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1571259211; bh=p1kX6cUsPZ1z0a7OYWUB8wR0E5tsWrFysNY4bhajvqg=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=kYWsTFJkZ448BcfxQRssaHo4wFZVkqNfF/nkCW4+jUGD5YDXa4ZZrrq8VRYs0jfW+ QZdgAkBUCx5fkoYxzdDTrPsu7o/sEg+zx4WW/X94OL2XVOEfHLSu80TK0593z988kS cl4Qu905RQj7VWuEG2/CSKeG1+ZTIIbHlmPusd+w=
Date: Wed, 16 Oct 2019 13:53:31 -0700
From: Martin Thomson <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/pull/3099/review/>
In-Reply-To: <quicwg/base-drafts/pull/>
References: <quicwg/base-drafts/pull/>
Subject: Re: [quicwg/base-drafts] Idle timeout indicates you will timeout (#3099)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5da7834bb10fe_25cc3ff848ecd96810323d"; 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, 16 Oct 2019 20:53:35 -0000

martinthomson requested changes on this pull request.

This doesn't read particularly well as written.  I've suggested something, but I'm not entirely sure that it works.

> @@ -2357,15 +2357,22 @@ containing frames other than ACK or PADDING (an ack-eliciting packet; see
 since last receiving a packet.  Restarting when sending packets ensures that
 connections do not prematurely time out when initiating new activity.
-The value for an idle timeout can be asymmetric.  The value advertised by an
-endpoint is only used to determine whether the connection is live at that
-endpoint.  An endpoint that sends packets near the end of the idle timeout
-period of a peer risks having those packets discarded if its peer enters the
-draining state before the packets arrive.  If a peer could timeout within a
-Probe Timeout (PTO; see Section 6.3 of {{QUIC-RECOVERY}}), it is advisable to
-test for liveness before sending any data that cannot be retried safely.  Note
-that it is likely that only applications or application protocols will
-know what information can be retried.
+Each endpoint can advertise a different idle timeout value. An idle timeout
+indicates the connection will be abandoned when the timer ends or soon
+afterwards.  If a peer advertises a smaller idle timeout value than the

Each endpoint advertises a different idle timeout, but the effective value is determined by taking the minimum of the two advertised values.  By announcing an idle timeout, endpoints commit to initiating an immediate close ({{immediate-close}}) if it abandons a connection prior to the effective value.

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