Re: [quicwg/base-drafts] Fix handling of Retry in recovery (#3148)

Martin Thomson <> Wed, 30 October 2019 03:57 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 710CC120821 for <>; Tue, 29 Oct 2019 20:57:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -7.999
X-Spam-Status: No, score=-7.999 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_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, 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 EbWRsBHIwGic for <>; Tue, 29 Oct 2019 20:57:39 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id E6685120052 for <>; Tue, 29 Oct 2019 20:57:38 -0700 (PDT)
Date: Tue, 29 Oct 2019 20:57:38 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1572407858; bh=O2qA07Ref3eQEkFn9RH6/GvUFXnIENrQsgBymcKejg4=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=aht9uKWG0GZFEc6xBarEPtWCuJ1jOYpUVuDKmlPjMZJq+t1mwVVMDIBuX/9CSVy5i 3IprdIRhbNk1R4lLOPqHADBnDXjgG5iTRpWwTWnr2QchjSijvlGApkC+P/58lLi8VA Z4+I8fGiTFmv0hQYWn9ldD5bBzYpR738YUr+3nGc=
From: Martin Thomson <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/pull/3148/review/>
In-Reply-To: <quicwg/base-drafts/pull/>
References: <quicwg/base-drafts/pull/>
Subject: Re: [quicwg/base-drafts] Fix handling of Retry in recovery (#3148)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5db90a323e8e8_31f03fb74f8cd96c100262"; 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: Wed, 30 Oct 2019 03:57:40 -0000

martinthomson commented on this pull request.

> +## Handling Retry Packets
+A Retry packet causes a client to send another Initial packet, effectively
+restarting the connection process.  A Retry packet indicates that the Initial
+was received, but not processed.  A Retry packet cannot be treated as an
+Clients that receive a Retry packet reset congestion control and loss recovery
+state, including resetting any pending timers.  Other connection state, in
+particular cryptographic handshake messages, is retained; see Section 17.2.5 of
+The client MAY compute an RTT estimate to the server as the time period from
+when the first Initial was sent to when a Retry or a Version Negotiation packet
+is received.  The client MAY use this value in place of its default for the
+initial RTT estimate.

I tend to agree.  I note that the goal would ordinarily to pick a server that is closer to the client.  In those cases, this will just produce a different overestimation of RTT.  Hopefully it is still less than 1 second.

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