Re: [quicwg/base-drafts] Crypto retx timeout should have higher priority than time based loss detection (#2565)

ianswett <notifications@github.com> Mon, 15 April 2019 13:52 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 EDF27120292 for <quic-issues@ietfa.amsl.com>; Mon, 15 Apr 2019 06:52:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.383
X-Spam-Level:
X-Spam-Status: No, score=-1.383 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_24=1.618, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no 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 fnYXlE1QOm67 for <quic-issues@ietfa.amsl.com>; Mon, 15 Apr 2019 06:52:02 -0700 (PDT)
Received: from o6.sgmail.github.com (o6.sgmail.github.com [192.254.113.101]) (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 696E012017E for <quic-issues@ietf.org>; Mon, 15 Apr 2019 06:52:02 -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=/sAwBNnQ22DhBRtzmNe4ViWZryQ=; b=urxrwwxM+drFK5FB kuiemDbOEyof2ZzpKo+B+B3bM2qV4302IM94vhj/YWAk++F945+1yCyjPv7jI5fm TSSvlc0AiNIt0C4tp0AZP1Nt5TUf/i8U8ikxrLOX37dKrthcxYLH+qhn+540crnv 0Xits5QTGj0SLH32/sdNgm6skQA=
Received: by filter1316p1mdw1.sendgrid.net with SMTP id filter1316p1mdw1-13559-5CB48C81-16 2019-04-15 13:52:01.361785287 +0000 UTC m=+560667.422780505
Received: from github-lowworker-89d05ac.cp1-iad.github.net (unknown [192.30.252.35]) by ismtpd0005p1iad1.sendgrid.net (SG) with ESMTP id 8glmKvvUQ76a73BJ5O2CSA for <quic-issues@ietf.org>; Mon, 15 Apr 2019 13:52:01.296 +0000 (UTC)
Received: from github.com (localhost [127.0.0.1]) by github-lowworker-89d05ac.cp1-iad.github.net (Postfix) with ESMTP id 45D9DAE05A4 for <quic-issues@ietf.org>; Mon, 15 Apr 2019 06:52:01 -0700 (PDT)
Date: Mon, 15 Apr 2019 13:52:01 +0000
From: ianswett <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abb9ddfe5be28c4259391f5c95f4bee89dd7c20ee292cebac1bf0192a169ce19747553@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2565/483260240@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2565@github.com>
References: <quicwg/base-drafts/issues/2565@github.com>
Subject: Re: [quicwg/base-drafts] Crypto retx timeout should have higher priority than time based loss detection (#2565)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5cb48c813f254_52203f90f5ed45c028587d"; 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: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak2anBRI1mnLVtrVTK5YundOKsZc8z2iwBUDxC gRqkgDTZ+Xjveh2PYM+1LZgsCbUd+/0EACtVuR9hKJqEivb7dbMroWS8YGSA2BYNWBWOfWMENF5oRB k6cgKOCuxsaKSLOfbLBtAjz5P0HZOhmvu7uIFK3BuNhxQDhNTqOQsW6X8nuNJMyAkWO/8GOhDxhjWu 0=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/XAU1w0Wnr1b6sxzA4JHPJXKsJPo>
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 13:52:05 -0000

+1 to @marten-seemann's comment.  Timers are necessary when you have no information about what might be lost, but if you do have information, there's no reason not to use that instead.

-- 
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/issues/2565#issuecomment-483260240