Re: IETF 107 and Corona Virus?

JORDI PALET MARTINEZ <jordi.palet@consulintel.es> Thu, 13 February 2020 14:50 UTC

Return-Path: <prvs=1312e6875b=jordi.palet@consulintel.es>
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 AEB111200C7 for <ietf@ietfa.amsl.com>; Thu, 13 Feb 2020 06:50:39 -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, LOTS_OF_MONEY=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=consulintel.es
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 rJcmREx9Q4oy for <ietf@ietfa.amsl.com>; Thu, 13 Feb 2020 06:50:33 -0800 (PST)
Received: from mail.consulintel.es (mail.consulintel.es [217.126.185.215]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6BCA8120013 for <ietf@ietf.org>; Thu, 13 Feb 2020 06:50:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1581605408; x=1582210208; i=jordi.palet@consulintel.es; q=dns/txt; h=User-Agent:Date: Subject:From:To:Message-ID:Thread-Topic:References:In-Reply-To: Mime-version:Content-type:Content-transfer-encoding; bh=hdkkMTNc pEh5L6iAMT4Sk96qJRVZ8uAALpHyi7g7gLU=; b=EFATpwuRPJeKM40wVZcpX2ow p1JbAAtRn4t8yIJn/ozWtzLXuUoY/6VOVZPwWOZwoAPEpql7r+2/DGgii83mOfAd VF9DKJdhZtX8qT4pfBRdXqoLYf3td3mQbeY4ebAKe49CwL+uPmZW2EJsF1QRPvKS 2NHo2csjXHgXzPFgpHM=
X-MDAV-Result: clean
X-MDAV-Processed: mail.consulintel.es, Thu, 13 Feb 2020 15:50:08 +0100
X-Spam-Processed: mail.consulintel.es, Thu, 13 Feb 2020 15:50:08 +0100
Received: from [172.17.88.15] by mail.consulintel.es (MDaemon PRO v16.5.2) with ESMTPA id md50000058720.msg for <ietf@ietf.org>; Thu, 13 Feb 2020 15:50:08 +0100
X-MDRemoteIP: 10.8.10.6
X-MDHelo: [172.17.88.15]
X-MDArrival-Date: Thu, 13 Feb 2020 15:50:08 +0100
X-Authenticated-Sender: jordi.palet@consulintel.es
X-Return-Path: prvs=1312e6875b=jordi.palet@consulintel.es
X-Envelope-From: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: ietf@ietf.org
User-Agent: Microsoft-MacOutlook/10.22.0.200209
Date: Thu, 13 Feb 2020 15:50:03 +0100
Subject: Re: IETF 107 and Corona Virus?
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: <ietf@ietf.org>
Message-ID: <DACFBEF8-93A6-429C-AF16-19E01A0BEA50@consulintel.es>
Thread-Topic: IETF 107 and Corona Virus?
References: <VE1PR03MB54220BB50CB38B6F4A72FC58EE1A0@VE1PR03MB5422.eurprd03.prod.outlook.com> <eb39f2cd-7a27-e0ff-3be4-6d03d13f31b8@gmail.com>
In-Reply-To: <eb39f2cd-7a27-e0ff-3be4-6d03d13f31b8@gmail.com>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/7Ta0Sd9VxUXXNfDhszNhr-OMmTA>
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 14:50:40 -0000

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.