Re: [Recentattendees] IETF 100, Singapore -- proposed path forward and request for input

Adam Roach <adam@nostrum.com> Tue, 17 May 2016 19:19 UTC

Return-Path: <adam@nostrum.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 8B1FB12D918; Tue, 17 May 2016 12:19:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.326
X-Spam-Level:
X-Spam-Status: No, score=-3.326 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-1.426] 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 CFiEjyvfhy2a; Tue, 17 May 2016 12:19:18 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2C47612D9B1; Tue, 17 May 2016 12:19:18 -0700 (PDT)
Received: from Orochi.local (99-152-145-110.lightspeed.dllstx.sbcglobal.net [99.152.145.110]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id u4HJJG2M021423 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Tue, 17 May 2016 14:19:17 -0500 (CDT) (envelope-from adam@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host 99-152-145-110.lightspeed.dllstx.sbcglobal.net [99.152.145.110] claimed to be Orochi.local
Subject: Re: [Recentattendees] IETF 100, Singapore -- proposed path forward and request for input
References: <20160517181436.24852.58610.idtracker@ietfa.amsl.com>
To: venue-selection@ietf.org, IETF list <ietf@ietf.org>
From: Adam Roach <adam@nostrum.com>
Message-ID: <3945cc1f-3e99-0fcb-e983-ed2e46fa871c@nostrum.com>
Date: Tue, 17 May 2016 14:19:16 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:45.0) Gecko/20100101 Thunderbird/45.1.0
MIME-Version: 1.0
In-Reply-To: <20160517181436.24852.58610.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/bJNZSlIXUEijk_LD3QZ4iXjiaho>
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, 17 May 2016 19:19:20 -0000

On 5/17/16 13:14, IAOC Chair wrote:
> The IAOC meetings committee reviewed the options for IETF 100, including investigating costs and possibilities of moving the meeting to a different location.  In keeping with the updated process outlined below, they checked with official advisory sources and consulted with specialty travel services, frequent travelers, and local representatives about the concerns that have been raised.  The input received from those sources is consistent with the text on http://travel.state.gov [1].
>
>  From that research, at a strictly practical level, the IAOC believes that it is possible to have a successful meeting in Singapore.  The IAOC proposes that holding the meeting in Singapore is the best option for IETF 100 at this time.
>
> Next Step:
>
> The IAOC would like to hear from the community by June 1st, 2016 on barriers to holding a successful meeting in Singapore. Responses should be directed to venue-selection@ietf.org


I have a hard time making a valid evaluation of this topic. I suspect 
many people who will weigh in over the next few weeks are in a similar 
situation, even if they don't realize it. I include the IAOC in this 
characterization.

It is very difficult to interpret the effect of potentially oppressive 
environments on the potentially oppressed if you are not a member of 
that group. It would be presumptuous for a majority straight population 
to make this decision on behalf of those people actually impacted.

So I'm going to withhold expressing support for or opposition to the 
proposed course of action until we hear from GLBTQ IETFers in light of 
the information the IAOC is offering as rationale for continuing to 
pursue Singapore as a venue.

But to be clear: I will almost certainly forgo attending a meeting at 
which any of my GLBTQ colleagues felt unwelcome. I would actively 
encourage others to adopt the same stance. Whether this forms a barrier 
to a successful meeting is up for debate; however, It would almost 
certainly be a setback for the working groups I chair.

/a