Re: [quicwg/base-drafts] Clarify when the PTO may need to be recomputed and reset (#3665)

ianswett <> Tue, 19 May 2020 21:11 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 2D95F3A0AB1 for <>; Tue, 19 May 2020 14:11:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.483
X-Spam-Status: No, score=-1.483 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_24=1.618, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_MSPIKE_H2=-0.001, 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 ORgoNQgnQQo8 for <>; Tue, 19 May 2020 14:11:29 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 558D73A0C35 for <>; Tue, 19 May 2020 14:11:29 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id AE21E6E1137 for <>; Tue, 19 May 2020 14:11:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1589922688; bh=2fH7064ZEy1KuKwHyDLCcAkLueaKHo5NY7XzTL+q0oI=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=1yTE3K3v2ttdoAipNzqxoZSWVioSvGQqVXfE8uGpoLjSBrl/IKjIc+nme7pNPoBTL Tmhkg0VkpdjIM0RsDG0BNGmbrlDyqEi6oUOg1YFWDyITO8p+CdK1NdFVykj40bhsEz kibA0L/YS5uFK+Qx2bLVkxBENc57Rv9M1JW2f6N4=
Date: Tue, 19 May 2020 14:11:28 -0700
From: ianswett <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/pull/3665/review/>
In-Reply-To: <quicwg/base-drafts/pull/>
References: <quicwg/base-drafts/pull/>
Subject: Re: [quicwg/base-drafts] Clarify when the PTO may need to be recomputed and reset (#3665)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5ec44b809e203_562a3fded36cd968236623"; 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
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: Tue, 19 May 2020 21:11:31 -0000

@ianswett commented on this pull request.

 When a PTO timer expires, the PTO backoff MUST be increased, resulting in the
-PTO period being set to twice its current value.  The PTO period is set based
-on the latest RTT information after receiving an acknowledgement. The PTO
-backoff is reset upon receiving an acknowledgement unless it's a client unsure
-if the the server has validated the client's address. Not resetting the backoff
-during peer address validation ensures the client's anti-deadlock timer is not
-set too aggressively when the server is slow in responding with handshake data.
+PTO period being set to twice its current value. The PTO backoff is reset upon
+receiving an acknowledgement unless it's a client unsure if the server has

SG, I tried to rework this with your suggestion.

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