Re: Next steps towards a net zero IETF

Alexander Pelov <a@ackl.io> Tue, 21 March 2023 22:06 UTC

Return-Path: <alexander@ackl.io>
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 A981AC1524A3 for <ietf@ietfa.amsl.com>; Tue, 21 Mar 2023 15:06:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.894
X-Spam-Level:
X-Spam-Status: No, score=-1.894 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, SPF_PASS=-0.001, 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=ackl-io.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 LOzpxjF-1W1L for <ietf@ietfa.amsl.com>; Tue, 21 Mar 2023 15:06:21 -0700 (PDT)
Received: from mail-lf1-x12e.google.com (mail-lf1-x12e.google.com [IPv6:2a00:1450:4864:20::12e]) (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 0BC19C1516E1 for <ietf@ietf.org>; Tue, 21 Mar 2023 15:06:20 -0700 (PDT)
Received: by mail-lf1-x12e.google.com with SMTP id q16so10129397lfe.10 for <ietf@ietf.org>; Tue, 21 Mar 2023 15:06:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ackl-io.20210112.gappssmtp.com; s=20210112; t=1679436378; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=D9+/uFTCqc6rHMwU0mn0y/pI9Nveh5JIm1BS25RHJ9U=; b=61GFnRvkpDI8XvTncEDVjDgVpXm2jkBESQSjaRAzoP2lFmKLAaZ33VVenELR1F34pZ XOtbuwGOXzJahXWN0F35ePhsBmXkLz8cSfkP2baF+ix1zwh/I6SpLPxGrtCeWCkart6k PCmIpj/pLuN1FKzQN4Yn4WzGYMkxtCyKU+VYbhza0EPFbxOAfZlnQ629lDk1cz8xhowF MJEtlnZBV/MqzAgzOiExKChqVkyWhWmBl8kmS1fiH/MAVRgUzWbx5C1pC79u4eNYONFn QojwvIE0u3aR35JHQSt4aQfTpj6WXSuDr9bctvfHRoDa+MZWdNFGc7jep67ifAi+DtFI bw2w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1679436378; 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=D9+/uFTCqc6rHMwU0mn0y/pI9Nveh5JIm1BS25RHJ9U=; b=E+ZzF0aAnWIcQaCtWMdWFb2T44jdbM6oF8UBlDK3DM9AmktrCkeUGWlT0+Wgs4o3MV nxEpXxErB0x6t0APMbjKmn7LssKpEVguIOLSFbvH+wbsmB2BW/VLmgEItKgXZ+Bkm3oP w8mfsVqlE+0wmmGRnHmpnZ8RXUbTPYlovUxo9qJHxiQdiw6Qi+IOfLE/oaHThZvnc6dd PBr28s/SafLysX7CdKXtj49t8iBILM1yGGb3tjoHUjYUUUUelaC9fDSUviZD+zT61ue7 yFfHLKTx/8T/bDPolJF7mETir4W0tSRVc2JQCmJHnKrbp9QM3nGrDddGV+q3TmT8JhHc ONtw==
X-Gm-Message-State: AO0yUKUvejjzImQyBMDLnflZLZZm2tPc3xwhP31AEf0AiclB0pIFy5mn 6RyeGdnLU6LqFxSMNEhyXXbB86O9t6LRKvubtHxqBA==
X-Google-Smtp-Source: AK7set8LFW8iGd/xVEaUpXUzjr44jdsDxwT9v4aBN9lb5twEPkIwkhlM8d6C5Io9vxIiS3mwK3YpLMWIIGUppbOrxlA=
X-Received: by 2002:ac2:508b:0:b0:4dd:9931:c555 with SMTP id f11-20020ac2508b000000b004dd9931c555mr52356lfm.0.1679436378282; Tue, 21 Mar 2023 15:06:18 -0700 (PDT)
MIME-Version: 1.0
References: <02F23373-9F6A-420E-91B3-C1ADE5AF2A60@staff.ietf.org> <928d9a46-ff69-12df-fc30-b0ff7f1f8cec@huitema.net> <B8DF18B2-77A2-4A6B-962A-DEFBB1EDFF5A@staff.ietf.org> <316ff116-535a-d0c0-31e8-ff2ca3fe5871@lear.ch> <97d4fa2f-6ba0-ff49-1e8a-a1d6ea13d8ad@gmail.com>
In-Reply-To: <97d4fa2f-6ba0-ff49-1e8a-a1d6ea13d8ad@gmail.com>
From: Alexander Pelov <a@ackl.io>
Date: Tue, 21 Mar 2023 23:06:06 +0100
Message-ID: <CACQW0EqZbM5NGE8Yy7c5d3UEsx+1rF8k3nv0_fR14nvLygkz+A@mail.gmail.com>
Subject: Re: Next steps towards a net zero IETF
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Cc: Eliot Lear <lear@lear.ch>, Greg Wood <ghwood@staff.ietf.org>, Christian Huitema <huitema@huitema.net>, admin-discuss@ietf.org, ietf@ietf.org
Content-Type: multipart/alternative; boundary="000000000000c030c205f77040d2"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/8Dzj9HKYMgZ1RTGi88kS3H7Rd3Y>
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: Tue, 21 Mar 2023 22:06:24 -0000

Hi all,

First, I'd like to thank the IETF LLC for measuring the carbon footprint
over the years and the events - I was hoping someone would do something
like that for any kind of conference / event and then provide a way to
compare/improve this metric.

Here's the thing : are we sure the IETF's footprint is *not already zero*?

I fully understand the notion of "current best practices" about this type
of calculation - my question is mostly related to - are these best
practices applicable to the IETF meetings? Are the laws of big numbers
applicable to a tiny (compared to all air traffic) group of people? And if
not - what should we do? (Probably nothing?)

Maybe I'll be adding to the "noise" in this discussion, but there has been
a question that's been bothering me for a while, and it is touching my
level of incompetence on the subject.

I have never chartered an airplane to go to a meeting, and none of the
people I know have done so. I don't know of any hotel having been built for
an IETF meeting, and although I tend to eat out more at in-person meetings,
I try sticking to 3 meals a day (cookies don't count).

Did London, or Prague, or Singapore see bigger planes arrive for the IETF?
Or more of them?

Air transportation doesn't seem to be "elastic enough" for a single meeting
of 2k-4k people somewhere around the world to make any difference. During
the lockdowns there were planes flying empty, just to keep the slots at the
airports occupied! (how crazy is that!)

My take on that is that even if we go entirely online, the *real* net
effect will be 0.
On paper there will be a difference, of course.

And in-person meetings seem *so much more productive* to me.

The real question that bothers me is - can the IETF do anything about it?
(even if we wanted to)
- We're obviously not going to be able to just say "hey, we're all good -
the system is not elastic, so nothing to do here"
- Get a draft about this and liaise to the organizations that provide the
BCP in carbon footprint estimation, so that the core of the issue is
addressed.. which sounds like a difficult topic.
- Something else?

Cheers,
Alexander




On Tue, Mar 21, 2023 at 10:13 PM Brian E Carpenter <
brian.e.carpenter@gmail.com> wrote:

> Eliot has a point. As long as the community instructs the LLC to organize
> f2f meetings every four months, carbon offsets are about all they can do,
> unless we also instruct them to invest in a large fleet of pedal-powered
> airships.
>
> Regards
>     Brian Carpenter
>
> On 22-Mar-23 09:48, Eliot Lear wrote:
> > As one of the people who made a stink about this, I would rather we not
> criticize the LLC for doing what they can to (a) quantify the situation
> (yay!) and (b) at least try to offset some of the damage that *WE* cause.
> Yes, the community is causing the damage by getting onto planes in the
> first place.  Some of that hard to avoid.  Let's face it: we sometimes have
> differences that really need face time and not just FaceTime.  That should
> not be used as an excuse to unnecessarily travel, and I encourage WG chairs
> and ADs to question the need for in person time at every opportunity.
> >
> > Eliot
> >
> > On 21.03.23 17:19, Greg Wood wrote:
> >> Hi Christian,
> >>
> >> Thanks for your note.
> >>
> >> A few points that are explained more thoroughly in the blog post and
> the report [1]:
> >>
> >> 1) “...changing how the IETF operates, such as by reducing the number
> of in-person IETF meetings, are out of scope for this [IETF LLC] effort as
> those should be community-led discussions.”
> >>
> >> 2) A significant part of the project was and is to calculate the carbon
> footprint of IETF operations, which would, it seems, be a foundation for
> community considerations about reductions. And, of course, reduction and
> offsetting are not mutually exclusive.
> >>
> >> Finally,  I want to be clear that “PR gain” was definitely not a
> motivator for, nor a goal of, this project.
> >>
> >> While skepticism about carbon offsetting is not unwarranted, I can say
> with confidence that the IETF LLC staff, Secretariat and other people who
> have worked on the project were and are focused on doing what we can to
> improve the actual situation, and not just appearances. IETF participants
> have fairly consistently indicated they are in favor of being more
> environmentally sustainable, and this seems like a reasonable step towards
> that goal, while also being in scope for the IETF LLC.
> >>
> >> Regards,
> >>
> >> -Greg
> >>
> >> [1]
> https://www.ietf.org/blog/towards-a-net-zero-ietf-next-steps/,https://www.ietf.org/media/documents/IETF-Carbon-Neutral-Strategy-20230216.pdf
> >>
> >>> On Mar 21, 2023, at 11:15, Christian Huitema<huitema@huitema.net>
> wrote:
> >>>
> >>> I am pretty disappointed to see the IETF LLC investing in the "carbon
> offset" strategy, let alone paying consultants to produce an expensive
> report.
> >>>
> >>> Carbon offset is basically all about PR -- an excuse for not reducing
> the carbon footprint of an organization. The actual benefits for the planet
> are mot often illusory, and quite often straightforward scams.
> >>>
> >>> Let's please focus on the harm reduction part, not the PR maximization
> part.
> >>>
> >>> -- Christian Huitema
> >>>
> >>> On 3/21/2023 6:42 AM, Greg Wood wrote:
> >>>> Hello,
> >>>> Built with input from the IETF community, we now have an initial
> approach and tools for calculating the IETF’s carbon footprint and a
> strategy for carbon offsetting. For 2023, we will implement this approach
> with data already available and seek to further improve it for future
> years. A blog post provides additional information and a link to a full
> report is at:
> >>>> http://www.ietf.org/blog/towards-a-net-zero-ietf-next-steps/
> >>>> We hope to explore options for improving carbon footprint
> calculations and to gather additional information about the community’s
> preferences for carbon offsetting during a side meeting during the upcoming
> IETF 116 meeting:
> >>>> Pacifico North
> >>>> Room G301
> >>>> 8:30 JST on 30 March 2023 (23:30 UTC on 29 March)
> >>>>
> https://ietf.zoom.us/j/86826219211?pwd=QjhvdkY5YmxIWi9YeE9iMzFReFh3dz09
> >>>> Meeting ID: 868 2621 9211
> >>>> Passcode: ietfco2
> >>>> Details are also available on the IETF 116 side meeting wiki:
> >>>> https://wiki.ietf.org/meeting/116/sidemeetings
> >>>> Further discussion is also encouraged onadmin-discuss@ietf.org
> mailing list (and reply-to for this email has been set to that list).
> >>>> Please feel free to contact me directly if I can provide additional
> information.
> >>>> -Greg
> >>>> –
> >>>> Greg Wood
> >>>> Director of Communications and Operations
> >>>> IETF Administration LLC
> >>>> ghwood@staff.ietf.org
>