Re: [quicwg/base-drafts] describe what happens when the PTO timer expires (#2455)

Martin Thomson <notifications@github.com> Tue, 12 February 2019 23:58 UTC

Return-Path: <bounces+848413-a050-quic-issues=ietf.org@sgmail.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 50BD6126C01 for <quic-issues@ietfa.amsl.com>; Tue, 12 Feb 2019 15:58:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.597
X-Spam-Level:
X-Spam-Status: No, score=-1.597 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_NONE=-0.0001, SPF_PASS=-0.001] 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 1BVxkuAGyu7l for <quic-issues@ietfa.amsl.com>; Tue, 12 Feb 2019 15:58:55 -0800 (PST)
Received: from o11.sgmail.github.com (o11.sgmail.github.com [167.89.101.202]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C364F1228B7 for <quic-issues@ietf.org>; Tue, 12 Feb 2019 15:58:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=qZxvaOLvu8OyWd89b4Y4OctEJtY=; b=dN1lWQWlpSVlfYUn cx0gyzoDEQ/Ji1FNfgrkdClbuwiHYGRq1DNq1gUdpuVyiOuCfMkgCbX3VCCFNwvG puRQbe4Zz3VXFHmMqeQ66ybPMm0ttly11UsYhCpOhO9Xj1kROF9z9AVwQh/c2RsN WG4rf9bUThNnUcOz+FUfTPj/l/s=
Received: by filter1504p1mdw1.sendgrid.net with SMTP id filter1504p1mdw1-8440-5C635DBD-3D 2019-02-12 23:58:53.953442205 +0000 UTC m=+615300.878448555
Received: from github-lowworker-dcc078e.cp1-iad.github.net (unknown [192.30.252.44]) by ismtpd0032p1iad2.sendgrid.net (SG) with ESMTP id 7SWKLFdtQh6de41RsN-8BA for <quic-issues@ietf.org>; Tue, 12 Feb 2019 23:58:53.899 +0000 (UTC)
Received: from github.com (localhost [127.0.0.1]) by github-lowworker-dcc078e.cp1-iad.github.net (Postfix) with ESMTP id D9A9B2C0B18 for <quic-issues@ietf.org>; Tue, 12 Feb 2019 15:58:53 -0800 (PST)
Date: Tue, 12 Feb 2019 23:58:54 +0000
From: Martin Thomson <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab3983b71f5106494402a258125ea0e2e48610e6ad92cf00000001187b1fbd92a169ce1861d625@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/2455/review/202970942@github.com>
In-Reply-To: <quicwg/base-drafts/pull/2455@github.com>
References: <quicwg/base-drafts/pull/2455@github.com>
Subject: Re: [quicwg/base-drafts] describe what happens when the PTO timer expires (#2455)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c635dbdd7ee6_22013fcfcdcd45c438838"; 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
X-GitHub-Recipient-Address: quic-issues@ietf.org
X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak38EtDOOnGi+u/fRgXtMKYvY+wHjDsR8cqrfk hYtTq1NLk0cH9gLzvzwkgLPpAZGTKIvJ6Rsrvj40i+sTkJBWuvEtHzPodDxWHmF++oAojeUTHn9cnz 4rDMfLQs7eJTx4ArT2Ik9NojJO89kiAQfTAMa6JammjuY3qZuTnjQnc0IBJlxUxMpnnFgq2eEx9jRc Q=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/aQk-czi001Gqx05FvhNca-JJCO4>
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: Tue, 12 Feb 2019 23:58:56 -0000

martinthomson commented on this pull request.



> @@ -506,9 +506,10 @@ delay sending an acknowledgement.
 The PTO value MUST be set to at least kGranularity, to avoid the timer expiring
 immediately.
 
-When a PTO timer expires, the PTO period MUST be set to twice its current value.
-This exponential reduction in the sender's rate is important because the PTOs
-might be caused by loss of packets or acknowledgements due to severe congestion.
+When a PTO timer expires, the sender sends a probe packet as described in the

Or simply nothing.  A probe packet is sent if two packets are sent, and this is not normative text.

-- 
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/2455#discussion_r256198149