Re: [quicwg/base-drafts] loss detection timer description could be simplified by definining a timer mode (#3151)

Marten Seemann <> Sat, 02 November 2019 01:50 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 3305C120B74 for <>; Fri, 1 Nov 2019 18:50:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.382
X-Spam-Status: No, score=-6.382 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_24=1.618, 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: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id rFgBj-s_Es_K for <>; Fri, 1 Nov 2019 18:50:45 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 3ADB7120AC5 for <>; Fri, 1 Nov 2019 18:50:44 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 5D28F9604A0 for <>; Fri, 1 Nov 2019 18:50:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1572659443; bh=+9QFBoxcHFZUhhVAXb3mfWlXSadYB4aAt1y4mQpYt4k=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=HOtx9jQ4PTjVq6sIMZoyNEj5UASZupHdbOvcmm2GwaZlXgu7sQZN95xVV1fxFOgnZ v44mWSxLvSInmntRVVTwIABIvd2Mvc1gYEY5UyK10IrHLn4ENMsnlaksYcDuK5MRze 38iusFNC3RQ+/3NDGk5cqI3A73qPJlkQauJyFtGA=
Date: Fri, 01 Nov 2019 18:50:43 -0700
From: Marten Seemann <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/issues/3151/>
In-Reply-To: <quicwg/base-drafts/issues/>
References: <quicwg/base-drafts/issues/>
Subject: Re: [quicwg/base-drafts] loss detection timer description could be simplified by definining a timer mode (#3151)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5dbce0f34e5c0_5eb83f89802cd96063832"; 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
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: Sat, 02 Nov 2019 01:50:46 -0000

@ianswett I have a half-baked PR on my disk, but I still need to figure out the details of how this interacts the amplification limit. It seems like on the client side, there's a third timer mode (send *anything* to unblock the server from the 3x limit).
I'll put some more work into my PR and post it by early next week.

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