IETF Logo Mail Archive

Re: Network Energy Management

Brian E Carpenter <brian.e.carpenter@gmail.com> Fri, 05 August 2022 23:42 UTC

Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1DE20C15949B for <ietf@ietfa.amsl.com>; Fri, 5 Aug 2022 16:42:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.109
X-Spam-Level:
X-Spam-Status: No, score=-7.109 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, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 Jes9qqWDoQ_B for <ietf@ietfa.amsl.com>; Fri, 5 Aug 2022 16:42:44 -0700 (PDT)
Received: from mail-pl1-x62d.google.com (mail-pl1-x62d.google.com [IPv6:2607:f8b0:4864:20::62d]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BAB09C15948C for <IETF@ietf.org>; Fri, 5 Aug 2022 16:42:44 -0700 (PDT)
Received: by mail-pl1-x62d.google.com with SMTP id x10so3892661plb.3 for <IETF@ietf.org>; Fri, 05 Aug 2022 16:42:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc; bh=FaLZejC5KZzV7dMLJo2pHb+KqShy2zjIMXZg599Jq8c=; b=VYIpfh4Ebfp88Yilkghum944vzE5wgOrEYO+VsYFI8lSvtaKFmv7f3X6wM6eRdJO4U wJJPKK2wKsTYaRbYmiHCIcWrhwxdWU5qIH2GoxHcXm4uGZ6bi/xMSvj3NV03vOakTil6 m8acYYFT+OaOuncRH/sQ2LgXWFhGfoa81Nv6MJ9++YBhphsmWkfvMkvVc9dLVIirpUJ6 sjB6p23T0C03EtibCyhlLJyjgI709sc3ac5aVf5KEXzLzlNOTCEkeeDw+64s1aOCECbP OqXM4smQnauiAn8rrY4e0HcPz9GJvTBkG1NY9v6vdyODVzEgJ/HXtaehnSroewt2UZUL GMzQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc; bh=FaLZejC5KZzV7dMLJo2pHb+KqShy2zjIMXZg599Jq8c=; b=7bYaMfClkoLDqsKnKF7sQvturM/x8Oyoao398iOcrXtPYWjY6G3tKWp32q8PZDAARK 5iBDBZQiYQiVci6yX8Z3D89r1HTwLlyhpDcjRGQcn98SsItM80yHrIhfmH3Sfm3oC9nt W0hL0Df8SDPVr866LQkisKU3IyyQX7ju8h6L8XusD3GTYk7LEka+3I84YDaiFKP/UBSc Wo9MhXaYjXMsb++IM5umKTcyqhmfnXZXo32v9lok8lx6ERdrDVEcRm7FVXsqET0132H1 JdYVTzFnAsBuq0g9EmR3PJn4Y6dFZWnLDQmZy2Z0dt1zdYj1WkkYQtxINhwV//2m9gGM EoJw==
X-Gm-Message-State: ACgBeo0GjMvPPjIXE7+w01ChFzRSx4c8FFexJb6XoUWyBwkiIm2hN3wu yA26cc2A8zMf97cunrYL/aA=
X-Google-Smtp-Source: AA6agR5Ki+eGTLebYjp29j0ZBpHhiLWNPA+T4F90rVy2rkFNpTek/UJnjTcgza0tKZBIdzrWLM0OHg==
X-Received: by 2002:a17:902:8d8a:b0:16f:21fb:b97a with SMTP id v10-20020a1709028d8a00b0016f21fbb97amr8861709plo.160.1659742964064; Fri, 05 Aug 2022 16:42:44 -0700 (PDT)
Received: from ?IPV6:2406:e003:1124:9301:80b2:5c79:2266:e431? ([2406:e003:1124:9301:80b2:5c79:2266:e431]) by smtp.gmail.com with ESMTPSA id u11-20020a170902e5cb00b0016b8746132esm3702832plf.105.2022.08.05.16.42.41 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 05 Aug 2022 16:42:43 -0700 (PDT)
Message-ID: <724ed1d0-fcc3-272c-708b-3911e6146148@gmail.com>
Date: Sat, 06 Aug 2022 11:42:39 +1200
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.10.0
Subject: Re: Network Energy Management
Content-Language: en-US
To: Joel Halpern <jmh@joelhalpern.com>, Hesham ElBakoury <helbakoury@gmail.com>, Fred Baker <fredbaker.ietf@gmail.com>
Cc: IETF <IETF@ietf.org>
References: <8FBAF87A-2690-4543-9713-0F22D1423B8E@gmail.com> <A8687A4E-BA7A-4375-B7E2-C57ADD396842@gmail.com> <CAFvDQ9r-G8O8dzYBvrdzorVHyAE=Edbb7FZkCzrhTzLh98DyAQ@mail.gmail.com> <8f308769-ad04-8f97-7a84-5f98ba27afee@joelhalpern.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
In-Reply-To: <8f308769-ad04-8f97-7a84-5f98ba27afee@joelhalpern.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: base64
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/OBHYJ5p9XfJH7xGsOPszd8KD5rU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Aug 2022 23:42:45 -0000

Two points:

1. It might be worth an effort to see if there are existing knobs to tweak for sustainability. For example, every recommended repetition rate for discovery or refresh messages, especially multicast, could be reviewed to see if it can usefully be slowed down. Every link-local protocol could be reviewed for compatibility with wake-on-LAN.

2. Network Energy Management could be a good topic for an IAB workshop or program.

Not a joke: before investing much effort in this topic, we should consider whether that effort (e.g. convening a workshop) will consume more energy than it saves.

Regards
    Brian

On 06-Aug-22 11:22, Joel Halpern wrote:
> I can't speak for Fred, but I don't think we as a community even know what "energy efficient protocol" means.  Much less how that trades off against all the other aspects of protocol design.
> 
> We do consider message size and frequency when we design protocols.  We consider those aspects along with lots of others. if that is "designing energy efficient protocols" then we already do so.  On the other hand, design for issues such as to to partially wake up a sleeping device is generally outside our remit and skill set.  And is meaningless for many of our devices.
> 
> Yours,
> 
> Joel
> 
> On 8/5/2022 7:18 PM, Hesham ElBakoury wrote:
>> Hi Fred,
>> Do you think  IETF engineers have the skill sets to design energy efficient protocols or enhance existing ones to be more energy efficient ?
>>
>> Thanks,
>> Hesham
>>
>> On Fri, Aug 5, 2022, 1:22 PM Fred Baker <fredbaker.ietf@gmail.com> wrote:
>>
>>     Echoing a previous post, I’m not sure sustainability is part of our skill set. If we were to try to forcibly add it, I suspect we’d get the same level of response security originally got: “sustainability is not specified in this document”.
>>
>>     Sent using a machine that autocorrects in interesting ways...
>>
>>     > On Aug 5, 2022, at 2:26 AM, Stewart Bryant <stewart.bryant@gmail.com> wrote:
>>     >
>>     > Perhaps it is time for a new mandatory section in RFCs: sustainability?
>>

v2.23.0 | Report a Bug | By Email