[CCWG] Éric Vyncke's Discuss on draft-ietf-ccwg-ratelimited-increase-06: (with DISCUSS and COMMENT)

Éric Vyncke via Datatracker <noreply@ietf.org> Mon, 03 August 2026 08:04 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: ccwg@ietf.org
Delivered-To: ccwg@mail2.ietf.org
Received: from [10.244.22.187] (gaia.k8s.ietf.org [4.156.85.76]) by mail2.ietf.org (Postfix) with ESMTP id 87BAD12291955; Mon, 3 Aug 2026 01:04:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1785744250; bh=u0Efw5KlvhkCGs0ZXw0MtzshUPBd4nyl0m4loQ1X6qk=; h=From:To:Cc:Subject:Reply-To:Date; b=mM53MqbbWD9Rc5HACroYCmuXprzQa8rsdXQMObeVT7FBuaMhrzU4wBa6OtDFryNJa 9QRWtI1mLbWTacSzeoMG612F6IsNjIhX7i/2k3l48UwIVOkGZuV/4Gh2cVx5/Jm7ga CnzZlwF9mY+OMgvPUMrsfvQqdf2x8Xc6CU5R6cpk=
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Éric Vyncke via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 12.69.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <178574425029.1851249.7147481595010966133@dt-datatracker-d4d6ff9d9-ql5mb>
Date: Mon, 03 Aug 2026 01:04:10 -0700
Message-ID-Hash: VOXAFYD2J3AU3D7XOV2R7WZXDZ4CGVTK
X-Message-ID-Hash: VOXAFYD2J3AU3D7XOV2R7WZXDZ4CGVTK
X-MailFrom: noreply@ietf.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: ccwg-chairs@ietf.org, ccwg@ietf.org, draft-ietf-ccwg-ratelimited-increase@ietf.org, ietf@tenghardt.net
X-Mailman-Version: 3.3.9rc6
Reply-To: Éric Vyncke <evyncke@cisco.com>
Subject: [CCWG] Éric Vyncke's Discuss on draft-ietf-ccwg-ratelimited-increase-06: (with DISCUSS and COMMENT)
List-Id: Congestion Control Working Group <ccwg.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ccwg/vXz4pQU7D4et8K9RbQWdoBA4cck>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ccwg>
List-Help: <mailto:ccwg-request@ietf.org?subject=help>
List-Owner: <mailto:ccwg-owner@ietf.org>
List-Post: <mailto:ccwg@ietf.org>
List-Subscribe: <mailto:ccwg-join@ietf.org>
List-Unsubscribe: <mailto:ccwg-leave@ietf.org>

Éric Vyncke has entered the following ballot position for
draft-ietf-ccwg-ratelimited-increase-06: Discuss

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/about/groups/iesg/statements/handling-ballot-positions/ 
for more information about how to handle DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-ccwg-ratelimited-increase/



----------------------------------------------------------------------
DISCUSS:
----------------------------------------------------------------------


# Éric Vyncke INT AD comments for draft-ietf-ccwg-ratelimited-increase-06
CC @evyncke

Thank you for the work put into this document.

Please find below one blocking DISCUSS points (easy to address), and one
non-blocking COMMENT points/nits.

Special thanks to  for the shepherd's detailed write-up including the WG
consensus and the justification of the intended status.

I hope that this review helps to improve the document,

Regards,

-éric

Note: this ballot comments follow the Markdown syntax of
https://github.com/mnot/ietf-comments/tree/main, i.e., they can be processed by
a tool to create github issues.

## DISCUSS (blocking)

As noted in
https://datatracker.ietf.org/doc/statement-iesg-handling-ballot-positions-20220121/,
a DISCUSS ballot is a request to have a discussion on the points below; I
really think that the document would be improved with a change here, but can be
convinced otherwise.

### Section 3.2.1

Why not a "MUST" (or lowercase "should") in `Therefore, congestion control
algorithms SHOULD implement a behavior that is equivalent to Rate-Limited
Increase, irrespective of whether they use a cwnd variable or not.` See also
the IESG statement about providing guidance when SHOULD is used
https://datatracker.ietf.org/doc/statement-iesg-statement-on-clarifying-the-use-of-bcp-14-key-words/


----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------


## COMMENTS (non-blocking)

### Section 3.1

Who is the "we" in `We illustrate the working of...` ? The authors ? The WG ?
The IETF community ? Please avoid ambiguities. Possibly also in other places.