Re: [Diversity] Concerns about Singapore

<nalini.elkins@insidethestack.com> Mon, 11 April 2016 00:31 UTC

Return-Path: <nalini.elkins@insidethestack.com>
X-Original-To: diversity@ietfa.amsl.com
Delivered-To: diversity@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 26D4112D9D6 for <diversity@ietfa.amsl.com>; Sun, 10 Apr 2016 17:31:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.62
X-Spam-Level:
X-Spam-Status: No, score=-2.62 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=yahoo.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 7qbT5t-VGQ2z for <diversity@ietfa.amsl.com>; Sun, 10 Apr 2016 17:31:27 -0700 (PDT)
Received: from nm22-vm4.bullet.mail.ne1.yahoo.com (nm22-vm4.bullet.mail.ne1.yahoo.com [98.138.91.182]) (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 8C31E12D920 for <diversity@ietf.org>; Sun, 10 Apr 2016 17:31:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1460334685; bh=iXA1s1p3FZiw2O+j5H72OpRJn79YZnpOgLGwHPwcuZc=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:From:Subject; b=q5ICcv+uQCJHdHoOYIwKLXqr+8yqtjlS5WWt8EQ/nkhYJlEwbJ2OElW4IUfThrHMSE9A/K4k2QVtW/ATRluZh8DMp/o5VIeFg7nM1xCd5KX54UMylFgCmG+hwpCA8YGn9X6xbIzaKUZo0jHrMaNLjVr0jMH/oi/rGe/U/pmHlVHwHoCNY1jAriZJ37MkKIigNGt648eP1NpDJx3Ag+l0ClgPfAsKrsPBpK64sGwz3Ttzhd+/0tvLmxU4lTvrNT9BvJ084hWNX3t8V30m6jl2WbiKi7ltGpjgIcvswjTZCtL09IVWytcIRs0uuw8Y+Dv6YltbAC0cUkrZWdRXPCkOBA==
Received: from [98.138.100.114] by nm22.bullet.mail.ne1.yahoo.com with NNFMP; 11 Apr 2016 00:31:25 -0000
Received: from [98.138.226.165] by tm105.bullet.mail.ne1.yahoo.com with NNFMP; 11 Apr 2016 00:31:25 -0000
Received: from [127.0.0.1] by omp1066.mail.ne1.yahoo.com with NNFMP; 11 Apr 2016 00:31:25 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 803674.94337.bm@omp1066.mail.ne1.yahoo.com
X-YMail-OSG: B3h_hJYVM1lg9dCDXzNbkCxKcb3hHwLpQVc4lJ.odASy8xR7LlAn_iZyS6rXJzQ BQpjEX2PNLpYUJK5dXkKgMkuBL2.PcQWyDQXc3JgWQ_QB8Ew0QqNCpQvR5hpH9S8..2R6kg_QDjC 2387d8rsC.tRb5N6YTtEu6oQcJQc..yW8qt4H8gzCmvL9ZYP4iYaXwkbTo1QLpBV1O4Mukd.gzQr dpTehmvaQl5U60aNcaq1iM5XId9R1WmcLmWfLyPK5rBBaWmgHHNDvC4mBrf09p9wy3RG7jYSlcyT UjvIoRzs4wqf.tZgXXHpga3.RTfp_vs2ArukfRfu997rpn2vkj0FpdfmEPGswOTl7fP.h4E0ZkQs 4.rzb9K2q7Gm2Tp_K1cwTX2d7aPXRFNBIK.8A_4A0dbD3mSXe98h9E795_AtFetbT8Gt04HtXAyZ gPRw6EZDXAuZcJZ2usmBJdNnWWvcfCVcEz8TiGPHRHB8JeYUbLetShYCFz5D4J.GeVvDSooa8eEU tQsne0ri7hOoEHmQ0V0ue88Q-
Received: by 98.138.105.203; Mon, 11 Apr 2016 00:31:25 +0000
Date: Mon, 11 Apr 2016 00:30:42 +0000
From: nalini.elkins@insidethestack.com
To: Vinayak Hegde <vinayakh@gmail.com>, SM <sm@resistor.net>, Fernando Gont <fgont@si6networks.com>
Message-ID: <704605888.359174.1460334642318.JavaMail.yahoo@mail.yahoo.com>
In-Reply-To: <CAKe6YvNWOVQQXMa+nGYhWkHGRgB7DM3yYcTCELWZ4AbipZAdwA@mail.gmail.com>
References: <CAKe6YvNWOVQQXMa+nGYhWkHGRgB7DM3yYcTCELWZ4AbipZAdwA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/diversity/v7yb3t0vTPE7H2VWfq0p3tQs9RM>
Cc: "diversity@ietf.org" <diversity@ietf.org>, Andrew Allen <aallen@blackberry.com>, Yoav Nir <ynir.ietf@gmail.com>, Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: [Diversity] Concerns about Singapore
X-BeenThere: diversity@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: nalini.elkins@insidethestack.com
List-Id: Diversity open mailing list <diversity.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/diversity>, <mailto:diversity-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/diversity/>
List-Post: <mailto:diversity@ietf.org>
List-Help: <mailto:diversity-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/diversity>, <mailto:diversity-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Apr 2016 00:31:28 -0000

>

> Stepping back a little, and going off-topic, the issue of a few years ago
> was diversity in the IESG.  The current issue is diversity in the IAOC.  It
> highlights a cultural insensitivity within the IETF.


+100

Guys, I want to put together some thoughts (for whatever they are worth) about what IMHO is really going on.  The venue issue is the canary in the coal mine that is highlighting some fundamental transitions that are taking place in the world.  The IETF is not immune from the changes that it itself has helped to create: that is the Internet and the power shifts that are taking place as a result.

Now, again IMHO, we can do this the hard way (try to really understand the problem, really listen to each viewpoint & try to understand each other's reality) or we can do it the harder way (ignore the fundamental problem, focus on details, and be non-transparent).

Naturally, once the "harder" way does not work, we will be back to the first.

When I was in my mid-twenties, I spent two of the happiest years of my life as a Peace Corps volunteer living at the edge of the bush in West Africa under a military dictatorship, with no free speech, no running water, and intermittent electricity.   The reason the time was happy was because of the generosity, warmth and kindness of the people who welcomed a stranger into their lives.

The reality of many parts of the world is very unfamiliar to people in the western world, and seems even "wrong".  IMHO, this is a part of what we are seeing with the whole "Singapore" issue.   People at the IETF have talked about wanting "diversity" for quite a while.  Well, it is coming quickly.  The reality of it demands changes and flexibility from all.

I feel that the IETF with its tradition of transparency and collaboration is uniquely equipped to handle this challenge.  If it can't work here, it can't work anywhere.  And, I think it can work at the IETF.  But the "how" may require some innovation in how we go about this.

I will write my thoughts up (again, if they can be of any help to the community).  But, I just got home & I am brain dead & exhausted.  So, after wrapping up a few other email thread, I am going on radio silence for a week or so.

Nalini