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

Yoav Nir <> Tue, 31 January 2017 12:42 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 226C1129E72 for <>; Tue, 31 Jan 2017 04:42:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Status: No, score=-2.7 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, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id gQqG6uBLzVvT for <>; Tue, 31 Jan 2017 04:42:01 -0800 (PST)
Received: from ( [IPv6:2a00:1450:400c:c09::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 874A7129993 for <>; Tue, 31 Jan 2017 04:42:01 -0800 (PST)
Received: by with SMTP id r141so77600769wmg.1 for <>; Tue, 31 Jan 2017 04:42:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=xoK77m2n439H66ch64m0sXxnemkyv2AOwkXZLzaAtjY=; b=oRNfg/f862QOVrkwWEFbDaspMEnpRxyNlzYLHf2EL5KFKRQG1ls+981vsS1IvfhOyy NB9BTT0YeuGJjT8N78TMJZchYdQfzkvTNYD19JeRJ36exaZTHX8JXdvlkjhxMMBZMw3s 52mzpMW3gF4AB53nQB4b7wdKd6H0K4cpw8NbGzg3ARkGyzRSMyJb04MivzA6baedyuj6 cwLDqBL66+mJ8x0YUBgv1+Ar6CS5EhbHj14m9FmO1YkM9gxyjaAPS66TT+XZyE0W+abC WQt1beskrjGaZWE4bODWM/BncqQEAKkmscwcsYND6jsa5rQN++TGW3LgDMCGFW8KMOmw uQKg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=xoK77m2n439H66ch64m0sXxnemkyv2AOwkXZLzaAtjY=; b=Ggap34zu7VBBnmTUP0meNcYI7HRyIvE1Iiskb7abgeH+CO9BEuet1SEFgX91lHuFyL BGSWNYxsbUJyWw9Sf8npoUG+VNktCRDLSDWClgLuKP9gmbl9FyY3HGSqOxUyWy47H9hg VpCKy4G33Y4KrWzIuzxbZ30rU4AB79ghIN3CN1cYoamLX6wPsC2/N7EkLQjesnnUtSwd ezItr4UgTPpTfTGFmw3MtbcpIzD8vTkeTbB9eBvegW0JhDEUnsiduswWV7LmwJcR4csc 0ghLZQloZOmkhMq+dH8rugrx1m7cHvSZHLq9WwQuMT6Wuve8A6R1doZbnMQ4yaTgk1qK D9tA==
X-Gm-Message-State: AIkVDXJi72kE6sLzTbbJQY+cIr3DpF4+HdzthyH8P47Ctr8gYbGEm7xFjFVkQiPIQgqYVQ==
X-Received: by with SMTP id y126mr18138960wmb.116.1485866519669; Tue, 31 Jan 2017 04:41:59 -0800 (PST)
Received: from [] ( []) by with ESMTPSA id s17sm28192413wrc.6.2017. (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 31 Jan 2017 04:41:59 -0800 (PST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: [Recentattendees] Background on Singapore go/no go for IETF 100
From: Yoav Nir <>
In-Reply-To: <>
Date: Tue, 31 Jan 2017 14:41:56 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <>
References: <> <> <> <> <> <> <> <> <> <> <> <> <> <> <>
To: Jordi Palet Martinez <>
X-Mailer: Apple Mail (2.3259)
Archived-At: <>
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 31 Jan 2017 12:42:03 -0000

> On 31 Jan 2017, at 11:56, JORDI PALET MARTINEZ <> 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.