[ippm] Re: Gorry Fairhurst's Discuss on draft-ietf-ippm-capacity-protocol-21: (with DISCUSS and COMMENT)

Ruediger.Geib@telekom.de Wed, 02 July 2025 08:29 UTC

Return-Path: <Ruediger.Geib@telekom.de>
X-Original-To: ippm@mail2.ietf.org
Delivered-To: ippm@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id BAFC73C9A908; Wed, 2 Jul 2025 01:29:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -4.167
X-Spam-Level:
X-Spam-Status: No, score=-4.167 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, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.232, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=telekom.de
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Gxbt5KR5skIF; Wed, 2 Jul 2025 01:29:08 -0700 (PDT)
Received: from mailout41.telekom.de (mailout41.telekom.de [194.25.225.151]) (using TLSv1.2 with cipher ECDHE-ECDSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id A843B3C9A8FE; Wed, 2 Jul 2025 01:29:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telekom.de; i=@telekom.de; q=dns/txt; s=dtag1; t=1751444948; x=1782980948; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=ILZDVN6LSvLK/ToPBbvZz4jHxwPnfC2d9TjIScezE/I=; b=T9RZGptBBfWC+JO/pLE/vqMA0FmlGEaVjoctf855qZSNhzBtojBT141u mgGAUXwbFlCciPvIsDX27odZSptA133g5Ub0eW3RPcVNyQt2HAPJ9t70O JAL7HV4QkzAxdWcTAw82elPWFE6Z48LbMOsFvYmWHwtA0c7nFHzPhL1pw UbC8Lj4G1mhQE4g00DDKKOCiUDckGEmvBQjoUtpmCnKuyTYT2T96Y39b0 JZ6p8+zj6PjMeZVZCdU5BS+FA8GriXDCnxZ2z8t7Pzn7IheX0CZncArQZ FKm/a2ivKTRe9F2lYycgwYdIlEobjor6QAFlNmxwHK03qFg8iOFPLjtiv Q==;
Received: from qde9xy.de.t-internal.com ([10.171.254.32]) by mailout41.dmznet.de.t-internal.com with ESMTP/TLS/ECDHE-RSA-AES128-GCM-SHA256; 02 Jul 2025 10:29:07 +0200
IronPort-SDR: 6864edd2_Tm+uzD3RZq+6vgWUkQ0yRdKAlWS6dx4JUDZqSrVBwyLfJ/x IbvYrBi2la/on8sPx92cwp9+gnt03IHsgyZsshA==
X-IronPort-AV: E=Sophos;i="6.16,281,1744063200"; d="scan'208";a="1060873321"
X-MGA-submission: MDFvls/0sA2a9b7yXRBMqJ/d+uHU+i106/ktQV1eF0AGXaPgKESXzZ/it93QkF2aziBNI7hMZMVZTOhz7QacgO4Dq//0wqCv/ltIDLtL408hE3ZpXpxMiMBvBhlhLUzn8XjhLb9lpAQa9XnIgBFR/FkH1fuIDSHbP8e4PX+k9buszg==
Received: from he101421.emea1.cds.t-internal.com ([10.169.118.197]) by QDE9Y1.de.t-internal.com with ESMTP/TLS/ECDHE-RSA-AES128-GCM-SHA256; 02 Jul 2025 10:29:06 +0200
Received: from HE101419.emea1.cds.t-internal.com (10.169.118.196) by HE101421.emea1.cds.t-internal.com (10.169.118.197) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1748.26; Wed, 2 Jul 2025 10:29:05 +0200
Received: from HE102770.emea1.cds.t-internal.com (10.171.40.42) by HE101419.emea1.cds.t-internal.com (10.169.118.196) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1748.26 via Frontend Transport; Wed, 2 Jul 2025 10:29:05 +0200
Received: from BEUP281CU002.outbound.protection.outlook.com (40.93.77.7) by O365mail07.telekom.de (172.30.0.239) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1748.26; Wed, 2 Jul 2025 10:29:05 +0200
ARC-Seal: i=1; a=rsa-sha256; s=arcselector10001; d=microsoft.com; cv=none; b=u+XNRr08wngYRkFQ4zl/+9+M6Qb4SlMotjymMC/MMwwAtq4zoFbt3dMFpdTUkFVEQz9Ygp6Y2mAYJjXM68XakTTmgEdA49ThPnNzJAnqgANrU5d/36O1tb92lZrGd2piPLD2odv13lcp3bFbtfKdnKB+7JebIHx2i8hR9oChh9UPe4WRsm+t2ej/2482gwdMu/UpKLgDYNmtwbA1bdfRGTcTbPvieDCxsejGi21IrXwsjOuvpo4anhrw8tnlVI1g13jBSedn7RNtWvN7oDmPApTNn9Zzv+SnjsyimhNI2yYhFOcZMVKdWIxfLchboY5zYde9Zvc/tinrhejh0KHBYg==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector10001; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=ILZDVN6LSvLK/ToPBbvZz4jHxwPnfC2d9TjIScezE/I=; b=q3tz7D3RSvzD6XHVcUfPIBYlX567BXQkK4wR3570yfyRm3NSKJ74EktjlpdS67y4BjwNOO7vslno6ZDrFHbJggKPQhwL3+P6BPJ8gAi3tWp5qMKmUinzzn/GVzCXMrlQBUwPIZovhKHG3tzyzXprbRmlUH4h06TAIh6sKQChO+RGsiVLygCOj1BjUixI0Me5qrCibRhg0TJFztec+tm5VdWBIYwcbrQQJWFLwpt3n6tgCV5EgAQUqWuVjsS+YhU1IoKjyF40sZ5oj0NeO2vaPOK2AAdjxKuofedS4bwWq0HzlsFgxqymBvnDjL0MZNZETbnsq0YJRFEVl7jt/SGWOA==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=telekom.de; dmarc=pass action=none header.from=telekom.de; dkim=pass header.d=telekom.de; arc=none
Received: from BEZP281MB2007.DEUP281.PROD.OUTLOOK.COM (2603:10a6:b10:57::6) by BE1PPF39BB4A911.DEUP281.PROD.OUTLOOK.COM (2603:10a6:b18::62d) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.8880.23; Wed, 2 Jul 2025 08:29:01 +0000
Received: from BEZP281MB2007.DEUP281.PROD.OUTLOOK.COM ([fe80::e80d:7e7e:b006:ea8a]) by BEZP281MB2007.DEUP281.PROD.OUTLOOK.COM ([fe80::e80d:7e7e:b006:ea8a%3]) with mapi id 15.20.8901.018; Wed, 2 Jul 2025 08:29:00 +0000
From: Ruediger.Geib@telekom.de
To: gorry@erg.abdn.ac.uk, iesg@ietf.org
Thread-Topic: Gorry Fairhurst's Discuss on draft-ietf-ippm-capacity-protocol-21: (with DISCUSS and COMMENT)
Thread-Index: AQHb5oqhALuwijq+e0yXtkWONbV26rQbyGKw
Date: Wed, 02 Jul 2025 08:29:00 +0000
Message-ID: <BEZP281MB20071B9A04BD2DA050EE9E329C40A@BEZP281MB2007.DEUP281.PROD.OUTLOOK.COM>
References: <175093607924.876281.13041808167748994652@dt-datatracker-6754d69b7c-p2xd7>
In-Reply-To: <175093607924.876281.13041808167748994652@dt-datatracker-6754d69b7c-p2xd7>
Accept-Language: de-DE, en-US
Content-Language: de-DE
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=telekom.de;
x-ms-publictraffictype: Email
x-ms-traffictypediagnostic: BEZP281MB2007:EE_|BE1PPF39BB4A911:EE_
x-ms-office365-filtering-correlation-id: ac5473f5-a79f-41b8-7e14-08ddb9427f2c
x-ms-exchange-senderadcheck: 1
x-ms-exchange-antispam-relay: 0
x-microsoft-antispam: BCL:0;ARA:13230040|376014|366016|1800799024|38070700018;
x-microsoft-antispam-message-info: HjMApVtij0spLAQBiwpbe0Clgwssa4H6mJnKz5RfEHGF386t5uL/ZsoXrS9AgX+XYAadmfqIySxf7KGJvg2kINVPP1DnCLciAL7TdnD2Taab5lEZYuyruslyKN6HUJt11m79hqFs9Kx9aLWwCrw8oOLOqC2eBwHwhuTdMsoLa5C29hMGYLuOvsQrCMlRm/Y7PYzK/jiXmyJISFvi6PtvrTSOULiKfZ86SKVsxmj6yLPatbKIpJceJ4yeu2mG/NjFQmEZGiYpScphGCmCGdhROKVAIt+DFt2hf7G+xpaaWMvDaTV0lorzh92F+FIOJsOYqb2vUdTVnnZkuRempT9/PG4SWTY4m1Fvd6hiZsE11LNu363JGtBtdo5eAOpApIEfZdo5OIX9/mEXFWnQKP+VbiIBtwTxL5ZuqP/QLY6EuttJ9tl0PfevOaqV+uXeuC9Ivv8W7vXHs+sR4zbxj2BntaFi/IJ+kZpNjvScVPzZdIbQzoT77SihdjFR+l1SMX+3BgfGWhgesdX/XoZSJC7x+xhK2RWkom3JYWI0CZY7GC0D2sUDc0/csSe1YFfraGANlSVtxJ6KBImfJH2VsS6A8sDj7jrju441g/mQVawmlvx8B4XbauZ26Zt9T97DE/7Rhe+gKHpGKCWonS8luV6x1bALlp4uKQtWgQzNUxxCGWZX1qa0iZ5lFKg9tcSJxqIK7Qfn5/qsAv2XzbeYenVIggrFJg4pLVJWKUEZs0+DKgsBmvLAkuIh3MJePhxzxz39UErdX0TRFAsgWkAipjpmaKYCW3YxzBLtZx8nIPMWk89d+Auk7nWVauwLkbBc0wP6bYDgotHO/sZ95hnt0o3nRawVgws30Bhi2T3U43g4kjwoSlH+4cY9HA8JAwLUuKKG4i84UgBaLshbQ4qGKawLj6OhpcYm4NyDjPtTaFCpATMSq9addUfEJVhU1EY9GNtu/5Ju5DVPbndvsjT3zmtFk+jgvdo+lG1hLlODOooiBQ7ugh04oWlmw1XTEmSl4HSBWtf7vYZBQFen5NVmKwEVZdRr+pc1cSQienRtqwpsaiBaixFGRzYW2+qKXpApvAvq9oIwDn/ZXRC7xPM8wQJlwLkYgng0MGPmuF2gTMC3lI5msRMeJn70Y+XPnajOPwpVytldO0DSG6n+x4qy9q92/wFQxL8ZLNxqmbNGjNIu0TlonHkyNMhdmKQEb0d9CGWQWq+t5Skj1PtjpjYxzCMGHP+Go7eF7ViuGumvGxXYO9+6p9G/FIrlSAj/QQSrGZV94vBU2LjWyqrDYJbMtaYmqIW9knmOdbhlNVUkUsl4wgmjehqmOGFWpuK+BJyBZeGyLssQv3/kltPBSJ20yHR0ya6TCO0zNpXUYcsg35S4qtM+W3lAMn15Q0wByeanyYJ/JPTvbOLBdFOblzcyMdMZy7LN4Fw24nN49CylodxIZ4k=
x-forefront-antispam-report: CIP:255.255.255.255;CTRY:;LANG:en;SCL:1;SRV:;IPV:NLI;SFV:NSPM;H:BEZP281MB2007.DEUP281.PROD.OUTLOOK.COM;PTR:;CAT:NONE;SFS:(13230040)(376014)(366016)(1800799024)(38070700018);DIR:OUT;SFP:1101;
x-ms-exchange-antispam-messagedata-chunkcount: 1
x-ms-exchange-antispam-messagedata-0: rfTJsC2i0Cy7bXXg06hMbYzCbbDj9UeVwa4nqPYnT8xh9JMRG1OZamiM3wSl9mxjQ6SgCWwaXOPrbJQkGFhrOmS+6167c/Lfw9sq0xleE9aVmiWnAnqDGb4OllsqK5YXrWZzB9BS59cYyBCvqH/RGzWj+ySIBDto55Yr/PdLhstOHgNt4iYkARPXDNzCGQizjtws44T1qYkTVWEa7urFKHGiKET1wZEF9X5Q8O7t04xjei5gOoCd3iPfX27SZxKO43d4xG71rsYKPfsqxGNPxHWYYnPe1wZ9gv8Z5hEfQkCRcpCl0oQXqhBd24Y+8nSCvmzSBpqhMNC6eaNAye+WFG9pSjKqkvAHv3MxZ2+ZwtMhhd/K8DTpLDyUVQ8Gl/dob5UsgvPELHyiWSF9xZCGOryVMhXOeI6MuNcyfAEFwsTpNEW6IyLpDSmSGd+NhAaGdH6kDTTHOymxlmIBNUXylKAfVqPZ8lbPV/RQWhPGS9iz1oWuqxiMP9Byk0c7wMpVJTpTPOVH8qG9t0vFQjf+kSNP89ZR4nfdK2+MYk/qP+EVGXefvjgRA6s44+Czj0D55DdiFVWGlQLdZuRYms3bfSmHy7iSVWRXJE+FIHaIf1FSzQlFV2sutMR7CP1f3wjKJ3bnbDukioI8yudxHYyIjH9fTstP/Rkc7UScvz67Wq04zKIrIMUhPnjGXrKA3g8G9MF/otmqqhua4btDBA8t3BPcqIh8xG5iI2bfdS3MDOAVt1zcbKKGGe/2UHeEBPqG+NdOwSqrRFpHwfVcwLj+YIHSkn0PmPwSxBy0vFTWoiR1SNosRjD9XGko8YtFBoTl5N3D/snQPska7GAMo8KU6NH5yIevCmIylf4pbF/YEegf1/Dt9KBByIiCAe4GoY7NiM9Nf1zOoSiJDbYRXCPUHkmIYDwiksb3DJjWX2tGZy1AqZ0pI3aYMduSV7dprwpq26H9OKuU1e0D3GOwndvl9EoJAR7urrDaV1WLhomW8aSvej0sYCJZvmbKm051LAwapM+A1t2zUeWPEZUTKMHt5OTgpK8anHQFFYSzXqE4RhFuTPxLmaIRRchVMUrZUIh0L28r3SJndMm0xT1JyR4Y0ZmIdEGWzexlhABl9bQzkS8aHbFLV1tmNO43VnwOzRj+eN9dvzvacZeXsMI/5SIfELLGU75uCLEkx/c2/AU9Cbir0bzZ1F9s8ecTTtG68TBypkY/IBIg22jchDeu/9mzNyBmjjW8aNiJvpnO1dOl6foWf16i2QCf8qMD/gu99PyTIDou2rGF3p01A99HNewXHJuTYcwZ8pfdaTaXiCm7tThK/16s7nOJD30LXQt/p8+sci60o0aIMFV+4jPZi+MgTYOdHcFQzWqA9NSPCJ2steT/6drUbl8Gqw36bLVY79D0mIymzktQ/Y+U0xZ94Qlc2qpMCwLP96+7NE19sLPq7LCjq9AIbumA2P2hfeDVaCsypqCTFRzfAAUzkYzOlu/zSBwZjbYIKXKih1sFDZZwRjABOO99lj+q8d5Hw0l059rSY+Alty5ydUeuUti/L3P+oTTzj8rg8VPuL7EPZixAOlBBhVPvZz+nxoWuTav+p9gD
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: BEZP281MB2007.DEUP281.PROD.OUTLOOK.COM
X-MS-Exchange-CrossTenant-Network-Message-Id: ac5473f5-a79f-41b8-7e14-08ddb9427f2c
X-MS-Exchange-CrossTenant-originalarrivaltime: 02 Jul 2025 08:29:00.8919 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bde4dffc-4b60-4cf6-8b04-a5eeb25f5c4f
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: fIkcwb8wI4wTELqNBBSHm/gkuHT5xw9vqOA2JaSQTxc9Se9qjxL4TDlllFpv1pA4WCJza614GJsZQqT8BxXnfDheT081AKiwfKz5v7OyL68=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BE1PPF39BB4A911
X-OriginatorOrg: telekom.de
Message-ID-Hash: 2PXQZUWSSYUCPHB6OI2QEQUN7S6RFBUH
X-Message-ID-Hash: 2PXQZUWSSYUCPHB6OI2QEQUN7S6RFBUH
X-MailFrom: Ruediger.Geib@telekom.de
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-ippm.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: draft-ietf-ippm-capacity-protocol@ietf.org, ippm-chairs@ietf.org, ippm@ietf.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [ippm] Re: Gorry Fairhurst's Discuss on draft-ietf-ippm-capacity-protocol-21: (with DISCUSS and COMMENT)
List-Id: IETF IP Performance Metrics Working Group <ippm.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ippm/tSCWryLUSHH4N08YDwvS3Ycx674>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ippm>
List-Help: <mailto:ippm-request@ietf.org?subject=help>
List-Owner: <mailto:ippm-owner@ietf.org>
List-Post: <mailto:ippm@ietf.org>
List-Subscribe: <mailto:ippm-join@ietf.org>
List-Unsubscribe: <mailto:ippm-leave@ietf.org>

Hi Gorry,

thanks for your comments. Please find replies marked [Authors] below. I've just posted  v -22 containing the suggested changes below, hopefully making some progress to clearing your DISCUSS. In some cases, I have trouble figuring out, what you expect. Suggesting text or a more detailed description of expected content would be appreciated.

Please note, I will be on vacation from/including Fri , 4.7.2025 until and including Mon 28.7.2025. I won't attend the Madrid IETF meeting.

Regards,

Ruediger

-----Ursprüngliche Nachricht-----
Von: Gorry Fairhurst via Datatracker <noreply@ietf.org>
Gesendet: Donnerstag, 26. Juni 2025 13:08
An: The IESG <iesg@ietf.org>
Cc: draft-ietf-ippm-capacity-protocol@ietf.org; ippm-chairs@ietf.org; ippm@ietf.org; tpauly@apple.com; tpauly@apple.com
Betreff: Gorry Fairhurst's Discuss on draft-ietf-ippm-capacity-protocol-21: (with DISCUSS and COMMENT)

Gorry Fairhurst has entered the following ballot position for
draft-ietf-ippm-capacity-protocol-21: 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-ippm-capacity-protocol/



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

Thank you for this I-D that defines a method for measuring Network Capacity
metrics. The measurement flows generate Internet packet flows that are
rate-controlled. The primary concerns are about the use of Datagrams
(addressing and packet size), the security model, and the congestion control
functions. This is therefore a significant piece of transport work and there is
a much longer than a normal DISCUSS. I have updated my ballot below, where
resolutions have alreday been implemented in rev-21 and expect to clear the
remaining, after more discussion.

----------------------
DISCUSS 2.2 At the end of Section 4.2:
To ensure readers are clear about the importance, I'd strongly recommend to add
a note stating that the described method is necessary also to avoid potentially
inducing congestion after there is a overload/loss on the control path.

[GF] One concern could be that the algorithm as specified can be used to mount
a DoS attack. That might be inevitable if it is not possible to put safeguards
to act to prevent this. That needs to be noted.

[Authors]: ADD in 4.3 (Security Mode Operations):
A load rate adjustment method matching Section 4.1 requirements is necessary also to    avoid potentially inducing congestion after there is an overload        or loss in general on the control path.

-----------------------

DISCUSS 2.4 In section 5.1. on the responsiveness (what CC experts often call
aggressive behaviour) of a flow: I note that the LOAD CONTROL as define uses a
statically configured watchdog interval -  which I think allows a flow to
contribute excess congestions for 3 seconds after this is detected, longer if
small levels of loss/congestion is not considered a trigger. For an arbitrary
path RTT this could be a large number of RTTs (e.g. 300 for a 10mS path). -
There are specific recommendations on the use of UDP that describe this case:
RFC 8085.

[GF] Please could you  add the following text after:
/The Method of Measurement discussed there deploys a feedback channel from the
receiver to control the sender's transmission rate in near-real-time./ NEW:
Section 8.1 of RFC 9097 specifies requirements for this method.

[Authors]: Thanks, Done.

-------------------------

DISCUSS Topics 3: How do we know the suitability of the specified rate
adaptation mechanisms?

DISCUSS 3.3  There seems little discussion of the risk to the network and other
flows when performing a fixed-rate test, or whether this is applicable usage
across an Internet path.

[GF] Please consider a separate discussion of this.

[Authors]: ADD
3.1. Fixed-Rate Testing

A network operator who's certain of the IP-Layer Capacity to be validated, may execute a fixed-rate test at the IP-Layer Capacity and avoid activating the measurement load rate adjustment algorithm (see section 8.1 of [RFC9097]).

Fixed-rate testing should only be activated for operation and maintenance purposes by operators within their network domain.

If a subscriber requests a diagnostic test from the network operator, this strongly implies that there is no certainty on the bottleneck capacity and initiating a UDP Speed Test based on the load adjustment algorithm is the preferred option. To protect against misuse, a client (and in general, a consumer) must not be able to initiate a fixed-rate test.A network operator may further conduct a fixed-rate test for stable measurement at the maximum determined by the load rate adjustment algorithm for debugging purposes

-----------------------

DISCUSS Topics 4. Concurrent flows.

4.1 In section 9.0:
   /It is obviously counterproductive to run more than one independent
   and concurrent test/
- Is there a congestion control or DoS issue here, I think so, can we discuss
why the I-D says this is allowed without a mechanism to defend against this?

[GF] See DISCUSS 3.3.

[Authors] Please suggest a change or addition to the current text, which limits number of concurrent, independent tests to one (or point out somewhat more precise, what you mean by "a mechanism"):
It is obviously counterproductive to run more than one independent and concurrent test (regardless of the number of flows in the test stream) attempting to measure the maximum capacity on a single path. The number of concurrent, independent tests of a path SHALL be limited to one.

--- ########################
DISCUSS Topics 5. Definition of an IANA Registry for alternative rate control
algorithms.

The present I-D says: "Test Activation PDU Rate Adjustment Algo.  Registry"
Why should the IETF publish a registry for this protocol with a private space
and no overarching congestion control framework?

In 11.2.8, the present I-D says:

   Value   Description             Reference
   (Numeric)
   ===================================================
    A(n/a)  Not used                <this RFC>

    B(0)    Rate algorithm Type B   <this RFC>

    C(1)    Rate algorithm Type C   <this RFC>

   Table 16: Initial Test Activation PDU Rate Adjustment Algo. values

---
DISCUSS 5.3 RFC 9473 has provided guidance on the IETF process if this is being
considered for use on Internet paths. Why is the IETF standardising use of a
rate adjustment algorithm defined elsewhere, without bounding its over-arching
congestion control properties? Please explain how these methods were evaluated,
and by whom. How in the future will this be tested for congestion control and
how this will be maintained.

---
DISCUSS 5.4  What is the scope of use for a rate adjustment algorithm defined
as experimental. RFC 9473 provided guidance on this topic. Why is this not
scoped only for use in limited domains?

---
DISCUSS Topics 6. How are new methods evaluated and specified?

I suggest discussion of how to provide IANA guidance for a new code point.

[Authors] All of these seem to be algo standard related. Draft text/ADD in section "Load Rate Adjustment Algorithm Requirements" (please suggest text or more precise proposals for changes, if we've missed a point):

This document specifies IETF's first active capacity measurement method using a load rate adjustment algorithm. While inducing congestion (active capacity measurement requires that), the load rate adjustment algorithm and the protocol specified by this document limit the duration of his congestion and stop the test if sudden impairments or a loss of connectivity in any or all directions occur.

The requirements following below and the currently standardised load rate adjustment algorithms B [Y.1540Amd2] and C [TR-471] result from years of experiments and testing by the original authors. These tests were performed in Labs, but also in the Internet and covered a set of different fixed, broadband, mobile and wireless access types and technologies in different countries and continents. Feedback received by performance measurement experts was included, as well as changes resulting from the standardisation of [RFC9097] (reflected also in algorithm B [Y.1540Amd2], which updates a prior version of this algorithm).

New standard load rate adjustment algorithms for capacity measurement MUST comply with the requirements specified by this this section. New standard load rate adjustment algorithms for capacity measurement MUST be reviewed by IETF experts prior to assignment of a codepoint in the IETF Test Activation PDU Rate Adjustment Algorithm Registry

##########################

DISCUSS 6.1 Please see this text:
 /On the other hand, the test configuration MAY use a fixed sending
   rate requested by the client, using the field srIndexConf./
- A fixed rate test brings additional concerns, and I didn't find this
analysis. Is there a need to scope this as a non-default mode? Should it be
restricted to certain domains.

[GF] See DISCUSS 3.3.

[Authors]: see DISCUSS 3.3.

===############# End of [Authors] replies ############


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

I have a number of non-blocking comments that I expect could be addressed in
the next revision of this I-D:

In section 3:
Typos:/resepcitvely/respectively/
/the bottleneck is congested,/if the bottleneck is congested,/
In section 4.2:
- Is /Once the modes requiring or optionally adding
   authentication or encryption are implemented and configured locally,
   the unauthenticated mode must be disabled./ - Could this be a MUST?
In section 5,1: /A IANA is/IANA is/
In section 5.2.2: I expect the following text helps, but does this ensure or
assist in the firewall traversal? /To ensure that a server's local firewall
will successfully allow
   packets received for the new ephemeral port, the server SHALL
   immediately send a Null Request with the corresponding values
   including the source and destination IP addresses and port numbers./
In 6.1,  /continuosly/continuously/
In 6.2, Server Processes Test Activation Request and Generates Response:

In this I-D, the following keyword use seems odd to me and could be improved:
 /   After the server receives the Test Activation Request on the new
     connection, it MUST choose to accept, ignore or modify any of the
     test parameters. /
- is this an exclusive list of things that is required or a list of all that
are required? I do wonder if this is simply a list of what the protocol does
next?

In section 12: /comprehensability/comprehensibility/
Also in section 12: /sheperded/shepherded/
===
There are some additional NiTs that I noted in rev-21:

/erquirements/requirements/
/sectiomn/secyion/
/PDU timeout which both stop/PDU timeout that both stop/

I agree with the requirement, but I see a problem that this directly follows
the discussion of the UDP checksum, but the word checksum could be confused
between the two. Could we insert a word before checksum here:, perhaps add the
word /PDU/ and a cross reference to section 5.2? /If a PDU sender is populating
the checkSum field,/

Similarly the keyword here could be confused, can we insert /PDU/ before
checksum here: / If checksum validation fails.../

Query: Ought this message to be rate-limited. i.e., "If sent, this message
SHOULD be rate limited to avoid exploitation as a DoS mechanism". /The
exception is for operations support: server         administrators are
permitted to send a Setup Response to support operations and troubleshooting./

Can this say a tiny bit more than this:
/note that not-ECT MUST be used./
NEW:
Note: This specification does not provide an ECN-capable transport, therefore
the sender SHALL set the ECN field to not_ECT./

===
And finally, so we do not forget waht was discuused, here are the currently
resolved DISCUSS positions:
---
Topics from the TSV-ART review. (Thought resolved in rev-21)
The I-D needs to therefore consider implications around security. Thanks to the
TSVART team for their review. In the security design, I saw many changes and
thank the editors et al for these updates in the present revision. Thanks. This
review also noted the way that datagram size was handled - and I note that this
is an important part of any service over UDP. In my review, I found the
guidance in the following section is inadequate :
   /A simplified approach is to choose the
   default datagram size small enough to prevent fragmentation.  MTU
   size detection prior to a test is out of scope of this document.  A
   method for a path MTU size discovery, as for example proposed by
   [RFC8899], is left for future design and implementation./
- RFC8899 could indeed be applicable, but the requires support is not defined
in this specification, so this is more than a future implementation issue. This
will actually require changes to the protocol, especially if a method is to be
interoperable.
---
Topics 1. Normative Dependencies. (Thought resolved in rev-21)
I would like to discuss the normative dependence on two external references for
key components of the design. There are two Normative References to external
documents:
   [TR-471]   Morton, A,, Editor., "Broadband Forum TR-471: IP Layer
              Capacity Metrics and Measurement, Issue 4", September
              2024, <https://www.broadband-forum.org/technical/download/
              TR-471.pdf>.
   [Y.1540]   ITU-T, "Internet protocol data communication service - IP
              packet transfer and availability performance parameters",
              ITU-T Recommendation Y.1540, December 2019,
              <https://www.itu.int/rec/T-REC-Y.1540-201912-I/en>.
DISCUSS 1.1 What is the process by which these have been revised by the IETF?
(Thought resolved in rev-21, now defined in I-D.)
- I have a concern about the external definitions for terms, metrics and
algorithms used in this I-D.
---
DISCUSS 1.2 TR-471 is used to normatively define a set of parameters - this
makes the current I-D normatively dependent on changes to another spec. Has the
working group fully considered the implications of changes to these
specifications, rather than normatively defining the operation to be identical
to the current specification of this external reference?
---
DISCUSS Topics 2.   (Thought resolved in rev-21, scope identified and required
method added in I-D.) This I-D defines a protocol layered on top of UDP.
Therefore, what level of IETF review has been performed to evaluate the way the
flow rate controlled? The I-D is subject to the BCP that defines UDP Usage
[RFC8085] that sets out expectations for when the protocol is used in the
Internet. It is defined for performance testing, and as such it is possible
generate considerable Internet load.
---
DISCUSS 2.1 (Thought resolved in rev-21, scope identified in I-D.)
RFC 2914 defines the need for congestion control. Section 3.1.1, 3.1.2 and
3.1.5 of RFC 8085 provides the current BCP guidance on Congestion Control.
RFC9743 (BCP 133) provides guidance on how to specify new congestion control
methods. RFC 8084 provides an alternative, to define an envelope that controls
the overall envelope of a connection. I think these RFCs apply to this I-D to
set the envelope.
---
DISCUSS 2.3 (Thought resolved in rev-21, scope identified in I-D.)
In section 7.1: If I understand the sending rate decrease based on feedback
intervals - which seems like it is heading in the correct direction. I do not
see how these intervals are adjusted to the path RTT, could they be?
---
DISCUSS 3.1 (Thought resolved in rev-21, required method added in I-D.)
In section 7.1 there is a description of another alternative congestion control
method. Algorithm (B, see [Y.1540]) is a CC algorithm defined outside the IETF,
please explain how this has been shown to be safe for use as a CC in the
Internet?
---
DISCUSS 3.2  (Thought resolved in rev-21, required method added in I-D.)
In section 7.1: The present I-D says:
   /Algorithm B also has two modes for increasing/decreasing the sending
   rate:/
If I understand the sending rate decrease based on feedback intervals - which
seems like it is heading in the correct direction. I did not see how these
intervals adjust to the path RTT. I would like to discuss how they adapt or why
they do not?
---
DISCUSS 3.4 (Thought resolved in rev-21, required method added in I-D.)
In section 7.2, Status PDU: Please explain (and specify in the text) what
happens in the case of the first para of section 7.2 when there is severe
congestion on the return path - I assume this could result in significant loss,
and no Status PDU is sent?
   The watchdog timer at the Load PDU sender SHALL be reset each time a
   Status PDU is received.  See non-graceful test stop in Section 8 for
   handling the watchdog timeout expiration at each endpoint.
---
DISCUSS 3.5  (Thought resolved in rev-21, applicability added in I-D.)
In section 7.2, Status PDU. The present I-D says:
/ The watchdog timer at the Load PDU sender SHALL be reset each time a
   Status PDU is received.  See non-graceful test stop in Section 8 for
   handling the watchdog timeout expiration at each endpoint./
- Please explain (and specify in the text) why is it safe to reset the timer
even if the Status PDU does not indicate correct reception?
---
DISCUSS 5.1: (Thought resolved in rev-21, removed.)
What is Value A in Table 16 (PDU Rate Adjustment)?
---
DISCUSS 5.2 : (Thought resolved in rev-21, required method added in I-D.)
There is no specification in this I-D for these algorithms.
---
DISCUSS 6.2 : (resolved in rev-21)
Please add a note to the reaction to lack of feedback in Section 4.2:
I agree that "the test session will prematurely terminate (no further load
traffic SHALL be transmitted)" - To be clear about the importance, I'd
recommend to add a note saying this is necessary also to avoid potentially
inducing congestion after there is a overload/loss on the control path.
---
DISCUSS 7.1  (Resolved in rev-21, aligns with recommended usage.)
In Section 4.5 on Optional Checksum, ought to be required.
---
DISCUSS 7.2    (Resolved in rev-21, aligns with recommended usage.)
IPv6 requires a UDP checksum except for very specific usage, this does not
appear to be one of those cases (tell me if I am wrong), and so can this
require an IPv6 checksum?
---
DISCUSS Topic 8:  (Resolved in rev-21, aligns with recommended usage.)
ECN:RFC 3819 specifies the requirements for new transport methods to utilise an
ECT() code point (see also 3.1.7 of RFC 8085). The transfer as defined does not
support ECN, i.e. it does not change its rate in response to ECN marks.
---
DISCUSS 9.1 (Resolved in rev-21)
I think this looks like it has no multicast considerations and hence it ought
to be scoped to only unicast and not broadcast or multicast addresses. Could
this be specified for unicast address only ?
---
DISCUSS 9.2  (Resolved in rev-21)
Could this method be used with an Anycast address?
---
DISCUSS Topic 10: (Resolved in rev-21)
Some parameters appear underspecified in this I-D, please check. e.g.:
seqErrLoss/seqErrOoo/seqErrDup