Re: Network Energy Management
Hesham ElBakoury <helbakoury@gmail.com> Sat, 06 August 2022 05:51 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 651C5C157B52 for <ietf@ietfa.amsl.com>; Fri, 5 Aug 2022 22:51:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.106
X-Spam-Level:
X-Spam-Status: No, score=-2.106 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, 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 uGi5ZE321wXD for <ietf@ietfa.amsl.com>; Fri, 5 Aug 2022 22:51:32 -0700 (PDT)
Received: from mail-qk1-x733.google.com (mail-qk1-x733.google.com [IPv6:2607:f8b0:4864:20::733]) (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 89C42C14CF11 for <IETF@ietf.org>; Fri, 5 Aug 2022 22:51:32 -0700 (PDT)
Received: by mail-qk1-x733.google.com with SMTP id w6so3269501qkf.3 for <IETF@ietf.org>; Fri, 05 Aug 2022 22:51:32 -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=yMJGB9b6EW9CsPRHDIfpThITyASqFLIEQxTECuOFPUc=; b=YP9XV9oiyFsk6jWHC8hE3ZtgWnGRGpFg5W21KF/EkjQkiSR89Z+Iemvjvf5HVfLg5c 0QayYlYvo19STjKNR5Qo2YCyoQNJxW14pRUXY8dlqE5RKIXcqGfoVPaB4Cai9FyOwCgZ IxkSrw35+OF4WldWErxaM4snLQpnlYE/j4T6a4u5qH0H2M2O0L8s5JBabl3g1l1JCasI RWURjvaQnvN8GarpmR3v5EpeE9YBAecXG2qQDS6eIOsW8kxMR4g1qYjqFax5eq9NlC5/ HjVEYCNVfBOTeMI7+dbgXUVVYVIOkAR4wP3Gif/91Y0JuctgJ4E+FqQiHe4I4rsZ3fSQ d+dQ==
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=yMJGB9b6EW9CsPRHDIfpThITyASqFLIEQxTECuOFPUc=; b=6cQ6oX5TdMbDIF8SaxC9M4pdWI+mtPQ1HX/hScFAG9eJhfUXeGiEmMx1eW2aqyvq7z kP0jFogNrqVY3SWBdPthkbVqDREs7gQiErUHCNEqvN9fbzBV01axh1NbpuqQ/vrZXBv/ HZiEMmu9HmP1Jr5VH5qZKwsSYd40rIwPAZ/GtBVdDnudVUm8ktIkbdaOwKo3WjPCJyIC USK++7IZNWpGPQ66dQUmyWBkeebKoqsEUMNxJ1q5IrmA/0jR50M0jnG159/gN7Kg08es EgIjh4P1Rnywmk2YOMLdrsXP3GiBgSGXcmgHbUy3b4viXcOiu9b5pjKfAQ2No663xJsX huYQ==
X-Gm-Message-State: ACgBeo0TCeQhSUPL3x55kSJNR3sq4Lgxj0RGyD9oMtkovzzRlFb9xlxx aNrjI4LHUdXuf7uxNwJ/6HFMtGl5VLE2TN8gLoY=
X-Google-Smtp-Source: AA6agR6LvZ6nAYfy8mmSyifPzaEZQLczePVy8Krbb/mAyt3Al9Vk3mQwbbsmETihdgLGevtdMfMO0pltZGofhstXMYk=
X-Received: by 2002:a05:620a:40d5:b0:6b8:ef34:fee6 with SMTP id g21-20020a05620a40d500b006b8ef34fee6mr7536438qko.639.1659765091448; Fri, 05 Aug 2022 22:51:31 -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>
In-Reply-To: <8f308769-ad04-8f97-7a84-5f98ba27afee@joelhalpern.com>
From: Hesham ElBakoury <helbakoury@gmail.com>
Date: Fri, 05 Aug 2022 22:51:18 -0700
Message-ID: <CAFvDQ9oU-cLeiHRyhyVjabj8K6ENv2PXyRb+5RyTm4TfkheDoA@mail.gmail.com>
Subject: Re: Network Energy Management
To: Joel Halpern <jmh@joelhalpern.com>
Cc: Fred Baker <fredbaker.ietf@gmail.com>, IETF <IETF@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000afbd0005e58c2cf9"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/k8m8eoGNbdSkvU03_ZLgfU8qBOo>
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 05:51:36 -0000
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? >> >>
- Network Energy Management Hesham ElBakoury
- Re: Network Energy Management George Michaelson
- Re: Network Energy Management shogunx
- RE: Network Energy Management Tianran Zhou
- Re: Network Energy Management Hesham ElBakoury
- RE: Network Energy Management Tianran Zhou
- Re: Network Energy Management Joel Halpern
- RE: Network Energy Management Tianran Zhou
- Re: Network Energy Management George Michaelson
- Re: Network Energy Management Hesham ElBakoury
- Re: Network Energy Management George Michaelson
- Re: Network Energy Management Hesham ElBakoury
- Re: Network Energy Management Tim Bray
- Re: Network Energy Management Stewart Bryant
- Re: Network Energy Management Michael Richardson
- Re: Network Energy Management Hesham ElBakoury
- Re: Network Energy Management Hesham ElBakoury
- Re: Network Energy Management Fred Baker
- Re: Network Energy Management Michael Richardson
- Re: Network Energy Management Hesham ElBakoury
- Re: Network Energy Management Joel Halpern
- Re: Network Energy Management Brian E Carpenter
- Re: Network Energy Management Hesham ElBakoury
- Re: Network Energy Management shogunx
- Re: Network Energy Management Hesham ElBakoury
- Re: Network Energy Management Phillip Hallam-Baker
- Re: Network Energy Management Hesham ElBakoury
- Re: Network Energy Management Stewart Bryant
- Re: Network Energy Management - research paper Joel Halpern
- Re: Network Energy Management - research paper Hesham ElBakoury
- Re: Network Energy Management Nevil Brownlee
- Re: Network Energy Management Christian Huitema
- Re: Network Energy Management Phillip Hallam-Baker
- Re: Network Energy Management - research paper Simon Pietro Romano