IETF Logo Mail Archive

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

Rich Kulawiec <rsk@gsp.org> Thu, 27 February 2020 13:58 UTC

Return-Path: <rsk@gsp.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 575EE3A091F for <ietf@ietfa.amsl.com>; Thu, 27 Feb 2020 05:58:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=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 HFCcn1jBmEGB for <ietf@ietfa.amsl.com>; Thu, 27 Feb 2020 05:58:15 -0800 (PST)
Received: from taos.firemountain.net (taos.firemountain.net [207.114.3.54]) (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 5859F3A0918 for <ietf@ietf.org>; Thu, 27 Feb 2020 05:58:15 -0800 (PST)
Received: from gsp.org (localhost [127.0.0.1]) by taos.firemountain.net (8.15.1/8.14.9) with SMTP id 01RDwKf1021936 for <ietf@ietf.org>; Thu, 27 Feb 2020 08:58:21 -0500 (EST)
Date: Thu, 27 Feb 2020 08:58:13 -0500
From: Rich Kulawiec <rsk@gsp.org>
To: IETF <ietf@ietf.org>
Subject: Re: Further update on COVID-19 (Coronavirus) and IETF 107 Vancouver
Message-ID: <20200227135813.GA8568@gsp.org>
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> <CAKKJt-eDGSd+B=Taf8Q=AoE=_mHj542PT1ChvqO3485oVKSWtw@mail.gmail.com> <CAOj+MMGX-MES7EOm-2OEPsQQS=_NjH0tnb9KL0xLUyTSCb2x0Q@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <CAOj+MMGX-MES7EOm-2OEPsQQS=_NjH0tnb9KL0xLUyTSCb2x0Q@mail.gmail.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/1Yuc2Kb8z8imQ6uqwEExLAhe2qo>
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, 27 Feb 2020 13:58:17 -0000

Without expressing an opinion on go/no-go, I'd like to point out a resource
that may be useful.  Johns Hopkins has put up a dashboard that is doing
an amazing job of COVID-19 tracking:

	Mapping 2019-nCoV
	https://systems.jhu.edu/research/public-health/ncov/

---rsk

v2.23.0 | Report a Bug | By Email