Re: [recipe] FYI: [admin-discuss] REMINDER: IETF carbon emission measurement workshops on 20 and 21 September

Toerless Eckert <tte@cs.fau.de> Fri, 30 September 2022 18:35 UTC

Return-Path: <eckert@i4.informatik.uni-erlangen.de>
X-Original-To: recipe@ietfa.amsl.com
Delivered-To: recipe@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 22D45C14CF03 for <recipe@ietfa.amsl.com>; Fri, 30 Sep 2022 11:35:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.658
X-Spam-Level:
X-Spam-Status: No, score=-1.658 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, 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=no autolearn_force=no
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 91H90MkRy1St for <recipe@ietfa.amsl.com>; Fri, 30 Sep 2022 11:35:33 -0700 (PDT)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:40]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 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 B56F4C14F6E7 for <recipe@ietf.org>; Fri, 30 Sep 2022 11:35:33 -0700 (PDT)
Received: from faui48e.informatik.uni-erlangen.de (faui48e.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:51]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (No client certificate requested) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTPS id 67543548586; Fri, 30 Sep 2022 20:35:26 +0200 (CEST)
Received: by faui48e.informatik.uni-erlangen.de (Postfix, from userid 10463) id 5D7784EBBC6; Fri, 30 Sep 2022 20:35:26 +0200 (CEST)
Date: Fri, 30 Sep 2022 20:35:26 +0200
From: Toerless Eckert <tte@cs.fau.de>
To: Bruce Nordman <bnordman@lbl.gov>
Cc: Michael Welzl <michawe@ifi.uio.no>, recipe@ietf.org
Message-ID: <Yzc27llX5bOvdf++@faui48e.informatik.uni-erlangen.de>
References: <Yy87opj7tkqfd85I@faui48e.informatik.uni-erlangen.de> <D3A1335A-022C-4F1F-BCCC-3160B1D3BB7C@ifi.uio.no> <YzDNTByMvA9tsE5c@faui48e.informatik.uni-erlangen.de> <CAK+eDP-G5WWCun9bzKyKbLnmy+gCVy5cMiTrsFU9FzzkWQf5Bg@mail.gmail.com> <DAB0D97B-1FB7-4466-A5EC-EF845FD23AAF@ifi.uio.no> <CAK+eDP_MSP5R2zLPXbT28iW5tpWOWnbVckhDTXL4i3DAaxcdkA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <CAK+eDP_MSP5R2zLPXbT28iW5tpWOWnbVckhDTXL4i3DAaxcdkA@mail.gmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/recipe/LNXyfThln6N6GHZv8ZuUeHtvIn0>
Subject: Re: [recipe] FYI: [admin-discuss] REMINDER: IETF carbon emission measurement workshops on 20 and 21 September
X-BeenThere: recipe@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "RECIPE \(Reducing Energy Consumption with Internet Protocols Exploration\)" <recipe.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/recipe>, <mailto:recipe-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/recipe/>
List-Post: <mailto:recipe@ietf.org>
List-Help: <mailto:recipe-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/recipe>, <mailto:recipe-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Sep 2022 18:35:38 -0000

On Mon, Sep 26, 2022 at 11:32:08AM -0700, Bruce Nordman wrote:
> I left out an important NOT above. My network equipment is on continuously
> - it doesn't sleep. I don't see entire network eqt. devices as plausibly
> going to sleep (at least in res/comm bldgs) though individual links can
> (e.g. 802.3az).

Unfortunately, that 802.1az feature was AFAIK never perpetuated to optical ethernet,
and i think also not 100G or faster. Not sure about 10G copper or the new lower bitrates.
One of the main issues is i think that the higher speed codecs require an even longer time
to resync. Which i think makes the 802.1az approach less and less useful (startup time).

I would hope that ieee would take a new look at this issue. Maybe with periodic/phase
driven on/off mode to overcome the need for continuous-on clocking signal. 

> The power levels of my network equipment probably go up
> with higher traffic levels, but I expect that the increment is quite small.
> Making up some #s here, if my network equipment uses 20W with no traffic
> and 20.5W on average when there is significant traffic, then I should
> allocate only the 0.5W as the marginal cost of its use in determining the
> impact of more or less traffic. The equipment will use the 20W even if
> there is no traffic (but since I have a (very) few IoT devices like my
> water heater, there is always some traffic).

I would hope/think that the lower the bitrate, the higher the margial cost, aka: a higher
percentage of energy can be saved when not transmitting traffic. But of course, depending
on codec/modulation the same long-term-sync issue may exist here too.

> This comes up when considering something like streaming a movie vs. mailing
> a DVD. There is an issue about long-run effects, e.g. if many people stream
> movies, will that induce increases in infrastructure capacity so that one
> can consider short-run marginal and long-run marginal. For automobiles, a
> lot of costs are fixed no matter if you drive a little or a lot, but when
> not having a car at all (I didn't for many years), then the fixed costs can
> come into play.

This is almost a universal infrastructure issue. Road, Rail, Water, Gas, Electricity,
Internet - what have you. And several of those infrastructures only woke up recently
to this problem wrt. charging for infra vs. payload. And the even bigger iss ue
that you can not simply say that trying to reduce the cost of infrastructure
is always best: because ultimately you want to minimize the cost of infra plus payload
for the exact payload profile that customer would want to ideally have if they
could afford it. Which you maybe not even be able to predict as long as pricing is different.

Cheers
    Toerless

> > I didn’t know about the factor 10, but considering the main finding of
> > this paper: ttps://onlinelibrary.wiley.com/doi/10.1111/jiec.12630  and
> > some other things I came across, including this often-cited paper which
> > makes *extreme* predictions (I have trouble believing them… but then
> > predictions are what they are … just guesswork, really):
> > https://www.mdpi.com/2078-1547/6/1/117   … I also got the impression that
> > the edge is where most of the gains can be achieved.
> >
> Given the past 20 years of history, the 'realistic' worst case for 2030
> does not seem realistic to me.
> >
> > It would be interesting to know the relationship in terms of energy usage
> > between hosts, WiFi APs, and cellular equipment. Is it really just hosts
> > where we should reduce energy usage?
> >
> We should work on them all, though should prioritize hosts since there are
> a lot more savings potential there. Network providers do have an incentive
> to pay attention to operational energy use (though that doesn't guarantee
> that all cost-effective efficiency measures are taken).  Owners of
> residential and commercial buildings are much less capable of optimizing
> their purchase and use patterns.
> 
> --Bruce
> 
> 
> -- 
> *Bruce Nordman*
> Lawrence Berkeley National Laboratory
> *nordman.lbl.gov <http://nordman.lbl.gov>*
> BNordman@LBL.gov
> 510-486-7089; m: 510-501-7943

-- 
---
tte@cs.fau.de