IETF Logo Mail Archive

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

Robert Raszuk <robert@raszuk.net> Wed, 26 February 2020 19:38 UTC

Return-Path: <robert@raszuk.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 932AA3A1281 for <ietf@ietfa.amsl.com>; Wed, 26 Feb 2020 11:38:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=raszuk.net
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 0-pYcF8L4tfV for <ietf@ietfa.amsl.com>; Wed, 26 Feb 2020 11:38:26 -0800 (PST)
Received: from mail-ot1-x32e.google.com (mail-ot1-x32e.google.com [IPv6:2607:f8b0:4864:20::32e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3A1EE3A127B for <ietf@ietf.org>; Wed, 26 Feb 2020 11:38:26 -0800 (PST)
Received: by mail-ot1-x32e.google.com with SMTP id w6so607448otk.0 for <ietf@ietf.org>; Wed, 26 Feb 2020 11:38:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=raszuk.net; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=cbBclfFnP+jkYF4WN926+E+EYp9I6i6dTRAsA5okic0=; b=AUXqqsD8mCcYKSx2a/Vms81OmIK9Df6DX47MUp69KNFDl7ArcO9iwH5PFLNFabH3Q1 v+XaALS24NdvLFf7fBslkqkkmxhQUQTovvDm08pAOxGPG0/3tCZFYBZVMPHCEOBG4Bko PSb5shDHhs8Eei3hfydssj5aFngvTVtJbCyozmfKEQadRuwoCSezfVqsPB0BmquwirGd SPjvHL/VuC/98PFJUzG/KUNRjVaAQ9l0t1nyfVzj0fb/8EYAOsFaqYS37TYNcJLOiYs9 zOOgVim/G/7wx55lDGCRmxybHE55LW8kE8AoUQGA5N4iYsU6BYIYFlXwBJgAueCf5szb We1w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=cbBclfFnP+jkYF4WN926+E+EYp9I6i6dTRAsA5okic0=; b=bX0UFjg00k3EXC8eCk5dRt+wHZnlnITmO4T8pLy/FnmRzTtOyas3XaXcSmGv57dpq4 +1AAjdy4fcdqZdkMyjgIF/BIHoI5whGkNvHCT89cvKuug0ypHR+0lauv2FY0RS+ACEV4 RoxI0ai/nYjj53Kbyo091yIcWMhD4IeSitI++HqLixlOkMDIIwIJB9kXcdsauPebzMG3 ry1nSr96/ubIJa7knQwjma25OKNLSKCi8tBL72z1kAS5tWJgW+1obR/hT5I9elzH6hVU WXkBBRlZQG+zO2GF0mMc2Imefoim5B2FEH0LYNzzDSIl/SKdney/WcDoLdpVkse86TS1 iQhg==
X-Gm-Message-State: APjAAAWyy+dA1RVk+OwZztgyXeaUGkhrAkYRg8+rWWfuH8feKioPXvOt Kl4MhZ0x16nM20keotMYWRV7NrvWt2MeSSVMNefekw==
X-Google-Smtp-Source: APXvYqzAYuyQchvyg5RBMznbJnk9flt+iQKZxSNoXaQcjQILBOyrRnCnbvx86+nFEucaBMX9XJtkvwOmVLjxxFwBJBM=
X-Received: by 2002:a05:6830:1385:: with SMTP id d5mr311964otq.61.1582745905181; Wed, 26 Feb 2020 11:38:25 -0800 (PST)
MIME-Version: 1.0
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>
In-Reply-To: <CAKKJt-eDGSd+B=Taf8Q=AoE=_mHj542PT1ChvqO3485oVKSWtw@mail.gmail.com>
From: Robert Raszuk <robert@raszuk.net>
Date: Wed, 26 Feb 2020 20:38:14 +0100
Message-ID: <CAOj+MMGX-MES7EOm-2OEPsQQS=_NjH0tnb9KL0xLUyTSCb2x0Q@mail.gmail.com>
Subject: Re: Further update on COVID-19 (Coronavirus) and IETF 107 Vancouver
To: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Cc: Joseph Potvin <jpotvin@xalgorithms.org>, Phillip Hallam-Baker <phill@hallambaker.com>, IETF Rinse Repeat <ietf@ietf.org>, IETF Announcement List <ietf-announce@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000072c6ce059f7fbfe1"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/4-XZ1-fLhOwB1fjiI_BvSDV8YuA>
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:38:28 -0000

> Canceling completely now is also an excellent way to find out that we are
nowhere near able to go Plan B full-online successfully.


AFAIK IETF operates fully-online 365 -15 days a year (tool: mailing lists).

Is seeing a moving person such a strong req ? If seeing just a face is that
strong requirement remote registration can ask for a photo upload. The crux
here seems to be able to select how we collaborate in a virtual meeting.

Sure 1:1 communication helps especially in cases where you are interacting
with unknown folks, but nothing stops me from having a video chat with
co-authors or to have a conversation with a group of people interested in
my work. That happens all the time.

Plenary could be a challenge - sure. Does this justify the full IETF
meeting ?

I admit I agree with all folks who recommend to cancel upcoming meeting in
person meeting. It is clear that battle to contain the virus has been lost.
It is not only spreading it is also undergoing mutation so even if vaccine
is found and tested for original version it may or may not work for other
mutations.

Best,
R.

v2.23.0 | Report a Bug | By Email