Re: [quicwg/base-drafts] A pacing algorithm (#3630)

MikkelFJ <> Wed, 06 May 2020 11:40 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 0A6E03A0998 for <>; Wed, 6 May 2020 04:40:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.006
X-Spam-Status: No, score=-2.006 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, DKIM_VALID_EF=-0.1, HTML_IMAGE_ONLY_16=1.092, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, 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 D7qYoXGRs1Gx for <>; Wed, 6 May 2020 04:40:28 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 463AC3A096B for <>; Wed, 6 May 2020 04:40:28 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 2A7096E0032 for <>; Wed, 6 May 2020 04:40:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1588765227; bh=KPX2XYxQRLV77R9qIU4WwtVSeNAMwVvxAV0JOn1WAsk=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=rs7gLAwbXmZRayK2D5gCV83W3hnMMFt2HDYtHrOoHTLaLQ0vLdgZ2jJCJaNRJYTU1 io/q/QP+alpi86O8Q4WOQqBw0L4SxriS0OedNcwHVQTJ7OCfTQ44XkFCrjqWemWfc8 mHZZvC4pPjQvz76p+b3UxCtqXpNTiVEjKHlhy6k0=
Date: Wed, 06 May 2020 04:40:27 -0700
From: MikkelFJ <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/pull/3630/>
In-Reply-To: <quicwg/base-drafts/pull/>
References: <quicwg/base-drafts/pull/>
Subject: Re: [quicwg/base-drafts] A pacing algorithm (#3630)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5eb2a22b1b4b2_1db83ff60d2cd95c11437b2"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: mikkelfj
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: Wed, 06 May 2020 11:40:31 -0000

Leaky bucket sidesteps the issue of shaping multiple streams, but I agree you do not need that level of detail here.

I don't understand the motivation for the N factor from a casual read. I guess it requires a deeper insight into the congestion controller. If it is a burst thing, it couldn't be for every interval `t[m]..t[n]`?

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