Re: [Diversity] Concerns about Singapore

Vinayak Hegde <vinayakh@gmail.com> Sun, 10 April 2016 23:40 UTC

Return-Path: <vinayakh@gmail.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 D83AD12D719 for <diversity@ietfa.amsl.com>; Sun, 10 Apr 2016 16:40:43 -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 7jBhCLPuuC5Z for <diversity@ietfa.amsl.com>; Sun, 10 Apr 2016 16:40:42 -0700 (PDT)
Received: from mail-wm0-x22e.google.com (mail-wm0-x22e.google.com [IPv6:2a00:1450:400c:c09::22e]) (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 3940312D1B1 for <diversity@ietf.org>; Sun, 10 Apr 2016 16:40:42 -0700 (PDT)
Received: by mail-wm0-x22e.google.com with SMTP id 191so67139813wmq.0 for <diversity@ietf.org>; Sun, 10 Apr 2016 16:40:42 -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 :cc; bh=IsACpxx9lVvpn/PA+DZi46hO8XdC1iohOtj2E9Kvysg=; b=jD8UoGwMDS5kbA8uYyDyl2bD2QTSHpnCF3heyIClCZtJI8Ocjv1XlWKpz+ho3wATWK PIFTIqDUX703Db0aSD5gi/Q24TfF/n9sz7Ul93tUU7ruMvak9M85MESxJvtESBUfJaES ocHoJUXAfIYj+NaLU4d0nP44NV8yV3/HvU75T+wqQtVOC/EhEJ0oq/dWk/tV5j7ciZLz E1jyY66FgcKjJnkJ6KVfI24vgy8LQGbkFKp1fcyIJAPtQJLVSmqNzc/A84NzFcCkDg3T xODcXLL6luRMgprBjDGPsTZ4AQpIAU09gWvMD9M/qUeXd9KDDPNDgqdU/eAEORWad3us 5aGQ==
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:cc; bh=IsACpxx9lVvpn/PA+DZi46hO8XdC1iohOtj2E9Kvysg=; b=O/QsfJiuc4Y9wE19T/dv1ReLJ9mvgvGQEsKSHuNzbOQuGkQM4t51U0SztgvNt5ezxp u75u3GOG/7Vj16ABJwnf4cTGz3NRQlvY9ZkJUPnO3HV4S5sv/q2ppUgojUq6b0bYl05W Dbx1erS77vCCCGq0ruopYxPlBw/oRvxYd0+n7q9DzqFQ4Ai3LCXCNM29sCC6hJ/DFutl 6WBfHaF8KVpqcXHlmDqFNF5VeYoD07MRgMH1iiq5stSY3nNEX0dYo2CFFHFzmmXtIZWo +8WLnmczcyF4X9cVy80GSiQN3FM5/qxl4t6dfw7J4VJMnqbD4c1ALg74raIK2dTPahve v7/A==
X-Gm-Message-State: AD7BkJKLotm2wRhuXHNxRl9srF1CB+mBbo7LkPGlW9Ai5dENooKqTGAI9NIKT+nT21MC+hHg3VFzAB8R4jCPYg==
MIME-Version: 1.0
X-Received: by 10.194.192.106 with SMTP id hf10mr19689541wjc.134.1460331640660; Sun, 10 Apr 2016 16:40:40 -0700 (PDT)
Received: by 10.194.133.99 with HTTP; Sun, 10 Apr 2016 16:40:40 -0700 (PDT)
In-Reply-To: <570A9419.5090009@dcrocker.net>
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> <570A9419.5090009@dcrocker.net>
Date: Mon, 11 Apr 2016 05:10:40 +0530
Message-ID: <CAKe6YvOMb+AHL6y7HG_Hp1P9aJQ-QAbJ=RcapwsEe3PLn9m-BQ@mail.gmail.com>
From: Vinayak Hegde <vinayakh@gmail.com>
To: Dave Crocker <dcrocker@bbiw.net>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <http://mailarchive.ietf.org/arch/msg/diversity/XesU90HlDrPG4fBBxvEJ8pSUsxM>
Cc: Andrew Allen <aallen@blackberry.com>, Nalini Elkins <nalini.elkins@insidethestack.com>, Yoav Nir <ynir.ietf@gmail.com>, "diversity@ietf.org" <diversity@ietf.org>, SM <sm@resistor.net>, 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
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 23:40:44 -0000

On Sun, Apr 10, 2016 at 11:27 PM, Dave Crocker <dhc@dcrocker.net> wrote:
> 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.

+100

> '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.

+100

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

I am not so sure about being cavalier about rejecting new venues. Especially
since the US internet population is now dwarfed by other countries and
regions like
LATAM, China and India. The meeting venues should reflect that atleast fairly
(if not in representative fashion).

Thanks
Vinayak