IETF Logo Mail Archive

Re: [113attendees] IETF 113 Update: 2022-02-10

"Joel M. Halpern" <jmh@joelhalpern.com> Wed, 16 February 2022 17:11 UTC

Return-Path: <jmh@joelhalpern.com>
X-Original-To: 113attendees@ietfa.amsl.com
Delivered-To: 113attendees@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 768D53A1419 for <113attendees@ietfa.amsl.com>; Wed, 16 Feb 2022 09:11:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.814
X-Spam-Level:
X-Spam-Status: No, score=-2.814 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, NICE_REPLY_A=-0.714, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=joelhalpern.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 dbt19cWFl0lm for <113attendees@ietfa.amsl.com>; Wed, 16 Feb 2022 09:11:24 -0800 (PST)
Received: from maila2.tigertech.net (maila2.tigertech.net [208.80.4.152]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 541983A141E for <113attendees@ietf.org>; Wed, 16 Feb 2022 09:11:24 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by maila2.tigertech.net (Postfix) with ESMTP id 4JzPcq72xZz6GYNP; Wed, 16 Feb 2022 09:11:23 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1645031483; bh=jdo/wkGtbW7cCXQXKtKMn2SMDgEIbEaR9/K479TIvKE=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=fmkwKtYHdix7pSNNBx5v4Zwuo+sl1YunwHex8RjYtiAPr//BO6TSYXW1UeGL+Aj8c JHWBfjnv4W0OF4MCYpQ6ks12JitTBZsssS6sB0GYqsIo4Fq1judK1XdDyPvN4lFPgz oF1lSr7JixC14N3Ilho9CKGQYphQWCu0o01O/YqM=
X-Quarantine-ID: <Ohi6-dbZgvPI>
X-Virus-Scanned: Debian amavisd-new at a2.tigertech.net
Received: from [192.168.22.111] (50-233-136-230-static.hfc.comcastbusiness.net [50.233.136.230]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by maila2.tigertech.net (Postfix) with ESMTPSA id 4JzPcq1kN7z6G8q0; Wed, 16 Feb 2022 09:11:23 -0800 (PST)
Message-ID: <c0928f11-b5a4-7d27-1d66-e641009f93f4@joelhalpern.com>
Date: Wed, 16 Feb 2022 12:11:22 -0500
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.6.0
Content-Language: en-US
To: Andrew Campling <andrew.campling@419.consulting>, Bob Hinden <bob.hinden@gmail.com>
Cc: Greg Wood <ghwood@staff.ietf.org>, "113attendees@ietf.org" <113attendees@ietf.org>
References: <9989E0B6-A0F6-4A4C-A681-FDB6C046455D@staff.ietf.org> <718578905.42881.1645007735648@appsuite-gw2.open-xchange.com> <E9A51103-58DB-47ED-A2D6-D83932150754@gmail.com> <LOYP265MB2094A4F9FD7386914BB06819C2359@LOYP265MB2094.GBRP265.PROD.OUTLOOK.COM>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
In-Reply-To: <LOYP265MB2094A4F9FD7386914BB06819C2359@LOYP265MB2094.GBRP265.PROD.OUTLOOK.COM>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/113attendees/RQhvLM52w2wEYja-Gz2C2dI7nQI>
Subject: Re: [113attendees] IETF 113 Update: 2022-02-10
X-BeenThere: 113attendees@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Mailing list for IETF 113 attendees <113attendees.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/113attendees>, <mailto:113attendees-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/113attendees/>
List-Post: <mailto:113attendees@ietf.org>
List-Help: <mailto:113attendees-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/113attendees>, <mailto:113attendees-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Feb 2022 17:11:36 -0000

Given that the room needs to be observed / managed, I had assumed that 
at least one chair or their delegate will need to be on site.

Yours,
Joel

On 2/16/2022 12:09 PM, Andrew Campling wrote:
>> On Feb 16, 2022, at 16:45, Bob Hinden <bob.hinden@gmail.com> wrote:
>> Further, a decision may be needed for each working group.  For example, if the chair(s) and responsible AD are not going to be in Vienna, it might be better to not hold a hybrid w.g. meeting and make it all virtual.
> 
> Having a mixture of hybrid and virtual sessions within the meeting would not be a great way forward.  The meeting FAQs at https://www.ietf.org/how/meetings/113/faq/ already addresses remote participation by chairs.
> 
> "Will session chairs be required to participate in person?
> No. Onsite participation is not required for anyone, including session chairs. Chairs will be able to use Meetecho to chair their sessions remotely. Training sessions and online guides will be available ahead of the meeting for remote chairs, and advance preparation is highly encouraged. More information will be provided as details are set."
> 
> 
> Andrew
>

v2.23.0 | Report a Bug | By Email