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

Toerless Eckert <tte@cs.fau.de> Sat, 24 September 2022 17:17 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 0A67DC14CEFC for <recipe@ietfa.amsl.com>; Sat, 24 Sep 2022 10:17:36 -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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=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 18oNexJHl7tu for <recipe@ietfa.amsl.com>; Sat, 24 Sep 2022 10:17:31 -0700 (PDT)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [131.188.34.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 97243C14CE2F for <recipe@ietf.org>; Sat, 24 Sep 2022 10:17:29 -0700 (PDT)
Received: from faui48e.informatik.uni-erlangen.de (faui48e.informatik.uni-erlangen.de [131.188.34.51]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTPS id 7C13F548529; Sat, 24 Sep 2022 19:17:22 +0200 (CEST)
Received: by faui48e.informatik.uni-erlangen.de (Postfix, from userid 10463) id 615334EBB33; Sat, 24 Sep 2022 19:17:22 +0200 (CEST)
Date: Sat, 24 Sep 2022 19:17:22 +0200
From: Toerless Eckert <tte@cs.fau.de>
To: Michael Welzl <michawe@ifi.uio.no>
Cc: Cedric Westphal <cedric.westphal@futurewei.com>, "recipe@ietf.org" <recipe@ietf.org>
Message-ID: <Yy87opj7tkqfd85I@faui48e.informatik.uni-erlangen.de>
References: <YynVI79e1yOgqjOo@faui48e.informatik.uni-erlangen.de> <FB2BDEC9-8E07-44ED-B53E-CFF58BC9FAE9@ifi.uio.no> <YynbBRBOwZd0pcgo@faui48e.informatik.uni-erlangen.de> <SN4PR13MB5811E6CCFE475BD1345AD2C2FF4C9@SN4PR13MB5811.namprd13.prod.outlook.com> <YyoYS3WhpuMd3T/w@faui48e.informatik.uni-erlangen.de> <BC48ED92-9D74-4BE2-A22A-0A1B6B01D32D@ifi.uio.no> <Yyykn/QtPqCohiOp@faui48e.informatik.uni-erlangen.de> <A61FAA0A-20B6-4C77-B78C-B320CABB321B@ifi.uio.no>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <A61FAA0A-20B6-4C77-B78C-B320CABB321B@ifi.uio.no>
Archived-At: <https://mailarchive.ietf.org/arch/msg/recipe/iZF7tQG7cvtWRqqc3N0ez2DOTt4>
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: Sat, 24 Sep 2022 17:17:36 -0000

On Sat, Sep 24, 2022 at 04:43:23PM +0200, Michael Welzl wrote:

[Carbon offsetting]

> Sure, such things is a useful thing to discuss - but still, to me, it may only be a drop in the bucket compared to the potential that the IETF has when it comes to reducing energy for the Internet.

Of course, looking at (1) carbon emissions of IETF meetings and maybe how to offset them and
(2) technology to reduce carbon emissions of Interneet technology start out as two completely
separate tracks now, but i find it quite hard to work on the second without starting
to have an opinion about the first. Especially when there is myths, pandering or sillyness
in the first.

> Whether the Internet truly makes up half, 1/4, even 1/10 of the aviation industry’s GHG emissions… just imagine the potential impact if we manage to even only reduce its energy by a small amount, but at a global scale!

Right. So when it comes to carbon offsetting of IETF meetings, instead of financing some
shady organizations that promise offsetting our travel emissions through 
"more trees in africa", instead we could account some of the reduction in the carbon
emissions in the Internet through our hopeful future work as our offset strategy.

> I think we shouldn’t focus on trade-offs too much. There are ways to reduce energy that do not embed a trade-off, and in some cases it can even be a win-win (shorter FCT = more sleep time for devices).

I know where you are coming from and i like that direction/work a lot as well, but i would
caution, that the benefits of it depend higly on the energy efficiency curve of compute/networking
equipment. All the "bulk" solutions will loose value if that curve would turn linear. 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).

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