[Tsv-art] Re: draft-ietf-bmwg-sr-bench-meth-07 ietf last call Tsvart review
Paolo Volpato <paolo.volpato@huawei.com> Thu, 13 August 2026 12:56 UTC
Return-Path: <paolo.volpato@huawei.com>
X-Original-To: tsv-art@mail2.ietf.org
Delivered-To: tsv-art@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 9ED151291F183; Thu, 13 Aug 2026 05:56:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1786625772; bh=/QiJuL6+daVN7cEbcIjgG6NK0g1gux5GuWy/U90gGgQ=; h=From:To:CC:Subject:Date:References:In-Reply-To; b=LornfkvrxLHL62kBlps+xGXdXgrByU0BmiJK/SQlHUgEr3Z+17BekulfG6EOEQOJO qxUwoZFflF5h0UeEEVMoL5/1nH1oNHrLb9FnKA269KZVKjZLag9nGADl/j+PrhSOa7 Efl3l6ilv9lPlrZvMWE9/5wGyeUzJAcdMPPAFKmw=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.094
X-Spam-Level:
X-Spam-Status: No, score=-2.094 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, RCVD_IN_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (1024-bit key) header.d=huawei.com
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 8C70BhcWUClO; Thu, 13 Aug 2026 05:56:05 -0700 (PDT)
Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id C30581291E872; Thu, 13 Aug 2026 05:46:28 -0700 (PDT)
dkim-signature: v=1; a=rsa-sha256; d=huawei.com; s=dkim; c=relaxed/relaxed; q=dns/txt; h=From; bh=/QiJuL6+daVN7cEbcIjgG6NK0g1gux5GuWy/U90gGgQ=; b=sHzxsX4pJ4ji96/Wd9lgYeYe/+SZTMfvuqRwYuKZzlcQK1/ng2fMIoBIHl2vqsQeOVdPtFZyY fiQLVHcJAquEQhC9DExRupIkpLMH/oOseMHjxRZ0s9PAAIl9s04pI09KKfoKLvOePNrkAfYKEjH KeA4Oxtpy4hXQKHAJYdfKOQ=
Received: from mail.maildlp.com (unknown [172.18.224.107]) by frasgout.his.huawei.com (SkyGuard) with ESMTPS id 4hLQ7S0FQ3zJ46Zk; Thu, 13 Aug 2026 20:45:24 +0800 (CST)
Received: from frapema500003.china.huawei.com (unknown [7.182.19.114]) by mail.maildlp.com (Postfix) with ESMTPS id 40F5C40584; Thu, 13 Aug 2026 20:46:22 +0800 (CST)
Received: from frapema500004.china.huawei.com (7.182.19.21) by frapema500003.china.huawei.com (7.182.19.114) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1544.11; Thu, 13 Aug 2026 14:46:22 +0200
Received: from frapema500004.china.huawei.com ([7.182.19.21]) by frapema500004.china.huawei.com ([7.182.19.21]) with mapi id 15.02.1544.011; Thu, 13 Aug 2026 14:46:22 +0200
From: Paolo Volpato <paolo.volpato@huawei.com>
To: Mirja Kühlewind <ietf@kuehlewind.net>
Thread-Topic: draft-ietf-bmwg-sr-bench-meth-07 ietf last call Tsvart review
Thread-Index: AQHdJlBZk36gi0BoSE6FoIUPDhg7drab87/A
Date: Thu, 13 Aug 2026 12:46:21 +0000
Message-ID: <6e2ea4458eed402da17721a261d676ea@huawei.com>
References: <178609542702.692.908034213236542075@dt-datatracker-559c48c7fb-llb9x>
In-Reply-To: <178609542702.692.908034213236542075@dt-datatracker-559c48c7fb-llb9x>
Accept-Language: it-IT, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.81.205.155]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Message-ID-Hash: P6BJWY6WXTLCCK347OE6D5PHPOYZMNKX
X-Message-ID-Hash: P6BJWY6WXTLCCK347OE6D5PHPOYZMNKX
X-MailFrom: paolo.volpato@huawei.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-tsv-art.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: "bmwg@ietf.org" <bmwg@ietf.org>, "draft-ietf-bmwg-sr-bench-meth.all@ietf.org" <draft-ietf-bmwg-sr-bench-meth.all@ietf.org>, "last-call@ietf.org" <last-call@ietf.org>, "tsv-art@ietf.org" <tsv-art@ietf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [Tsv-art] Re: draft-ietf-bmwg-sr-bench-meth-07 ietf last call Tsvart review
List-Id: Transport Area Review Team <tsv-art.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsv-art/R_GAXma3CndRx2CnCdunCMLYrUY>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tsv-art>
List-Help: <mailto:tsv-art-request@ietf.org?subject=help>
List-Owner: <mailto:tsv-art-owner@ietf.org>
List-Post: <mailto:tsv-art@ietf.org>
List-Subscribe: <mailto:tsv-art-join@ietf.org>
List-Unsubscribe: <mailto:tsv-art-leave@ietf.org>
Dear Mirja, Many thanks for your detailed review of draft-ietf-bmwg-sr-bench-meth. You will see our comments inline, marked as [PV]. Please consider that we have in plan to submit a new revision after the summer break to address the comments received. On behalf of the co-authors, Best regards Paolo -----Original Message----- From: Mirja Kühlewind via Datatracker <noreply@ietf.org> Sent: Friday, August 7, 2026 11:37 To: tsv-art@ietf.org Cc: bmwg@ietf.org; draft-ietf-bmwg-sr-bench-meth.all@ietf.org; last-call@ietf.org Subject: draft-ietf-bmwg-sr-bench-meth-07 ietf last call Tsvart review Document: draft-ietf-bmwg-sr-bench-meth Title: Benchmarking Methodology for Segment Routing (SR) Reviewer: Mirja Kühlewind Review result: Ready with Nits This document has been reviewed as part of the transport area review team's ongoing effort to review key IETF documents. These comments were written primarily for the transport area directors, but are copied to the document's authors and WG to allow them to address any issues raised and also to the IETF discussion list for information. When done at the time of IETF Last Call, the authors should consider this review as part of the last-call comments they receive. Please always CC tsv-art@ietf.org if you reply to or forward this review. This is a clearly written document! I couldn’t identify any transport issues as this is describing benchmarking and not production traffic. Some minor nits that catched my eye when reading: 1) There are some acronyms that could be extended: NFV, SUT, PSP, USP, USD, POS/PPP [PV] Ok, we'll expand the acronyms. 2) Section 2.2 >The SID list should not be tested for operations beyond the announced capabilities of OSPF or ISIS on the DUT, but, if there is an interest, it may be tested how the DUT reacts in this situation. Should normative language be used here? Otherwise I propose “is not required to test for…” [PV] We'll rephrase to be unambiguous. The meaning here is that actually, there is no need to test unwanted capabilities of the IGP protocols. > It is RECOMMENDED that the top SID on the list should emulate the traffic engineering scenario. I don’t understand this sentence. Which traffic engineering scenario is meant here? But maybe that just me… [PV] The idea is the top SID is always explicitly associated to the next hop in the SR path (for example, the top label from the "SR local block"). If the sentence is not clear we'll rephrase it in the next version of the draft. 3) Section 5 seems good advice but it’s that advice more generic than for the SR tests? [PV] Well, the point is that we are discussing lab tests, it is difficult to highlight something different. Anyway, we'll look also at section 5 to identify some more specific considerations.
- [Tsv-art] draft-ietf-bmwg-sr-bench-meth-07 ietf l… Mirja Kühlewind via Datatracker
- [Tsv-art] Re: draft-ietf-bmwg-sr-bench-meth-07 ie… Paolo Volpato