[Green] Re: [bmwg] Re: draft-ietf-bmwg-powerbench

"Chengen(GenChen)" <chengen@huawei.com> Tue, 25 August 2026 09:09 UTC

Return-Path: <chengen@huawei.com>
X-Original-To: green@mail2.ietf.org
Delivered-To: green@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 6972A12EF5DB8; Tue, 25 Aug 2026 02:09:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1787648986; bh=gm7KXDqjwZWUfB2V6+EJvtf9zDtWtL0ExrJnJjz4dgo=; h=From:To:CC:Subject:Date:References:In-Reply-To; b=FbySDJ9+u5km+ZyCBmDZXm2gQmZk+GH3AguYqV0iIdCBRR4XxUe+Afx84nZqizVAI GTCld8aDxSOxXO1IKx5aj6VBvsbE5GvnYN3NrnInF2+I6J3D7Hc7xfJKePCyTNLCkM oBOCW7dqwVqoBKKu+KM3pJitFPkBbfNrQPviv5eE=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.793
X-Spam-Level:
X-Spam-Status: No, score=-2.793 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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=ham 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 5A7jLG3C-k_B; Tue, 25 Aug 2026 02:09:44 -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 1A33112EF5DB1; Tue, 25 Aug 2026 02:09:44 -0700 (PDT)
dkim-signature: v=1; a=rsa-sha256; d=huawei.com; s=dkim; c=relaxed/relaxed; q=dns/txt; h=From; bh=gm7KXDqjwZWUfB2V6+EJvtf9zDtWtL0ExrJnJjz4dgo=; b=1sl+GipgjOJIPdFQ4kbL+K82En363N2jGnSjDC8YyJwExLMNxdnkFqW+VXDslgQUy861gzV9D B8ieCBKN5zhW8ZTXY7K+7BFIE7biMxojrQPebuvouegmibQmaXNiRc2hxXaM6pOa843qrhTAZq5 tx28oOMnFdQeRH9mPzCLWg0=
Received: from mail.maildlp.com (unknown [172.18.224.107]) by frasgout.his.huawei.com (SkyGuard) with ESMTPS id 4hThmT6Td6zJ46bN; Tue, 25 Aug 2026 17:09:13 +0800 (CST)
Received: from kwepemh500011.china.huawei.com (unknown [7.202.181.142]) by mail.maildlp.com (Postfix) with ESMTPS id 75B084058B; Tue, 25 Aug 2026 17:09:31 +0800 (CST)
Received: from dggpemf500004.china.huawei.com (7.185.36.213) by kwepemh500011.china.huawei.com (7.202.181.142) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1544.11; Tue, 25 Aug 2026 17:09:23 +0800
Received: from dggpemf200006.china.huawei.com (7.185.36.61) by dggpemf500004.china.huawei.com (7.185.36.213) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1544.11; Tue, 25 Aug 2026 17:09:23 +0800
Received: from dggpemf200006.china.huawei.com ([7.185.36.61]) by dggpemf200006.china.huawei.com ([7.185.36.61]) with mapi id 15.02.1544.011; Tue, 25 Aug 2026 17:09:23 +0800
From: "Chengen(GenChen)" <chengen@huawei.com>
To: "Benoit@everything-ops.net" <benoit@everything-ops.net>, Marisol <marisol.ietf@gmail.com>, "mohamed.boucadair@orange.com" <mohamed.boucadair@orange.com>
Thread-Topic: [Green] Re: [bmwg] Re: draft-ietf-bmwg-powerbench
Thread-Index: AQHdM+PBi3IMmz1Xr0mOI4DHNwK0xbauc+aw
Date: Tue, 25 Aug 2026 09:09:22 +0000
Message-ID: <7b6a2504ea884f4db1322b0cd1594668@huawei.com>
References: <PAUP264MB6756A6C01926274D6B2CD5D288C02@PAUP264MB6756.FRAP264.PROD.OUTLOOK.COM> <CAO+xsekVhAnONnTOSrj=ZGvVh4AEnu=hiJKpEwUT6a+=mXrmNg@mail.gmail.com> <028a3957-7173-4b97-bc1a-22a2609b0a60@everything-ops.net>
In-Reply-To: <028a3957-7173-4b97-bc1a-22a2609b0a60@everything-ops.net>
Accept-Language: zh-CN, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.164.112.208]
Content-Type: multipart/alternative; boundary="_000_7b6a2504ea884f4db1322b0cd1594668huaweicom_"
MIME-Version: 1.0
Message-ID-Hash: JFTXQXHEBDHCUGWILSEDUKJURHSKLYTY
X-Message-ID-Hash: JFTXQXHEBDHCUGWILSEDUKJURHSKLYTY
X-MailFrom: chengen@huawei.com
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: Getting Ready for Energy-Efficient Networking Discussion List <green@ietf.org>, bmwg <bmwg@ietf.org>, ippm <ippm@ietf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [Green] Re: [bmwg] Re: draft-ietf-bmwg-powerbench
List-Id: Getting Ready for Energy-Efficient Networking WG <green.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/green/Po5_7Bkg18j_j-KIIDhquGkl6Yg>
List-Archive: <https://mailarchive.ietf.org/arch/browse/green>
List-Help: <mailto:green-request@ietf.org?subject=help>
List-Owner: <mailto:green-owner@ietf.org>
List-Post: <mailto:green@ietf.org>
List-Subscribe: <mailto:green-join@ietf.org>
List-Unsubscribe: <mailto:green-leave@ietf.org>

