IETF Logo Mail Archive

Re: Meeting schedule (was: Re: [admin-discuss] IETF 113 Updates on 2022-01-19)

Lars Eggert <lars@eggert.org> Mon, 31 January 2022 20:26 UTC

Return-Path: <lars@eggert.org>
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 2B7CF3A1667; Mon, 31 Jan 2022 12:26:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=eggert.org
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 t8C7FZ0x_way; Mon, 31 Jan 2022 12:26:44 -0800 (PST)
Received: from mail.eggert.org (mail.eggert.org [91.190.195.94]) (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 71ADA3A1664; Mon, 31 Jan 2022 12:26:44 -0800 (PST)
Received: from smtpclient.apple (unknown [IPv6:2a00:ac00:4000:400:49a9:3c31:e49e:a32a]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.eggert.org (Postfix) with ESMTPSA id 4885C1D3B4D; Mon, 31 Jan 2022 22:26:35 +0200 (EET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=eggert.org; s=dkim; t=1643660795; bh=9N8lskn741hfAUE3BMCt6We920zjL0dR3yb8LCJUWTE=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=QMXN1X/iJ18Kz3gMF0PGzsGY0X+6OyZ/VApHnkL0Ah/4kBbDyJLNnWMW4W+ToTcTJ 7y8U3+0hivFGks0Wq/p7Pr3KWkcF/N78iqqMhqgNTSuID0rwbW3NH3xfOLr4kLwq+A rf1hDzBp8j9e/wN9rkBHMtPo8SdBQaXsJsjhPsYc=
Content-Type: multipart/signed; boundary="Apple-Mail=_36D3710B-43B0-4F69-8F44-F683CB4CBB37"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 15.0 \(3693.60.0.1.1\))
Subject: Re: Meeting schedule (was: Re: [admin-discuss] IETF 113 Updates on 2022-01-19)
From: Lars Eggert <lars@eggert.org>
In-Reply-To: <2e3cf39a-a40e-26b8-f429-a94f88eeb7cb@comcast.net>
Date: Mon, 31 Jan 2022 22:26:31 +0200
Cc: ietf@ietf.org, The IESG <iesg@ietf.org>
Message-Id: <7EE1E6FB-779D-4DEA-95BC-CF901EA549CF@eggert.org>
References: <321C40AC-5B24-49F5-B2C1-1AD8AF20F2DC@staff.ietf.org> <93750011-435f-bd78-f61d-4941386ae9a4@gmail.com> <DC779FD8-9500-4BFC-A8AF-23A7E9621222@eggert.org> <2e3cf39a-a40e-26b8-f429-a94f88eeb7cb@comcast.net>
To: Michael StJohns <mstjohns@comcast.net>
X-MailScanner-ID: 4885C1D3B4D.A430E
X-MailScanner: Found to be clean
X-MailScanner-From: lars@eggert.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/hS8G0CI6n9m-_sFsAUx76yB7vmc>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <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: Mon, 31 Jan 2022 20:26:49 -0000

Hi,

On 2022-1-31, at 21:51, Michael StJohns <mstjohns@comcast.net> wrote:
> Two questions to follow up to Brian's note:
> 
> 1) Have you given any consideration to running a few of the smaller WGs as completely virtual?  E.g., to save some of the effort that would otherwise be required for things like disinfection and Secretariat support and maybe to shrink the necessary hotel support.

the IESG hasn't discussed this. Personally, I believe that such WGs should skip meeting during the IETF week and instead schedule an interim in another week, in order to reduce meeting week conflicts.

> 2) What's the setup for the WGs where none of the chairs make it to the IRL meeting?  Have the AD's identified proxies or some other model to support those cases?

Meetecho is growing support to allow remote chairing. I have not myself seen this functionality. I'd expect it to be available during the usual chairs' test drive that Meetecho has been scheduling prior to the meetings. I would assume that chairs might also want to identify some of their regular participants to help with any in-room issues that might arise.

Thanks,
Lars

v2.46.0 | Report a Bug | By Email | System Status