Re: IETF 107 Vancouver In-Person Meeting Cancelled

JORDI PALET MARTINEZ <jordi.palet@consulintel.es> Tue, 10 March 2020 23:15 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 E6B2F3A0897 for <ietf@ietfa.amsl.com>; Tue, 10 Mar 2020 16:15:35 -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 9s6GVfXTkFOe for <ietf@ietfa.amsl.com>; Tue, 10 Mar 2020 16:15:33 -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 471DC3A0896 for <ietf@ietf.org>; Tue, 10 Mar 2020 16:15:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1583882131; x=1584486931; 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=ZNSSqYLO S/fU5VJoS4gHFHJww/EuE4E5PKNj7Di1yec=; b=fICXtZ8z8Z8T9qUj7GJ7M+FO RbpHM8EyLRkBvOPykMqipAZbmwN0u+X/5rgqPOAdSxGrynNjVsA0QfVy0usFNT76 Vjyr1PUoKXTmpgCrY+Fe6d8WNZpTLhFK3/kZNuf60fhuw+9j+B2bBCh/DRFJwNtN YRhNNGZ4bb/BDiX+v6s=
X-MDAV-Result: clean
X-MDAV-Processed: mail.consulintel.es, Wed, 11 Mar 2020 00:15:31 +0100
X-Spam-Processed: mail.consulintel.es, Wed, 11 Mar 2020 00:15:30 +0100
Received: from [10.10.10.130] by mail.consulintel.es (MDaemon PRO v16.5.2) with ESMTPA id md50000087005.msg for <ietf@ietf.org>; Wed, 11 Mar 2020 00:15:29 +0100
X-MDRemoteIP: 2001:470:1f09:495:cd6c:a4bd:63ef:40c7
X-MDHelo: [10.10.10.130]
X-MDArrival-Date: Wed, 11 Mar 2020 00:15:29 +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: Wed, 11 Mar 2020 00:15:27 +0100
Subject: Re: IETF 107 Vancouver In-Person Meeting Cancelled
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: <ietf@ietf.org>
Message-ID: <12801E94-9730-44FD-B1CA-8B054F797587@consulintel.es>
Thread-Topic: IETF 107 Vancouver In-Person Meeting Cancelled
References: <158386742797.16091.1025684270011519738@ietfa.amsl.com> <7D26D5BD-FD39-47D1-81D5-73D7BFCF09F8@consulintel.es> =?utf-8?q?=3CFRXPR01M?= =?utf-8?q?B064510B3CC63EBBDFD33B5E498FF0=40FRXPR01MB0645=2EDEUPRD01=2EPROD?= =?utf-8?q?=2EOUTLOOK=2EDE=3E?= <E124B52F-638D-4843-A0F9-0F518716C5C7@consulintel.es> <985D1867-2160-4050-BD15-B4C97FF47318@sobco.com>
In-Reply-To: <985D1867-2160-4050-BD15-B4C97FF47318@sobco.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/QifGmmNv8NH84LWYETlSKsI-Vm8>
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 23:15:36 -0000

Hi Scott,

I'm not a lawyer, but I've checked with them, and I recall that this was exactly the same situation that a month ago occurred when the Mobile congress was cancelled. The insurance denied paying because they cancelled even if there was not a "force major" declared by the government and the organization said that the cost of all the compensations will be around 450 million euros at a minimum. The organizers are also an US company, I think?

I think you're right and maybe the use of "force major" is not good here, and it was only the way the Mobile congress organization "described why the insurance doesn't want to pay". Said in a different way: it was cancelled because *exclusive decision of the organizers*, like the IETF.

I think that the laws that apply will be from each participant, but I may be wrong. If I decide to sue an event organizer, I will go to the courts in my jurisdiction.

Note that I've not said that I'm going to sue IETF, but I think we must be aware that anyone could take that path.

 

