Follow-ups: Concerns about Singapore

"Carlos Pignataro (cpignata)" <cpignata@cisco.com> Fri, 08 April 2016 20:57 UTC

Return-Path: <cpignata@cisco.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 A0B1712D66A for <ietf@ietfa.amsl.com>; Fri, 8 Apr 2016 13:57:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.531
X-Spam-Level:
X-Spam-Status: No, score=-14.531 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 sIx2EJOuKieT for <ietf@ietfa.amsl.com>; Fri, 8 Apr 2016 13:57:23 -0700 (PDT)
Received: from aer-iport-2.cisco.com (aer-iport-2.cisco.com [173.38.203.52]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AB27812D1D4 for <ietf@ietf.org>; Fri, 8 Apr 2016 13:57:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2651; q=dns/txt; s=iport; t=1460149042; x=1461358642; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=NtK9xnckBrfQxP49q165InYAcJ1/rhAPdyUbgxiUvcQ=; b=FffeK2j95bkpi5nMCJpl47SXFsJQ2dvUpmfpzzp/D73Y9sO5B5J+9y9Q SvXfg6rc3ktFQAg9nerLvvrnFWzDPCBPPHVPReIKZPe7dcf9uf0i7mf+O TMDMEnRpCvLdLgRfRUT6JwLTkY0L+VFts8pQloC03ziGdjozwyPftav6k w=;
X-Files: signature.asc : 841
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0B9AgB4GghX/xbLJq1chAp9Bro/DoFzF?= =?us-ascii?q?wqFIkoCgWsUAQEBAQEBAWUnhEIBAQQBAQEgSxsCAUcDAgInCxQRAgQTDgaIEw4?= =?us-ascii?q?DrmyRZgEBAQEBAQEBAQEBAQEBAQEBARAEBIYhgXUIig0rgisFh2cChxeEGYRrA?= =?us-ascii?q?YMjgWZtiBWPDYY4iGwBHgFDg2dsiDt+AQEB?=
X-IronPort-AV: E=Sophos;i="5.24,454,1454976000"; d="asc'?scan'208";a="634061986"
Received: from aer-iport-nat.cisco.com (HELO aer-core-1.cisco.com) ([173.38.203.22]) by aer-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 08 Apr 2016 20:57:20 +0000
Received: from XCH-RTP-020.cisco.com (xch-rtp-020.cisco.com [64.101.220.160]) by aer-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id u38KvKaZ006805 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL) for <ietf@ietf.org>; Fri, 8 Apr 2016 20:57:20 GMT
Received: from xch-rtp-020.cisco.com (64.101.220.160) by XCH-RTP-020.cisco.com (64.101.220.160) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Fri, 8 Apr 2016 16:57:19 -0400
Received: from xch-rtp-020.cisco.com ([64.101.220.160]) by XCH-RTP-020.cisco.com ([64.101.220.160]) with mapi id 15.00.1104.009; Fri, 8 Apr 2016 16:57:19 -0400
From: "Carlos Pignataro (cpignata)" <cpignata@cisco.com>
To: IETF discussion list <ietf@ietf.org>
Subject: Follow-ups: Concerns about Singapore
Thread-Topic: Follow-ups: Concerns about Singapore
Thread-Index: AQHRkOMZq+MCcr0Tk0mYGURd2vrzsZ9/GCcAgAAATwCAAAuKAIAACE6AgAD6eICAAAvNgIAAOMwAgAAA3QCAAAUnAIAATyuAgAAIkACAAAqfgA==
Date: Fri, 8 Apr 2016 20:57:19 +0000
Message-ID: <25300889-93D6-48E8-B71D-3CCA27017681@cisco.com>
References: <CAB75xn6fmj84ROUtG5eUB3GerHx83hrEr3w5vSADY_g=BRg5FA@mail.gmail.com> <1481689286.47880.1460111891664.JavaMail.yahoo@mail.yahoo.com> <alpine.OSX.2.01.1604080418530.36488@rabdullah.local> <594.1460126622@obiwan.sandelman.ca> <5707C458.7080107@dcrocker.net> <20160408150512.6283348.55871.10388@blackberry.com> <3746.1460144915@obiwan.sandelman.ca> <alpine.OSX.2.01.1604081315580.38286@rabdullah.local>
In-Reply-To: <alpine.OSX.2.01.1604081315580.38286@rabdullah.local>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.82.247.9]
Content-Type: multipart/signed; boundary="Apple-Mail=_13E7CC2E-F921-47EB-AC3B-C0556B69DAEE"; protocol="application/pgp-signature"; micalg=pgp-sha256
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/oeS4XCp67SUgSTfsSMM5VQlqcVs>
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: Fri, 08 Apr 2016 20:57:24 -0000

Hi,

[This note is sent as part of the Facilitators experiment, to maximize the effectiveness of discussions at the IETF-Discussion mailing list]

As this thread started with the concerns express during the plenary about Singapore as a meeting venue, I wanted to summarize the arguments, and refocus and redirect the discussion:

Several details on both the letter and the practicality of the Singapore law that discriminates agains LGBTQ, and its implications, followed these community-expressed concerns. A number of suggestions, recommendations, and additional pieces of information about other countries and locations were also shared.

The IAOC and its Meetings Committee acknowledged the issue, and shared a two-point plan at [1].

Meeting venue selection and its associated criteria is naturally a relevant and most important topic for the community. At this point, the most effective channel for providing input and discussion is at the MTGVENUE mailing list [2] [3], following the MTGVENUE BoF. That would ensure feedback and requirements are appropriately captured.

Thanks!

— Carlos.

[1] https://mailarchive.ietf.org/arch/msg/ietf/hKwBYOwPkE6VTA4mxxf00NTLLF0
[2] https://www.ietf.org/mailman/listinfo/mtgvenue
[3] mailto:mtgvenue@ietf.org