Re: [quicwg/base-drafts] Clarify time threshold vs crypto timer (#2620)

ianswett <> Mon, 15 April 2019 21:32 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id AD73212023E for <>; Mon, 15 Apr 2019 14:32:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.597
X-Spam-Status: No, score=-6.597 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_28=1.404, 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 p9YkIr9NFXC4 for <>; Mon, 15 Apr 2019 14:32:23 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id AD10A1201D7 for <>; Mon, 15 Apr 2019 14:32:23 -0700 (PDT)
Date: Mon, 15 Apr 2019 14:32:22 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1555363942; bh=/H5UNlUhMwN4do/8u+WiC/YnTw5hcylDcYyO4hV6YP0=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=aU0K8etlJQh7od0SBzEeJ6aSBp00LaN21rv6xg65jOZI6KmiBMLAdoShQ6vHScTWl MJ9lWcGGHTDpA/80G/Fw3oekN5Rlf4bsFnqRp70XgQi0RT15snFP3dUiRtnNTeG46A g8F1tv14fYREaZuBi8N7R0VtNxu3Jdhp3cNmcKus=
From: ianswett <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/pull/2620/review/>
In-Reply-To: <quicwg/base-drafts/pull/>
References: <quicwg/base-drafts/pull/>
Subject: Re: [quicwg/base-drafts] Clarify time threshold vs crypto timer (#2620)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5cb4f8669e5b5_f613f843dad45c0688b5"; 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: Mon, 15 Apr 2019 21:32:26 -0000

ianswett commented on this pull request.

> @@ -537,8 +537,13 @@ and otherwise it MUST send an Initial packet in a UDP datagram of at least
 1200 bytes.
 The crypto retransmission timer is not set if the time threshold
-{{time-threshold}} loss detection timer is set.  When the crypto
-retransmission timer is active, the probe timer ({{pto}}) is not active.
+{{time-threshold}} loss detection timer is set.  The time threshold loss
+detection timer is both expected to expire earlier than the crypto
+retransmission timeout and be much less likely to spuriously retransmit data.
+The Initial and Handshake packet number spaces are typically going to have a

If the number of packets is small, it's unlikely you'll hit the packet threshold loss detection, making time threshold much more important.

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