Re: [quicwg/base-drafts] Keep idle timeout asymmetric (#2745)

Mike Bishop <notifications@github.com> Wed, 22 May 2019 11:07 UTC

Return-Path: <noreply@github.com>
X-Original-To: quic-issues@ietfa.amsl.com
Delivered-To: quic-issues@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5B53B120128 for <quic-issues@ietfa.amsl.com>; Wed, 22 May 2019 04:07:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.009
X-Spam-Level:
X-Spam-Status: No, score=-3.009 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_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4xukOsw67txQ for <quic-issues@ietfa.amsl.com>; Wed, 22 May 2019 04:07:00 -0700 (PDT)
Received: from out-20.smtp.github.com (out-20.smtp.github.com [192.30.252.203]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F1AB212003F for <quic-issues@ietf.org>; Wed, 22 May 2019 04:06:59 -0700 (PDT)
Date: Wed, 22 May 2019 04:06:59 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1558523219; bh=w9vKFzFKO8OeXr7eRMbI4qjJ/MpS0ZkmaeNH8ukzEAI=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=krjKgIgp7DebVdeb5BK/PhVcQxd5aPsg339sIk247NjULkiFY/S3sMBwb4IdcOp+U gJe2tbAYJRETUYQeuZr34d2MKc2lAZGe8i+iw3oN/hiWkznIkrVVxnHJa/rqmxopGx 8ggbQ2BzuvE/Utbjza1qWrrwMXJjE7H2H2QJVpOQ=
From: Mike Bishop <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK4AEJ7LQFZZTKPNPIF26JP5HEVBNHHBVJNZHA@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/2745/review/240559180@github.com>
In-Reply-To: <quicwg/base-drafts/pull/2745@github.com>
References: <quicwg/base-drafts/pull/2745@github.com>
Subject: Re: [quicwg/base-drafts] Keep idle timeout asymmetric (#2745)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5ce52d5318219_5c283fcaef6cd960558848"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: MikeBishop
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: quic-issues@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/Rr_te2W15r3RJk3OWjF6E-D4gTs>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Notification list for GitHub issues related to the QUIC WG <quic-issues.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic-issues/>
List-Post: <mailto:quic-issues@ietf.org>
List-Help: <mailto:quic-issues-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 May 2019 11:07:01 -0000

MikeBishop commented on this pull request.



> -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 an
-Probe Timeout (PTO; see Section 6.2.2 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 point can advertise a different idle timeout value.  An idle timeout does
+not guarantee that the connection will be abandoned when the timer ends.  The
+value advertised by an endpoint is only used to determine whether the connection
+is live at that endpoint.  By announcing an idle timeout, an endpoint commits to
+sending a CONNECTION_CLOSE if it abandons a connection within that period.
+
+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 an Probe Timeout

```suggestion
before the packets arrive.  If a peer could time out within an Probe Timeout
```

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/quicwg/base-drafts/pull/2745#pullrequestreview-240559180