IETF Logo Mail Archive

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

ianswett <notifications@github.com> Mon, 15 April 2019 21:36 UTC

Return-Path: <bounces+848413-a050-quic-issues=ietf.org@sgmail.github.com>
X-Original-To: quic-issues@ietfa.amsl.com
Delivered-To: quic-issues@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8123812029F for <quic-issues@ietfa.amsl.com>; Mon, 15 Apr 2019 14:36:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.597
X-Spam-Level:
X-Spam-Status: No, score=-1.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_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id obLxpmEDBL5U for <quic-issues@ietfa.amsl.com>; Mon, 15 Apr 2019 14:36:01 -0700 (PDT)
Received: from o9.sgmail.github.com (o9.sgmail.github.com [167.89.101.2]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5541112024D for <quic-issues@ietf.org>; Mon, 15 Apr 2019 14:36:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=qOHkHwPHmX4UqRN4kr+XzBzgzvM=; b=ZYSHwwt1bWyLN32+ BXf+u4DqY1zKwE+1Pfsn1f/1Gyzh6UwU6lvmmpPizPPVB39ULnQ5zxKU4MoBF5pN 9kE93pkcoy1i5F/i9n+3Sr5wf+2CtkaV9UvzfzSAmU/7pcQnNhDJUKRg6/FzjVN3 0emu0sW98A3YaZLELhy3Nd9TEQg=
Received: by filter0575p1iad2.sendgrid.net with SMTP id filter0575p1iad2-14469-5CB4F940-9 2019-04-15 21:36:00.171551599 +0000 UTC m=+597688.735130668
Received: from github-lowworker-e55e3e3.cp1-iad.github.net (unknown [192.30.252.41]) by ismtpd0001p1iad1.sendgrid.net (SG) with ESMTP id 3qi8341TTZ-ywmAPl_DyqA for <quic-issues@ietf.org>; Mon, 15 Apr 2019 21:36:00.051 +0000 (UTC)
Received: from github.com (localhost [127.0.0.1]) by github-lowworker-e55e3e3.cp1-iad.github.net (Postfix) with ESMTP id 08FA41806B5 for <quic-issues@ietf.org>; Mon, 15 Apr 2019 14:36:00 -0700 (PDT)
Date: Mon, 15 Apr 2019 21:36:00 +0000
From: ianswett <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab6805164cf33c2bff7f788a5603cc8d46d323a29c92cebac22bc092a169ce19d3a2f6@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/2620/review/226892642@github.com>
In-Reply-To: <quicwg/base-drafts/pull/2620@github.com>
References: <quicwg/base-drafts/pull/2620@github.com>
Subject: Re: [quicwg/base-drafts] Clarify time threshold vs crypto timer (#2620)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5cb4f940796a_78e3fbf428d45b447480"; 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
X-GitHub-Recipient-Address: quic-issues@ietf.org
X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak2HTBuqjhSioxbNpobP5yiJl+TUj/EYMvpoea 9MRW2QDCo9ZTeS2OStq+d3/SVfRzQgokAc2hkjJIT66nGVgqQ75TAt+V31yXUGZ3LFe1ZSCu5CKnzP VCfo75DLCERyZfkD90/DL2ScxzUmJYFdqQukYKhakOV6Se5aWtHRKndmgA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/ZxXg1-B0p_6rgem7Ij84bsqMMQU>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Notification list for GitHub issues related to the QUIC WG <quic-issues.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic-issues/>
List-Post: <mailto:quic-issues@ietf.org>
List-Help: <mailto:quic-issues-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Apr 2019 21:36:03 -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

I tightened up the text, but feel free to suggest further clarification.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/quicwg/base-drafts/pull/2620#discussion_r275554274

v2.30.2 | Report a Bug | By Email | System Status