Re: [quicwg/base-drafts] Packet-threshold loss detection poorly interacts with packet coalescing (#2653)

ianswett <> Thu, 25 April 2019 12:39 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 0A684120072 for <>; Thu, 25 Apr 2019 05:39:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -8
X-Spam-Status: No, score=-8 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_32=0.001, 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 dA_wVKgqXRhm for <>; Thu, 25 Apr 2019 05:39:31 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 55B4D120047 for <>; Thu, 25 Apr 2019 05:39:31 -0700 (PDT)
Date: Thu, 25 Apr 2019 05:39:29 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1556195969; bh=ysYQKx0g8qHUabUEt8BgX/hEjuiDleLq6poWbatm/hQ=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=mPSITha9Rs56emEh7PdhDS9EVLTUF+PYaybRJqkZxPeAoXfoECKWkj4jA22PJMwFp W17W+wA+cz0BFdmy4//EijX70pdGo7m/z7S26BF4eobQ2SYixFiI2ANgemfw9iHNlA bCzjvMqTvc4JrCuPGPVD6BC5hjW5MRt54cjuaHjw=
From: ianswett <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/issues/2653/>
In-Reply-To: <quicwg/base-drafts/issues/>
References: <quicwg/base-drafts/issues/>
Subject: Re: [quicwg/base-drafts] Packet-threshold loss detection poorly interacts with packet coalescing (#2653)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5cc1aa81d6640_514e3f85ea0cd96021247a"; 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
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: Thu, 25 Apr 2019 12:39:33 -0000

Can you be more specific about the issue you're seeing and how packet coalescing is relevant, because I don't understand the issue.

If you were allocating packet numbers from a single space when doing multiple PN spaces, then unless you adjust for that, you could become very sensitive to reordering, but that is implementation specific and doesn't involve coalescing.

We could disable packet threshold for Initial and Handshake PN spaces, and it likely wouldn't matter during the handshake since it's rare to have 3 packets outstanding at once anyway, so time threshold is likely to kick in sooner.

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