Re: [quicwg/base-drafts] loss of only two packets can lead to an unrecoverable situation (#2267)

Nick Banks <> Mon, 28 January 2019 05:08 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 88418130FA3 for <>; Sun, 27 Jan 2019 21:08:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -10.935
X-Spam-Status: No, score=-10.935 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_24=1.618, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id DHNyWAAzPLJ6 for <>; Sun, 27 Jan 2019 21:08:30 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id E1781130F8B for <>; Sun, 27 Jan 2019 21:08:29 -0800 (PST)
Date: Sun, 27 Jan 2019 21:08:29 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1548652109; bh=PI70xB0hJVd4TYzVPa0OUqe1knE1uB4oKZn7rvah3aI=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=NbaZcnFg7C/UzYItjQXBNxwAM+EGnv8lJOcZpjNAsLhKVPmZhyQZKdYCqZNmappM8 LchavfKIMhL3M24IHxqKHd9agL2aCEx79bmekDbG7Fnc2XaGfo3qfcDXsCpRIIBXZM E0+X7afmbjTNpH0pA+Vh2NuTVI3PXa7SEU0ZXi/M=
From: Nick Banks <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/issues/2267/>
In-Reply-To: <quicwg/base-drafts/issues/>
References: <quicwg/base-drafts/issues/>
Subject: Re: [quicwg/base-drafts] loss of only two packets can lead to an unrecoverable situation (#2267)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c4e8e4d3fcad_11753fa24f6d45bc1874936"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: nibanks
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
Archived-At: <>
X-Mailman-Version: 2.1.29
List-Id: Notification list for GitHub issues related to the QUIC WG <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 28 Jan 2019 05:08:32 -0000

My vote would be to have an explicit signal instead of a timer based solution. The loss recovery / congestion controller could use the exact same signal to fix any necessary state. I like the Handshake Done solution.

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub: