Re: IETF 107 Vancouver In-Person Meeting Cancelled

JORDI PALET MARTINEZ <jordi.palet@consulintel.es> Tue, 10 March 2020 20:37 UTC

Return-Path: <prvs=133801c307=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 BC9423A0C67 for <ietf@ietfa.amsl.com>; Tue, 10 Mar 2020 13:37:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Level:
X-Spam-Status: No, score=-1.997 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, SPF_HELO_NONE=0.001, URIBL_BLOCKED=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 jAZVMoHNhlTK for <ietf@ietfa.amsl.com>; Tue, 10 Mar 2020 13:37:40 -0700 (PDT)
Received: from mail.consulintel.es (mail.consulintel.es [IPv6:2001:470:1f09:495::5]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 96FB73A07DF for <ietf@ietf.org>; Tue, 10 Mar 2020 13:37:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1583872658; x=1584477458; 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=UcjHYkde A7tu8NvKkhWUhG81SgNxnFydUq+7YCGzZqU=; b=hxnOtDxXjlNwidw4PhGai8BJ a1XBsBID+Lf44JymwoawrjGY8pjaL0bScb/boj7w2wcM7Dn8VaNUkX6jxDpDqaV5 Mhxtf5d+prQStFT0KIYrrMPxObl5tkpWNEwZ73AZvZrrzX7FKNHfqZc+cEFPXatO TQTCZ1Qts+WBAgCz+g8=
X-MDAV-Result: clean
X-MDAV-Processed: mail.consulintel.es, Tue, 10 Mar 2020 21:37:38 +0100
X-Spam-Processed: mail.consulintel.es, Tue, 10 Mar 2020 21:37:38 +0100
Received: from [10.10.10.144] by mail.consulintel.es (MDaemon PRO v16.5.2) with ESMTPA id md50000086813.msg for <ietf@ietf.org>; Tue, 10 Mar 2020 21:37:37 +0100
X-MDRemoteIP: 2001:470:1f09:495:d5e4:ce9:969f:1214
X-MDHelo: [10.10.10.144]
X-MDArrival-Date: Tue, 10 Mar 2020 21:37:37 +0100
X-Authenticated-Sender: jordi.palet@consulintel.es
X-Return-Path: prvs=133801c307=jordi.palet@consulintel.es
X-Envelope-From: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: ietf@ietf.org
User-Agent: Microsoft-MacOutlook/16.35.20030802
Date: Tue, 10 Mar 2020 21:37:34 +0100
Subject: Re: IETF 107 Vancouver In-Person Meeting Cancelled
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: "ietf@ietf.org" <ietf@ietf.org>
Message-ID: <25231974-29B2-4651-ACE3-E7616E8E302A@consulintel.es>
Thread-Topic: IETF 107 Vancouver In-Person Meeting Cancelled
References: <158386742797.16091.1025684270011519738@ietfa.amsl.com> <52EE5E3F-E83A-4F81-8F48-6B94AB0A5C7D@akamai.com> <4B6380B9-CBBB-4275-BDA6-F086D66D6DBA@cooperw.in> <A893CAF9-B9B3-4E1A-9D09-0EEEE996E635@akamai.com> <1C525937-E47A-48F8-90D1-7903EC2881A3@cooperw.in>
In-Reply-To: <1C525937-E47A-48F8-90D1-7903EC2881A3@cooperw.in>
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/1K-ZLqts-H6EtFZOuEOn5mgiyqo>
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: Tue, 10 Mar 2020 20:37:43 -0000

According to lawyers, at least in the case of Spanish law, from what I got about 10 minutes ago, if an event organizer cancels a meeting, it is responsible and liable for any cancellation's costs to participants, unless there is a "force major cause" (which clearly is not the case, until it is declared by the corresponding government).

This is what it happened to the Mobile congress in Barcelona. They have calculated 450 million euros in compensations.

Has this liability been considered for possible claims when taking the decision?

Even if this is sad to say, the only way to scape to this will be if the Canadian government declares that situation.

Regards,
Jordi
@jordipalet
 
 

El 10/3/20 21:32, "ietf en nombre de Alissa Cooper" <ietf-bounces@ietf.org en nombre de alissa@cooperw.in> escribió:

    Hi Rich,
    
    One more bit to add on to what Adam said:
    
    > On Mar 10, 2020, at 3:42 PM, Salz, Rich <rsalz@akamai.com> wrote:
    
    > To put it in common business terms, I think we're owed a root cause analysis of the full decision-making process by all parties. 
    
    As the message from the IESG said, together with the IRTF Chair we decided to cancel the meeting on the basis that a majority of sessions would not be viable if we were to hold the in-person IETF meeting. We received input from the chairs of 98 WGs and RGs before making this decision. We care about the health of our participants, but this decision was based on our ability to have an effective meeting, not advice from public health authorities.
    
    Alissa
    
    



**********************************************
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.