Re: IETF 107 and Corona Virus?

Kyle Rose <krose@krose.org> Thu, 13 February 2020 15:32 UTC

Return-Path: <krose@krose.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 281D912012E for <ietf@ietfa.amsl.com>; Thu, 13 Feb 2020 07:32:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, LOTS_OF_MONEY=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=krose.org
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 yBquGPTU5I92 for <ietf@ietfa.amsl.com>; Thu, 13 Feb 2020 07:31:57 -0800 (PST)
Received: from mail-yw1-xc2f.google.com (mail-yw1-xc2f.google.com [IPv6:2607:f8b0:4864:20::c2f]) (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 769D6120121 for <ietf@ietf.org>; Thu, 13 Feb 2020 07:31:57 -0800 (PST)
Received: by mail-yw1-xc2f.google.com with SMTP id 192so2775162ywy.0 for <ietf@ietf.org>; Thu, 13 Feb 2020 07:31:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=krose.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Vt1YyPik2bLtLM5xsJUyZUWA4xzJvp2KBx5/zPzERi8=; b=I8KWpSpQbE19LVO+uGOeY2nCeJMXiCwQYZlem8I1eNykRn2zHU0YXBbWm9ULxJ6aU8 rbO2F+6R1SIbF8WxnyftkRD6db/0WujjOo5vVk/ronWP6rtcUX/GS6NS/1hTbEbz6Ahk 2vl3BAf7vbCx0+2aETuHa/+bcmP5J5GIBDvnk=
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=Vt1YyPik2bLtLM5xsJUyZUWA4xzJvp2KBx5/zPzERi8=; b=ttx6sYNjxM/8OyWNsO72dLuqI8o9RfsUPKY01U0ODvyvSlvYSkrWet2+pFNEf3RbRs C/RLnzvS3fD2uyTnf+GtnPjVcO9pZwKTDQxFFbfqUYoKwA6mrNf+VrZRa0IIAii+g7hP /wTfPpYK2DXXHZcbJTnVM6isnUZg8/y3AC9iisoR44DAoFWfijd2sEai7g1XiJqJnJ1x iEKt5IhQ8su0xzg/xEHnQnzjKJOrAXIwO1+0sy8L7T6DeZ5nvfTKY8jL4dpKr7TBBJie N0okz55peU2XUFcB/450oD9yHnj8Veu3grf8FjydeJ4HynDGzj6DqBPzf4kPyzAQn/2+ Aotw==
X-Gm-Message-State: APjAAAWi9iLWbshVennyHFmDFf8Dd8oSW0QyuqWZ3pwYzkVef9ACd2pj /lKkISTfgLrD3fdVVQx3DC72BbMJttzCVzqQWLAXM6aJSLA=
X-Google-Smtp-Source: APXvYqzsd1MApuli+u3Px/7jgiQGAHUAFDx/VcaJ90lxk1XHW0TTJBc6+kA/bv8OCn2qLnoMmlyDocTAlle+rFDTB4U=
X-Received: by 2002:a0d:e745:: with SMTP id q66mr14265922ywe.503.1581607916484; Thu, 13 Feb 2020 07:31:56 -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> <PR1PR07MB500133F262F9883BE4F60DFD911A0@PR1PR07MB5001.eurprd07.prod.outlook.com> <D2E775EE-CEB8-414B-BDBD-666EE0E693EE@consulintel.es> <CAOj+MMHG+idm5OmDU5Eknq3q=q3BV0VMS+nz69a18V2Mm3HYYw@mail.gmail.com>
In-Reply-To: <CAOj+MMHG+idm5OmDU5Eknq3q=q3BV0VMS+nz69a18V2Mm3HYYw@mail.gmail.com>
From: Kyle Rose <krose@krose.org>
Date: Thu, 13 Feb 2020 10:31:45 -0500
Message-ID: <CAJU8_nW6rzXdKr_kh53CgxOqQn8nH++isDKNYODdRZ8xJy4kXQ@mail.gmail.com>
Subject: Re: IETF 107 and Corona Virus?
To: Robert Raszuk <robert@raszuk.net>
Cc: JORDI PALET MARTINEZ <jordi.palet=40consulintel.es@dmarc.ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000000956ca059e76ca29"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/URMwjSPIG7zf6c4zoYLMC4yAfjE>
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 15:32:00 -0000

Anyone uncomfortable with traveling to Vancouver can self-cancel, i.e.,
attend remotely. Others will make the same risk assessment and come to a
different conclusion. I don't see why this needs to be decided centrally.


On Thu, Feb 13, 2020 at 10:24 AM Robert Raszuk <robert@raszuk.net> wrote:

> Just in case you missed it.
>
>
> https://www.arnnet.com.au/article/671016/coronavirus-cancels-cisco-live-melbourne/
>
>
> And this is not only about the event itself .... it is also about sitting
> in partially recirculated plane for hours. And this is not about panic
> either. Till this specific virus can be 100% cured it is just common sense.
> Would anyone from IETF mgmt would want to risk even a single person due to
> this ?
>
> Sure it is not the same, but perhaps this situation gives us an
> opportunity to instead of cancelling it making it first virtual IETF ?
> After all overlay technology seems to be very common these days :)
>
> There is also another option - making it semi-virtual. rent 3 conf places
> in Asia, 2 in EMEA, 3 in Americas and join those via telepresence.
>
> Best,
> R.
>
>
> On Thu, Feb 13, 2020 at 4:02 PM JORDI PALET MARTINEZ <jordi.palet=
> 40consulintel.es@dmarc.ietf.org> wrote:
>
>> Yes, if the risk is big, but is not the case. I'm talking about the
>> situation in this case, and right now.
>>
>> I think we should avoid speculating and if we need to take a decision, it
>> need to be by consensus.
>>
>> Regards,
>> Jordi
>> @jordipalet
>>
>>
>>
>> El 13/2/20 15:58, "ietf en nombre de Belotti, Sergio (Nokia -
>> IT/Vimercate)" <ietf-bounces@ietf.org en nombre de
>> sergio.belotti@nokia.com> escribió:
>>
>>     When you're talking about "health" , the covering of expenses is
>> something that should be at lower priority , this is what I personally
>> would expect .
>>
>>     Regards
>>     Sergio
>>
>>     -----Original Message-----
>>     From: ietf <ietf-bounces@ietf.org> On Behalf Of JORDI PALET MARTINEZ
>>     Sent: Thursday, February 13, 2020 3:50 PM
>>     To: ietf@ietf.org
>>     Subject: Re: IETF 107 and Corona Virus?
>>
>>     And then will you cover the expenses (flights, hotels) of people that
>> has booked it already, because I don't think the IETF has an insurance to
>> cover for it.
>>
>>     In the case of the Mobile Congress, they said the cost is over 450
>> million euros for the cancellation, plus claims that may come. It is a
>> totally different level and it only make sense because big companies
>> decided not to participate.
>>
>>     But in the case of IETF we are individuals, not companies and the
>> size of the meeting, and consequently the risks are totally different.
>> Clearly the Canada government will not allow anyone with risk of infecting
>> others to come into the country, so the IETF is already covered by that.
>>
>>     There is no such reason to cancel it. It will be only needed if our
>> meeting is in China.
>>
>>     Regards,
>>     Jordi
>>     @jordipalet
>>
>>
>>
>>     El 13/2/20 15:35, "ietf en nombre de Alexandre Petrescu" <
>> ietf-bounces@ietf.org en nombre de alexandre.petrescu@gmail.com>
>> escribió:
>>
>>         I think it should be cancelled.
>>
>>         It is not a good perspective to cancel something that is dear,
>> but under
>>         exceptional circumstances there might be need of exceptional
>> measures.
>>
>>         Alex
>>
>>         Le 13/02/2020 à 07:48, Andrew Alston a écrit :
>>         > Hi All,
>>         >
>>         > I am just wondering if there are any thoughts on the status of
>> the IETF 107 meeting in light of the corona virus.
>>         >
>>         > Particularly in light of the fact that for safety reasons
>> mobile world congress has been cancelled and we're seeing other events
>> being cancelled in light of this as well.  Should it be considered a safe
>> and responsible move to go ahead with this meeting or should we be looking
>> at an entirely virtual meeting in light of the situation?
>>         >
>>         > Andrew
>>         >
>>
>>
>>
>>
>>
>>     **********************************************
>>     IPv4 is over
>>     Are you ready for the new Internet ?
>>     http://www.theipv6company.com
>>     The IPv6 Company
>>
>>     This electronic message contains information which may be privileged
>> or confidential. The information is intended to be for the exclusive use of
>> the individual(s) named above and further non-explicilty authorized
>> disclosure, copying, distribution or use of the contents of this
>> information, even if partially, including attached files, is strictly
>> prohibited and will be considered a criminal offense. If you are not the
>> intended recipient be aware that any disclosure, copying, distribution or
>> use of the contents of this information, even if partially, including
>> attached files, is strictly prohibited, will be considered a criminal
>> offense, so you must reply to the original sender to inform about this
>> communication and delete it.
>>
>>
>>
>>
>>
>>
>>
>> **********************************************
>> IPv4 is over
>> Are you ready for the new Internet ?
>> http://www.theipv6company.com
>> The IPv6 Company
>>
>> This electronic message contains information which may be privileged or
>> confidential. The information is intended to be for the exclusive use of
>> the individual(s) named above and further non-explicilty authorized
>> disclosure, copying, distribution or use of the contents of this
>> information, even if partially, including attached files, is strictly
>> prohibited and will be considered a criminal offense. If you are not the
>> intended recipient be aware that any disclosure, copying, distribution or
>> use of the contents of this information, even if partially, including
>> attached files, is strictly prohibited, will be considered a criminal
>> offense, so you must reply to the original sender to inform about this
>> communication and delete it.
>>
>>
>>
>>
>>