Re: Background on Singapore go/no go for IETF 100

tom p. <daedulus@btconnect.com> Thu, 26 May 2016 08:02 UTC

Return-Path: <daedulus@btconnect.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 9101312D632 for <ietf@ietfa.amsl.com>; Thu, 26 May 2016 01:02:33 -0700 (PDT)
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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, LOTS_OF_MONEY=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=btconnect.onmicrosoft.com
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 e3EXF_ricElh for <ietf@ietfa.amsl.com>; Thu, 26 May 2016 01:02:31 -0700 (PDT)
Received: from EUR01-HE1-obe.outbound.protection.outlook.com (mail-he1eur01on0115.outbound.protection.outlook.com [104.47.0.115]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9B8E412D60C for <ietf@ietf.org>; Thu, 26 May 2016 01:02:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=btconnect.onmicrosoft.com; s=selector1-btconnect-com; h=From:To:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=3iT6z4zKJlW3QGPdtV5nUywBSolbae6Vbs22Gi5gAG0=; b=XW1LbxjnrSHSAx2o8d8aVidY2aF3+957MXuF6WWxe90Q5r+o3YgHsIGDDRfuxMnmwAMTrtLU2YvV0NSqbcKAc2R3Mlx6NKamV8ZQbfJTRv3AUDIt+i+Ejp3qsw58n+LQ1GZvZWvYUruPr0fPVnA7xHv3D1QLMiyDnS3TybLG+Uk=
Authentication-Results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=btconnect.com;
Received: from pc6 (109.145.193.232) by DB5PR07MB1557.eurprd07.prod.outlook.com (10.165.212.135) with Microsoft SMTP Server (TLS) id 15.1.506.9; Thu, 26 May 2016 08:02:27 +0000
Message-ID: <027501d1b724$632c2c40$4001a8c0@gateway.2wire.net>
From: tom p. <daedulus@btconnect.com>
To: <ietf@ietf.org>
References: <20160525220818.18333.71186.idtracker@ietfa.amsl.com>
Subject: Re: Background on Singapore go/no go for IETF 100
Date: Thu, 26 May 2016 08:57:53 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Originating-IP: [109.145.193.232]
X-ClientProxiedBy: DB4PR05CA0036.eurprd05.prod.outlook.com (10.160.40.46) To DB5PR07MB1557.eurprd07.prod.outlook.com (10.165.212.135)
X-MS-Office365-Filtering-Correlation-Id: 2dc4b2a8-5906-4e91-fe2a-08d3853c14a3
X-Microsoft-Exchange-Diagnostics: 1; DB5PR07MB1557; 2:/tztYywG4cscV2M8rci2QxMJMOeC1MWokaaJP4xXcnMMRycXE4G80UPHye0NZn/ff3B0DuocKdX4g9u51lzt4kiQaEePCKlLMXxUSegBwF28NCK+nZkdWGGoRHPrHvFJLVaiiQkraTn8lVECY5A+Ew/+i6q70kc1emJE5r1/5KXiH4VIP9vRj2qd3JZXiGSO; 3:5V7O4kO+OonG1hH4RGIDBck15TjSHNdrn2eAzVu/S/DN1NvdIbR+WKR67BeLlFpmTPrZivMB5qjHRQsRmey8QPg0pBJxubLkGuINYQMxI9UAuSQVa+tXsSym1uHaClv0
X-Microsoft-Antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:DB5PR07MB1557;
X-Microsoft-Exchange-Diagnostics: 1; DB5PR07MB1557; 25:S7kNSrTdxvPb2Btbwbolu73r0rRkCw6ZzItxaBX8Ll9KAPC2ykdlgd7t+SZLO9g/seunl+Y4JMCoidsMcYck7bG0a7FUSXQK+qxYNTBOl8uh3LnAUQOLivSk4pF8G7qSOL7iANDK8hmIcjyBiOPNDiNhw8o5WAtr4k9pqOhLVTHtKp0HkMW1TZkoqgYcP1/VIXa+4Fq6URcI5vleRbJDkKmiGHCf/H7oqvRRGiXImNefKacTMu41ROHbFYqVu823NV9GDeyyXABoakOCqpWzZT5oAdBEbuJhM1mIygPof6Xynre0ZxLvvEjVtWSTn0fBMMJTKpUtsYhDh+8QD4pkocYLsabRvRnA3V2+Mxdn3pxm2q3vu4gtfAewQWdIOsx9y+UzShDZesGH3T0ZEWi8uSmRq6f16GwBVt6WyL4M724eLM9+FXgDg/L7VPO6sZmzlAT3vAesAoQ4qgS5ceISlufNmwz98HaANGySL/IVS3TVX59LuYFcvCw3ETb6LUBHZkbufwOhaGjbTXdGo0wYXI8N/Hnm7Hn73WKXctWW68nL/dyEJdDnmvoVPI5f3cenucvhpyDtdVL9Pv3/qGoVBSQEwYryocnNG0YTw/bzbtwhdWmeP6Oe5eKOROZ6C5WN1dLVhNv4sL5urZZspb6My7vm4eSNtBD+I+RmgVA2jyfTwMfXnasgkBuiQyrhhIZcE0XCQoSKSwAGKHBXsAo1WT/v+fQ0vQ980gL69M3hXXY=
X-Microsoft-Antispam-PRVS: <DB5PR07MB1557459F3B9A1F1F35BAB449C6410@DB5PR07MB1557.eurprd07.prod.outlook.com>
X-Exchange-Antispam-Report-Test: UriScan:;
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(601004)(2401047)(8121501046)(5005006)(3002001)(10201501046); SRVR:DB5PR07MB1557; BCL:0; PCL:0; RULEID:; SRVR:DB5PR07MB1557;
X-Microsoft-Exchange-Diagnostics: 1; DB5PR07MB1557; 4:CKbYIre2JzmOWq/Qha7vruqm1ibzaoHUcc8NH51lH2spKpnVQ41KdM9LiZ3tEUzn2g9qghEnajkE3PL+jE+rj2xWqbVx7seUdQNy5g0c9hvnWXHpWmHTkOsF/ho4DW2DV0VHlKG90CiowY43/aWhJ/AkBkwWK1+Ewcw8u09cb7jZ7g5tFqTGitce6ER5EClGKp0J7eoDWi6RgY4mwm5CfC0CTiIJAL2boBWdF+0EIjbcxJELdCocHrCIMLFWnu90bwhXlddqmWZC81KZsSkibz0E1ORksr1wWIaAuIlAz/x0kdD2/dDHgaLPI+mGnVhrNVD70qw4amih+S3+yoaGsRoTp+KU1JWo4Eh2wmMwtYwsf9Ty61bERhVnotbLgjdD
X-Forefront-PRVS: 0954EE4910
X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10019020)(4630300001)(6009001)(13464003)(50854003)(377454003)(52044002)(62236002)(44716002)(1556002)(2870700001)(50466002)(8676002)(81166006)(3846002)(61296003)(33646002)(2351001)(6116002)(86362001)(47776003)(9686002)(42186005)(66066001)(586003)(19580395003)(110136002)(5008740100001)(92566002)(50986999)(44736004)(1456003)(81686999)(76176999)(189998001)(19580405001)(84392002)(2906002)(23676002)(14496001)(116806002)(107886002)(77096005)(50226002)(5004730100002)(81816999)(5820100001)(450100001)(74416001)(7726001)(4720700001); DIR:OUT; SFP:1102; SCL:1; SRVR:DB5PR07MB1557; H:pc6; FPR:; SPF:None; MLV:nov; PTR:InfoNoRecords; LANG:en;
X-Microsoft-Exchange-Diagnostics: =?utf-8?B?MTtEQjVQUjA3TUIxNTU3OzIzOlNsVTJjdGZsSlNNbmthZmNnNGRuVjhzQXpB?= =?utf-8?B?ODNuV1o2d2ZrOGIvOXRNYjRaQ0k0YmhRakk1OWVRY2N5Nmo5K0F6TlhsSlNq?= =?utf-8?B?dEI5TnN3VUF0VUlpSi8rY0hPWGZ5RjJmdUJUZlRnTzhRZFgzakFYUXpLZG5T?= =?utf-8?B?K2lBd1hJQzJkNWlKNHZ3SmFDSDl2andKRmJ6VDFPMGo2aWhpcXczZFFTMEVi?= =?utf-8?B?UW5ML3BGSDRYTklLMGd6NVVUUjdkQkxLV1RPR2drQjExWUZaRm43MDBJb0ps?= =?utf-8?B?djIwckV4amsrd2pTblNURU1RRUFoaHI1V1VuTUJBbHpINEtaUzIwdVhLQytm?= =?utf-8?B?NXcrd1RpUFdEeUpnVENVa1lpY09EUGtJZHJ0Qzd4WEdHUys2ZllWeENRdFdV?= =?utf-8?B?a1NUKzJxTy9CckxIT1pXNUdVNFZ0Q01jWlVGZXROTUpka2Q5RmEvSjFtc2dw?= =?utf-8?B?ZC9JL1J1NjArZVZKZUNEYTNEdDFMZEFwcDdqKzhLbVlVblBCeml1a2RxdTh1?= =?utf-8?B?dEt5U3NmZEUxekY3eXc5d2k0YzBERkRqQ0xEdWlGTHF4MVlSblgvNEdaalN6?= =?utf-8?B?UlhlWlhKV1R4ZURXZ2ZWZTVHUnhrczZwRXkxN1NKQjRJcER2dDJjTllJRGRo?= =?utf-8?B?M05rL0V6Q0JZR2IyWUlCL2MvSmhWRitwRGpGcmlJSitDME10cjU3L0JsNDl1?= =?utf-8?B?d25QN3hWaDN1L0E0RGc3SjFteDliWGdZSWR0VUM5L00xUG03eUhOSU16R0JG?= =?utf-8?B?Z3RaUUx6MXZXZlhrWXgrR3NhOG1lblZKODhndFFwZWd6QTY0UEk0RUE5VmRC?= =?utf-8?B?V2VzME13L0M3MncyUlNOTnNTcWdWMUFRdC8ydEk2dnF5WWtJVTNBOVgxTjZz?= =?utf-8?B?T3N0bUZNcmp1dS9reUNsd3phV1FkTFBTOVgvVVA0OFRLdHRKbkJyL29SaDYr?= =?utf-8?B?SmRiMzAyczA0ME0vR0oyRHZFNzdKMlZncDNUVnV6VXU4dWtPMHJRK3N5S0pI?= =?utf-8?B?dGdGV3Rqam9BbklRbm96VStRMEhBU1puYnhFOUF1SDJadDZoODBuNUhidWFt?= =?utf-8?B?VGhoUWE5TWRNVHh1RHBXRXlHR2UrclNjaWw5RWpEUWV4cHJiQTQ1L2dtblJ6?= =?utf-8?B?TXQ5dXdRTENXR2hCWnJUS3FBajFybzNtR0MrbW1WRDJYWTNVU3ZSY1g1dExh?= =?utf-8?B?RHVaNzF4VGhQUFdwRENncGVqVytiaHgrbGxRV29SbTB3RDZVaXRWRmJ0R0h3?= =?utf-8?B?bU96a1V5MWovellTQnZWZEQwZWZleWl4N05qK1QwRmJ2VEhuRDR5QVZHZUY5?= =?utf-8?B?YzM1NXQ2dnZjVjRDSUJabTVhVktuOTVrSG9kTzVqdlh1bXk2UzdPeEVRWG5P?= =?utf-8?B?aXBWaG01UGNlMlpidEQ2MFU0dW9DQTFpcWlCVVpXajN5SkZJQTI0UHpvcnox?= =?utf-8?B?cStpRmRhYjFvRUprVFdMb3U0QTFPcEEyejVkQTNrTXUxdHJPNk5FU1REeVhp?= =?utf-8?B?UTluNXA2QVJuTDNRZUN5TnpqZWlFYVR5TDRZTGJWNFBEZm93Q1ZlVUMvZWFY?= =?utf-8?B?ZTIxcENFRE9vWjNlckY0M0kxRUIwSWtYV3VnVmVYZ2hJVmZCaWloWGZMcjd6?= =?utf-8?B?ZVVFMHJEMWlTdGF0VXpNakl2L2sya3MvMFpkVjVCby9ZdGFDaWxaV2FDeU5O?= =?utf-8?Q?0ydFnQ2UUt/m6RAvB4mMg47flYmj4Mn+eIkt5QG?=
X-Microsoft-Exchange-Diagnostics: 1; DB5PR07MB1557; 5:T+V+2mHk8dqVrbKQPXV65LfbqLiVVkyMXQfehSVlpBuatv2ICeL/+kCTaQeW9+uSIbaObcYnwwt7NtVRimAu1r43n6vbW5/9gJVHuFiRwZ5aSDcBOr754UfpXMektzJpOuKYYaobmIFsYxnbi+xH0w==; 24:Slwk18n/ykTJxkrFQbFEXnmXhlmio4zF3VgWHQKw9/2vTQfHvflqA04Z8PyMFJnMz56l5/NoY4/Wt/ZhYAYofxLrM72d+5qiR+kChVRN5EI=; 7:aBJg0nIck0sRcWFXJquR31Weh1UdhAg0ACgBfrGmi0VGvspRA/mkz+doxWCpsvkBHjVVexRPJw9QHMXsu3UMjV+scv5gvJmtF3A4r1UOcsbfAc7aqpKMlSVs/iD2B5zOPdr6frMhJ5mTPAVFdksQ/YVEXs64nTGNalxasQRMtT/xIbgqUCE6ZgVkXFf4uAik
SpamDiagnosticOutput: 1:23
SpamDiagnosticMetadata: NSPM
X-OriginatorOrg: btconnect.com
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 26 May 2016 08:02:27.8789 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB5PR07MB1557
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/LwI06hWX9OB1U0F1_CKdeFvg8ic>
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: Thu, 26 May 2016 08:02:33 -0000

