Re: [admin-discuss] Next steps towards a net zero IETF

Abdussalam Baryun <abdussalambaryun@gmail.com> Tue, 04 April 2023 23:20 UTC

Return-Path: <abdussalambaryun@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 5843BC15256B; Tue, 4 Apr 2023 16:20:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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_NONE=-0.0001, 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 V1yg8qU47zxX; Tue, 4 Apr 2023 16:20:49 -0700 (PDT)
Received: from mail-lf1-x131.google.com (mail-lf1-x131.google.com [IPv6:2a00:1450:4864:20::131]) (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 C809DC14CEFA; Tue, 4 Apr 2023 16:20:49 -0700 (PDT)
Received: by mail-lf1-x131.google.com with SMTP id br6so44331891lfb.11; Tue, 04 Apr 2023 16:20:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; t=1680650448; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=0VIAWvD3KlfxnejnTTSKk6imQc3uLUNKSUhDhTV0N5M=; b=fuO5XHBLaAKOcDI5CH1HIW0+iWSHHLc6GIX8J2k+h+dX6xnXSIbrUMK8Z04lRYusw6 oFRjkQ82hHb2KorSL1jUOVgoIRJy9cpIMpUBVGRGH5VGsSAtqixvYdfQM3RkR0Qpt0+w fRasEwTulHCdOL/RGS/rEsS20bMjbNiiXkEBhb1BohEMnMO4+wVV7r9SJgEZt0AENHaf bPx9MqR6Gmeq5nG2FF6n1DXGZIOkndg7jtzn7zebeVmzgomkPNdu8pMeuRT6ymc/52l/ CfxMm0SrERFjCgT94qTE4bhN/6OHcZPK6KO1pflEqEsZJqXgj2tHUeP3E3aIXGrr31j5 wrIg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1680650448; 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=0VIAWvD3KlfxnejnTTSKk6imQc3uLUNKSUhDhTV0N5M=; b=XCQFGXcgXMHm7RENSQT1ohV2YkYk/+wzRqbUnJjF6j7DaZ4MhLF3vYV7t5yx9tgH8w 3H/JqNJODcpLAGmizGJQIHYeFXqpOdw9gb9a7eHkNCb4680W4i8aDA3CT1l8ziVPHwNr XfbMHwg86lx+TbWl78OaAFFckiWdyap+UNXn80Oi/VlBI7JrueexGdqqlKdtdnVfNXYl agUYvOjkOnNj1hz4CS0eJEWDlMwO49ewnc2jsvzrIr6quk+7bspc2A0OzQSO1ZyuBAsG Ug3p702WClAUTPMr92aWMb2ooDdQuRKzJR768aXXP9voM5ZxL8ud4Lx2Qf+Pg/blFxHM PCFw==
X-Gm-Message-State: AAQBX9ciPQY1yK0QFjOG4x3pRG3WzNDip0ZtrBSwSJNBJRvxcvtZJ1Nd DW4UmatGh473c1oXcrTjmv3+jD5qDbg3Ogtu+yg=
X-Google-Smtp-Source: AKy350ZGJJIAEpWcbFN2sdsU/AYRDlSIdpHe/gN8XIjNrpH6g9db5ajBL96iCr/TRbDViTsXreGIlsTNfRw+0+PyWRo=
X-Received: by 2002:a19:7515:0:b0:4ea:fa82:7f73 with SMTP id y21-20020a197515000000b004eafa827f73mr1265391lfe.5.1680650447750; Tue, 04 Apr 2023 16:20:47 -0700 (PDT)
MIME-Version: 1.0
References: <13153.1680560012@localhost> <2658CD52-2D36-43E5-973B-39EB713E6A27@eggert.org>
In-Reply-To: <2658CD52-2D36-43E5-973B-39EB713E6A27@eggert.org>
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
Date: Wed, 05 Apr 2023 01:17:50 +0200
Message-ID: <CADnDZ8-666_JE1GHBNKkGw7igozdh4zZdpCJwVyy8cPCoYBqxw@mail.gmail.com>
Subject: Re: [admin-discuss] Next steps towards a net zero IETF
To: Lars Eggert <lars@eggert.org>
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, admin-discuss@ietf.org, ietf@ietf.org
Content-Type: multipart/alternative; boundary="000000000000ee091005f88aec35"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/14rlSafTp5hv7rmfMkHRJzUxebU>
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, 04 Apr 2023 23:20:50 -0000

On Tue, Apr 4, 2023 at 8:21 AM Lars Eggert <lars@eggert.org> wrote:

> Hi,
>
> On 4. Apr 2023, at 01:14, Michael Richardson <mcr+ietf@sandelman.ca>
> wrote:
> > Or we could just start with having three f2f meetings per year, with more
> > slots for informal meetings...
>

IETF may will need to have a formula as when do we do three f2f or four f2f
per year, IMHO it depends on the technology/RFCs demands and the number of
f2f attendance and the accumulated travel distances, and on ietf_data
analysis per WG and per Area. Furthermore, we need to know if the WG became
a remote WG_meeting or WG_in_person per IETF meeting (i.e. if more than 10
persons are attended then it is not remote_WG_meeting).


> I just wanted to point out that we're seeing a different push in the IESG
> from WG chairs, many of which want more WG session time during IETF
> meetings. That isn't to say that they wouldn't also want more informal
> time, but there is a tussle here.


There are a lot of wasted time because it does not depend on WG
priorities/activities, the Chair or AD need to discuss priorities of time
with All participants per WG. In meetings we may see presentations with no
discussions per f2f meeting, so I think it is a wasted f2f time, also there
are times in plenary meeting with no discussions per long_presentation. So
we need shorter presentations for less priority/activities and
longer_enough presentation for more high priority/productive_discussions.
Furthermore, our f2f meetings help us (remote and person_attended) make
better wg_decisions.


>
> Additional tracks and/or longer days and/or full-length Fridays will
> likely be needed and the community should weigh those against their
> downsides for in-person and remote attendees.
>

yes agree, and that needs to be discussed on the list per WG and per Area,
IMHO, the ietf_Area discussion on that issue is not active per future f2f
meeting.

Best Wishes,
AB