IETF Logo Mail Archive

[quicwg/base-drafts] loss recovery of crypto packets is less aggressive, not more aggressive (#2435)

Marten Seemann <notifications@github.com> Thu, 07 February 2019 01:15 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 6F4DF130FA3 for <quic-issues@ietfa.amsl.com>; Wed, 6 Feb 2019 17:15:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -11.149
X-Spam-Level:
X-Spam-Status: No, score=-11.149 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-4.553, 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: 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 lVo1EVlUOlru for <quic-issues@ietfa.amsl.com>; Wed, 6 Feb 2019 17:15:38 -0800 (PST)
Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 13E1E130F82 for <quic-issues@ietf.org>; Wed, 6 Feb 2019 17:15:38 -0800 (PST)
Date: Wed, 06 Feb 2019 17:15:37 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1549502137; bh=+UADYPAg7JzYgaWeETBwAKMBUNVVBOA/067dSq2JwFE=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=CBOlScR8mc6y7rYU8zbdpuP+3KdKEeeDJvPzgyAF5/zaaah9btjj0PDXuva2g06VC jg7jPmHW0QWxGWYQLy1hof9Tet7dIa4Sq8S1SQ6K6chOqXoNI/4Q4QKqFMBucF7wDL dy+wDUPGX4IgFEuWMpLFqi+jRZud0XNheH0sMoX8=
From: Marten Seemann <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab5a83c4f3dab19fa0ab5a0fe3db562bfb5a09cfd792cf00000001187348b992a169ce184a02c3@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2435@github.com>
Subject: [quicwg/base-drafts] loss recovery of crypto packets is less aggressive, not more aggressive (#2435)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c5b86b9306bb_3203fa6fded45c01070f5"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: marten-seemann
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/rfLsceXXXdwhaZXwqK9mWgpkZRs>
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: Thu, 07 Feb 2019 01:15:39 -0000

We claim that 
> Data in CRYPTO frames is critical to QUIC transport and crypto negotiation, so a more aggressive timeout is used to retransmit it.

As pointed out in #2417, the only mechanisms we have for retransmitting crypto packets is Fast Retransmit (i.e. when an ACK declares a packet lost) and the Crypto Retransmission timer. Specifically, we don't have an Early Retransmit timer for crypto packets. This means that if a tail packet in one packet number space is lost, we wait 2 RTTs before retransmitting it, whereas with Early Retransmit the retransmission would have happened after 9/8 RTT.

-- 
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/2435

v2.23.0 | Report a Bug | By Email