Re: Next steps towards a net zero IETF

Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com> Sat, 01 April 2023 11:13 UTC

Return-Path: <kathleen.moriarty.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 48ADAC151B35 for <ietf@ietfa.amsl.com>; Sat, 1 Apr 2023 04:13:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.098
X-Spam-Level:
X-Spam-Status: No, score=-7.098 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, RCVD_IN_DNSWL_HI=-5, 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 eounvT2Xcq9h for <ietf@ietfa.amsl.com>; Sat, 1 Apr 2023 04:13:24 -0700 (PDT)
Received: from mail-qv1-xf35.google.com (mail-qv1-xf35.google.com [IPv6:2607:f8b0:4864:20::f35]) (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 A305DC151535 for <ietf@ietf.org>; Sat, 1 Apr 2023 04:13:19 -0700 (PDT)
Received: by mail-qv1-xf35.google.com with SMTP id kr22so4106488qvb.5 for <ietf@ietf.org>; Sat, 01 Apr 2023 04:13:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; t=1680347598; x=1682939598; h=to:cc:message-id:subject:date:mime-version :content-transfer-encoding:from:from:to:cc:subject:date:message-id :reply-to; bh=jJhUtKxkIEGOQe2ijwUj7NBYdY1+CDACxCXtx0hQIdc=; b=JKey945COaE+Tjwj8Q8XOpuoaZ2/dwJztrgMZF6Ad6N0BKYtuH1spvhSj30IYelZbD J+H1jt1zyrHELXlvJldfSdsj24NoaBzman3IsQsJja2K8zU4vvFbqhlISrkOUrJF+7cD XbhP+uHZK4PzXtmpJe9Vx7TYFZA9IvRTJh4c35SiTG+wjtHmmMGzuQW2jJn/FOZtXhc2 muye6qYzJASbgu0CvKCieLro+zvmzKdbILI/mhAuVDu4+hrxcQ9sb4jtzdwgwlvIsJUK W3YTdqyeP3Iyw3Yzx/YVStKnBMWkbe8tPWTKwnI6R8lN9bdMpfI5XSCtJ91nOyRz4LmV xuOQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1680347598; x=1682939598; h=to:cc:message-id:subject:date:mime-version :content-transfer-encoding:from:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=jJhUtKxkIEGOQe2ijwUj7NBYdY1+CDACxCXtx0hQIdc=; b=q5Bs+Yv3Ujh+lcsDguGOhPMBIHstiyBChymaxxI8MHVai39mtvKp1sqn7bC5gHl30v HqS6gnjiQz1DADF3Lye1AaiLmT9OsYWptyAUTx37uxAiZYWgwisT3ZbzKwZ3ottS8qad nOkVtdkrwZPn7vF3IOtw5WXqCLxzKjoNHms7S0Ih9Dr9yhkVA4BsSWIdI8N6v6rhM0NS IEgg5Aj2ruF2tnpQIKXJGJnCnUUBEmboGAp5FBSE0vctfJO1E7J7HTSdMIkEyQhgFqGm SiHy6yv5zed6/QYYQyxCM5MqjI1EbphyLnF8CSWkT8cfFDJsarIWQzwmlRGVdtvEF0H8 E4PA==
X-Gm-Message-State: AAQBX9dyNGaJ1TI2jlPK2tBFIvO4mYFrgz45QH6fV6dE99lAJ/1wFjvR H+sn3G5bGN1FywxkjX3gSXYERYRRugk=
X-Google-Smtp-Source: AKy350bY4GgOhJm8gRpj6LzsCcmMAb3rpO4RLtEbptmpeqb7bJd/P8N7ZPlx2ypsmhe/Wu0LfN6oVQ==
X-Received: by 2002:a05:6214:23c5:b0:5b4:89b4:1b0a with SMTP id hr5-20020a05621423c500b005b489b41b0amr42690566qvb.10.1680347598397; Sat, 01 Apr 2023 04:13:18 -0700 (PDT)
Received: from smtpclient.apple (146-115-101-80.s7246.c3-0.arl-cbr1.sbo-arl.ma.cable.rcncustomer.com. [146.115.101.80]) by smtp.gmail.com with ESMTPSA id oh4-20020a056214438400b005dd8b9345e6sm1228872qvb.126.2023.04.01.04.13.17 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sat, 01 Apr 2023 04:13:17 -0700 (PDT)
From: Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>
X-Google-Original-From: Kathleen Moriarty <Kathleen.Moriarty.ietf@gmail.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (1.0)
Date: Sat, 01 Apr 2023 07:13:06 -0400
Subject: Re: Next steps towards a net zero IETF
Message-Id: <6A6D9CCA-A2DB-4D95-AA11-1C7D5657F9FF@gmail.com>
Cc: ietf@ietf.org
To: John Levine <johnl@taugh.com>
X-Mailer: iPhone Mail (20C65)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/xqLbMzIFCOcd4oYq-8LZdi1cffA>
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: Sat, 01 Apr 2023 11:13:25 -0000

Greetings!

Earlier in the thread, there was a request to hear from remote participants. I remained remote for this meeting as the distance to travel added too much away time in total. I am planning to be in San Francisco. 

In the past, I did stay up all hours to attend meetings. This was because of a direct responsibility as an AD at the time. For this meeting, I attended all sessions where I was a chair or presenting. I had co-chairs in the room or this would not have been possible. 

The presentation went well with me remote (my perception), but I did have someone in the room in case that helped.

I’m going to watch the recordings of meetings that happened in the very late hours and of course something is missed. 

I do think we can achieve more remotely, but we need to work together for that to be possible.

Michael’s suggestion for plenary meetings makes sense. I also appreciate WGs that meet frequently in between meetings as that lessens the need for travel too. The only problem with that (for me) is that I have a standing conflict with one of them and gave to decide each week what to attend.

I do think we can do better. We have to be willing.

Best regards,
Kathleen 

Sent from my mobile device

> On Apr 1, 2023, at 6:25 AM, John Levine <johnl@taugh.com> wrote:
> 
> It appears that Hesham ElBakoury  <helbakoury@gmail.com> said:
>> 
>> Hydrogen-powered planes were voted as one of breakthrough technologies this
>> year.
> 
> Not by anyone who understands the physics. To get a useful amount of
> H2 in a reasonable volume, it's compressed to 700 bar (10,000 psi)
> which requres a big heavy tank to contain it.  Unlike kerosene, H2
> is extremely flammable if it leaks; 4% in air can explode.
> 
> Even if someone figured out how to make the big heavy tank fit in
> an airplane, would you like to ride in a flying bomb?  I wouldn't.
> 
> Battery planes with rarely used jet fuel range backup might make sense
> if you can deal with the weight of both the battery system, electric
> motors driving some kind of propellor, and the fuel system, probably
> something like an existing jet engine. I'm not holding my breath for
> that, either.
> 
> I have seen claims about planes running on biodiesel made from
> plant and food waste but scaling that up will be a challenge.
> 
> I would rather the IETF stick to plausible technology and start
> with realistic models of the carbon budgets for our meetings and
> how they would change if we changed the way we met.
> 
> R's,
> John
>