Re: IETF 107 and Corona Virus?

Stewart Bryant <stewart.bryant@gmail.com> Thu, 13 February 2020 20:03 UTC

Return-Path: <stewart.bryant@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 044141201CE for <ietf@ietfa.amsl.com>; Thu, 13 Feb 2020 12:03:45 -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, FREEMAIL_FROM=0.001, LOTS_OF_MONEY=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 A9tGDq2W_n6V for <ietf@ietfa.amsl.com>; Thu, 13 Feb 2020 12:03:42 -0800 (PST)
Received: from mail-wr1-x433.google.com (mail-wr1-x433.google.com [IPv6:2a00:1450:4864:20::433]) (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 03F0512022A for <ietf@ietf.org>; Thu, 13 Feb 2020 12:03:42 -0800 (PST)
Received: by mail-wr1-x433.google.com with SMTP id z3so8267342wru.3 for <ietf@ietf.org>; Thu, 13 Feb 2020 12:03:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=pwwCDcgTbxsB0pZ7zCzCe56FSJL9+rK8m7yrGocksCY=; b=H96bZBew8VC02PTbhYRdwi5vHyGMjOb5wAw1dGOApEwJ4zHizNJnkmgrzDdp0JGK2W 1q1JWXBq5HdUw4jxL0l89AtR7Xd6W6kkfwelBQ48LwgjbL8d5nd12q/gHsiIcnlAOQeK pKq7kIfiJ4B30ueRox78I+vyTTrjpm0crxgbukaV//tMLTpxiRNd1H5hTFzzAB4aFVEU 4Qh0R+ZkppJGW3c/LVZa5mxbOwqvkelmRSJFnn1IiF0LqRN/4j8ZxGl3eTbWTlGsKkew p+qzfJ1PgvZ0mlvX9UP1GIAPaRPOPHshnHjfxwkZDnt7XaEbRiOCjt0I7cdDf0QKRYHT JoaQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=pwwCDcgTbxsB0pZ7zCzCe56FSJL9+rK8m7yrGocksCY=; b=TPDJ0pZPIcQJxYLdHCYB64IaVHO/maHprjUBhjYsTOXBqKuswbpaMTPdQ/zrEV8WTJ TxcC3+GWPBSpBK1ptmPovTRj4barUI6Mt9B06ATWqypxtnKDlJHDJTaRdfo35hSlvVq6 p+yrvmmhbBO/XkPjcx43Plguw8BapgrhQVaXWg2VauR6ZfXmDDjAz2FOIOt540ouu1bP Yi65Ewg4HATzhTx6XHgWIRZGMwUoE+l3JXGdH5Mukc4BYFfcyqVdNngeM2Pmrd3mBZ7P 6MZlbFAu4tU/oiRooowx/mkIujafrkNy2COlvHIbz4n/yx0psA8x/4GR1ixr+kus7+qZ tZfQ==
X-Gm-Message-State: APjAAAUmWxuGBz1+3tKsnk1iUzVKqQqM9AXZN5LpXA6n9vuQKUZkfbsW tFtceVu+pEocWOowkTB2wipbNC0mu/0=
X-Google-Smtp-Source: APXvYqyoXyfeI5LOtW9lzSyEqrmCkV9AvrJIwC7bowK8gB0cpynTp2WNY5XEhci17FxDQT2ZVbJqMQ==
X-Received: by 2002:adf:cd03:: with SMTP id w3mr23913196wrm.191.1581624219535; Thu, 13 Feb 2020 12:03:39 -0800 (PST)
Received: from [10.2.122.47] ([82.132.242.220]) by smtp.gmail.com with ESMTPSA id a13sm4141185wrp.93.2020.02.13.12.03.38 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 13 Feb 2020 12:03:38 -0800 (PST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (1.0)
Subject: Re: IETF 107 and Corona Virus?
From: Stewart Bryant <stewart.bryant@gmail.com>
X-Mailer: iPhone Mail (16G161)
In-Reply-To: <PR1PR07MB500133F262F9883BE4F60DFD911A0@PR1PR07MB5001.eurprd07.prod.outlook.com>
Date: Thu, 13 Feb 2020 21:03:35 +0100
Cc: JORDI PALET MARTINEZ <jordi.palet=40consulintel.es@dmarc.ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <3FEDFDE1-7E57-4C31-B875-C12D0F0A1666@gmail.com>
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>
To: "Belotti, Sergio (Nokia - IT/Vimercate)" <sergio.belotti@nokia.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/4ImqDdV0o3_ITFrNuSJEWjHhkNU>
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:03:45 -0000

If you do not feel safe, then do not go.

Others should make up their own mind using whatever criteria and sources of advice that they feel appropriate.

Stewart 

> On 13 Feb 2020, at 15:57, Belotti, Sergio (Nokia - IT/Vimercate) <sergio.belotti@nokia.com> wrote:
> 
> 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.
> 
> 
>