Leslie

I am unclear what, if any, action is expected as a result of this
message.

I understand that the IAOC has to make a decision and yes, I can provide
more input via venue-selection if I wish to, but is that all?  Will the
IAOC now decide?  If not, what is it waiting for (and how long is it
waiting)?

Tom Petch

----- Original Message -----
From: "IAOC Chair" <iaoc-chair@ietf.org>;
To: "IETF Announcement List" <ietf-announce@ietf.org>;
Cc: <recentattendees@ietf.org>;; <ietf@ietf.org>;
Sent: Wednesday, May 25, 2016 11:08 PM

> All,
>
> In the IAOC's previous message on this topic we stated that the IAOC
believed that it is possible to hold a successful meeting in Singapore,
and that meeting in Singapore is the best option for IETF 100.  This
statement was based on several factors, including evaluation of the site
based on the requirements and process now being updated and tracked in
draft-baker-mtgvenue-iaoc-venue-selection-process-02.  In particular,
this included consulting with the additional information sources
identified in the document (specialty travel services, etc), and no
specific issues were identified as to actual situation in Singapore.
More detail on the information we have to hand is provided below.
>
> Additional arguments have come forward since our earlier messages,
which leads us to continue exploring.  The IETF Chair has been in touch
with the meeting host, which is obviously another factor in whether we
can/should move.   But we need to make a decision, so this message
contains such information as we have at present.  We understand that it
is difficult to express a view about what to do in the absence of known
alternatives; but we do not know what the alternatives are now, and we
need urgently to make a decision, so we are sharing the incomplete
information we have in the interests of transparency.
>
>
> Laying this out in a pro/con format:
>
>
> Not Singapore:
> --------------
>
> If we cancel the contract we have for Singapore for IETF 100, the
onward positive impacts include:
>
> . We might have the opportunity to establish the meeting in a venue
that permits more IETF participants to be comfortable being present and
engaging in a celebration of this milestone meeting, which is important
to some.
>
>
>
> If we cancel the contract we have for Singapore for IETF 100, the
onward negative impacts include:
>
> . Losing approximately $80,000 (USD) hotel agreement cancellation
fee[1]
>
> . Losing up to approximately $150,000 (USD) in Singapore government
incentives [2]
>
> . Re-prioritizing people time to find a new location (the IAD,
Secretariat staff) who have full plates for lining up other future
meetings; there’s an unknown amount of impact in terms of how that
impacts *other* meetings (N.B.:  some of this effort is already underway
to obtain the information on possible alternatives and outline the
pros/cons outlined here).
>
> . Likelihood of IETF 100 in Asia is very small — we have few prospects
and it takes us months to get all the pieces aligned to get to a signed
contract in Asia (Singapore took over a year).  This would create
additional challenges for our Asian community members (travel distance,
visas).
>
> . Possible shift of dates — to be able to find a venue elsewhere that
works
>
> We have some wiggle room in the point about time to find a new venue
insofar as it would be easiest to use a North American site that we have
used before.   If we have to consider non-North American, and/or new
venues where a site visit is needed, effort and cost will be higher.
>
> Note, we should only cancel the Singapore contract once we know that
an alternative venue, that is acceptable to community, is ready to put
under contract.   The cost of cancellation ($80k now) goes up to $192k
if we don’t cancel before November 2016 (i.e., a few months from now).
>
>
> We do have to give the hotel a reason for canceling our contract:
>
> Reasons for Cancellation of IETF 100 Meeting in Singapore, and the
IAOC understands that to be:
>
> “    Singapore laws against same-sex relationships between men and
>     preventing the recognition of same-sex marriages could create
>     difficulties for same-sex partners and their children; these have
>     discouraged affected members of our community from participating
>     at the IETF meeting in November of 2017 and have also influenced
>     others to decline to attend in principled solidarity with them.
>
>
>     Accordingly, the IETF has decided to postpone indefinitely the
meeting
>     in Singapore and is pursuing alternative venues.”
>
>
>
> If we stick with Singapore for IETF 100:
> ----------------------------------------
>
> If we keep the contract we have for Singapore for IETF 100, the onward
> positive impacts include:
>
> . we have a functional meeting venue set for our 3rd meeting of 2017
>
> . meeting site research resources can remain focused on filling in the
remaining gaps in the 3-4 year timeframe
>
> . we don’t have the financial hit of the cancellation fee, and
possible loss of government incentives
>
> If we keep the contract we have for Singapore for IETF 100, the onward
negative impacts include:
>
> . we have a meeting at a location where some community members will
perceive themselves as unwelcome and unsafe, unable to bring family
>
> . possibly fewer attendees than we might otherwise expect — which is a
consideration for both getting work done and financial reasons
(registration fees per person)
>
>
>
>
>
>
>
> The above is the practical information as we can best scope it.
>
>
> If you would like to provide some considered feedback on this matter,
please feel free to send it to venue-selection@ietf.org .  Please note
that mailing list is a PUBLICLY archived “drop box” [3].
>
>
> Leslie Daigle, for the IAOC.
>
>
> [1] The cancellation fee can be recovered if it is used as a deposit
at a later meeting with those hotels in Singapore, if it is before 2020;
for this discussion, it’s perhaps best to consider it gone.
>
> [2] Government business incentives are not unusual; we might obtain
these in another country hosting IETF 100, but we are late to be
expecting incentives and opportunities for good deals, and are unlikely
to get this in a North America venue.
>
> [3] The venue-selection mailing list is not open for subscription, and
it is not intended to archive dynamic conversations (i.e., don’t cc it
on an e-mail discussion thread, because there will be too many
addressees and your mail won’t go through).
>
> --
>
> -------------------------------------------------------------------
> Leslie Daigle
> Principal, ThinkingCat Enterprises LLC
> ldaigle@thinkingcat.com
> -------------------------------------------------------------------
>