Re: [Diversity] Concerns about Singapore

SM <sm@resistor.net> Tue, 12 April 2016 08:15 UTC

Return-Path: <sm@resistor.net>
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 B4F2512DD11 for <diversity@ietfa.amsl.com>; Tue, 12 Apr 2016 01:15:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.79
X-Spam-Level:
X-Spam-Status: No, score=-1.79 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_NONE=-0.0001, T_DKIM_INVALID=0.01] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=opendkim.org header.b=KCiQKfeo; dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=resistor.net header.b=oT8ccCRH
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 IPr8S8zrcZiY for <diversity@ietfa.amsl.com>; Tue, 12 Apr 2016 01:15:15 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 8676912DBF5 for <diversity@ietf.org>; Tue, 12 Apr 2016 01:15:15 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id u3C8F6tF008546 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 12 Apr 2016 01:15:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1460448912; x=1460535312; bh=5aKeltWpY5GirN+JxF2WUEG6i6kPlzcZA6UpKG3YOVY=; h=Date:To:From:Subject:In-Reply-To:References; b=KCiQKfeopmUSMc/jZck8XPo1NQthOOwZnCG999igpJYUEqVJVDqFi1FysTKkl2GK5 h/5In19EB/GiKxT/hQxC/1exph30JIS/QJW3tNjny6Fyo0BtlL1J19rx8NhfgI1UUT cjzCiUh4E4jiLDE0OGV7mnYsrJHvZVr+kFPGw0Bg=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1460448912; x=1460535312; i=@resistor.net; bh=5aKeltWpY5GirN+JxF2WUEG6i6kPlzcZA6UpKG3YOVY=; h=Date:To:From:Subject:In-Reply-To:References; b=oT8ccCRHReZk9ElqpNiJ1QnMwX0ePKvQQw34QYK1zfdD6V3ppimxRMOqYGDu09CVr KtaK9/nNmPzH43k7DMHMGe9Kk1oQ1k5Sz21xe1o2WFMn3J3XQQ94jfUbV0mbFrnhiU 6mcS25HLCJeWMs3LDuhXKbmASEFZ1kL2+0R5m1zY=
Message-Id: <6.2.5.6.2.20160411230601.0f95daf0@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 12 Apr 2016 01:08:44 -0700
To: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>, Vinayak Hegde <vinayakh@gmail.com>, diversity@ietf.org
From: SM <sm@resistor.net>
In-Reply-To: <CAKKJt-eHpqbh+i+ZfaF6BtsrP6nzPTzOMzgwxnWMURC5SwPxJQ@mail.g mail.com>
References: <20160410063603.6283348.44889.10575@blackberry.com> <459690655.171220.1460293717474.JavaMail.yahoo@mail.yahoo.com> <6.2.5.6.2.20160410074445.0de30c68@resistor.net> <570A8B0E.5060505@cs.tcd.ie> <CAKe6YvMgZCA8NkKAbhGzdc8XQj+S+ma90_jw788qTs0xLOZRyQ@mail.gmail.com> <CAKKJt-eHpqbh+i+ZfaF6BtsrP6nzPTzOMzgwxnWMURC5SwPxJQ@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Archived-At: <http://mailarchive.ietf.org/arch/msg/diversity/_RCCP2xNLzH34R7TZndXhvQyL1Y>
Subject: Re: [Diversity] Concerns about Singapore
X-BeenThere: diversity@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
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: Tue, 12 Apr 2016 08:15:18 -0000

Hi Spencer, Vinayak,
At 19:28 11-04-2016, Spencer Dawkins at IETF wrote:
>This may sound like I'm arguing with you, but I'm agreeing on your meta-issue.

[snip]

>Now, if you read what I've said so far, you'll notice that even 
>working for a large multinational that routinely sends dozens of 
>participants who require visas to IETF meetings, and spending five 
>years on the IAB and IESG, I don't know very much about the state of 
>play here. I've got a lot of "I heard"s, and a lot of "I don't know X, but"s.
>
>So, if your meta-issue is that more transparency would be awesome, 
>I'd agree wholeheartedly! Because one of the side effects of 
>translucence, or even opacity, is that people work their asses off, 
>and most of us never hear about it, even if we would benefit by 
>knowing about what they had done.

Would I believe a "I heard" or "I don't know X but"?  I might do so 
the first time.  As I experience the problem again and again I might 
wonder whether the "good people" understand the problem I am 
facing.  When I see IETF attendees complaining about a room 
temperature problem I wonder whether that is what the IETF Community 
considers as the priority.

I read the minutes of proceedings of the last plenary.  There was the 
following comment: "An important venue selection principle is that it 
is inclusive".  I don't see that in the IAOC slides (2013) about 
venue selection.  Do I need to attend an IETF meeting to know about 
that principle?  Is that transparency?

Regards,
-sm