[ippm] draft-ietf-ippm-capacity-protocol-16 telechat Perfmetrdir review
Giuseppe Fioccola via Datatracker <noreply@ietf.org> Tue, 13 May 2025 12:51 UTC
Return-Path: <noreply@ietf.org>
X-Original-To: ippm@ietf.org
Delivered-To: ippm@mail2.ietf.org
Received: from [10.244.8.181] (unknown [104.131.183.230]) by mail2.ietf.org (Postfix) with ESMTP id 9E47B27F1089; Tue, 13 May 2025 05:51:22 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Giuseppe Fioccola via Datatracker <noreply@ietf.org>
To: pm-dir@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 12.39.2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <174714068249.1796617.14353923603014757380@dt-datatracker-58d4498dbd-6gzjf>
Date: Tue, 13 May 2025 05:51:22 -0700
Message-ID-Hash: P5JUQUWAHTJII76PC3HIDBKNMU3X6TG7
X-Message-ID-Hash: P5JUQUWAHTJII76PC3HIDBKNMU3X6TG7
X-MailFrom: noreply@ietf.org
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.all@ietf.org, ippm@ietf.org, last-call@ietf.org
X-Mailman-Version: 3.3.9rc6
Reply-To: Giuseppe Fioccola <giuseppe.fioccola@huawei.com>
Subject: [ippm] draft-ietf-ippm-capacity-protocol-16 telechat Perfmetrdir review
List-Id: IETF IP Performance Metrics Working Group <ippm.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ippm/heZHzErCSho-LtzI_BxF8pCtwuw>
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>
Document: draft-ietf-ippm-capacity-protocol Title: Test Protocol for One-way IP Capacity Measurement Reviewer: Giuseppe Fioccola Review result: Has Issues This document specifies the UDP Speed Test Protocol (UDPSTP) which enables network capacity measurements, as defined by RFC 9097. While I found the document useful and well-written, it left me with some questions. >From a PERFMETRDIR point of view, I think that some clarification would be helpful, in particular: - In the Introduction, it is mentioned that this new protocol supports measurement features which were not available by standard measurement protocols, such as OWAMP, TWAMP, STAMP etc. For sake of clarity, it would be good to clarify the motivation and explain why you chose to design a new protocol instead of extending existing tools to implement the capacity measurement. - In section 2, I think it is necessary to specify better the applicability. I guess the method can be applied in different scenarios, e.g. controlled domain or connection over the internet. I would highlight the different aspects, especially in terms of security, based on the application. - Section 4.2 and section 2 could be related. If section 2 will be improved by adding the possible applicability scenarios, the different security mode operations of section 4.2 can be linked to those scenarios. - In section 6.2.1, it is mentioned that the server has the option to modify the request made by the client. If I have understood correctly looking at section 6.3, when the client receives the response it can only accept the test parameters modified by the server and the negotiation ends, right? I suggest to make it clearer. - Since section 9 is quite short, I would suggest to incorporate its content elsewhere in the document, maybe in section 2. Therefore, section 9.1 can become section 9 or moved too.
- [ippm] draft-ietf-ippm-capacity-protocol-16 telec… Giuseppe Fioccola via Datatracker
- [ippm] Re: draft-ietf-ippm-capacity-protocol-16 t… Ruediger.Geib
- [ippm] Re: draft-ietf-ippm-capacity-protocol-16 t… Giuseppe Fioccola