Re: [recipe] And another new draft revision: Green Networking Metrics

Alexander L Clemm <ludwig@clemm.org> Tue, 21 February 2023 00:33 UTC

Return-Path: <ludwig@clemm.org>
X-Original-To: recipe@ietfa.amsl.com
Delivered-To: recipe@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 240B1C169509; Mon, 20 Feb 2023 16:33:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.898
X-Spam-Level:
X-Spam-Status: No, score=-6.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_NONE=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IM44kby5UwBN; Mon, 20 Feb 2023 16:33:50 -0800 (PST)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.196]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6D420C15155E; Mon, 20 Feb 2023 16:33:50 -0800 (PST)
Received: from [172.16.0.44] ([73.189.160.186]) by mrelay.perfora.net (mreueus003 [74.208.5.2]) with ESMTPSA (Nemesis) id 0MEovc-1pJqT90kEU-00G1SF; Tue, 21 Feb 2023 01:33:49 +0100
Message-ID: <341227d4-9d8b-7d82-13cd-ff458e5fbca1@clemm.org>
Date: Mon, 20 Feb 2023 16:33:47 -0800
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.7.2
Content-Language: en-US
To: recipe@ietf.org, e-impact@ietf.org
References: <d90dc815-5de2-32ca-cab6-84f53fc29451@clemm.org> <3496a0c0-1659-a1e2-8ad4-08f932ec4b51@gmail.com>
From: Alexander L Clemm <ludwig@clemm.org>
In-Reply-To: <3496a0c0-1659-a1e2-8ad4-08f932ec4b51@gmail.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
X-Provags-ID: V03:K1:+fG0TzBzFW2VCWz366jrYEnM6X7iaOQnLbU713QhdElJuRbdsmZ sYOAk7JOeBC9GkfAOVxhfB4KKFVacGj3qHvKY9b5hU7YY0kax8M7pYdTQKdp0SkuHG5nesc oCD4Dp8NJ1SsDrZ+Ln6MJdxlOYX8CFJv75/w50koTVrPPxOM7ie5jt+eD/vRsglCkljK064 FkrfMKab12IIzrS3UgFtw==
UI-OutboundReport: notjunk:1;M01:P0:J40XMyLQiRY=;VdcHrqL8NmAYZai/K0YYk5mx3lJ hFLkxg1F2KdZI4CAij5FZbWRhwiNJIuaqS7BaGLHWHbgVa1TrdmSNOSyVhNUmmfeSv9+sCb4J /b4k/PeeOk1sfA195oqqAZHPhA4gDceO2FtdXBtCKOTWXhfnUoya4FjeK4DRc8rsWfqidmDZs AC0iVFHuv/+nsXWPJ59x00PfSVrLUoP2m6VGiEnb3nqOzBSUzG4XOx2xBUKRtvDC/Z3dxZbbT gLMN6kR71JRC9/hfsInXslbcE4+n/683BcUvF/BUssRZDiOkI0DpokuwZ0dZ1doq/e1hFjT0x 65GeKii2Btiy6OUHEtHiv55D8LENX5wZEjjB/JWtvQrYYHqjTbioGuIZ2VJqt39kbKXNmxY+N Rdbzd5YB/yP/DEOF4lOcnOlcxXfb/N2+FrNEURRMT1xDZBOE20HyeLBWAvUX3mprbzerHvtur D2r4RaPLZ9aOfZSWTChoIBot+3dwHOvFwHB7EuFjGYXY1bYMmPbQYcVmYpBm6OkhBsgzMtpEi /W5mRXnmwhYsH1pS77213u8Otwit7Ez/pUisUCmxEmU/B+EceBZ5KAHKPCGkvisxFGttTivHr 7nytWWnFOcb/OQBkVdBCWg6PNZ8UxqvqOyNBm90qUtJJbXh5p83aW+T67A5t2xJ7XgATExoqa IBLnPwW8JS89+XFQ/3bVngj4ssGX98nw2R6x0nOK6A==
Archived-At: <https://mailarchive.ietf.org/arch/msg/recipe/wu4MjF-Icglp39Lfqk2otKfviL8>
Subject: Re: [recipe] And another new draft revision: Green Networking Metrics
X-BeenThere: recipe@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "RECIPE \(Reducing Energy Consumption with Internet Protocols Exploration\)" <recipe.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/recipe>, <mailto:recipe-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/recipe/>
List-Post: <mailto:recipe@ietf.org>
List-Help: <mailto:recipe-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/recipe>, <mailto:recipe-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Feb 2023 00:33:55 -0000

