Re: IETF 107 and Corona Virus?

Alexandre Petrescu <alexandre.petrescu@gmail.com> Thu, 13 February 2020 20:54 UTC

Return-Path: <alexandre.petrescu@gmail.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 0DCC012026E for <ietf@ietfa.amsl.com>; Thu, 13 Feb 2020 12:54:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.632
X-Spam-Level:
X-Spam-Status: No, score=-1.632 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, FREEMAIL_REPLY=1, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_SOFTFAIL=0.665] autolearn=no 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 WEi_lwy77Qhw for <ietf@ietfa.amsl.com>; Thu, 13 Feb 2020 12:54:29 -0800 (PST)
Received: from cirse-smtp-out.extra.cea.fr (cirse-smtp-out.extra.cea.fr [132.167.192.148]) (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 5B41B120096 for <ietf@ietf.org>; Thu, 13 Feb 2020 12:54:29 -0800 (PST)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by cirse-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id 01DKsQUI043661 for <ietf@ietf.org>; Thu, 13 Feb 2020 21:54:26 +0100
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 99EA92067D4 for <ietf@ietf.org>; Thu, 13 Feb 2020 21:54:26 +0100 (CET)
Received: from muguet1-smtp-out.intra.cea.fr (muguet1-smtp-out.intra.cea.fr [132.166.192.12]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 8F9D520673F for <ietf@ietf.org>; Thu, 13 Feb 2020 21:54:26 +0100 (CET)
Received: from [10.11.240.7] ([10.11.240.7]) by muguet1-sys.intra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id 01DKsPa9013615 for <ietf@ietf.org>; Thu, 13 Feb 2020 21:54:26 +0100
Subject: Re: IETF 107 and Corona Virus?
To: ietf@ietf.org
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>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <1669a4ef-b4ef-6e53-1977-bc5bb68ffc22@gmail.com>
Date: Thu, 13 Feb 2020 21:54:25 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.5.0
MIME-Version: 1.0
In-Reply-To: <CAL02cgRMG=NL+VGfGhyO8nm+UGq1zdscB_-CRTMXmDg7-j36pQ@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: fr
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/YhV_rtaQzK87DFi2KUBwAvpqFRw>
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 20:54:31 -0000


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
>