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

Harish Pillay <harish.pillay@gmail.com> Mon, 23 May 2016 14:38 UTC

Return-Path: <harish.pillay@gmail.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 2230A12B02A for <ietf@ietfa.amsl.com>; Mon, 23 May 2016 07:38:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
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: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 jRAa1ZgJ93XX for <ietf@ietfa.amsl.com>; Mon, 23 May 2016 07:38:25 -0700 (PDT)
Received: from mail-io0-x22c.google.com (mail-io0-x22c.google.com [IPv6:2607:f8b0:4001:c06::22c]) (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 2BDA31200A0 for <ietf@ietf.org>; Mon, 23 May 2016 07:38:25 -0700 (PDT)
Received: by mail-io0-x22c.google.com with SMTP id p64so103238293ioi.2 for <ietf@ietf.org>; Mon, 23 May 2016 07:38:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to; bh=lQxfBl6ac3ueo1j4Zz6pTKiD7XC3t4hOPFMPwxXvo+Y=; b=RnwNwDrPmARJ9al6HZ7Md63mCfWKbSaIBfYD6nO2KoZpOcbVzRohGfqfmKg6CWxOtC 9oyWA4AjJ1l6VIyTgG3L/tnCRPQHg607GT50yxFN85hqvyqMCHIH0mLq1QXk/O5l+xaa gt2gH5/5pPlTKVVRg+tTMayYSSsv4hsjWyH1L2MlMb73Oc2mLjieMHC5ZnI4Y1cANzV/ WqETb1uwPymG+e2tAm/H2M4D+/sOPDNBw+a9HpBGUtB/lf4s0PDHvfHCCbj5bRUnvsmB p+Vbvwekom2+X9la6Aq101EReB4SEDQ1FLSkGp0j7HVl88U7iW4yttCUbYIsqeKSFzD5 ipuw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to; bh=lQxfBl6ac3ueo1j4Zz6pTKiD7XC3t4hOPFMPwxXvo+Y=; b=fo/BN6IxSO93a6PW8DVuUytKkjXc9ykJOw+Hkck5CAhDwQmSlAyG6QD3mTknkhqUd4 Ufrp1rIckn1+RFbWk5E0gCRMgd92aNt6hN6OYAjs1UwK9ALvvp7RmFb3ArdOvvr5k/Gs uI32OFp2GuCkGnF3mE0MzdWtV+X2CpYc11PxBtcrg1SAfcNQMdkH/rta5QHYQVGzDc2F rFaTgZrTvSMekGj40zDo2AqZxQiI9QTuthUbQS7H0MMk1Z4LXfGu1TXIS3/rrJj5lDsj UtoOCUnbZG6NaawchzoG2One3XFJtgu8Pi9YL6mi1AxsGIAT+qZ8R4FAlt8n8ORqRO/F Wdqg==
X-Gm-Message-State: AOPr4FVzygPLDEeWw3ZwbdI0TsoIeXjQIf1/gcfv+MZo0HHB5e1soEQqfAAA3C9ACuWmSZDfdjQ8Z1cEQo172A==
MIME-Version: 1.0
X-Received: by 10.107.161.195 with SMTP id k186mr13403197ioe.190.1464014304326; Mon, 23 May 2016 07:38:24 -0700 (PDT)
Received: by 10.107.47.11 with HTTP; Mon, 23 May 2016 07:38:24 -0700 (PDT)
In-Reply-To: <2e95fd51-23b8-39e7-d4ca-a9fc9d49559c@gmail.com>
References: <D3662363.190A96%jon.peterson@neustar.biz> <CAP8yD=spam0tQdfD-ssA6y_n-cuugHtrHKwTYieSruo8SMg_VQ@mail.gmail.com> <CAHkmkwtEtDk4sPv3GjkrSFqOdRV3HBA5i2_uZu3X2D4RxSF4wA@mail.gmail.com> <2e95fd51-23b8-39e7-d4ca-a9fc9d49559c@gmail.com>
Date: Mon, 23 May 2016 22:38:24 +0800
Message-ID: <CAHkmkwsf3YfFfR7jUHYnaw6dCrasMOazjbXPJRRhZS28k8HV0w@mail.gmail.com>
Subject: Re: [Recentattendees] IETF 100, Singapore -- proposed path forward and request for input
From: Harish Pillay <harish.pillay@gmail.com>
To: ietf@ietf.org
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/x5v9_KiLsHt9_2JSs6JjWmTwBk8>
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: Mon, 23 May 2016 14:38:27 -0000

On Mon, May 23, 2016 at 10:09 PM, Melinda Shore <melinda.shore@gmail.com> wrote:
> On 5/23/16 12:33 AM, Harish Pillay wrote:
>>
>> For that matter, and this is something I brought up previously as well,
>> if there is indeed active prosecution, how would you explain
>> http://pinkdot.sg
>> happening in Singapore year in, year out? It is a very public event and
>> no one was prosecuted. Zilch.
>
> I'm unclear on why this is a guarantee that, say, familial rights
> will be respected.  There were GLBT pride marches for decades in
> the US, Canada, England, and so on before that became the case.
>
> It used to be common in threat analytic frameworks to define the
> cost, or risk, of a particular threat as a function of the threat's
> likelihood and its impact.  That is to say, a low-likelihood threat
> that had potentially devastating impact was identified as a very
> high priority despite its unlikely occurrence, specifically
> because of the dire consequences if it did happen.
>
> The situation in Singapore is that bigotry has the force of law, and
> should a GLBT person run into that rare medical professional who has a
> particular animus towards gay people, or a cop who's having a bad day,
> or whatever, the law in Singapore does not provide protection against
> that bigotry - rather, the law is on the side of the bigot.  To say
> that the law is rarely enforced doesn't actually make things better -
> it introduces a level of uncertainty that may lead people who don't
> deal with these things to think everything's okay but still leaves the
> possibility for bad outcomes and high risk for GLBT people, as the
> power of the state is behind the bigots.

The view in the the preceding paragraph is coloured by the lenses of
your personal/national experience - which is very normal.

We do not (at least have not) had situations where the police officer
"on his bad day" did what you suggest. FWIW, and at the risk of
mixing examples, gun ownership is not what we have as a right in
Singapore. Although the police do carry weapons, it is very rarely
ever used. That is my world experience. When I travel to the US and
I see people carrying weapons, how am I supposed to react/respond?
It is very bizarre for me to see gun stores in malls in the US. I know
my two young sons were shocked to see the range of guns on sale
in the store in California. That is not the reality here. I have calibrated
my world view based on those experiences. [disclosure: I have done
my national service and using a weapon is not an alien thing.]

> It seems clear that there are two basic sub-threads here: 1) whether
> the situation in Singapore is actually a problem, and 2) what supporting
> "diversity" in the IETF means in practice.  I think it's pretty clear
> that yes, there's a problem in Singapore in that while it's unlikely
> that someone will run into conflict, the consequences if they do are
> potentially shattering.  As for what "diversity" means in the IETF,
> I dunno.  Pretty much every discussion of gender, GLBT issues, and so
> on gets diverted into a discussion of geography.

I hear your concerns. I hear your anxiety about medical situations.
I cannot guarantee that you won't have an issue, but my gut sense
is that this is being blown way out of proportion. Yes, it is a critical
issue and a big deal for you. All I can say is that you have to decide
for yourself what you should do. I would warmly welcome you to
Singapore, warmly assert that you won't have an issue, but in the
end, it is up to you.

Should the IETF, in making sure that there is "diversity" accommodate
all of the variations of expectations and worldviews of the IETF
community? In an ideal world, yes. We, however, do not live in an
ideal world. We have to make the best of what we have. We have
to weigh the pros and cons and take an action. Else it would be
paralysis and that cannot be a good thing.

Harish