Hi Alex,

thank you for the pointer to your past draft.  Apparently it was never 
posted in IETF but it can be found on ResearchGate. Clearly, the metrics 
associated with sending and receiving a packet in your draft are 
relevant also to the draft here. An interesting aspect from your draft 
is to express lower and upper bounds to express a range or degree of 
certainty.

What the Green Networking Metrics draft does not plan to address, but 
what is the focus of your prior work, concerns the specification of 
solutions that would actually make use of those metrics.  You mentioned 
that you had an implementation; could you share what happened with this 
and if it was found useful? It would be great to have some use cases 
with positive experience reports to point to.

Kind regards
--- Alex

(Crossposting to the e-impact mailing list as it was proposed to move 
the energy-related discussion from recipe to there.)

On 1/9/2023 6:30 AM, Alexandre Petrescu wrote:
> Hi,
>
> Thank you for this draft.
>
> I find it to contain some idea that was too valuable to some of us 
> here, a while back.  We wrote a draft about "Energy Metrics for IPv6 
> Links" but I cant remember whether we published it or not. See it 
> attached. (the missing 'a' from author is on purpose).
>
> We had an implementation of the IPv6 energy routing metrics in OSPF 
> and and RA, in a context of an in-home network and 
> IPv6-over-powerline-communications.
>
> For reading convenience I paste below the center of the ToC:
>
> 3. Energy Encoding as a Metric for Links . . . . . . . . . . . . 7
> 3.1. The Proposal . . . . . . . . . . . . . . . . . . . . . . . 7
> 3.2. Other Concepts of Energy for Links . . . . . . . . . . . . 8
> 4. Energy Metric Option in Router Advertisement . . . . . . . . . 9
> 5. Energy Metric Encoded in RIPng RTE . . . . . . . . . . . . . . 11
> 6. Energy Metric Encoded in OSPF Opaque LSA . . . . . . . . . . . 14
> 7. Potential Applications . . . . . . . . . . . . . . . . . . . . 18
> 7.1. Common Representation of Energy Data . . . . . . . . . . . 18
> 7.2. Devices Lacking Energy Management Chipset . . . . . . . . 18
> 7.3. Energy-aware Default Route Choice . . . . . . . . . . . . 18
> 7.4. Energy-aware Shortest Paths . . . . . . . . . . . . . . . 18
> 8. Hardware Representations . . . . . . . . . . . . . . . . . . . 19
> 8.1. OMAP TPS65950 MADC repr for Power Management . . . . . . . 19
> 8.2. PM7500 . . . . . . . . . . . . . . . . . . . . . . . . . . 19
> 8.3. Xscale . . . . . . . . . . . . . . . . . . . . . . . . . . 19
> 9. How to Measure Energy for Links . . . . . . . . . . . . . . . 20
> 10. Security Considerations . . . . . . . . . . . . . . . . . . . 21
>
> Alex
>
>
>
> Le 21/10/2022 à 05:53, Alexander Clemm a écrit :
>> As subject line:  FYI, we have just posted a new revision of 
>> draft-cx-green-metrics, "Green Networking Metrics", here: 
>> https://datatracker.ietf.org/doc/draft-cx-green-metrics/
>>
>> The updates are mostly of a relatively minor nature to provide 
>> further editorial quality.
>>
>> --- Alex (on behalf of coauthors)
>>
>> _______________________________________________
>> recipe mailing list
>> recipe@ietf.org
>> https://www.ietf.org/mailman/listinfo/recipe