Hi Benoit and All,

Based on the initial review of the GREEN and BMWG power/energy drafts, I would like to propose the following three alignment issues and potential optimization directions.

1. Power Measurement states in the BMWG draft to be aligned with GREEN Power State
Issue: The BMWG draft defines five power measurement states (Base, Idle, Idle+, Typical, and Power with Traffic Load). The term "low-power mode" appears once in the Idle and Idle+ power measurement description, but no explicit mapping to GREEN's "Power State" concept.
Potential Optimizations: BMWG draft to explicitly mention in its five measurement states to consider the GREEN Power States info for reference, the existing "low-power mode" reference to be aligned with GREEN's Power State taxonomy.

2. EER Definition Alignment
Issue: GREEN draft defines EER using total throughput while BMWG draft defines EER using weighted throughput.
Potential Optimizations: GREEN draft to update its EER definition to clarify using both NDR-based total throughput and weighted throughput meet the requirement as they have linear relationship.

3. Traffic Model Definition in GREEN
Issue: GREEN terminology currently lacks any traffic model definitions. BMWG uses traffic type (IMIX or rfc2544 packets), load levels (e.g., 0%/30%/100%), and weighting factors (Bi) without foundational terminology in GREEN.
Potential Optimizations: Add to GREEN terminology Traffic Model (traffic mix, load levels, weighting factors). BMWG draft to reference these GREEN terms where it uses traffic type, load levels and weighting factors.

BR,
GenChen


From: Benoit@everything-ops.net <benoit@everything-ops.net>
Sent: 2026年8月25日 0:15
To: Chengen(GenChen) <chengen@huawei.com>; Marisol <marisol.ietf@gmail.com>; mohamed.boucadair@orange.com
Cc: Getting Ready for Energy-Efficient Networking Discussion List <green@ietf.org>; bmwg <bmwg@ietf.org>; ippm <ippm@ietf.org>
Subject: Re: [Green] Re: [bmwg] Re: draft-ietf-bmwg-powerbench

Dear all,
On 23/07/2026 13:26, Chengen(GenChen) wrote:
Hi All,

I agree with Marisol and would like to emphasize the following points.

1. The two efforts are complementary without conflict. BMWG doc addresses offline laboratory power measurement and benchmarking, while GREEN docs focuse on online energy monitoring and energy management for live network operations.
Complimentary but terribly aligned.
https://datatracker.ietf.org/doc/html/draft-ietf-bmwg-powerbench figure 1 is completely aligned with figure 3 in https://datatracker.ietf.org/doc/draft-ietf-green-framework/
The fact that the BMWG document focuses on a DUT in lab, as opposed to the GREEN one that focuses on a real device with a physical meter, is not that important.
Both uses the Metering Relationship relationship
​
2. Terminology and metrics need joint review. BMWG shall extend based on GREEN’s foundational terminology and metrics, instead of defining separate standalone vocabulary. Cross review is essential to prevent inconsistent semantics.
Yes, please.
​
3. The BMWG doc may elaborate on lab measurement precision, relationship properties and fundamental measurement capabilities, and clarify how offline benchmark measurements can align with GREEN-defined base policies.
Even if we know that BMWG uses the DUT as black box, it would great to know the DUT Power State.

