Re: Network Energy Management

Stewart Bryant <stewart.bryant@gmail.com> Sat, 06 August 2022 08:20 UTC

Return-Path: <stewart.bryant@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 D30CDC159498 for <ietf@ietfa.amsl.com>; Sat, 6 Aug 2022 01:20:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.104
X-Spam-Level:
X-Spam-Status: No, score=-2.104 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, MIME_QP_LONG_LINE=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, URIBL_BLOCKED=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] 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 zo9iFykNPTRT for <ietf@ietfa.amsl.com>; Sat, 6 Aug 2022 01:20:25 -0700 (PDT)
Received: from mail-wm1-x32f.google.com (mail-wm1-x32f.google.com [IPv6:2a00:1450:4864:20::32f]) (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 0C826C159496 for <ietf@ietf.org>; Sat, 6 Aug 2022 01:20:25 -0700 (PDT)
Received: by mail-wm1-x32f.google.com with SMTP id r1-20020a05600c35c100b003a326685e7cso4466126wmq.1 for <ietf@ietf.org>; Sat, 06 Aug 2022 01:20:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=to:references:message-id:cc:date:in-reply-to:from:subject :mime-version:content-transfer-encoding:from:to:cc; bh=u41dcEVy7f9j/pOCvqYxQNtlhy2pHbw7rl5/7HBmzUw=; b=ad8SjxwukaL6KV0RfKYtNApWiEN3llNATyGAG0C+jJX85sp5XBKQfOXWoJKFPD9IK9 MjCQXdbAZ9F39Ih51oG/b2bjp73F6CNeOwLNM9ZF06b5QvlWkuM4AIhyhCpViVwnJegq DVfroZkHzYlvLqAo0xK2u6MLoXJCeZDcl8tDbeu0qlwfk6htneH3I3FslERQtran9IUN nWBJtCRTLkLXJJpGFZtypijqzB1a6kM91x9BAeT3fj9BEdBdkFv451N+Tq3EyEDaMblf BeDt0yqTAh+9+sGTjPDLnWaZtk0Dn7PVGYXpW8MihDM03PaV1k0ILQ+BDQlt8YE7xP5U yvXw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=to:references:message-id:cc:date:in-reply-to:from:subject :mime-version:content-transfer-encoding:x-gm-message-state:from:to :cc; bh=u41dcEVy7f9j/pOCvqYxQNtlhy2pHbw7rl5/7HBmzUw=; b=m7xXS/1508+1I902B0PjfzyKSHBxk/LGG3KPg4pVlmzxvYWx2VPsFJjtWS1pEY88l9 jatebOf6apAP1K0vBLbt0JF1pO6M16wdnyOWt+dsMIH1uawQH+dNzzprUEtawTbUjCeM xIhGdvi3SNL/B7B6W5ZzJqcE9xH25V/jjmJFO6Gz5fPGaQ//p+mKQiLPb7KsGNCqnI/E /2W1KNRG2wUIv+v8BYFT4LNnuNSgYqI77+oqplobTWnEmM+QFBxUOHXfWHiaKLxRLTfZ csNaqQrscvCZy4KKbyKcDWJGvijL4LKf7mqyOo3EhjrGH+AkIIeie9pdjZ9MiItP/eoT MoRA==
X-Gm-Message-State: ACgBeo0OC9RgxXhLMS+aAa+/+lzuANYbHnBaS88HtG4QvlSN1vkR+JHk pbMnKJaLJmKvRziOyTHHbcQNUXoC1cQSYQ==
X-Google-Smtp-Source: AA6agR4xs3pPpni7yp1xZS+J1cOTA/puBnWh2+9/koY/Mhv73VPm70pFah72prnFA5KsQhGZt1it2w==
X-Received: by 2002:a05:600c:19d2:b0:3a3:3aca:a83d with SMTP id u18-20020a05600c19d200b003a33acaa83dmr7178117wmq.88.1659774022623; Sat, 06 Aug 2022 01:20:22 -0700 (PDT)
Received: from smtpclient.apple ([148.252.129.96]) by smtp.gmail.com with ESMTPSA id b2-20020a5d4d82000000b0021f73c66198sm5777459wru.1.2022.08.06.01.20.21 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sat, 06 Aug 2022 01:20:21 -0700 (PDT)
Content-Type: multipart/alternative; boundary="Apple-Mail-CCBFA612-B95E-4CBC-8EC5-CED5F7F42860"
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (1.0)
Subject: Re: Network Energy Management
From: Stewart Bryant <stewart.bryant@gmail.com>
In-Reply-To: <CAFvDQ9oU-cLeiHRyhyVjabj8K6ENv2PXyRb+5RyTm4TfkheDoA@mail.gmail.com>
Date: Sat, 06 Aug 2022 09:20:20 +0100
Cc: Joel Halpern <jmh@joelhalpern.com>, IETF <ietf@ietf.org>
Message-Id: <AE55269B-DC76-498C-9E49-80AE239253C2@gmail.com>
References: <CAFvDQ9oU-cLeiHRyhyVjabj8K6ENv2PXyRb+5RyTm4TfkheDoA@mail.gmail.com>
To: Hesham ElBakoury <helbakoury@gmail.com>
X-Mailer: iPad Mail (19G71)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Sy35mb4qjPwaUhm5sk4mG8l2cVI>
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 08:20:28 -0000

A comment that I would make on this not having skills line of argument, is that about 25 so years ago, very few had security skills and that very few thought about the security aspects of their protocol designs. Then the mandatory security section was introduced and the security area started objecting to protocols that had poor security. Now, I hope that we all think about the security implications of our work.

I don’t know what technique we should apply to sustainability, but I do know that all long journeys start with a first step, often with an incomplete idea of the route and the difficulties. 

Stewart

Sent from my iPad

> On 6 Aug 2022, at 06:53, Hesham ElBakoury <helbakoury@gmail.com> wrote:
> 
> 
> Hi Joel,
> Why IETF does not have the skill set to define extensions to OSPF to be more energy efficient ? Example of such extensions is described in this recent paper https://arxiv.org/pdf/2207.00035.
> 
> Thanks
> Hesham
> 
>> On Fri, Aug 5, 2022, 4:22 PM Joel Halpern <jmh@joelhalpern.com> 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?
>>>>