IETF Logo Mail Archive

Re: Next steps towards a net zero IETF

Wes Hardaker <wjhns1@hardakers.net> Tue, 21 March 2023 17:10 UTC

Return-Path: <wjhns1@hardakers.net>
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 DE01CC14CE47; Tue, 21 Mar 2023 10:10:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 qEYguSCokGbT; Tue, 21 Mar 2023 10:10:19 -0700 (PDT)
Received: from mail.hardakers.net (mail.hardakers.net [107.220.113.177]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 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 2914AC14CE40; Tue, 21 Mar 2023 10:10:19 -0700 (PDT)
Received: from localhost (unknown [10.0.0.9]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mail.hardakers.net (Postfix) with ESMTPSA id D4ACF206F2; Tue, 21 Mar 2023 10:10:18 -0700 (PDT)
From: Wes Hardaker <wjhns1@hardakers.net>
To: Greg Wood <ghwood@staff.ietf.org>
Cc: Christian Huitema <huitema@huitema.net>, admin-discuss@ietf.org, ietf@ietf.org
Subject: Re: Next steps towards a net zero IETF
References: <02F23373-9F6A-420E-91B3-C1ADE5AF2A60@staff.ietf.org> <928d9a46-ff69-12df-fc30-b0ff7f1f8cec@huitema.net> <B8DF18B2-77A2-4A6B-962A-DEFBB1EDFF5A@staff.ietf.org>
Date: Tue, 21 Mar 2023 10:10:18 -0700
In-Reply-To: <B8DF18B2-77A2-4A6B-962A-DEFBB1EDFF5A@staff.ietf.org> (Greg Wood's message of "Tue, 21 Mar 2023 12:19:35 -0400")
Message-ID: <ybl5yaujait.fsf@wd.hardakers.net>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.2 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/BJrTJoA9n2lzenC9Ke3p7l3RTpQ>
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 17:10:20 -0000

Greg Wood <ghwood@staff.ietf.org> writes:

> 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.”

Let's say that we [the IETF community] wanted to start with at least a
shift to 1 online meeting a year.  What's the next earliest meeting we
could try that with [and I say try knowing full well we've done many
online meetings]?  IE, it would need to be one that we're not under
contract with, or not super close to contracting right?  That would mean
IETF 119?  The upcoming meetings list currently has places listed for
everything through July of 2025 but IETF-119.

-- 
Wes Hardaker
USC/ISI

v2.23.0 | Report a Bug | By Email