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

"MH Michael Hammer (5304)" <MHammer@ag.com> Tue, 31 January 2017 13:31 UTC

Return-Path: <MHammer@ag.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 B461F129EDA for <ietf@ietfa.amsl.com>; Tue, 31 Jan 2017 05:31:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 GuJjE7QGijqd for <ietf@ietfa.amsl.com>; Tue, 31 Jan 2017 05:31:08 -0800 (PST)
Received: from agwhqht.amgreetings.com (agwhqht.amgreetings.com [207.58.192.4]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C0005129ECB for <ietf@ietf.org>; Tue, 31 Jan 2017 05:31:06 -0800 (PST)
Received: from USCLES544.agna.amgreetings.com ([fe80::f5de:4c30:bc26:d70a]) by USCLES532.agna.amgreetings.com ([::1]) with mapi id 14.03.0266.001; Tue, 31 Jan 2017 08:31:05 -0500
From: "MH Michael Hammer (5304)" <MHammer@ag.com>
To: "jordi.palet@consulintel.es" <jordi.palet@consulintel.es>, "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: [Recentattendees] Background on Singapore go/no go for IETF 100
Thread-Topic: [Recentattendees] Background on Singapore go/no go for IETF 100
Thread-Index: AQHSemMdtz+BYbM/YUyZmAb3LjspL6FRbwdAgAEwUQCAAAziAIAAA4SAgAAuHQCAAArKgP//rmCw
Date: Tue, 31 Jan 2017 13:31:04 +0000
Message-ID: <CE39F90A45FF0C49A1EA229FC9899B052BD4FBF9@USCLES544.agna.amgreetings.com>
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>
In-Reply-To: <B94C79D8-F26E-44A9-93E4-182B9D9D3336@consulintel.es>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.144.6.74]
x-kse-attachmentfiltering-interceptor-info: protection disabled
x-kse-serverinfo: USCLES532.agna.amgreetings.com, 9
x-kse-antivirus-interceptor-info: scan successful
x-kse-antivirus-info: Clean, bases: 1/31/2017 11:19:00 AM
x-kse-dlp-scaninfo: Skipped
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/sDRWzcPV8A1AvunQbv2Q2dqI45U>
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 13:31:16 -0000

I think the simplest solution is for individuals to purchase their own travel insurance to cover the cost of cancellation/move of the event. IETF insures against the risk contractually (And possibly with insurance) and individuals insure their own risks. This would seem to me to be the cleanest and most straight forward solution.

Mike

> -----Original Message-----
> From: ietf [mailto:ietf-bounces@ietf.org] On Behalf Of JORDI PALET
> MARTINEZ
> Sent: Tuesday, January 31, 2017 8:21 AM
> To: ietf@ietf.org
> Subject: Re: [Recentattendees] Background on Singapore go/no go for IETF
> 100
> 
> I don’t think it is relevant if this happens to 2 participants or 20 or 200. For
> those that pay from their own pocket the traveling expenses and IETF
> registration fee, saving a 10-20% or whatever is the saving, is very relevant
> and it is our right to do so.
> 
> When IETF makes an official announcement of a venue, according to law, IT
> IS a contractual announcement and is liable for damages and expenses if
> that’s changed.
> 
> 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.
> 
> 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).
> 
> I think at that time, somebody suggested that it will be cheaper for IETF to
> cover those expenses (in case of cancellation) to those that may claim it than
> paying for the insurance for each meeting, but I’m not really sure that’s
> correct. Have we tried to get quotes for that insurance?
> 
> Regards,
> Jordi
> 
> 
> -----Mensaje original-----
> De: ietf <ietf-bounces@ietf.org>; en nombre de Yoav Nir
> <ynir.ietf@gmail.com>; Responder a: <ynir.ietf@gmail.com>;
> Fecha: martes, 31 de enero de 2017, 13:41
> Para: Jordi Palet Martinez <jordi.palet@consulintel.es>;
> CC: <ietf@ietf.org>;
> Asunto: Re: [Recentattendees] Background on Singapore go/no go for IETF
> 100
> 
> 
>     > On 31 Jan 2017, at 11:56, JORDI PALET MARTINEZ
> <jordi.palet@consulintel.es>; wrote:
>     >
>     > I was referring in general, not a specific meeting.
>     >
>     > For the 2018 SF meeting, I will buy my ticket around July-August 2017. I
> always do one year in advance, same for the hotel if I can book a cheaper
> nearby (to the venue) hotel.
> 
>     I’m pretty sure you’re in a minority doing that. I can’t even get the OK for
> making the trip more than 4 months in advance.
> 
>     > Most of the airlines, according to my experience, sell lower price non-
> refundable tickets 11-12 months ahead.
> 
>     Buying non-refundable tickets is your choice. I don’t see why it needs to
> become a cost for the IETF (whether through refunding or through
> insurance). My employer (and I’m sure many others) only buys refundable
> tickets so they are free to cancel my trip on short notice.
> 
>     > So, we should rule something in the line that an IETF cancellation
> insurance must cover the expenses of bookings for that. If we can’t cover
> that, we MUST NOT cancel a meeting,
> 
>     “MUST NOT”?  What if Earth’s youngest volcano is standing where the
> venue used to be? Still MUST NOT? San Francisco is always at risk of an
> earthquake. It doesn’t even have to be “the big one” to make it impossible
> to meet. Still MUST NOT?  And the eastern US has hurricanes, Europe has
> frosts and Japan has Kaiju. Do we still meet?
> 
>     > otherwise, the participants that made that expense, have the legal right
> to claim to the ISOC/IETF the associated expenses, and I’m sure they will get
> it, if a court is involved.
> 
>     Meeting fee? Probably. Travel expenses? I doubt it.
> 
>     > This brings to the idea that, when we select countries for hosting the
> IETF, we should consider, political changes that may affect participants. Of
> course, we don’t have the crystal ball, but in the case of actual US situation, I
> think the chances were so high, that we made a mistake going to Chicago. As
> it may affect a significant % of participants.
> 
>     I don’t think this was at all predictable.
> 
>     > Now, we have, depending on the contract signed for SF, the chance to
> move that meeting, but only if we do it right now, not in 6 months from now,
> as that will impact people that may have already booked flights and hotels.
> 
>     I don’t think our meetings committee should be constrained like that.
> There might be some guidance to be given by mtgvenue for this, but I don’t
> think that this should be a considerations if changes are made at least 6
> months in advance.
> 
>     Yoav
> 
> 
> 
> 
> 
> 
> **********************************************
> IPv4 is over
> Are you ready for the new Internet ?
> http://www.consulintel.es
> The IPv6 Company
> 
> This electronic message contains information which may be privileged or
> confidential. The information is intended to be for the use of the individual(s)
> named above. If you are not the intended recipient be aware that any
> disclosure, copying, distribution or use of the contents of this information,
> including attached files, is prohibited.
> 
>