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

Hesham ElBakoury <helbakoury@gmail.com> Sat, 24 September 2022 14:52 UTC

Return-Path: <helbakoury@gmail.com>
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 E30B5C152567 for <recipe@ietfa.amsl.com>; Sat, 24 Sep 2022 07:52:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.105
X-Spam-Level:
X-Spam-Status: No, score=-7.105 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.001, 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, 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=gmail.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 ILkkq9Xsecv9 for <recipe@ietfa.amsl.com>; Sat, 24 Sep 2022 07:52:24 -0700 (PDT)
Received: from mail-qv1-xf34.google.com (mail-qv1-xf34.google.com [IPv6:2607:f8b0:4864:20::f34]) (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 0DCFDC1524D1 for <recipe@ietf.org>; Sat, 24 Sep 2022 07:52:24 -0700 (PDT)
Received: by mail-qv1-xf34.google.com with SMTP id c6so1759128qvn.6 for <recipe@ietf.org>; Sat, 24 Sep 2022 07:52:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=in-reply-to:from:references:to:content-language:subject:user-agent :mime-version:date:message-id:from:to:cc:subject:date; bh=F2Km9hlpcStI4j+KqTNp4YMcevs/8A7eLkJHEMQ+Slk=; b=Klmti3is+PYQ2YDs+SrnFVpMuXRoXUMLU1zdNZZ5cvlbkYcHf2IVwerwTBA63fzgPz rsio6CDBOYr3C+vAzupoea1aDIAMrvGtLCfisEjwjiJEINzKQ4FewwiQG3NjMQrQJmrq /LXvZaVvTun9Dg9H43Zts5HwMZiqJEJH5RBtLMNs5kCAU6WVsApKFFhCo5flXvWUom3p CWuRizrXDYazdCexHkP4x4UHyJseXxi87haT9mfyK93rkos0oFzGrEVSt0MUMzFcxKK9 ey52qEGUNRQIopNKUY9CgzzAGA1eg+jN8V/g+LtpygLBlUDGEDsVFKP3Bom9vcUTUKMd ueeA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=in-reply-to:from:references:to:content-language:subject:user-agent :mime-version:date:message-id:x-gm-message-state:from:to:cc:subject :date; bh=F2Km9hlpcStI4j+KqTNp4YMcevs/8A7eLkJHEMQ+Slk=; b=F73fEIykBLQxv/7mvtIqCEIiAsHQGYVjEuZ13eh2CS2HpOugq85RD4pGS+VF751V8o RZGELBRKMDf8pTYMwkvjxXNdwCwXw/INtWKfrs7HnpvERHJ0NaUf/BqmxHp6G6lnhk7m bGHgCYy1F8/n5RPAC5rS8u1AsYF3W80mLJcWanQ61u0eRE6/XGmRytkumWoQ1rEsCgR3 nLgafjYGG6Va7ZFOT94g1x1Bges+HGkRFZsn4TEhrOHj1RPmyXH8uP2P5T/4/dGiB8QR WIGOYhPo65UNFrxz03QWDqepL2QtlJA63IqZIPwN9XS38aXOv5DgADgntulQHNHnpJAn TWhg==
X-Gm-Message-State: ACrzQf2jkOnGJ2k1QsFbZJeeIor9D7lI0fkn3mHY/QO2GiZ2aiYIhBTo nijS8mtT+33zD65VnSQ2OnEEHrPURsq/xQ==
X-Google-Smtp-Source: AMsMyM5Fy3oWnp8YJmHA+qz2CZXDE+IlN42GAbHVTPl4Zyc+9Y1NiEGrvLmKUPUHKwXRmIZKXQEc3A==
X-Received: by 2002:a05:6214:5289:b0:4ac:c9f9:909c with SMTP id kj9-20020a056214528900b004acc9f9909cmr10810525qvb.34.1664031142039; Sat, 24 Sep 2022 07:52:22 -0700 (PDT)
Received: from ?IPV6:2602:306:cc88:d219:40cf:293d:d47a:d433? ([2602:306:cc88:d219:40cf:293d:d47a:d433]) by smtp.gmail.com with ESMTPSA id j12-20020ac8440c000000b0035d0655b079sm7018826qtn.30.2022.09.24.07.52.20 for <recipe@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sat, 24 Sep 2022 07:52:21 -0700 (PDT)
Content-Type: multipart/alternative; boundary="------------hpb8QoX9CRNP0800ogeEPVMS"
Message-ID: <17d5c7cd-f5ce-9974-7fba-5bf63a27667c@gmail.com>
Date: Sat, 24 Sep 2022 07:52:17 -0700
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.13.0
Content-Language: en-US
To: recipe@ietf.org
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>
From: Hesham ElBakoury <helbakoury@gmail.com>
In-Reply-To: <A61FAA0A-20B6-4C77-B78C-B320CABB321B@ifi.uio.no>
Archived-At: <https://mailarchive.ietf.org/arch/msg/recipe/7I6dqzCHZDaPiCbMt4j7MXCSeq0>
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 14:52:29 -0000

I certainly agree with Mike about what he mentioned below: "*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.**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!"*

Hesham*
*

On 9/24/2022 7:43 AM, Michael Welzl wrote:
> Hi !
>
> I’m answering to both Toerless and Cedric in one email here.
>
> Toerless:
>
>> On Sep 22, 2022, at 8:08 PM, Toerless Eckert <tte@cs.fau.de> wrote:
>>
>> Michael:
>>
>> There where unfortunately only very few folks attending the IETF LLC 
>> admin meeting here
>> the current IETF plan to simply start to estimate the IETF meetings 
>> CO2/greenhouse-emissions
>> was presented. But it did look like a good first small step on a long 
>> road.
>>
>> For something like IETF meetings the next logical step IMHO is to 
>> discuss if or how there
>> is a benefit in some form of carbon offsetting. I think they've 
>> planned that as a next step.
>> I'd certainly like to learn more about that option because all i've 
>> read so far about it
>> is that most carbon offsetting seems to look fairly problematic to 
>> me. But maybe there are
>> some good options.
>
> 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.
> 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!
>
>
>> On the admin-discuss mailing list there was also an interesting 
>> pointer to a european
>> conference recommendations how to minimize carbon emissions for 
>> meetings. It looked
>> pretty good except that it didn't put different options into 
>> perspective. E.g.: it said
>> that reduccing video conference resolution from HD/4k to SD would 
>> reduce up to (forgot, e.g.:)
>> 70% energy consumption. Which i think may be true that lets say some 
>> 5% of the total
>> video stream network required energy might be changing based on 
>> resolution, even the whole
>> 100% of the network/end-user energy requirements. Which in itself 
>> would likely be just a small
>> portion of the energy of in-person meeting. In my 
>> draft-eckert-ietf-and-energy-overview,
>> i cited https://www.sciencedirect.com/science/article/pii/ 
>> S0140366414000620 which is a bit
>> old by now (aka: energy consumption of video likely having gone down 
>> already due to lower energy
>> per bit now), but still a good example of a comparative approach.
>
> I would be against trading quality of online meetings: as you say, 
> this is a tiny portion of the energy of in-person meeting … so it’s 
> probably more important to ensure the best possible online experience.
> 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).
>
> 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/ 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 (or: 
> 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
>> 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
>
>
> _______________________________________________
> recipe mailing list
> recipe@ietf.org
> https://www.ietf.org/mailman/listinfo/recipe