Re: Network Energy Management

Nevil Brownlee <nevil.brownlee@gmail.com> Sun, 07 August 2022 00:16 UTC

Return-Path: <nevil.brownlee@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 AC16CC157B5C for <ietf@ietfa.amsl.com>; Sat, 6 Aug 2022 17:16:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.107
X-Spam-Level:
X-Spam-Status: No, score=-2.107 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, HTML_MESSAGE=0.001, 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 nRIQMgFlzQoY for <ietf@ietfa.amsl.com>; Sat, 6 Aug 2022 17:16:27 -0700 (PDT)
Received: from mail-io1-xd34.google.com (mail-io1-xd34.google.com [IPv6:2607:f8b0:4864:20::d34]) (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 3C5BCC157B5B for <IETF@ietf.org>; Sat, 6 Aug 2022 17:16:27 -0700 (PDT)
Received: by mail-io1-xd34.google.com with SMTP id e69so4585808iof.5 for <IETF@ietf.org>; Sat, 06 Aug 2022 17:16:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc; bh=/sGB1by7eGXMxR3HR9k2b60I4oP9gyrkMYRcA54UqFQ=; b=SKateK3hH4dlywU/Nqrc0sSpPu+MrYmIwJQ/0b0kzmVkzPpxia5Xp1O/2ml2noSyU9 1L0G+BPr+jVjUHYAIkfHbg6KP1TzFGRR6+w/GN226iz9G06ERR1BAipLUu3NPiQrsI2Y CuY46IlV1lj7zbiwC8HDE3n/WhqyaL2y1aRgf0IcTAb+IevqFTk/7Gwk2nvEsxzj2PdB 1AfQl1/FqUb94cHCyFlwvnk8eSrbGrB/9GkKVr2tT269eFwcAbfk8wueTPWp6YTJV5SP OJ2cz6GMGxrwCvZBJWJkitJXeOzvTtB4gYC5fLw0NKhVQbVjJptN822wILxGcxoS79KK uqgQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc; bh=/sGB1by7eGXMxR3HR9k2b60I4oP9gyrkMYRcA54UqFQ=; b=lsI6QCq0AqvMFTNx5KwgJkOkucYmwgBafF/sIZmvzTPn/SAMcs0KwH8YEkokcl6Duo wkTE/Ke+1IeRrOm4YA2CcYsIbgTH6AaPwz/1Md5j24B/jHr0GTZ23ivSFz+oH5LNKGZO tSnaExpwfHoLUMcHwy+OafCy2BFuWLfBsPkFW25oo/AQxXgCAA/Psr7KtUexNgAXLUSb 3H44fMsIlhLZ/J/tJSNHdWgJkIgcU+tsyFbbj1D9u92uUOHVjn3ZvI5H337uYGWJJhry ViTrXioumVR9T5WRIu1evQ0yjncNPP9jjE0di9D7//bqlXjMcliIaie5c7P7GZJTM5Vl iwZQ==
X-Gm-Message-State: ACgBeo0LSI5UwlQQecS5ok5ImiSUJLShYFoFwWwA3gjKJ+mNE0nYgfxG 0KAcbWjV4B+K1WYiAcTHKRZhZzNZROFwXvkLjU0=
X-Google-Smtp-Source: AA6agR55/YhTzQgIJUGLhlIs0SHjxGin6l3XhSGFyl24kekeH/A8+O0uQBHUR5mnivbEpDQwRw/gVYeAqiYZHjbhLkc=
X-Received: by 2002:a6b:671e:0:b0:684:5b48:659e with SMTP id b30-20020a6b671e000000b006845b48659emr2219943ioc.174.1659831386275; Sat, 06 Aug 2022 17:16:26 -0700 (PDT)
MIME-Version: 1.0
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> <724ed1d0-fcc3-272c-708b-3911e6146148@gmail.com>
In-Reply-To: <724ed1d0-fcc3-272c-708b-3911e6146148@gmail.com>
From: Nevil Brownlee <nevil.brownlee@gmail.com>
Date: Sun, 07 Aug 2022 12:15:59 +1200
Message-ID: <CACOFP=hZgNW7p2OHSPEe6WBSfQ3hKF=E8XmOsOHtuHJJX=B74g@mail.gmail.com>
Subject: Re: Network Energy Management
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Cc: IETF <IETF@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000002a823005e59b9c41"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/8s-1wuuyhHcA_Fr9KIPzhEW1n54>
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: Sun, 07 Aug 2022 00:16:27 -0000

Ahem, the IETF did have an Energy Management WG, eman, which published
several RFCs.  Of those, 6988 Requirements for Energy Management, and
7326 Energy Management Framework, seem relevant to this thread.
Of course, eman focussed on device management rather than protocol design -
but that now seems important too.

Cheers, Nevil

On Sat, Aug 6, 2022 at 11:43 AM Brian E Carpenter <
brian.e.carpenter@gmail.com> wrote:

> 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?
> >>
>


-- 
-----------------------------------
Nevil Brownlee, Taupo, NZ