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

Bruce Nordman <bnordman@lbl.gov> Mon, 26 September 2022 03:52 UTC

Return-Path: <bnordman@lbl.gov>
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 D6691C1522B7 for <recipe@ietfa.amsl.com>; Sun, 25 Sep 2022 20:52:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.883
X-Spam-Level:
X-Spam-Status: No, score=-1.883 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, T_KAM_HTML_FONT_INVALID=0.01, T_SCC_BODY_TEXT_LINE=-0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=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=lbl-gov.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 DjtbwfUn6tTV for <recipe@ietfa.amsl.com>; Sun, 25 Sep 2022 20:52:45 -0700 (PDT)
Received: from mail-qt1-x832.google.com (mail-qt1-x832.google.com [IPv6:2607:f8b0:4864:20::832]) (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 394D1C14CE30 for <recipe@ietf.org>; Sun, 25 Sep 2022 20:52:45 -0700 (PDT)
Received: by mail-qt1-x832.google.com with SMTP id g12so3437019qts.1 for <recipe@ietf.org>; Sun, 25 Sep 2022 20:52:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lbl-gov.20210112.gappssmtp.com; s=20210112; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date; bh=E0rruM7t1Sb2axMSPM3vkLeDUEJtY0U8UR9CNQdJWjg=; b=dhmiJDUCEhXJUHcN+sCGmMd9ZY0RRUJzhPpEHZFhFonNkwQYQHeqT1ifWrAij9BziO 2VrhQU9Ihb/FVfqvOrJ8Ym9s+YPSjHS6XV/tmY0ECWET4j7lyLX/MyJtruCumoKtxIE/ 45LlwbOW11wwBE6qSwVVQQo3msnaPtXh0pzUj4MgMhnaIUXuokco++0eoBTgNthNJd1r 37yEl865a8DAg4G4BrmBzP2b6Sv1l8ydLCRzoep8yZccirzuSitfg+HEV+b+QBJ9aZph PNov/eGvYftLY9TC1tzfydr+DLVvqGBZVaBgjHEvXSnXW3Q8KjhacjBcxfYbaXkUjedV 2oBQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-message-state:from:to:cc:subject:date; bh=E0rruM7t1Sb2axMSPM3vkLeDUEJtY0U8UR9CNQdJWjg=; b=ChqLRePV40oj6izy4MGsuU+P+Jk1SKpdJg9TfdZ8JJE1bkzcC1C6uCtC9ArRr9IR7z Squ1DcjxzzNXPBm4aTOU4cqHaEoeAo03cOiIbs9LCzn6tiTuT5N6kZDoyLQQk4WfGq7S VD4lrM8v9ekc+x0f0YGqhCVFrwUeTZRbyd/hjtR4rSPsaQeFiDtqStUsEf8gvFwyHTbc 8RF1cTR/+5d6nfVND7eWYTaSyfER6bbKF+X6yP12bnPhQ9WyiDtqdVcfO5csQ8jy/Oj7 sU/s3b79fb3AG3IJQFqNuD/5Dx3lh+ny/2Ii7Fk/kvJECHTA/+H0GdAgLxqwSPblJRyB keQg==
X-Gm-Message-State: ACrzQf3ZpvVHUiVQyeMpM/9lUaDP7HxlNbphL+mqI/iav0wlcLfMR9KK r87c1L+qGduQ0pjBzZ5c/XT/Aeds/WfJI8QZPMwF0vQLqSKJSVpHkhGD4xtExwonB9N+qyGhy30 fq411qxO/ZBTypzrRMzXs9KsgwQfTGCtpoBA5c3HjzL9eWrKpYnyOXu3NUczdp7jvOvViVwkUu8 zWs84Kl0w1h44=
X-Google-Smtp-Source: AMsMyM5bO2+kV1k/Q+SPYAGueh7wNk1YOemK69mMWktJ4DYqeZefA71r7utYy/8xcLjm3Wz1BRkvrcm/l08bcB2SCac=
X-Received: by 2002:ac8:5c50:0:b0:35b:b246:c457 with SMTP id j16-20020ac85c50000000b0035bb246c457mr15859646qtj.128.1664164363295; Sun, 25 Sep 2022 20:52:43 -0700 (PDT)
MIME-Version: 1.0
References: <Yy87opj7tkqfd85I@faui48e.informatik.uni-erlangen.de> <D3A1335A-022C-4F1F-BCCC-3160B1D3BB7C@ifi.uio.no> <YzDNTByMvA9tsE5c@faui48e.informatik.uni-erlangen.de>
In-Reply-To: <YzDNTByMvA9tsE5c@faui48e.informatik.uni-erlangen.de>
From: Bruce Nordman <bnordman@lbl.gov>
Date: Sun, 25 Sep 2022 20:52:32 -0700
Message-ID: <CAK+eDP-G5WWCun9bzKyKbLnmy+gCVy5cMiTrsFU9FzzkWQf5Bg@mail.gmail.com>
To: recipe@ietf.org
Content-Type: multipart/alternative; boundary="000000000000b9085005e98c75b0"
Archived-At: <https://mailarchive.ietf.org/arch/msg/recipe/6xMKc35pL8iCZ56yUa1mlpC6uc8>
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: Mon, 26 Sep 2022 03:52:49 -0000

All--

  I think thinking about the carbon consequence of IETF meetings is a
useful thought exercise, but the amount of energy potentially leveraged by
IETF RFCs is orders of magnitude larger and so should be the follow-on, and
much more in depth, exercise. I will stay out of the carbon offset question.

  The phrase ‘energy use of the Internet’ really makes no sense. I think
that when people use this they really mean one of a variety of other
questions. These include some combination of:

-A: Energy use of network equipment

-B: Energy use servers dedicated to web serving (directly or indirectly).

-C: Energy use of network equipment and telecom infrastructure

-D: Energy use of electronics with an IP connection

-E: Energy use of any device with an IP connection

E is the most silly since it includes things like water heaters and many
automobiles, but regardless, I think it is most helpful to focus on A as
what is most central to the Internet.

  The last time I waded into this territory quantitatively, was 2014 - with
data mostly from about 2010: Light at the end of the tunnel for electronics
energy use?
<https://www.aceee.org/files/proceedings/2014/data/papers/9-889.pdf> Before
that: Network equipment energy use - U.S. total estimate for 2008
<https://drive.google.com/open?id=0B8B9XW6B7prlR0x3N0JaZ3pCMDg>

  Estimates of energy/carbon often collide head-on into the average vs
marginal question. My home network equipment is needed for me to send this
email, but it is on 24/7 regardless of what I do - and even if I am home.
Any incremental use for incremental traffic is tiny in annual energy use.
Sometimes it is appropriate to use average, but I think more often marginal
is more appropriate to decisions that could be made using the data.

  Jon Koomey was mentioned - I have worked with him (sporadically) for over
25 years - also with Eric Masanet.

  For comparing network eqt. energy use to aviation, think of health care.
Certainly cancer and heart disease are huge problems in industrialized
countries and deserve a lot of attention, but that doesn’t mean that
diseases that harm fewer people don’t also deserve some. We need to work on
all topics, but in proportion to how much progress is achievable. We have
expertise in certain areas so should focus on that.

  In rough terms, electronics connected to the Internet use about 10x what
network equipment uses, so the IETF can make the best contribution by
helping to reduce the energy use of hosts.

  I should engage with the ID underway.

  I am happy to get individual emails in addition to reading this list.

  My work of late has shifted to coordinating energy use and buildings with
variable renewable supply on the grid - or microgrid operation. This and
the use of Direct Current power.

  Thanks.

--Bruce


On Sun, Sep 25, 2022 at 2:51 PM Toerless Eckert <tte@cs.fau.de> wrote:

> On Sun, Sep 25, 2022 at 11:57:44AM +0200, Michael Welzl wrote:
> > > So my
> > > primary question is: are there any "natural" limits in linearizing
> this curve ? Then as a pessimist,
> > > i would love to design / evaluate against those limits instead of
> against the inferior hardware we have
> > > today. Especially because i only need to look at mobile device HW/CPU
> to see that there is a
> > > lot of room for improvement (AFAIK).
> >
> > I guess this is about evaluating the cost of sleep/awake transitioning
> over the years…  how has this evolved, will it become miniscule?
>
> Indeed. I am just worried that it do not know that it will not become
> miniscule, which
> makes me somewhat worried into promoting investing into solutions that
> depend on it
> not being miniscule. After all, we have past experiences with betting
> investments into
> assumptions that turned out to be changed inparallel, rendering the
> investments mostly void.
>
> Aka: Would love to see, if research can also come up with predictions
> about this factor
> (non minisculity of transitioning, if that's even a word ;-)
>
> Cheers
>    Toerless
>
> > Cheers, Michael
> >
> > >
> > > Cheers
> > >    Toerless
> > >
> > >> Cedric:
> > >>
> > >>>> On Sep 22, 2022, at 11:53 PM, Cedric Westphal <
> cedric.westphal@futurewei.com> wrote:
> > >>>
> > >>> HI Michael & Toerless:
> > >>>
> > >>> Michael: thank you very much for the data points.
> > >>>
> > >>> Regarding your paper: I really like the idea that protocols can help
> saving energies. When we wrote our draft
> https://datatracker.ietf.org/doc/draft-cx-green-ps/ <
> https://datatracker.ietf.org/doc/draft-cx-green-ps/> we were a bit
> disappointed that the protocol side of things didn’t have great
> opportunities for reducing energy consumption – aside of course of
> facilitating sleep modes as you suggest in your paper. If you have a chance
> to read it, we would welcome your comments. I’m currently updating it for
> London.
> > >>
> > >> I did read the draft, but didn’t have any comments. I did find it
> interesting though!  I’ll be in London too, btw, and I’ll give a brief
> presentation on the relationship between energy saving and congestion
> control (just the simple result from my paper) to ICCRG there. I think
> there are plenty of opportunities in protocols - they just need to be
> worked out, evaluated, …   I mean, you point out some interesting
> opportunities in your own draft.
> > >>
> > >>
> > >>> Your paper seem to argue that short/high bandwidth transmissions are
> better than longer/slower ones – we wrote something like this in our
> paperhttps://
> scholar.google.com/citations?view_op=view_citation&citation_for_view=5WcgOxMAAAAJ:rJyh6hJnyfgC
> <
> https://scholar.google.com/citations?view_op=view_citation&citation_for_view=5WcgOxMAAAAJ:rJyh6hJnyfgC>
> (upon which the draft is based on) and we got some pushback to the extent
> that: short/fast = burstiness = high buffers = packet loss =
> re-transmissions.
> > >>
> > >> Thanks, i’ll read this.
> > >> Regarding bursts, I think we shouldn’t think about “bursts” and even
> use a different word. Bulk? “Send data in bulk” as opposed to "sending a
> burst”?
> > >>
> > >> This is an important distinction because data in bulk can (and
> probably should) still be paced - we really shouldn’t be sending bursts if
> we can avoid them. What I mean is something like sending 100 paced packets
> in 1 RTT instead of 10 packets per RTT over 10 RTTs.  In fact, the Internet
> does the latter kind of transmission often enough. Given typical flow
> lengths and growing capacities, the primary role of congestion control in
> today’s Internet seems to be to waste our time with round-trips (before
> transmissions are over).   Some hints about this:
> https://ieeexplore.ieee.org/document/9817041 <
> https://ieeexplore.ieee.org/document/9817041>  (or:
> http://arxiv.org/abs/2206.06642 <http://arxiv.org/abs/2206.06642> ) … and
> references therein, e.g. https://dl.acm.org/doi/10.1145/3472305.3472321
> > >>
> > >>
> > >>> I checked the spreadsheet on the other paper – they haven’t been
> updated.
> > >>
> > >> I did the same!  Disappointing, isn’t it.
> > >>
> > >>
> > >>> It’s a strange paper, that makes a lot of assumption regarding
> energy consumption, but you have to start somewhere. I’m surprised you’re
> saying there hasn’t been follow up to that, it’s such an important topic.
> > >>
> > >> I don’t think I said that? There are plenty of studies out there, but
> … it’s a jungle.
> > >>
> > >>
> > >>> I definitely will add some paragraph or section on “emergy” in the
> next version of the draft.
> > >>>
> > >>> This paper evaluates the emissions from virtual conferences – to
> keep in mind when comparing with IETF emissions from combined
> hybrid/in-person conference:
> https://forum.legacy-events.com/uploads/short-url/zmI7aFu6X6ojBESqz9IWKke4GW4.pdf
> <
> https://forum.legacy-events.com/uploads/short-url/zmI7aFu6X6ojBESqz9IWKke4GW4.pdf
> >
> > >>> This paper assesses the value of in-person vs virtual to be 66 times
> higher from the travel alone (but that’s 99% of the in-person energy cost!)
> > >>
> > >> Thanks!
> > >>
> > >>>
> > >>> Toerless: was that paper cited at the workshop???
> > >>>
> > >>> Best,
> > >>>
> > >>> C.
> > >>
> > >>
> > >> Cheers,
> > >> Michael
> > >>
> > >
> > > --
> > > ---
> > > tte@cs.fau.de
>
> --
> ---
> tte@cs.fau.de
>
> _______________________________________________
> recipe mailing list
> recipe@ietf.org
> https://www.ietf.org/mailman/listinfo/recipe
>


-- 
*Bruce Nordman*
Lawrence Berkeley National Laboratory
*nordman.lbl.gov <http://nordman.lbl.gov>*
BNordman@LBL.gov
510-486-7089; m: 510-501-7943