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 998023A09BB
 for <quic-issues@ietfa.amsl.com>; Fri, 27 Mar 2020 07:45:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.008
X-Spam-Level: 
X-Spam-Status: No, score=-2.008 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, DKIM_VALID_EF=-0.1,
 HTML_IMAGE_ONLY_16=1.092, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1,
 SPF_HELO_NONE=0.001, 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 4f7e1d658nBb for <quic-issues@ietfa.amsl.com>;
 Fri, 27 Mar 2020 07:45:31 -0700 (PDT)
Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by ietfa.amsl.com (Postfix) with ESMTPS id 3246E3A0041
 for <quic-issues@ietf.org>; Fri, 27 Mar 2020 07:45:31 -0700 (PDT)
Received: from github-lowworker-3a0df0f.ac4-iad.github.net
 (github-lowworker-3a0df0f.ac4-iad.github.net [10.52.25.92])
 by smtp.github.com (Postfix) with ESMTP id 06E0E9604A8
 for <quic-issues@ietf.org>; Fri, 27 Mar 2020 07:45:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com;
 s=pf2014; t=1585320330;
 bh=GV8Cl6bfuD1Nvozc3BdV0xih4Z1yZM0M6Wl6b10nEnM=;
 h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID:
 List-Archive:List-Post:List-Unsubscribe:From;
 b=DJiRRthw8JaLsZuU5ua+E+p/6cIfNIX4qAdF4mFCmTMQ8dbf7a6yb5INR5SnUAO1F
 2/A6Lih6TIKbOGhzsT0wglZJb20po4gZHBDQZ5XlVt7CE1OwhmmvUtnNz5r8sSYwqt
 j6cFWLmi+PDNyjl96uAOfSyHuAZck0J/g3+DhcoQ=
Date: Fri, 27 Mar 2020 07:45:29 -0700
From: ianswett <notifications@github.com>
Reply-To: quicwg/base-drafts
 <reply+AFTOJK7BKKW6QNXQPE3Q4654RHZITEVBNHHCGDM7NY@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/3546/605039296@github.com>
In-Reply-To: <quicwg/base-drafts/issues/3546@github.com>
References: <quicwg/base-drafts/issues/3546@github.com>
Subject: Re: [quicwg/base-drafts] PTO probes are sent too frequently (#3546)
Mime-Version: 1.0
Content-Type: multipart/alternative;
 boundary="--==_mimepart_5e7e1189ec36b_4fa13fbffa4cd96c109051";
 charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: ianswett
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/uosiyYggq8eVTYr0FpwNAfqo2uQ>
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: Fri, 27 Mar 2020 14:45:36 -0000


----==_mimepart_5e7e1189ec36b_4fa13fbffa4cd96c109051
Content-Type: text/plain;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

We only reset pto_count upon receiving an Initial ACK, not any Initial packet, but I think your suggestion could work well.  It amounts to continuing with exponential backoff until the client has Handshake keys.

It's fairly simple to implement, and I wouldn't expect it to cause a noticeable regression, so unless someone comes up with something better, let's do it.

-- 
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/issues/3546#issuecomment-605039296
----==_mimepart_5e7e1189ec36b_4fa13fbffa4cd96c109051
Content-Type: text/html;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

<p></p>
<p>We only reset pto_count upon receiving an Initial ACK, not any Initial packet, but I think your suggestion could work well.  It amounts to continuing with exponential backoff until the client has Handshake keys.</p>
<p>It's fairly simple to implement, and I wouldn't expect it to cause a noticeable regression, so unless someone comes up with something better, let's do it.</p>

<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">&mdash;<br />You are receiving this because you are subscribed to this thread.<br />Reply to this email directly, <a href="https://github.com/quicwg/base-drafts/issues/3546#issuecomment-605039296">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AFTOJKZTSF5T6C6QF6KMI5DRJS3YTANCNFSM4LT4F2OA">unsubscribe</a>.<img src="https://github.com/notifications/beacon/AFTOJKYK5H7HSJMYULFDRPDRJS3YTA5CNFSM4LT4F2OKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEQICVQA.gif" height="1" width="1" alt="" /></p>
<script type="application/ld+json">[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/quicwg/base-drafts/issues/3546#issuecomment-605039296",
"url": "https://github.com/quicwg/base-drafts/issues/3546#issuecomment-605039296",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>
----==_mimepart_5e7e1189ec36b_4fa13fbffa4cd96c109051--

