Re: IETF 107 and Corona Virus?

Victor Kuarsingh <victor@jvknet.com> Thu, 13 February 2020 21:10 UTC

Return-Path: <victor@jvknet.com>
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 61F8F120236 for <ietf@ietfa.amsl.com>; Thu, 13 Feb 2020 13:10:58 -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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=jvknet-com.20150623.gappssmtp.com
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 x37fMNP5Ou1G for <ietf@ietfa.amsl.com>; Thu, 13 Feb 2020 13:10:56 -0800 (PST)
Received: from mail-wm1-x32f.google.com (mail-wm1-x32f.google.com [IPv6:2a00:1450:4864:20::32f]) (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 9AC1D120273 for <ietf@ietf.org>; Thu, 13 Feb 2020 13:10:55 -0800 (PST)
Received: by mail-wm1-x32f.google.com with SMTP id m10so598809wmc.0 for <ietf@ietf.org>; Thu, 13 Feb 2020 13:10:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=jvknet-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=X3wlUiqF5FSemlbUjqHhrHadG9D8Gq5ZrblV5Hs8ftI=; b=mSwg2NolPEXm9ntnfw6weyjWro42qVnfyBImvRrQXWQZathqXCiFeqkJtorSQDG5JI QrzDZo4MvYcLlG00G5q6j/WjNMMKOI4HEKKjE0yPsvCcSOKXvrDZ8WGHArBkSZJ7cVjK xBIvLqXT2gn8qbYpDP3UqwMJaPRdYEDqvi5L0SPeekx0prD4lGRNfPciysW6dd4d/LQB GVmg7JYhq8dL6aba+M2vfJ9clEA3qqfRglyRTwGvN+DOs1IcDne9VdsHuytK+40JFbwk p/eNOTY9R6m+QRzKxUk0U2jT/VIBKqGDNacyMRYL2FK+7ZZfE3TwPskRL2dQyY4+rdAp J1eg==
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=X3wlUiqF5FSemlbUjqHhrHadG9D8Gq5ZrblV5Hs8ftI=; b=NQHvwdGl45NqKQucH/wgGchLtkkYy/BztCeneK5jYcv+vpA/O+S+zUuDcHE2odUwQg Xj+6bixBBwFiDVXI08acBgVydVVziN8lP+SkHpdaEin8UJzTm2m6Pf/mAiu/mYloeWpR 7Vt3PwDhI4FshdIKiwWBjP0kEM1xC+F50egMXOfHeS/qDYUUIpZZezU3NsskH1EeXDAg kv90OsNHQlaSbSGVrexfipM250vqKlkqvFEppwESgwEgNEV1BPmWAacKGKvzek6HzYbA 9bVQZ7sajHSeQXrP0EKcp573LS3jinPoBf2uTiWJerc6Eyxn1uzrDhwd6UmYUUFWccmv Ipiw==
X-Gm-Message-State: APjAAAX2xfvJky+XSUR164b57+kS54gf+8LAo/jNwIDkKfCp4HwjeKjE FZIelnlDGyl3cwmnuvhXzIJgVE7XP5157jfRBvORg5Q36X+2Fg==
X-Google-Smtp-Source: APXvYqx1frpchMFkYyXyucaV+9/L5/KqlzYbvAeLhkLimAcM8AgjLuDXQqlMHOW7iGuvfjRExa7ILCpegxke5HDgrC4=
X-Received: by 2002:a1c:16:: with SMTP id 22mr21565wma.8.1581628253837; Thu, 13 Feb 2020 13:10:53 -0800 (PST)
MIME-Version: 1.0
References: <VE1PR03MB54220BB50CB38B6F4A72FC58EE1A0@VE1PR03MB5422.eurprd03.prod.outlook.com> <eb39f2cd-7a27-e0ff-3be4-6d03d13f31b8@gmail.com> <DACFBEF8-93A6-429C-AF16-19E01A0BEA50@consulintel.es> <CAHbuEH42ZYRZfjVTSnAHnBaVM+9M1Bt843U37F+2Y97Sdx1iQg@mail.gmail.com> <6E1C07A9-AF8A-4ACD-A299-E7D0E757F8C4@tzi.org> <CAHbuEH5Z0TAdj1Y4UUArsLv1M6JHAqqdm27f-MD3rJXKWbGU9w@mail.gmail.com> <CAL02cgRMG=NL+VGfGhyO8nm+UGq1zdscB_-CRTMXmDg7-j36pQ@mail.gmail.com> <1669a4ef-b4ef-6e53-1977-bc5bb68ffc22@gmail.com>
In-Reply-To: <1669a4ef-b4ef-6e53-1977-bc5bb68ffc22@gmail.com>
From: Victor Kuarsingh <victor@jvknet.com>
Date: Thu, 13 Feb 2020 13:10:42 -0800
Message-ID: <CAJc3aaMo16cBYBKqAWp+tkEDemr3fFMxPG1YmaJFbtJ6DL1fUQ@mail.gmail.com>
Subject: Re: IETF 107 and Corona Virus?
To: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Cc: IETF Discussion <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000003cab81059e7b8660"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/MR40xofuDa4gAqxMLp_tyz0J1pU>
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, 13 Feb 2020 21:10:58 -0000

> Would G7 meet if 1 does not come?

Not sure that's a comparable event.

The IETF, IMO, is quite different in terms of how we operate and get work
done.  So although there is a challenge to be evaluated here, it's not
directly comparable to either what happened with MWC or G7 meetings.  Where
as in both of those examples, folks who don't attend cannot participate at
all, that's not the case for an IETF meeting.  There are side meetings and
direct interaction which one cannot do remote (so some impact noted),
however, discussions and attendance can be managed with remote folks
(Meetecho, Jabber, Email lists).

I am not suggesting we take any specific course of action at this point
since the situation is fluid.

I am certain, following this particular event and surrounding circumstance,
we can build this into ways to address such situations for future meetings.

regards,

Victor K

On Thu, Feb 13, 2020 at 12:54 PM Alexandre Petrescu <
alexandre.petrescu@gmail.com> wrote:

>
>
> Le 13/02/2020 à 21:50, Richard Barnes a écrit :
> >
> >
> > On Thu, Feb 13, 2020 at 3:37 PM Kathleen Moriarty
> > <kathleen.moriarty.ietf@gmail.com
> > <mailto:kathleen.moriarty.ietf@gmail.com>> wrote:
> >
> >     Hi Carsten,
> >
> >     There's one consideration you left out -
> >
> >     On Thu, Feb 13, 2020 at 3:18 PM Carsten Bormann <cabo@tzi.org
> >     <mailto:cabo@tzi..org>> wrote:
> >
> >         On 2020-02-13, at 15:55, Kathleen Moriarty
> >         <Kathleen.Moriarty.ietf@gmail.com
> >         <mailto:Kathleen.Moriarty.ietf@gmail.com>> wrote:
> >          >
> >          > That said, my travel is mostly booked and I am planning to
> >         attend, but will watch to see what happens with any IETF
> >         pandemic planning.
> >
> >         Which is what is probably true for most of us.
> >
> >         We already know that companies’ and countries’ policies will
> >         place some limitations on the meeting (which actually is having
> >         some limited impact on planning for the meeting).  With the
> >         knowledge we have today (2020-02-13), we can assume that we will
> >         have a productive meeting, not the least because we have good
> >         remote attendance possibilities for those who can’t (or choose
> >         not to) make it.
> >
> >         On a health/responsibility level (and, again with the knowledge
> >         of today), there simply is no reason to cancel the meeting.  It
> >         is still way more likely for an IETF attendee to have a traffic
> >         accident than to be impacted by COVID-19.
> >
> >
> >     Individuals from an entire nation likely cannot attend what is meant
> >     to be a global meeting. This deserves some thought.
> >
> >
> > I agree that this is unfortunate, but I don't see how it follows from
> > this that nobody else should meet.
>
> One could turn that question in many different ways.
>
> Would G7 meet if 1 does not come?
>
> There are many other ways in which to turn it.
>
> Alex
>
> >
> > --Richard
> >
> >
> >
> >     Best regards,
> >     Kathleen
> >
> >
> >         Now that knowledge we have today may change (a.k.a.
> >         “surprises”), so the IETF leadership needs to stay in a position
> >         to make different decisions based on emerging situations, and
> >         new expert advice that may become available.
> >
> >         I still think of the plenary where it was announced that we
> >         would meet in Korea and somebody went to the microphone with the
> >         concern that North Korea could be attacking Seoul at any time.
> >         Yes, COVID-19 can attack at any time, but it is just one of many
> >         risks that we have to juggle.
> >
> >         Grüße, Carsten
> >
> >
> >
> >     --
> >
> >     Best regards,
> >     Kathleen
> >
>
>