Re: [quicwg/base-drafts] Recovery would be simpler if the Handshake timer was unified with the PTO timer (#2650)

Jana Iyengar <> Thu, 25 April 2019 06:20 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id B4A861200FE for <>; Wed, 24 Apr 2019 23:20:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -8
X-Spam-Status: No, score=-8 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_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 MLVAq9APWEcZ for <>; Wed, 24 Apr 2019 23:20: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 41434120075 for <>; Wed, 24 Apr 2019 23:20:39 -0700 (PDT)
Date: Wed, 24 Apr 2019 23:20:38 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1556173238; bh=6fdTLXMvrN9xHezYQUD/SEPk3Qk4Gly2hJ9pBEuhNCE=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=TJ6+4k2Afnx7M+GZZ5KNJCcJKCl6DoQ7veQMdv7vee8SK8vZcKWiybISrsF4H43XP vrofBfpdAmfifEfhShslL0n+fYnQBwEYqjWtWBSnEuHB5fSKg4PlJaeNS5RbFVuGOZ 7hCUsOfzIV2r6/zmKQko7nEz9/x6NUqna36Nc0bA=
From: Jana Iyengar <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/issues/2650/>
In-Reply-To: <quicwg/base-drafts/issues/>
References: <quicwg/base-drafts/issues/>
Subject: Re: [quicwg/base-drafts] Recovery would be simpler if the Handshake timer was unified with the PTO timer (#2650)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5cc151b616b2b_555e3f88d46cd96841148e"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: janaiyengar
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: Thu, 25 Apr 2019 06:20:41 -0000

Yes -- I was heading in this direction with #2648, and it is how we're implementing recovery in quicly. I realized that we have a false separation between the crypto retransmission timer and the PTO timers. Using _only_ the PTO timer basically is the most sensible approach.

We need to ensure that max_ack_delay is used only after handshake, and there's some care required there, but that's still much better than what we have now.

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