Re: [Diversity] Concerns about Singapore

Dave Crocker <dhc@dcrocker.net> Sun, 10 April 2016 17:58 UTC

Return-Path: <dhc@dcrocker.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 05D7B12B05F for <diversity@ietfa.amsl.com>; Sun, 10 Apr 2016 10:58:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] 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 I_oHfTTI4hhF for <diversity@ietfa.amsl.com>; Sun, 10 Apr 2016 10:58:00 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3FC0F12B053 for <diversity@ietf.org>; Sun, 10 Apr 2016 10:57:59 -0700 (PDT)
Received: from [192.168.1.168] (76-218-10-206.lightspeed.sntcca.sbcglobal.net [76.218.10.206]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id u3AHvoJi001876 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Sun, 10 Apr 2016 10:57:51 -0700
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>, SM <sm@resistor.net>, nalini.elkins@insidethestack.com, Andrew Allen <aallen@blackberry.com>, Yoav Nir <ynir.ietf@gmail.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>
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
Message-ID: <570A9419.5090009@dcrocker.net>
Date: Sun, 10 Apr 2016 10:57:45 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <570A8B0E.5060505@cs.tcd.ie>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Sun, 10 Apr 2016 10:57:53 -0700 (PDT)
Archived-At: <http://mailarchive.ietf.org/arch/msg/diversity/FNFIM6CB4GsTyxNyaVw0YcSXo3g>
Cc: diversity@ietf.org
Subject: Re: [Diversity] Concerns about Singapore
X-BeenThere: diversity@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: dcrocker@bbiw.net
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: Sun, 10 Apr 2016 17:58:02 -0000

On 4/10/2016 10:19 AM, Stephen Farrell wrote:
> What I think needs to happen is that the IAOC need to decide that
> information they process or create will be openly available as the
> default, while also identifying the specific kinds of information
> that they do need to keep confidential (e.g. hotel contract details).


That model can and does work for criteria subject to relatively 
objective and relatively consistent analysis.

On matters of political, social and environment concern, the community's 
concerns and reactions are significantly less predictable.

The IAOC (and the Meetings Committee that I participate in) means well 
and attempts to be diligent, but it simply is not certain (or IMO, 
likely) to adequately assess these kinds of community concerns well 
enough.  Last week demonstrated that.

'Transparency' is not a magical incantation.  The specifics of its 
nature and timing determine its efficacy.  In this case, merely 
publishing 'criteria' leaves an entire analysis process to be 
unpredictable; and having everyone inspect that process in real-time -- 
this is called a fishbowl) is not practical.  Having them inspect it 
post hoc is, at best, inefficient.

My own view is that the only way to make sure that a venue is acceptable 
to the community is to publish a list of candidate venues, as early as 
possible, and let the community debate any concerns it might have.

We already have a repertoire of acceptable venues.  IMO, we therefore 
can afford to be quite cavalier about rejecting new venues.


d/
-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net