Re: Next steps towards a net zero IETF

Daniel Migault <mglt.ietf@gmail.com> Wed, 22 March 2023 03:05 UTC

Return-Path: <mglt.ietf@gmail.com>
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 29BEAC14CE4D; Tue, 21 Mar 2023 20:05:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level:
X-Spam-Status: No, score=-2.096 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, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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 0Z7zAMUBCi7p; Tue, 21 Mar 2023 20:05:23 -0700 (PDT)
Received: from mail-yw1-x1135.google.com (mail-yw1-x1135.google.com [IPv6:2607:f8b0:4864:20::1135]) (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 CEA2CC14CEFA; Tue, 21 Mar 2023 20:05:23 -0700 (PDT)
Received: by mail-yw1-x1135.google.com with SMTP id 00721157ae682-5416b0ab0ecso315313607b3.6; Tue, 21 Mar 2023 20:05:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; t=1679454322; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=gij/AVGLcVzZONsNxuGky4gH3vFr1k5ZeHIuMenhLNs=; b=UG30slgQa4p4OFFHmb8LO1ORbNasa4jUGizex4i6qvhC1L7kgccvP9+84+TJN+5GfM s2pkRzBLa781KQ1/ShLAARuMbOmFNPWSTT/nb5QuM81GIR1m9bIXDnIQDWKdYuoW9Nmc neuccqCoA0LHk4qcZw/e2E5xV0EHfvxYsngm2vGGYysC9a7HG/KTCmau6YqsJbvr/OYv en2wl33Q6Wzpq6pKy68uuHZlU+ZIlVTzFy9dR3Fg/bD+jttID357KQnhJLeHTU3EBSuC 9EI7SlB1gvCafaHMYKQZ+poCvVL9zPOolnGzeNPML/CpXOaNsJRTrqav2PknCqKBhZ1z JF2A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1679454322; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=gij/AVGLcVzZONsNxuGky4gH3vFr1k5ZeHIuMenhLNs=; b=Tf/o3smgem+1aaxAWJ/4MLTapc9sL9SqLIRXO0XxTrOpgYOa1tOSe4UUbcs7sMn9J+ dSNo7eDpafVO4D28yyuHiYKEI1sv00BNsx4H0fyXTKZDANH8PM1oz78gqa8mMaiTcRXO J+WA5cg9v3CrZ/0CotnrWG7tyHusUupYAaaK8gzqdq9gEfmwWPX1ac4XutpHO6j5od4C SOflu7sFBwXogLnjd8CuSnmzHrY7cs/mMQ3pNmTNzv1JypPbdfQgD4VQjiJUGcjrXWGX 5PqZQyWl9sAHdkAKP2garUi9kl4isC+lCiOqfLstCSvLr442L+f/Ur9URZbFbkUfK0CG 27Dw==
X-Gm-Message-State: AAQBX9ewVDTjGRWwxmpFaE+9tpFyLe3aiR8rqWlvserlbwL+jhYYhvI2 3EomhEYdn0xCmdnwDJA2yjvPSVGvOFLCnE25HuKnAM48qFelkw==
X-Google-Smtp-Source: AKy350aUtkgMVT3LSs3gHB3M5Ymo7BnRZ6PrD0tN9Dtz1EaG83MGW6y7OYlfm80+ZFZRSTxmzDcGzRVA8uPGIK4qw9c=
X-Received: by 2002:a81:a8c4:0:b0:545:621b:5076 with SMTP id f187-20020a81a8c4000000b00545621b5076mr521754ywh.2.1679454322772; Tue, 21 Mar 2023 20:05:22 -0700 (PDT)
MIME-Version: 1.0
References: <02F23373-9F6A-420E-91B3-C1ADE5AF2A60@staff.ietf.org> <9E0F20AE-11BC-4CFC-84FB-83F8E1969A4F@live555.com> <MEYP282MB356447F9DCCAC59C5E978B63A3869@MEYP282MB3564.AUSP282.PROD.OUTLOOK.COM> <10fff5a5-6faa-9fe0-8e8f-da05e6e75c16@huitema.net>
In-Reply-To: <10fff5a5-6faa-9fe0-8e8f-da05e6e75c16@huitema.net>
From: Daniel Migault <mglt.ietf@gmail.com>
Date: Tue, 21 Mar 2023 23:05:11 -0400
Message-ID: <CADZyTkkzn6GH8x6VUyFQSWucQJq2sN+ko-+LY4yC8R9bkUY7ew@mail.gmail.com>
Subject: Re: Next steps towards a net zero IETF
To: Christian Huitema <huitema@huitema.net>
Cc: Raghu Saxena <poiasdpoiasd@live.com>, Ross Finlayson <finlayson@live555.com>, admin-discuss@ietf.org, ietf@ietf.org
Content-Type: multipart/alternative; boundary="000000000000534e4305f7746e1b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/8bgtkQhtnWcVvMjQUD1hICm57ag>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "IETF-Discussion. This is the most general IETF mailing list, intended for discussion of technical, procedural, operational, and other topics for which no dedicated mailing lists exist." <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: Wed, 22 Mar 2023 03:05:26 -0000

On Tue, Mar 21, 2023 at 10:11 PM Christian Huitema <huitema@huitema.net>
wrote:

>
>
> On 3/21/2023 6:39 PM, Raghu Saxena wrote:
> > That's a pretty interesting note, and one which I think deserves a
> > proper discussion. Considering how much more energy use is going towards
> > the internet everyday, I do believe IETF plays a crucial role in
> > increasing the efficiency (energy wise) of the internet.
> >
> > For instance, by moving towards HTTP/3, if we reduce the RTT to
> > establish a connection, that's less CPU time spent on establishing the
> > connection, less electromagnetic radiation (fiber optics / wireless)
> > required, since now x less packets need to be transmitted etc.
> >
> > I do think using available funds for further advancing the goals of IETF
> > directly would be a better use - you could argue that IETF is producing
> > carbon offsets as a direct consequence of its work!
>
> Efficiency increases are an obvious good thing but in the past,
> efficiency increases have been matched by increases in Internet usage,
> such as more videos or larger images, and I am not sure the total energy
> consumption decreased over time. If it did decrease, that means saving
> energy, but most of the energy saved comes in the form of electricity.
> Only a fraction of the electricity is produced by burning carbon based
> fuels, and that fraction is supposedly decreasing over time as cleaner
> techs replace burning coal, oil or gas.
>

Regarding the emissions associated with a phone or a cpu during its
lifetime, I think that most of these emissions happen during the
manufacturing and transport of the device/hardware - as opposed to the
device running. That is more or less what you are saying below.


>
> We could argue that tools such as video conferences do directly save
> carbon emissions by reducing the need for physical travel. That's
> plausible, but very hard to measure because the Internet also enables
> making friends in remote places, which is a very good thing but
> ultimately encourages more traveling.
>
> And then there is a counter argument that the Internet enables more
> international commerce, e.g., someone in America buying widgets from a
> producer in China through Amazon or Ali-Baba. These items have to be
> shipped across continents, so in a sense the Internet contributes to
> increased carbon emissions. I have no idea how all that balances, and I
> would indeed be delighted to read a good study. But that seems a job for
> ISOC, not the IETF.
>
> As far as the IETF is concerned, the direct challenge ought to be
> whether we can be as efficient while traveling less, or at least by
> relying less on long distance air travel. We did run a two years
> experiment during Covid, and the results have been mixed: work kept
> progressing, but some measures like number of version-00 drafts did
> regress. We have to do better!
>
I am questioning the metric here - especially if that is the only thing we
have found - as a 00 draft is probably the easiest way to justify the need
to travel ;-).


>
> -- Christian Huitema
>
>

-- 
Daniel Migault
Ericsson