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

Martin Thomson <> Tue, 19 May 2020 22:55 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id D62893A11D1 for <>; Tue, 19 May 2020 15:55:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.555
X-Spam-Status: No, score=-1.555 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_20=1.546, 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 j6T55xPNXmXe for <>; Tue, 19 May 2020 15:55:01 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 0B88B3A11D0 for <>; Tue, 19 May 2020 15:55:00 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id C1138A11C7 for <>; Tue, 19 May 2020 15:54:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1589928899; bh=eFxqf1EFMXq+zshg9TmQvSR171AKz5eGLg7/szfwv+U=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=ohqc21LBW9+TTcN1mLdlgLmi/mFtuScoWx1FF+cR7VPdwZuQ8rSopWCNQlR04MBvC brcR4M1P+MYFmfsL7hhK9IGsdJvbbGzgkTvS41nSTXa7DQEVkfj80bEs96iawWvLPW VXz7qQGnPA7nmC4DDH8qhXJ46msIQ9KTi9M7n12o=
Date: Tue, 19 May 2020 15:54:59 -0700
From: Martin Thomson <>
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_5ec463c3b2374_70dc3fee084cd96c80533"; 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: Tue, 19 May 2020 22:55:04 -0000

@martinthomson commented on this pull request.

> +PTO period being set to twice its current value. The PTO backoff is reset upon
+receiving an acknowledgement, except when a client receives an acknowledgment
+from a server prior to the server validating the client address. A client
+keeps increasing the PTO backoff until the server's address validation
+completes to ensure the client's PTO timer is not set too aggressively
+when the server is slow in responding with handshake data.

But that's fine.  This doesn't need to more aggressive than confirmation.

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