Re: Network Energy Management
George Michaelson <ggm@algebras.org> Fri, 05 August 2022 02:33 UTC
Return-Path: <ggm@algebras.org>
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 E0C62C14CF10 for <ietf@ietfa.amsl.com>; Thu, 4 Aug 2022 19:33:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.908
X-Spam-Level:
X-Spam-Status: No, score=-1.908 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, 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=algebras-org.20210112.gappssmtp.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 8M2fQxjPmjIa for <ietf@ietfa.amsl.com>; Thu, 4 Aug 2022 19:33:49 -0700 (PDT)
Received: from mail-yb1-xb2d.google.com (mail-yb1-xb2d.google.com [IPv6:2607:f8b0:4864:20::b2d]) (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 DA19CC14F73F for <ietf@ietf.org>; Thu, 4 Aug 2022 19:33:49 -0700 (PDT)
Received: by mail-yb1-xb2d.google.com with SMTP id k12so1888571ybk.6 for <ietf@ietf.org>; Thu, 04 Aug 2022 19:33:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=algebras-org.20210112.gappssmtp.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc; bh=fjiMrxkKJ4fHco/mUdNBeGVLmfYBLuuSkSXDTSMaLGU=; b=6M347rSjPXXPvCF8xX4qgSjDtDD0AxKXgoXcnLGnmg2WC0yN/j9ugdPANjdZcx3bSP f83hcrioXebrI4exsmXZml8ypp3WP/yykCmdr8m3S5OiNJz+CaJEKE1FNlWxkKWuHtvn f+sDTKnSEhncoWGbEQFEin+tr9/jAvwEB1EJUcqr99uCI3HwuxOiDr7/JYI5PYLAUeNd LfvGP1MN3CjLZNy9q0ZtI0YQw07uB0gehLdX5prjpp+IDxo1c7pSfeyF4lhLVOPNWJLH n+TvjZifDxNkd0lgc4MghGI2q00FO2cOKrke49RwNqwcypAaEk2YwYb4NfFkINzlgO6R eUWg==
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=fjiMrxkKJ4fHco/mUdNBeGVLmfYBLuuSkSXDTSMaLGU=; b=reEHLeivIGN7x7b9n3Ip7bD9WB/jjSQFKaUTWk7FJsP8ac0QCGaEub7lOGe/KPFxJ1 cBl5wVLf2T2Tn2yd+Kl3F2RArTR0gOtiJ57EIcN8rH43C6OchoQ3xl82eBDmIGSHwB6f ziOPIDNPgx9h88eDAQExcTIsYzhLXa4qnsacYnHLuLeE0iIUr78PhQ+JTDUZrdVG/0gQ gCwf6dFUPVLOyoU3/ir/sjZg2t1rv4Su1AImbUznfPA5awZFIpUG1I76qD3xVvfiqZRK cRcEXMWOEn88+KtYMHT0Dd8fQP9q++WA5YZGMeG1HGomGXNZvSC8BlesCoxivZ6hXULl 5F4A==
X-Gm-Message-State: ACgBeo2aezjAfGXg4ORVS5PhYthAvTsP7KYIoR/IXO87JThCn7DMnBUp 6L9oy4iTttRTSsdTuruQuadrZH6OnDyygd1ghl1nfIT1pLs=
X-Google-Smtp-Source: AA6agR5DxSkHo8nnUoaWnDnOLz+0kI6fWE3vEnWjj/liQQP1vBnhiwQRrbyLEoQRvU8udYPb4jO7fRYJdCJIWqXlH5E=
X-Received: by 2002:a25:d44b:0:b0:671:cdb7:ba69 with SMTP id m72-20020a25d44b000000b00671cdb7ba69mr3856035ybf.453.1659666828452; Thu, 04 Aug 2022 19:33:48 -0700 (PDT)
MIME-Version: 1.0
References: <81c9a652-81d2-9511-1c4a-3da06e80b48b@gmail.com> <c23c3f60359249f3959e14d616f014c4@huawei.com> <CAFvDQ9qQKTD5QSmmsD7Yuv+KihBxusXi4BD8wcuWxRGhy556HA@mail.gmail.com> <7dcc2e2d7cf245c88ab7788f0df36148@huawei.com> <acb080c1-3409-58e5-2814-3284413497e2@joelhalpern.com>
In-Reply-To: <acb080c1-3409-58e5-2814-3284413497e2@joelhalpern.com>
From: George Michaelson <ggm@algebras.org>
Date: Fri, 05 Aug 2022 12:33:37 +1000
Message-ID: <CAKr6gn22kJ86zquNe8YMkM-NehofpjpyAacGpyYvvGEvAQ2cBA@mail.gmail.com>
Subject: Re: Network Energy Management
To: Joel Halpern <jmh@joelhalpern.com>
Cc: Tianran Zhou <zhoutianran=40huawei.com@dmarc.ietf.org>, Hesham ElBakoury <helbakoury@gmail.com>, IETF <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000c177f705e5754b20"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/dh47lJIyGSh2r8KVRQMgXHyZTcc>
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 02:33:53 -0000
Which is pretty much what was said to microphone in OPSAWG at 114. G On Fri, 5 Aug 2022, 12:13 pm Joel Halpern, <jmh@joelhalpern.com> wrote: > I am finding this conversation somewhta strange. > > Having the ability to monitor energy consumption and report it is > understandable. And I can see how the reporting of that could fall into a > YANG module or similar construct done in the IETF. > > But power distribution, power storage, power rearrangement? That is for > power engineers, not the IETF. We don't tell people how to power their > routers. We don't tell them whether to put batteries in the router, in > their UPS, or somewhere else entirely. Not our expertise. > > We have in the past discussed turning things off when not in use. As > noted earlier in the thread, from where we sit, rather tricky. Someone > developing an AI / ML system to drive heuristics for it may or may not be > useful. But again doesn't look like IETF business. Our job is to provide > the data such systems would need. Which we already do. > > Yours, > > Joel > On 8/4/2022 9:53 PM, Tianran Zhou wrote: > > Hi Hesham, > > To be specific, what’s your thoughts on the following two use cases. > > > > 3- Use traffic analysis and modeling techniques perhaps with AI/ML > algorithms to predict which elements to power down/up and when, in such a > way to avoid service disruption. > 4- Use renewable energy, store it in the router and return back to the > energy source the energy that is not used so that someone else can use it. > > > > Thanks, > > Tianran > > > > *From:* Hesham ElBakoury [mailto:helbakoury@gmail.com > <helbakoury@gmail.com>] > *Sent:* Friday, August 5, 2022 9:08 AM > *To:* Tianran Zhou <zhoutianran@huawei.com> <zhoutianran@huawei.com> > *Cc:* IETF <ietf@ietf.org> <ietf@ietf.org> > *Subject:* Re: Network Energy Management > > > > There are publicatipns about changes to IP, TCP, Routing Protocols, > Traffic Engineering, ... etc but I am not sure if these changes are > implemented and deployed in service provider networks. > > > > Thanks > > > > Hesham > > > > On Thu, Aug 4, 2022, 5:49 PM Tianran Zhou <zhoutianran@huawei.com> wrote: > > While I think this is an very interesting topic that I would like to > follow, I am confused most of the proposal here may not related to network > protocol. > I.e, I am not sure what IETF can help on this. > > Best, > Tianran > > -----Original Message----- > From: ietf [mailto:ietf-bounces@ietf.org] On Behalf Of Hesham ElBakoury > Sent: Friday, August 5, 2022 7:12 AM > To: IETF <ietf@ietf.org> > Subject: Network Energy Management > > There has been some discussions in IETF 114 about how to reduce the > network energy consumption and carbon footprint. Most of the energy-aware > routing and traffic engineering publications that I have seen rely on > powering down network elements such as interfaces, line cards and routers > to save power. The problems with this approach are: 1) to power up these > elements when they are needed may take long time which may cause > undesirable service disruption, and 2) network operators may not trust > routing and traffic engineering software to power down and up these > elements without operator intervention. > > To address these problems we may do one of the following: > > 1- Do not power down any network element, and try some other way to reduce > energy such as adjusting the cooling level based on network load. > > 2- Do not power down any network element, but put the element in low power > idle state to consume least amount of power while it is not used to forward > traffic. In this state it is quicker to bring the element into fully > operational state. This solution may require hardware support. > > 3- Use traffic analysis and modeling techniques perhaps with AI/ML > algorithms to predict which elements to power down/up and when, in such a > way to avoid service disruption. > > 4- Use renewable energy, store it in the router and return back to the > energy source the energy that is not used so that someone else can use it. > > 5- If you have other approaches, please let us know. > > In all these approaches we need to instrument the network to monitor its > traffic loading and energy consumption. > > Comments ? > > Hesham > >
- 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