Re: Network Energy Management

Hesham ElBakoury <helbakoury@gmail.com> Sat, 06 August 2022 00:18 UTC

Return-Path: <helbakoury@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 EB2E8C15A73D for <ietf@ietfa.amsl.com>; Fri, 5 Aug 2022 17:18:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.107
X-Spam-Level:
X-Spam-Status: No, score=-7.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_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 3MOSm9QkKu9n for <ietf@ietfa.amsl.com>; Fri, 5 Aug 2022 17:18:17 -0700 (PDT)
Received: from mail-qk1-x72d.google.com (mail-qk1-x72d.google.com [IPv6:2607:f8b0:4864:20::72d]) (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 7DBB2C15A728 for <IETF@ietf.org>; Fri, 5 Aug 2022 17:18:17 -0700 (PDT)
Received: by mail-qk1-x72d.google.com with SMTP id o3so1684735qkk.5 for <IETF@ietf.org>; Fri, 05 Aug 2022 17:18:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=5mY0K26f41/5xIUF50ojK7BRA2dEOj9oBiSqJfZPQvk=; b=ansRMUIPH38N/hw25rWIcfnd1qzMmu2uD+PwYqOf3KiUw6/Wl8x+FVmZ9SNM9z7y5I 4m1x8T4HFTDqHAj4T1UeCpYfm0hdxuEukSLTA7+JyD6X4Y8a3fOVeH28Ze4dD1bUA8/N gKq45KW8tZ4eYYUl0SP2bD5TBoc5N8Pk7tiMvhxnOsUMFZX3NMvg51vYjLD35uZXAUTq jBeyBefJYVoQF46yfzkgTrgwfPp+6vvYxdr+wT47//vl5M+hafzzXO0XlWUISKpl3m2n 48z6zEAi+pYZBAHJxT4UxVVPE8e3bxrkeibQeMG0qycOUYxtvvQLvxEF/hYYwB6nDIp1 Csrw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=5mY0K26f41/5xIUF50ojK7BRA2dEOj9oBiSqJfZPQvk=; b=S91U8lD+hv57tOttup2dO71nT/Dy0SAnaS7mYn3J0sqZLhxKfZ8xahJnoeuhpRzGvU Ceyo6LcPJ2E756vdFWPyMQjTCa3uuaSuR6S4s3jOOyWsQPasY6KwzQfTS4ePICOPNg6r LMjxaMy7bZNOY0aiBeIiDHYMOc+wWtSOslJVgi8BPq3Ai/O7YfdYSHigyux2mRPYC6HS BKkqgirTC2v1Mokp8yKIDFx1rVVAav4vouk8/SwINoovsklLpN96cfLhzmrESpRp71dL QGoZlKCfaB/8DqC0WtRLi5ygkmEXvj2VcU6CQ6ov844TBhs5cS+Hzu7m2unrwWlgK2kg mXJA==
X-Gm-Message-State: ACgBeo3iM9bhqfD2PQ9S9rJnyX9kXFIdjxZ0PUIU5wIAnngGfd7N2i9s 7Yx6p4K4LRcqhQVdG1MzLGcW0VwPmZob3M9T8parhOIm
X-Google-Smtp-Source: AA6agR7pzDZlxhAze+MYgwsqgj/Stw5HhWyUkzyNn6lWvmU80qDhYFzRp0fiftobnAOv6QjT5Ke00698BcCxyIWW++U=
X-Received: by 2002:a05:620a:40d5:b0:6b8:ef34:fee6 with SMTP id g21-20020a05620a40d500b006b8ef34fee6mr7004623qko.639.1659745096072; Fri, 05 Aug 2022 17:18:16 -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: Hesham ElBakoury <helbakoury@gmail.com>
Date: Fri, 05 Aug 2022 17:18:03 -0700
Message-ID: <CAFvDQ9q2O2c7oi=4V=9CAHWUa_GiqMgJOTqfjY7SyLKaL=Kcsw@mail.gmail.com>
Subject: Re: Network Energy Management
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Cc: Joel Halpern <jmh@joelhalpern.com>, Fred Baker <fredbaker.ietf@gmail.com>, IETF <IETF@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000de7ffb05e587845c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/DNVdnxmRsv46KWjj7_T2yHjapm4>
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: Sat, 06 Aug 2022 00:18:18 -0000

Jari Akkro mentioned during IAB opening that he plans to have a workshop on
energy management. He is supposed to send the announcement after IETF 114.

To save energy used by this workshop, we can have it online in which case
we will sacrifice the benefits of F2F interactions.

Hesham

On Fri, Aug 5, 2022, 4:42 PM 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?
> >>
>