Re: Concerns about Singapore

Ole Jacobsen <olejacobsen@me.com> Sun, 10 April 2016 15:08 UTC

Return-Path: <olejacobsen@me.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 1081D12D5BF for <ietf@ietfa.amsl.com>; Sun, 10 Apr 2016 08:08:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.596
X-Spam-Level:
X-Spam-Status: No, score=-3.596 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, RP_MATCHES_RCVD=-0.996, 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 iEpARnxovSon for <ietf@ietfa.amsl.com>; Sun, 10 Apr 2016 08:08:20 -0700 (PDT)
Received: from st11p02im-asmtp002.me.com (st11p02im-asmtp002.me.com [17.172.220.114]) (using TLSv1.2 with cipher DHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6DD4C12D16C for <ietf@ietf.org>; Sun, 10 Apr 2016 08:08:20 -0700 (PDT)
Received: from [31.133.164.144] (dhcp-a490.meeting.ietf.org [31.133.164.144]) by st11p02im-asmtp002.me.com (Oracle Communications Messaging Server 7.0.5.36.0 64bit (built Sep 8 2015)) with ESMTPSA id <0O5F009A9BDSA710@st11p02im-asmtp002.me.com> for ietf@ietf.org; Sun, 10 Apr 2016 15:08:19 +0000 (GMT)
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2016-04-10_08:,, signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 clxscore=1015 suspectscore=0 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1510270003 definitions=main-1604100226
Content-type: multipart/alternative; boundary=Apple-Mail-131EC800-0DE7-4D34-B88F-6C9506008312
MIME-version: 1.0 (1.0)
Subject: Re: Concerns about Singapore
From: Ole Jacobsen <olejacobsen@me.com>
X-Mailer: iPhone Mail (13E238)
In-reply-to: <CAKKJt-cjYe-FgRW9n-Ve7KWPq2ALYUDwQb=nuAHONQFpbGb8Fw@mail.gmail.com>
Date: Sun, 10 Apr 2016 12:08:16 -0300
Content-transfer-encoding: 7bit
Message-id: <BE6114E3-5CFA-4416-8C36-DB05B0239F18@me.com>
References: <0D914666-C3D4-4CCE-AD5E-4E5B34EA1A73@piuha.net> <20160407182936.GA21340@pfrc.org> <CAB75xn780nNDjGa_Cc222J20-+1CCHt09Xp8KHzaK=n0xx51pg@mail.gmail.com> <5706B100.9040509@mnt.se> <CAB75xn6fmj84ROUtG5eUB3GerHx83hrEr3w5vSADY_g=BRg5FA@mail.gmail.com> <9B723FB0-6B93-4C85-ADD9-D423F873CF08@virtualized.org> <20160409155300.6283348.41255.10529@blackberry.com> <ADC8666A-436C-4AD4-BD48-9277601069F8@gmail.com> <20160410063603.6283348.44889.10575@blackberry.com> <CAKKJt-cjYe-FgRW9n-Ve7KWPq2ALYUDwQb=nuAHONQFpbGb8Fw@mail.gmail.com>
To: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/_3gjljS5g1VMP0N7OW7-WEIXBUg>
Cc: ietf@ietf.org
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: Sun, 10 Apr 2016 15:08:22 -0000

Please rest assured that we are gathering information on precisely these issues!

Ole J. Jacobsen
Editor & Publisher
The Internet Protocol Journal
Cell: +1 415 370-4628
docomo: (090) 3337 9311
http://protocoljournal.org

Sent from my iPhone

> On Apr 10, 2016, at 12:01, Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com> wrote:
> 
> This has been a wide-ranging conversation that I've been content to watch quietly, but Andrew just stepped on the land mine ...
> 
> On Apr 10, 2016 01:36, "Andrew Allen" <aallen@blackberry.com> wrote:
> >
> >
> > That's why I proposed that IETF check with the hotels that this isn't going to be an issue. The other potential issue I foresee which needs checking with the authorities is if there will be a problem with customs and immigration forms with questions regarding marital status and number of family members traveling with you.
> 
> Bingo.
> 
> I've been coming to the IETF since 1996, and I know a fair number of GLBTQ IETF participants, but I knew most of them for years, and in a few cases for more than a decade, before realizing that.
> 
> For my GLBTQ friends from the US, it has been relatively recent for most of them to live their lives openly.
> 
> The gay man who automatically came to IETF meetings even ten years ago with no "paper trail" ten years ago is now much more likely to show up with a paper train now.
> 
> If he shows up with another man with the same last name, the same address on IDs, each other as emergency contacts on every form that asks for that, and (for extra credit) one or more kids with the same last name in tow, it's a lot harder to miss in 2016 than it was in 2006, and at least some of that is still visible even if he leaves the family at home.
> 
> Our friends who were forced to suffer in silence until recently would have a much more difficult time doing that today, even if they wanted to.
> 
> Spencer