Re: [Manycouches] Daniel presentation @ 113

Daniel Migault <mglt.ietf@gmail.com> Tue, 12 April 2022 16:44 UTC

Return-Path: <mglt.ietf@gmail.com>
X-Original-To: manycouches@ietfa.amsl.com
Delivered-To: manycouches@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 315D53A09EB; Tue, 12 Apr 2022 09:44:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.107
X-Spam-Level:
X-Spam-Status: No, score=-2.107 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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rjCYE1AErch1; Tue, 12 Apr 2022 09:44:07 -0700 (PDT)
Received: from mail-lj1-x22c.google.com (mail-lj1-x22c.google.com [IPv6:2a00:1450:4864:20::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3CB843A095C; Tue, 12 Apr 2022 09:44:07 -0700 (PDT)
Received: by mail-lj1-x22c.google.com with SMTP id m8so7336461ljc.7; Tue, 12 Apr 2022 09:44:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=lQI+2HcuELVwQ24c3I0krrCqmOu6KvHyhuIRMJgfb/g=; b=fPEpUCytLMDp4qrWa+uXHhOCyPFvh8QV5XG9pLP86BJEav6WQaibxvRkXHvW2Ac7vT OcZp1vUoga6AqLa3WBo56zJZtRBE7JRI+COw3tjalao+O6UjDfXGKGZmFWspu/L+/3sG LvPNtsoIvxo8pctvFUrhdGdF7RaTuam6kM3xfKiFZ+K6oowi3cNBuyAWHuXr/lnAGcng QUHvJ/TOQEMtXWZMaIEjBVRHXs/Od+eE0nuIy1VazcxLhbOOJhZHMVULK2+8Gct9gwTG 3SF+ExEk7uEL9PzQ+Dduuyb9+Gy2Ufebgr9vbA9HKuqfF+qmGeCWfCBRsTw3eGnEZW4X YWZg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=lQI+2HcuELVwQ24c3I0krrCqmOu6KvHyhuIRMJgfb/g=; b=IG1pQDaxAactgacDDBNKIg+LpLghHugLDdctTW+t/IaCt4EPu2QQDfeO1ycDh62hjE Tk9qfMQquwhFOCmbX6AtEaUtYUt6U+ar/916bZJ9Hz1LpMyFXqfn/UzDy/CX3X9RO2Nt ejdk8rEugnBcv3SAT7EznsgFE+bfZ0smnvTxZJs5hUvKoI8GvKH289pjCpMuHyUYIhPu 0l8turojxyv1Vk5QUUJ6YM+yfQtQ2PQG8iQs76TlM2PMVPECIfCDMcDOiLeDtvTe9315 f8oNcbHijswkNTM8S8LCv2qn10D0Pu2k7WtWSpxD2IuGmDePyyRZQcCkJej+Ihk8OVuP LOLw==
X-Gm-Message-State: AOAM531KEwNTl0V1bWV6wxoDJlNCVNuYHG6aYb9wueshHvj5gL+xWdDM lvieQD9HaUkezGejOyjilO5IpCjySRFBHWVFunIvvgOJKYQ=
X-Google-Smtp-Source: ABdhPJxL14Jd0z0znosNrhwrtMloFrAFr/KtcuPGcrVZTuZjFiu24qnClXaSKqG+81c9BRJi5e0pRkwf9BOXvbro8bs=
X-Received: by 2002:a05:651c:901:b0:24b:23ff:b7a9 with SMTP id e1-20020a05651c090100b0024b23ffb7a9mr23517531ljq.194.1649781844689; Tue, 12 Apr 2022 09:44:04 -0700 (PDT)
MIME-Version: 1.0
References: <7e716ee4-d243-1a1b-cd61-b2adb541350a@lear.ch> <7985BE2D-F76A-454D-A87D-43D4B4968314@ietf.org> <a04d6879-fd32-56c7-f3da-ae37231c29a3@lear.ch>
In-Reply-To: <a04d6879-fd32-56c7-f3da-ae37231c29a3@lear.ch>
From: Daniel Migault <mglt.ietf@gmail.com>
Date: Tue, 12 Apr 2022 12:43:53 -0400
Message-ID: <CADZyTkmP-KvXMMFhc7ZrB8p=FGTrjtxB9Xxuzh=HxrUSHyw4EQ@mail.gmail.com>
To: Eliot Lear <lear@lear.ch>
Cc: Jay Daley <exec-director@ietf.org>, Manycouches@ietf.org
Content-Type: multipart/alternative; boundary="000000000000cf481805dc77c462"
Archived-At: <https://mailarchive.ietf.org/arch/msg/manycouches/WZFa4iONLtM1bUYSzaYjN4H1zz8>
Subject: Re: [Manycouches] Daniel presentation @ 113
X-BeenThere: manycouches@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "List for discussion of remote meeting attendance and virtual IETF meetings, as well as for SHMOO working group" <manycouches.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manycouches>, <mailto:manycouches-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/manycouches/>
List-Post: <mailto:manycouches@ietf.org>
List-Help: <mailto:manycouches-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manycouches>, <mailto:manycouches-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Apr 2022 16:44:13 -0000

Hi,

We are mostly talking about reducing the number of IETF meetings as three
meetings represents on average 12 673 tonnes of CO2 / year. It is
measurable. It is a main source of upstream emissions in corporate
organizations (see [1]). We have a direct impact on it. It is a direct
offset and it shows the path to other organizations.

I do agree that we need to focus on the solutions that have the most
potential. This is especially where offset can be challenged and the reason
to publish a sustainability and corporate responsibility report for the
IETF - as did Ericsson recently for example [1].

As a side comment, the evocation of the kerosene lamps - at the shmoo
meeting resonated with me a bit with a 1000'nish wealthy people asking 1.3
billion of (poor) people to replace their lamp so we can travel. I would
like to clarify that the intent was to illustrate that one needs to focus
where it has the most impact.

The potential that protocol represents remains to be shown. I am happy that
those raising such assertions share their data, publications. So far - as
mentioned in the session - my understanding is that most emissions come
from the extraction, manufacturing and transport of the products. As a
result, I am relatively not optimistic on the impact of a section "Carbon
emissions considerations" - but happy to be wrong.

Yours,
Daniel

[1]
https://www.ericsson.com/en/about-us/sustainability-and-corporate-responsibility/sustainability-report

On Tue, Apr 12, 2022 at 11:29 AM Eliot Lear <lear@lear.ch> wrote:

> Hi Jay,
>
> Thanks for your message.  Please see below.
> On 12.04.22 11:56, Jay Daley wrote:
>
> Hi Eliot
>
> The major point about offsetting, which I think we agree about, is that
> offsetting is an "after the fact" action, not a preventative measure.  I
> understand that some will say "what’s the harm in meeting X times, if we
> offset all the emissions" but, without commenting on the rights and wrongs
> of that, the response to that should not be to attack offsetting as a
> concept.  Instead, we should be taking the approach that it is vital for us
> to offset all of our emissions, whatever the level of those emissions.  In
> other words whether we meet three times a year or once a year, we should be
> offsetting those emissions.
>
> I 100% agree.  And I further agree that we MUST meet.  I opine that we
> should meet in person LESS but when we do meet, we SHOULD offset our
> impact.  What we SHOULDN'T do is think of offsets as a pure substitute.
>
>
>
> When it comes to choosing the offsetting mechanism(s), the plan I outlined
> at shmoo was to bring in experts to hold some open sessions where they
> explain the various methods and help us make an informed choice.  As
> someone in shmoo pointed out, one of the largest aggregate emitters of
> carbon are kerosene lamps and schemes aimed at replacing those are direct
> offset schemes, not a carbon credit market.
>
> Good to know.
>
>
>
> When we discuss how often to meet in person, I strongly recommend looking
> at the data from our post-meeting surveys:
> https://www.ietf.org/how/meetings/past/  Reading through all of those
> shows some clear data points:
>
> - productivity at in-person meetings is, on average, much higher than
> remote meetings,.  Sure, we can’t quantify this and we don’t have the other
> links in the chain to measure if that increase in productivity leads to a
> reduction in effort elsewhere.
>
> - the ability of people to come to in-person meetings depends very much on
> where the meeting is held.  If we drop down to one meeting per year then we
> will rotate through every region over a three year cycle and for many
> people that will mean they can only meet in person once every three years.
>
>
> Neither of those are meant to be "that’s why we should continue to meet 3x
> a year" arguments, just points to consider in the overall debate.
>
> As I wrote, I didn't provide a specific recommendation.  That's because I
> could see this working in quite a number of ways forward, and I'd like to
> see shmoo explore them.  A few possibilities include the following:
>
>    - Mandatory virtual interim meetings at a certain tempo
>    - Mandatory in-person interim meetings
>    - Raising the requirements for working groups to meet in person,
>    including at the plenary meetings.
>       - Required controversy
>       - Virtual meetings held
>    - A cap on the number of in person meetings for working groups.
>
> These are just a few possibilities, and it is by no means an exhaustive
> list.
>
> I realize figuring our way forward here would wreak havoc with our
> conference planning, and with the lives of the people who provide us an
> excellent experience, but at least to me, the risks of not acting are too
> high.
> Eliot
> _______________________________________________
> Manycouches mailing list
> Manycouches@ietf.org
> https://www.ietf.org/mailman/listinfo/manycouches
>


-- 
Daniel Migault
Ericsson