Re: [quicwg/base-drafts] Crypto Retransmission Timeout interacts poorly with Congestion Control (#2886)
ianswett <notifications@github.com> Tue, 09 July 2019 20:45 UTC
Return-Path: <noreply@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 3AD6F120024 for <quic-issues@ietfa.amsl.com>; Tue, 9 Jul 2019 13:45:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.454
X-Spam-Level:
X-Spam-Status: No, score=-6.454 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_20=1.546, 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: 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 B0FJAzmpp-Rd for <quic-issues@ietfa.amsl.com>; Tue, 9 Jul 2019 13:45:49 -0700 (PDT)
Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 685EF12000E for <quic-issues@ietf.org>; Tue, 9 Jul 2019 13:45:49 -0700 (PDT)
Date: Tue, 09 Jul 2019 13:45:48 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1562705148; bh=H0Wyj+GFYU9tOzj0NHcl/sy8nDlYa/sdHyHcm4fphPk=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=avR7aSk1f7izj51pAsH0dc9f6On1gikMnRbUeeTMxGRpd79mLk+h3ACycXKD7S49g 8OUNTEcGN+Ozncze72S4mGkdGP08x7ugbwBm7qgwZWViSaYQCB2HYyPhUHIo9ei7YU 8i8JQtC7XXkfOXFVxL2BUWGmXOtCJ4+D45KmCwEU=
From: ianswett <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK4OOAF3SFJ36DWWIPV3GIXXZEVBNHHBXRIJFY@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2886/509800585@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2886@github.com>
References: <quicwg/base-drafts/issues/2886@github.com>
Subject: Re: [quicwg/base-drafts] Crypto Retransmission Timeout interacts poorly with Congestion Control (#2886)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5d24fcfc6fbca_6b463fb1caccd95c341622"; 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
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/TYnmVgTHoIE-RwViBquq2FitLa0>
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: Tue, 09 Jul 2019 20:45:51 -0000
It was not intended for crypto timeout retransmissions to be blocked by the congestion controller. Does PR# 2806 fix this by merging them? -- 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/2886#issuecomment-509800585