Re: [107all] Update on IETF 107 Vancouver and COVID-19

Paul Wouters <paul@nohats.ca> Thu, 05 March 2020 03:16 UTC

Return-Path: <paul@nohats.ca>
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 E7ECD3A0A0B; Wed, 4 Mar 2020 19:16:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.095
X-Spam-Level:
X-Spam-Status: No, score=-2.095 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, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, SPF_HELO_NONE=0.001, SPF_NONE=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=nohats.ca
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 egael4nV83GD; Wed, 4 Mar 2020 19:16:29 -0800 (PST)
Received: from mx.nohats.ca (mx.nohats.ca [193.110.157.68]) (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 32E6D3A0A08; Wed, 4 Mar 2020 19:16:28 -0800 (PST)
Received: from localhost (localhost [IPv6:::1]) by mx.nohats.ca (Postfix) with ESMTP id 48XwrW0YGqz3Bw; Thu, 5 Mar 2020 04:16:27 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nohats.ca; s=default; t=1583378187; bh=1dTmzKiuDpCpEnsPyfxtStcdt5FkDKRWIMr1Zj/ZVcY=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=GVfTiKU4h1uWDsFB+EYJE6ZKMmCY4CNH87RaqF/O4LeDqUU2U1f7jiJ8IbgF9lVLj lmnRNFCZwCt47O45ZuJ6puI6Oxsj8XciUXr/o6dE5EBLprPvxkDVGkdtsO2d0k+Zm8 Zmb4WYEI81eGZ+x5OC9kgELQGN51DblMgbpZLEyo=
X-Virus-Scanned: amavisd-new at mx.nohats.ca
Received: from mx.nohats.ca ([IPv6:::1]) by localhost (mx.nohats.ca [IPv6:::1]) (amavisd-new, port 10024) with ESMTP id 7VbCq7dwnKTq; Thu, 5 Mar 2020 04:16:26 +0100 (CET)
Received: from bofh.nohats.ca (bofh.nohats.ca [76.10.157.69]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx.nohats.ca (Postfix) with ESMTPS; Thu, 5 Mar 2020 04:16:25 +0100 (CET)
Received: from [10.150.41.149] (199-7-157-42.eng.wind.ca [199.7.157.42]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by bofh.nohats.ca (Postfix) with ESMTPSA id 9B5B96029B99; Wed, 4 Mar 2020 22:16:24 -0500 (EST)
Content-Type: multipart/alternative; boundary="Apple-Mail-25C7E44A-6C8D-4570-A603-E1AD6F059C21"
Mime-Version: 1.0 (1.0)
Subject: Re: [107all] Update on IETF 107 Vancouver and COVID-19
From: Paul Wouters <paul@nohats.ca>
X-Mailer: iPhone Mail (16G102)
In-Reply-To: <CAHw9_i+yuojs6gkX+GmP8xCxPZn_MBvZH66YHf42bM6Xsip4-Q@mail.gmail.com>
Date: Wed, 04 Mar 2020 22:16:22 -0500
Cc: Robert Raszuk <robert@raszuk.net>, IETF <ietf@ietf.org>, "exec-director@ietf.org" <exec-director@ietf.org>
Content-Transfer-Encoding: 7bit
Message-Id: <653F4F12-E11B-4843-90AD-EBD35D19E21D@nohats.ca>
References: <158335136585.29295.1109218817393181187@ietfa.amsl.com> <D4FDE701-CE29-44BE-877A-B45266FEFF08@cisco.com> <CAOj+MMG+OhM9_G3+ikfGxXSqi6PMO0EJeZ=vCC3Wne=YWHLLhg@mail.gmail.com> <CAHw9_i+yuojs6gkX+GmP8xCxPZn_MBvZH66YHf42bM6Xsip4-Q@mail.gmail.com>
To: Warren Kumari <warren@kumari.net>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/iYrkf_7ja7TQh8s8zPFFHOrMEyA>
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: Thu, 05 Mar 2020 03:16:31 -0000

L
> On Mar 4, 2020, at 19:33, Warren Kumari <warren@kumari.net> wrote:
> 
> 
> 
> 
> Simply because the chairs cannot make it does not automatically mean that the WG meeting is cancelled -- WGs chairs can ask the WG secretary, or appoint a temporary secretary or just ask an in-person participant to do the physical onsite things, like bluesheets, pushing the big red button, etc. 

I agree and I will happily volunteer to chair a meeting where needed.

Paul