IETF Logo Mail Archive

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

Lixia Zhang <lixia@cs.ucla.edu> Mon, 07 February 2022 17:46 UTC

Return-Path: <lixia@cs.ucla.edu>
X-Original-To: admin-discuss@ietfa.amsl.com
Delivered-To: admin-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7DE5B3A1008; Mon, 7 Feb 2022 09:46:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 xsUye6iXhsEh; Mon, 7 Feb 2022 09:46:32 -0800 (PST)
Received: from zimbra.cs.ucla.edu (zimbra.cs.ucla.edu [131.179.128.68]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B606A3A0FD4; Mon, 7 Feb 2022 09:46:32 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by zimbra.cs.ucla.edu (Postfix) with ESMTP id 3039D16007E; Mon, 7 Feb 2022 09:46:30 -0800 (PST)
Received: from zimbra.cs.ucla.edu ([127.0.0.1]) by localhost (zimbra.cs.ucla.edu [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id RxrShm2RosxE; Mon, 7 Feb 2022 09:46:29 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by zimbra.cs.ucla.edu (Postfix) with ESMTP id 5C02A160156; Mon, 7 Feb 2022 09:46:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at zimbra.cs.ucla.edu
Received: from zimbra.cs.ucla.edu ([127.0.0.1]) by localhost (zimbra.cs.ucla.edu [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id Bl5ZIpChHU88; Mon, 7 Feb 2022 09:46:29 -0800 (PST)
Received: from smtpclient.apple (cpe-76-91-255-77.socal.res.rr.com [76.91.255.77]) by zimbra.cs.ucla.edu (Postfix) with ESMTPSA id 26819160155; Mon, 7 Feb 2022 09:46:29 -0800 (PST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 15.0 \(3693.40.0.1.81\))
From: Lixia Zhang <lixia@cs.ucla.edu>
In-Reply-To: <DC779FD8-9500-4BFC-A8AF-23A7E9621222@eggert.org>
Date: Mon, 7 Feb 2022 09:46:27 -0800
Cc: Brian E Carpenter <brian.e.carpenter@gmail.com>, admin-discuss@ietf.org, 113attendees@ietf.org, ietf@ietf.org, manycouches@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <4568E613-11C4-4293-BD91-1230C45B403A@cs.ucla.edu>
References: <321C40AC-5B24-49F5-B2C1-1AD8AF20F2DC@staff.ietf.org> <93750011-435f-bd78-f61d-4941386ae9a4@gmail.com> <DC779FD8-9500-4BFC-A8AF-23A7E9621222@eggert.org>
To: Lars Eggert <lars@eggert.org>
X-Mailer: Apple Mail (2.3693.40.0.1.81)
Archived-At: <https://mailarchive.ietf.org/arch/msg/admin-discuss/BBeDAhxuvl4RgGpKntG57-LrQ38>
Subject: Re: [admin-discuss] Meeting schedule (was: Re: IETF 113 Updates on 2022-01-19)
X-BeenThere: admin-discuss@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Discussion list for IETF LLC administrative issues <admin-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/admin-discuss>, <mailto:admin-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/admin-discuss/>
List-Post: <mailto:admin-discuss@ietf.org>
List-Help: <mailto:admin-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/admin-discuss>, <mailto:admin-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Feb 2022 17:46:38 -0000

the msg below (dated 1/31) talked about more info "early next week" about the meeting time. 
Since a week has passed: wonder any update available now?

Lixia

> On Jan 31, 2022, at 11:35 AM, Lars Eggert <lars@eggert.org> wrote:
> 
> Hi,
> 
> On 2022-1-28, at 2:30, Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
>> As far as I can tell, it's impossible to tell from any of the posted information what time the meetings will start and end each day. That's vital information for anyone considering remote participation.
> 
> I apologize that we haven't published details yet.
> 
> The plan is to roughly stick with the schedule of a fully online meeting, i.e., start at around mid-day local time and run for around six hours.
> 
> I'm waving my hands a bit here, because we are still discussing with the venue about some required procedures, such as for meal breaks and room disinfection, among others. Depending on the details, those may necessitate some longer breaks than we had during fully online meetings. So we may need to start somewhat earlier than we did for the fully online meetings, and/or we may need to run for a bit longer, in order to end up with sufficient session time.
> 
> We're hoping to have all the information from the venue early next week.
> 
> Thanks,
> Lars
>

v2.8.7 | Report a Bug | By Email