El 10/3/20 23:28, "Scott O. Bradner" <sob@sobco.com> escribió:

    can you point to the specific laws - particularly in the US (where the IETF LLC is based) and Canada (where the event was to be)
    
    
    imo - insurance coverage is based on the conditions in the insurance contract not some general laws
    in addition, my understanding is the reverse as far as  force majeure is concerned - force majeure tends to cancel insurance
    (there is a court case right now where an insurance company is claiming they should not have to cover hacking
    of a major company because they claim it was an act of war bu the North Koreans
    
    e.g. 
    "Force majeure refers to a clause that is included in contracts to remove liability for natural and unavoidable catastrophes that interrupt the expected course of events and restrict participants from fulfilling obligations.” 
    https://www.investopedia.com/terms/f/forcemajeure.asp
    
    Scott
    
    
    > On Mar 10, 2020, at 6:20 PM, JORDI PALET MARTINEZ <jordi.palet=40consulintel.es@dmarc.ietf.org> wrote:
    > 
    > Because law says that if there is no force major, insurance will not cover it and at the same time the event organizer is liable? Is not that a good reason?
    > 
    > 
    > 
    > 
    > El 10/3/20 22:11, "ietf-bounces@ietf.org en nombre de N.Leymann@telekom.de" <ietf-bounces@ietf.org en nombre de N.Leymann@telekom.de> escribió:
    > 
    >    Hi,
    > 
    >    why should the IETF cover this? You are participating and booking as an individual. If you booked the hotel within one of the IETF blocks IETF will probably try to negotiate with the hotels for the flight you are on your own.
    > 
    >    For the future - if you book from your own pocket - it might be a good idea to cover the bookings with a travel insurance (many credit cards come with a travel insurance anyway - check with the credit company).
    > 
    >    Regards
    > 
    >    Nic
    > 
    >    -----Ursprüngliche Nachricht-----
    >    Von: ietf <ietf-bounces@ietf.org> Im Auftrag von JORDI PALET MARTINEZ
    >    Gesendet: Dienstag, 10. März 2020 20:15
    >    An: iesg@ietf.org; IETF Announcement List <ietf-announce@ietf.org>
    >    Cc: irtf-announce@irtf.org; ietf@ietf.org; 107all@ietf.org
    >    Betreff: Re: IETF 107 Vancouver In-Person Meeting Cancelled
    > 
    >    I don't think this is right.
    > 
    >    Not having an official ban from the Canada authorities makes impossible to get a refund for:
    > 
    >    1) Flight
    >    2) Hotel
    > 
    >    So, for those that have paid that from their own pocket, in advance, to make it cheaper, is the IETF insurance going to cover that?
    > 
    >    Regards,
    >    Jordi
    >    @jordipalet
    > 
    > 
    > 
    >    El 10/3/20 20:11, "IETF-Announce en nombre de The IESG" <ietf-announce-bounces@ietf.org en nombre de iesg@ietf.org> escribió:
    > 
    >        The IESG and the IRTF Chair have decided to cancel the in-person IETF 107 Vancouver meeting. This decision is based on input we gathered from Working Group (WG) and Research Group (RG) chairs about our ability to hold productive WG and RG sessions at IETF 107. Our assessment of this feedback is that a majority of sessions would not be viable if we were to hold the in-person IETF meeting. On this basis, we believe we cannot hold an effective in-person meeting. 
    > 
    >        As a result of this cancellation, the in-person Hackathon, Code Sprint, all other in-person events planned for the weekend of March 21-22, the chairs training scheduled for March 20, and all other in-person sessions during the week are cancelled.
    > 
    >        The IESG is working on an alternative all-virtual agenda for the week of March 21-27 with a limited schedule adapted to accommodate the time zones of as many participants as possible. We are also planning to support an increased volume of virtual interim meetings during the weeks that follow.. We will send another update to the community soon with more information about these plans. The Hackathon organizers are also considering plans for virtual Hackathon support.
    > 
    >        We have re-opened Internet-Draft submissions, which had been closed on March 9 in anticipation of the in-person meeting. Internet-Drafts may be submitted at <https://datatracker.ietf.org/submit/>.
    > 
    >        A separate announcement from the IETF Executive Director will follow with details about registration cancellations and refunds.  
    > 
    >        These are unusual times given the circumstances created by the spread of COVID-19.  We hope that everyone remains safe and healthy.
    > 
    >        Regards,
    >        The IESG and the IRTF Chair
    > 
    >        _______________________________________________
    >        IETF-Announce mailing list
    >        IETF-Announce@ietf.org
    >        https://www.ietf.org/mailman/listinfo/ietf-announce
    > 
    > 
    > 
    > 
    >    **********************************************
    >    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.
    > 
    > 
    > 
    
    



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