Re: Further update on COVID-19 (Coronavirus) and IETF 107 Vancouver

Jared Mauch <jared@puck.nether.net> Wed, 26 February 2020 19:22 UTC

Return-Path: <jared@puck.nether.net>
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 5CAD63A1271 for <ietf@ietfa.amsl.com>; Wed, 26 Feb 2020 11:22:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 uoIoLWxq_Pjj for <ietf@ietfa.amsl.com>; Wed, 26 Feb 2020 11:22:31 -0800 (PST)
Received: from puck.nether.net (puck.nether.net [IPv6:2001:418:3f4::5]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ECC113A126F for <ietf@ietf.org>; Wed, 26 Feb 2020 11:22:30 -0800 (PST)
Received: from [10.0.0.129] (c-68-32-79-179.hsd1.mi.comcast.net [68.32.79.179]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by puck.nether.net (Postfix) with ESMTPSA id 38F00540224; Wed, 26 Feb 2020 14:22:20 -0500 (EST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3608.60.0.2.5\))
Subject: Re: Further update on COVID-19 (Coronavirus) and IETF 107 Vancouver
From: Jared Mauch <jared@puck.nether.net>
In-Reply-To: <DM6PR05MB634809ED4CD6D49036B47A25AEEA0@DM6PR05MB6348.namprd05.prod.outlook.com>
Date: Wed, 26 Feb 2020 14:22:19 -0500
Cc: Joseph Potvin <jpotvin@xalgorithms.org>, "EXT-Andrew.Alston@liquidtelecom.com" <Andrew.Alston@liquidtelecom.com>, IETF Best Practices <ietf@ietf.org>, Phillip Hallam-Baker <phill@hallambaker.com>
Content-Transfer-Encoding: quoted-printable
Message-Id: <7FE2757F-F4A1-4134-A5FF-9E203754DD07@puck.nether.net>
References: <158258721017.24319.9082233711977122647.idtracker@ietfa.amsl.com> <CAAObRXJ=NnrxLAGgtas8Cs_jw-AJ0YsgYpMmYtrHy+PjKsfqvg@mail.gmail.com> <CAMm+Lwh17iOi_8qZ7at8gHQ6R38YwVuUZ8O1cpsJU7MKh+nMmA@mail.gmail.com> <DBBPR03MB5415B842B32E90BF91D0C361EEEA0@DBBPR03MB5415.eurprd03.prod.outlook.com> <CAAuWHCKRhe-ct2tP5TqBaCn_fSTBoFSkrppTKOyhoP_xW6Ydag@mail.gmail.com> <DM6PR05MB634809ED4CD6D49036B47A25AEEA0@DM6PR05MB6348.namprd05.prod.outlook.com>
To: Ron Bonica <rbonica=40juniper.net@dmarc.ietf.org>
X-Mailer: Apple Mail (2.3608.60.0.2.5)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/sKzKXPtegr3W4UzNpnxJtwwWfcc>
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: Wed, 26 Feb 2020 19:22:33 -0000


> On Feb 26, 2020, at 2:13 PM, Ron Bonica <rbonica=40juniper.net@dmarc.ietf.org> wrote:
> 
> Joseph,
>  
> The IETF’s current practice of holding three in-person meetings per year is not sustainable. If not today, at some time in the future, the IETF will be forced to hold a fully on-line meeting. This may be motivated by:
>  
> 	• The next public health issue
> 	• Environmental concerns
> 	• Geopolitical or visa concerns
> 	• Economic concerns
>  
> Since we are going to have to learn how to hold an on-line meeting sooner or later, why not now?
>  

Ron,

I think we should try it as an experiment and add a virtual interim before we’re forced to.  I don’t know what the next N-days until travel to YVR hold, but  as of right now I plan to be there.

I think organizing something planned even as a test would be interesting though.

I think it’s also important that WGs use their lists efficiently as well.

- Jared