Re: Network Energy Management

George Michaelson <ggm@algebras.org> Fri, 05 August 2022 04:25 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 B2BF5C14792A for <ietf@ietfa.amsl.com>; Thu, 4 Aug 2022 21:25:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.909
X-Spam-Level:
X-Spam-Status: No, score=-6.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, 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=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 eB9pjC66iAl0 for <ietf@ietfa.amsl.com>; Thu, 4 Aug 2022 21:25:24 -0700 (PDT)
Received: from mail-yw1-x1134.google.com (mail-yw1-x1134.google.com [IPv6:2607:f8b0:4864:20::1134]) (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 2DB47C14F748 for <ietf@ietf.org>; Thu, 4 Aug 2022 21:25:23 -0700 (PDT)
Received: by mail-yw1-x1134.google.com with SMTP id 00721157ae682-32269d60830so14317637b3.2 for <ietf@ietf.org>; Thu, 04 Aug 2022 21:25:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=algebras-org.20210112.gappssmtp.com; s=20210112; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc; bh=DZkTCryaADWx1dUbSqGwIyykiVuvrQ1X5l43qzijj/E=; b=P5aABckkJwjf17EbATs2s080V7s2f75qx/BdO45BN36XiobHcKW0bzXZGGaESQ9j+h hpBO/CV4OywCOKwuPDTrKiEsTtZoIvzPI5w0zcLXMQsBz5J5n/tnmj+lNm+lksVcQqtN GiIpbnMuj2tbbk6eXYZ8qSxtPawoanihwRTYfX6F832hQTBIaFAnNvJoEY9Vtvogr/ZY bVbDZgwocC3mJjsy4iP8wPRtiHcGLF2QhcqkysDDjZToWNk1mYAb5uV9DMcnNEaXYcmE 25VIV6VA7gjBpYmx8uqAn58umfq4I3iHZZO2XWIDo3roMFPri60OyuCROSRinvaJMJel 0X8g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc; bh=DZkTCryaADWx1dUbSqGwIyykiVuvrQ1X5l43qzijj/E=; b=WH+igpVnWMzor9vRpdz3M/k4Dx+JOUO+/QbxFsZBQ974Pu47qaDYdGUQ0V/Y/e6DYt 35Ppu/7iehUx4qaPFS9gsiZcwXr721u5KWIp1CctSBNTOGnchGpNAYQBZh6ogFmDYbrT uOHg8w7k/xiTLsyOu5880595ekTM5j/3KP1odcgD4VMgDhq0LW+EH8JLpPlqc2mEfpR7 zZC4t1xBsDFsaT9YhHvY/hHfenWzNhZxd5KHhrv+xBLa455/gk4ANE6f5L4O4lyJSBUR hlkXvzarQ7TPRfKlpoEmfLgVJBQlPt7tPP/CyjKFZECv3Y9LanIQcxiNUpP404vLAmGa Hf6Q==
X-Gm-Message-State: ACgBeo3ckqb942SY7dHbTq0V092jeXbaKUXBR1GBjDuiDPjNpScSX91N 6692JdXQU7CAXh/7SVJcGNbp49VNW+I2Np1UsJpo6Q==
X-Google-Smtp-Source: AA6agR63zSD1yXAn+HnxVGML1UZ+aQ30TAN4YAJGeQKWf6twboJc0CzM/7HenzLlziqNcAPsDsdgk7bHeKj03sC9Tk0=
X-Received: by 2002:a81:5294:0:b0:320:2c98:96f with SMTP id g142-20020a815294000000b003202c98096fmr4456032ywb.504.1659673522723; Thu, 04 Aug 2022 21:25:22 -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> <2c3b9597-c1f4-a062-50ba-ba55d342c7d2@gmail.com>
In-Reply-To: <2c3b9597-c1f4-a062-50ba-ba55d342c7d2@gmail.com>
From: George Michaelson <ggm@algebras.org>
Date: Fri, 05 Aug 2022 14:25:11 +1000
Message-ID: <CAKr6gn2T=Lu3h0w3_tdD2Yu-iTXdGky1ei1pXUWs46k8-dyqhw@mail.gmail.com>
Subject: Re: Network Energy Management
To: Hesham ElBakoury <helbakoury@gmail.com>
Cc: Tianran Zhou <zhoutianran@huawei.com>, IETF <ietf@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/h12DgWhErZPiPAdR5gmjawsV59s>
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 04:25:28 -0000

If you want to ask SP's a question, a NOG list or a WG is a better
place than an IETF wide list.

-G

On Fri, Aug 5, 2022 at 2:11 PM Hesham ElBakoury <helbakoury@gmail.com> wrote:
>
> Actually, I am interested to find out from service providers what solutions they need to deploy to achieve their Net-Zero goal and what needs to be standardized (if any) to deploy these solutions.
>
> Hesham
>
> On 8/4/2022 6: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]
> Sent: Friday, August 5, 2022 9:08 AM
> To: Tianran Zhou <zhoutianran@huawei.com>
> Cc: IETF <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