Regards, Benoit

BR,

Genchen

发件人:Marisol <marisol.ietf@gmail.com<mailto:marisol.ietf@gmail.com>>
收件人:mohamed.boucadair@orange.com<mailto:mohamed.boucadair@orange.com> <mohamed.boucadair@orange.com<mailto:mohamed.boucadair@orange.com>>
抄 送:Getting Ready for Energy-Efficient Networking Discussion List <green@ietf.org<mailto:green@ietf.org>>;bmwg <bmwg@ietf.org<mailto:bmwg@ietf.org>>;ippm <ippm@ietf.org<mailto:ippm@ietf.org>>
时 间:2026-07-23 11:31:09
主 题:[bmwg] Re: [Green] draft-ietf-bmwg-powerbench

Hi Med,
this might require a bit more time, but now that we are still in
Vienna, and we can discuss things "life" just want to highlight a few
things.


PowerBench defines a laboratory benchmarking methodology,  under
controlled conditions.
The consideration for PowerBench is to have external Power Meter
measuring PSU input power on a Device Under Test (DUT) under
controlled traffic loads. It is not an operational monitoring
framework.
This distinction is important: GREEN is about what a device reports
about itself during operations;
PowerBench is about what an external instrument measures in a test
lab. They are complementary, not competing.
I think PowerBench it is ideal to deep dive in idle power and give
some baseline for some of the real time measurements considered in
GREEN WG, setting up thresholds to consider in operations.


* PowerBench defines EER:
PowerBench gives it a name, a unit, and a precise method/formula. The
GREEN framework discusses the concept but never settles on a formula
or name. Im not convinced we need to include it in GREEN framework
though.
There are other terminology that should be aligned or mentioned in the
terminology GREEN draft:
* Total Power (PowerBench) and total-power-input(GREEN) at device
level are equivalent terms
* Base Power(PowerBench), No GREEN power-state maps to this exactly
>>> to be considered in GREEN data model
* Idle Power and Typical power (PowerBench), not alignment in GREEN
* Alignment on the  measurement accuracy from GREEN is missing in
PowerBench: PowerBench uses an external Power Meter measuring PSU,
this should corresponds idealy with accuracy-measured-gold
* The GREEN power state model (power-state-on/off/low-power), has been
discussed in the working group already, but it is not aligned with
powerbench:  Base → Idle → Idle+ → Typical → Full Load.
* PowerBench lists RFC 7460 (EMAN MIB) as a normative reference, I
think it should be informative. And make a note for informative
reference as well for GREEN YANG data model as it replaces RFC 7460,
and framework.
* PowerBench Reporting Format can maps almost entirely onto GREEN YANG leaves.


rgds,
Marisol

Marisol Palmero
https://tidycal.com/marisolietf


On Thu, Jul 23, 2026 at 9:32 AM <mohamed.boucadair@orange.com><mailto:mohamed.boucadair@orange.com> wrote:
>
> Hi all,
>
>
>
> draft-ietf-bmwg-powerbench was just presented in IPPM/BMWG joint session. It would be appreciated if some volunteers here in GREEN can look into that document and share comments with IPPM/BMWG.
>
>
>
> Thank you.
>
>
>
> Cheers,
>
> Med
>
> ____________________________________________________________________________________________________________
> Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
> a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
> Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
>
> This message and its attachments may contain confidential or privileged information that may be protected by law;
> they should not be distributed, used or copied without authorisation.
> If you have received this email in error, please notify the sender and delete this message and its attachments.
> As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
> Thank you.
>
> _______________________________________________
> Green mailing list -- green@ietf.org<mailto:green@ietf.org>
> To unsubscribe send an email to green-leave@ietf.org<mailto:green-leave@ietf.org>

_______________________________________________
bmwg mailing list -- bmwg@ietf.org<mailto:bmwg@ietf.org>
To unsubscribe send an email to bmwg-leave@ietf.org<mailto:bmwg-leave@ietf.org>



_______________________________________________

Green mailing list -- green@ietf.org<mailto:green@ietf.org>

To unsubscribe send an email to green-leave@ietf.org<mailto:green-leave@ietf.org>