Re: [Recentattendees] Background on Singapore go/no go for IETF 100

Michael StJohns <mstjohns@comcast.net> Tue, 31 January 2017 16:53 UTC

Return-Path: <mstjohns@comcast.net>
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 0B546129FC4 for <ietf@ietfa.amsl.com>; Tue, 31 Jan 2017 08:53:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.899
X-Spam-Level:
X-Spam-Status: No, score=-5.899 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, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-3.199, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=comcast.net
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 lY81XBs0ac_h for <ietf@ietfa.amsl.com>; Tue, 31 Jan 2017 08:53:56 -0800 (PST)
Received: from resqmta-ch2-10v.sys.comcast.net (resqmta-ch2-10v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:42]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CF511129FC5 for <ietf@ietf.org>; Tue, 31 Jan 2017 08:53:56 -0800 (PST)
Received: from resomta-ch2-02v.sys.comcast.net ([69.252.207.98]) by resqmta-ch2-10v.sys.comcast.net with SMTP id Ybg0cUeTmuQ8yYbgpcBa0Y; Tue, 31 Jan 2017 16:53:55 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20161114; t=1485881635; bh=ast4NQxPjQcDELBk7MCoDoZTr7RfoByk6YNMVIvVH3c=; h=Received:Received:Subject:To:From:Message-ID:Date:MIME-Version: Content-Type; b=F5JkX9KWgQImSr1pBaDrTPBqzPChhAK5SQ5sE0SgmpoWM4wZPWv2HYGEzliyAKvlu /y5bs215r7i1mACdi0Owt4X1FGSfCjm4qRcVlpqcf83HPkYdYMf0GBEpTwWNOu3VRE yBWQydkYrOYc32MRl7F1dfakU24gj4vbspQs4I5UQYnb8Z1B3rNJkCnJfWY+ZEOXdV q0KlppbzDSedhOTJyQlDliZ1Hbzdqo7l1zPTkmo5P3QI4lSQlnviU8FQ7IWl37HUtf 84Gs0iwu45mr/m7VBwO46yjzOb+AzukAK5etVBpwy1xvEY+rFHA7v6+CYglziVYweB fl4imsS53LKoA==
Received: from [IPv6:2601:152:4400:9b5f:c8f0:67e5:88b1:2975] ([IPv6:2601:152:4400:9b5f:c8f0:67e5:88b1:2975]) by resomta-ch2-02v.sys.comcast.net with SMTP id YbgocNYvxLagLYbgpcdNJU; Tue, 31 Jan 2017 16:53:55 +0000
Subject: Re: [Recentattendees] Background on Singapore go/no go for IETF 100
To: ietf@ietf.org
References: <20160525220818.18333.71186.idtracker@ietfa.amsl.com> <700D9CB7-4EFD-459B-AA12-133A6BB04E90@senki.org> <1C8639E6-1058-4D04-84ED-0C354E6567D1@cisco.com> <9CBABA69-1814-4676-9C69-E129F04AD24C@cisco.com> <5DFDEA43-8156-491D-A300-2BCED1AED1A4@gmail.com> <5747909C.20403@si6networks.com> <955df2106aa2e12cefbd450be022e779.squirrel@www.trepanning.net> <D36D49EE.35116%jefft0@remap.ucla.edu> <CE39F90A45FF0C49A1EA229FC9899B05266663BF@USCLES544.agna.amgreetings.com> <CA+ruDECdMAC2PQqibqQijc-nLHUxOGw0h-ZYyh8FnZZaeZ8sTA@mail.gmail.com> <CA+ruDEBHyzk5cg5Vmq-anKJTxLkZpHrb9APwkfbDGn6FeFzR_w@mail.gmail.com> <CE39F90A45FF0C49A1EA229FC9899B052BD4B85D@USCLES544.agna.amgreetings.com> <A0BBD037-851F-4F47-A7F2-44EFC73166AD@consulintel.es> <CAEjQQ5Wbxi0_fEVf3uh1_K=o02KK11jRgGhdpeiBhAojhtt76g@mail.gmail.com> <2A1F5023-F0E8-4312-945C-88E8B0795DAE@consulintel.es> <A965E752-158F-41FF-BB7E-EA4203F346F0@gmail.com> <B94C79D8-F26E-44A9-93E4-182B9D9D3336@consulintel.es>
From: Michael StJohns <mstjohns@comcast.net>
Message-ID: <a1227757-d5ef-f4d0-2235-212592853fe7@comcast.net>
Date: Tue, 31 Jan 2017 11:53:57 -0500
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <B94C79D8-F26E-44A9-93E4-182B9D9D3336@consulintel.es>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
X-CMAE-Envelope: MS4wfO1umies0EeQ9jWRxNJSCQ7qCCr+sKlKxPEKgbVkRpfqESgN7YsVugXcTd/S+Xnmj3YSd8DZQSrobm73bOGq9QIoDu3/5yIRlVQ7ttzJS/zXNb//9AiH 86Sqa+IrR9hwcCPao+BxFAoDixB6WJZf32GyTDrF/aZuwPHTpQPf4DbzEznNvuDnwJbtpxHXskOsMA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/_CKqR9tvmN1NwPwLc5L1Kc4jOfI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
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, 31 Jan 2017 16:53:58 -0000

On 1/31/2017 8:20 AM, JORDI PALET MARTINEZ wrote:
> I’m not a lawyer, however, I checked this with an American lawyer a few years ago, when I suggested the first time for the need to the insurance, and I was working in the first version of the venue-selection-criteria ID. I don’t think laws changed in those years about this.

Jordi - first thing to do is fire your lawyer.  Or at least make sure 
his card doesn't say "I just play one on TV".

> Even if it is a refundable ticket, the expenses to change or refund that, will be also responsibility of the IETF, unless there is what laws call “overwhelming force”, which it most of the cases will be only accepted by courts if there is no chance for 99% of the participants to held the meeting (venue collapsed because a fire, earthquake, or something similar)

Taken to an extreme, I can see you trying to claim to some expo like RSA 
that they have to refund your airline ticket if a session you really, 
really wanted to see was cancelled because the presenter was sick.

And the term you're looking for is "force-majeure".   In the instant 
case it *might* apply between the IETF and a banned attendee as the ban 
was unforeseeable (at the times the contracts were signed), external to 
the parties involved (the US government in the form of an executive 
order from the US President), and unavoidable (a greater force - in this 
case enforcement by law and border officials of a sovereign nation).  In 
that case, it's like the agreement was never made.  In any event, I 
would assume the secretariat will work with the banned attendee(s) to 
refund their registration fees and to help them cancel their hotel 
reservations without cost.

The banned attendee can probably also argue the same with the airline 
involved - I would be surprised if any airline or contract of carriage 
would refuse to refund their ticket prices of someone who is prohibited 
from entering the country. [And yes, I know about the folks that had to 
buy their own tickets home - different matter and one I expect will be 
litigated or resolved or put down to sovereign immunity.]

In any event, the law is complex, and trying to make the claim that the 
IETF is a party to contracts that it is not, or that the IETF is 
responsible for making you whole for actions it has no control over will 
not win you friends.  Please avoid doing so in the future.

Mike