Re: [tcpm] [iccrg] Cwnd growth after fast convergence in CUBIC

Lars Eggert <lars@eggert.org> Fri, 06 November 2020 08:28 UTC

Return-Path: <lars@eggert.org>
X-Original-To: tcpm@ietfa.amsl.com
Delivered-To: tcpm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 22DF33A0EA8 for <tcpm@ietfa.amsl.com>; Fri, 6 Nov 2020 00:28:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=eggert.org
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 5fTgeqvXmzdB for <tcpm@ietfa.amsl.com>; Fri, 6 Nov 2020 00:28:27 -0800 (PST)
Received: from mail.eggert.org (mail.eggert.org [91.190.195.94]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D82AC3A0EB3 for <tcpm@ietf.org>; Fri, 6 Nov 2020 00:28:26 -0800 (PST)
Received: from [IPv6:2a00:ac00:4000:400:1d5b:6b9d:45f1:2c5b] (unknown [IPv6:2a00:ac00:4000:400:1d5b:6b9d:45f1:2c5b]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.eggert.org (Postfix) with ESMTPSA id 09AB56103D6; Fri, 6 Nov 2020 10:28:16 +0200 (EET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=eggert.org; s=dkim; t=1604651297; bh=n/N7oTfEFfGYC6aiRqekLXBsr3n+OSIJAmCY5SrzE1w=; h=From:Subject:Date:In-Reply-To:Cc:To:References; b=aoHfZrd3OBn3ikfA0p7L1ees4ODNS26EHxfu05k4iyuE/XhY5gPVUdObncktzkTDQ sifKQeSPhYm1irXA/gPDz4iDdWtSUGfW7Ob9OvQ3ad0N1tkzIQEb43ap+xxB8jIjjI lnI50N5+BbzWZmKbr3jp9EKDEaA/Folm+Ezx6KIA=
From: Lars Eggert <lars@eggert.org>
Message-Id: <BC43606C-F2C7-4327-A43C-016B068514D0@eggert.org>
Content-Type: multipart/signed; boundary="Apple-Mail=_2D1B332D-E9BC-4A9A-93CC-2BA541A9C8DD"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
Date: Fri, 06 Nov 2020 10:28:16 +0200
In-Reply-To: <DAB97903-5D7B-4310-9A66-0237CAE4428E@apple.com>
Cc: "Rosenblum, Wesley" <wesleyr=40amazon.com@dmarc.ietf.org>, "tcpm@ietf.org" <tcpm@ietf.org>, iccrg@irtf.org, Martin Thomson <mt@lowentropy.net>
To: Vidhi Goel <vidhi_goel=40apple.com@dmarc.ietf.org>
References: <C0FCC036-0040-4C2A-9C39-15DF1A9A1146@amazon.com> <DAB97903-5D7B-4310-9A66-0237CAE4428E@apple.com>
X-MailScanner-ID: 09AB56103D6.A3098
X-MailScanner: Found to be clean
X-MailScanner-From: lars@eggert.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/tcpm/ZZVysvFA8dXyyEcuR5aH7HsSCfc>
Subject: Re: [tcpm] [iccrg] Cwnd growth after fast convergence in CUBIC
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcpm>, <mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tcpm/>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>, <mailto:tcpm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 06 Nov 2020 08:28:28 -0000

Hi,

On 2020-11-6, at 6:45, Vidhi Goel <vidhi_goel=40apple.com@dmarc.ietf.org> wrote:
> IMO, we should not be applying beta to W_max after convergence factor has been applied in the K formula. Perhaps, it was an oversight in K’s formula.

the other authors of the CUBIC RFC are experts on the algorithm, I mostly just helped get it through the IETF process.

That said, the intent was to document what the Linux code was doing at the time. Is there a difference between the RFC and what Linux has been doing or is doing now? If yes, it might be time to revise the RFC.

(I think Martin Thomson also found some nits recently.)

Thanks,
Lars