Re: [quicwg/base-drafts] Lost Server Initial Takes Too Long to be Retransmitted (#3078)

Martin Thomson <notifications@github.com> Wed, 16 October 2019 23:50 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 0CBDE1200F7 for <quic-issues@ietfa.amsl.com>; Wed, 16 Oct 2019 16:50:49 -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 MYSY0VczC6Hz for <quic-issues@ietfa.amsl.com>; Wed, 16 Oct 2019 16:50:47 -0700 (PDT)
Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 111B0120086 for <quic-issues@ietf.org>; Wed, 16 Oct 2019 16:50:47 -0700 (PDT)
Received: from github-lowworker-2300405.va3-iad.github.net (github-lowworker-2300405.va3-iad.github.net [10.48.17.39]) by smtp.github.com (Postfix) with ESMTP id 304CC1C0A05 for <quic-issues@ietf.org>; Wed, 16 Oct 2019 16:50:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1571269846; bh=AhkJHjDedeMMUqelG86w3woIQujSqv7HtOJbOZvTS1U=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=r4m6X2sBXW94M1AwGXoDpqIiaVG4pvysY4E4YCg0VXCeOo1w+SZLTnhOmgjv3qQLG NDbFGradvR4D4Wz4XSab+4H5nx7L34RE8WREpa1w9/Kjm9czdSeMtu/72kaGc8rueA MFp2t2sTvCqZpa/Nn+cdXE8rDhOV+c2K9Q3UQkSw=
Date: Wed, 16 Oct 2019 16:50:46 -0700
From: Martin Thomson <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK5DZCVQ4IVGIS6B7FV3WTWWNEVBNHHB34LR2Y@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/3078/542937029@github.com>
In-Reply-To: <quicwg/base-drafts/issues/3078@github.com>
References: <quicwg/base-drafts/issues/3078@github.com>
Subject: Re: [quicwg/base-drafts] Lost Server Initial Takes Too Long to be Retransmitted (#3078)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5da7acd620bcf_5d393f99bb0cd96c530ce"; charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: martinthomson
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/V_uU406Cu0qBM1uAgfqJUSmHhi4>
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: Wed, 16 Oct 2019 23:50:49 -0000

The proposed "fix" could lead to a deadlock where the server consumes its entire congestion window without making progress.  If the server receives too many Initial packets (bad RTT estimate at the client, say), then it will send lots of data without getting an ACK.  As suggested, this is just an optimization, so limiting the number of times this optimization can be used might avoid that problem.

-- 
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/3078#issuecomment-542937029