Re: [Diversity] Concerns about Singapore

Stephen Farrell <stephen.farrell@cs.tcd.ie> Mon, 11 April 2016 06:33 UTC

Return-Path: <stephen.farrell@cs.tcd.ie>
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 44C8112E69A for <diversity@ietfa.amsl.com>; Sun, 10 Apr 2016 23:33:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.297
X-Spam-Level:
X-Spam-Status: No, score=-5.297 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.996, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cs.tcd.ie
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 nRP5k4_J0i8o for <diversity@ietfa.amsl.com>; Sun, 10 Apr 2016 23:33:50 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4A45212E694 for <diversity@ietf.org>; Sun, 10 Apr 2016 23:33:49 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 088C0BDF9; Mon, 11 Apr 2016 07:33:47 +0100 (IST)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id p2OFSnwSQuhK; Mon, 11 Apr 2016 07:33:45 +0100 (IST)
Received: from [10.87.49.100] (unknown [86.46.23.241]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 0316EBDCC; Mon, 11 Apr 2016 07:33:44 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; s=mail; t=1460356425; bh=1rwm5p5FxHklrKeH/UmLxW06KnQ5x+2K1WQKA3iwQM4=; h=Subject:To:References:Cc:From:Date:In-Reply-To:From; b=Da8FpDBQYgzAkHjZ7s2VRHkpWvwjJ/VYDFHhYMF3UrqSL/5smvIkIkV4/e82eS+0a JeJwMX9iq+7VOw2Q7wEQwCwAgkYP+OY/ZzIpK7r6B7zVWB1DY74+OdvAyolfEHWbgH 2tTujR9FK7D3FX9T2RYWtYMkBUFzBelNhm1FWCRg=
To: dcrocker@bbiw.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> <570A9419.5090009@dcrocker.net> <570AA89F.5050302@cs.tcd.ie> <570AAE2E.9060000@dcrocker.net> <570ACAC9.5070008@cs.tcd.ie> <570B15DA.4010302@dcrocker.net>
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Openpgp: id=D66EA7906F0B897FB2E97D582F3C8736805F8DA2; url=
Message-ID: <570B4546.7020907@cs.tcd.ie>
Date: Mon, 11 Apr 2016 07:33:42 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0
MIME-Version: 1.0
In-Reply-To: <570B15DA.4010302@dcrocker.net>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha-256"; boundary="------------ms000909070601040608050008"
Archived-At: <http://mailarchive.ietf.org/arch/msg/diversity/5E-Pumd6NUzcGzIk1LD71WRBy9M>
Cc: diversity@ietf.org
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: Mon, 11 Apr 2016 06:33:53 -0000


On 11/04/16 04:11, Dave Crocker wrote:
> 
> More importantly there is nothing about that effort that needs to be in
> the critical path of responding directly to the very specific problem
> that surfaced last week.  And putting it into the critical path almost
> certainly means that responding to that specific problem will be delayed.

I agree with that.

If the IAOC were taking the path I'd like to see 'em take, they'd
just announce that they plan to move to default-open with a list of
exceptions to be published/discussed after they're done sorting out
the issues related to IETF-100. I would hope that ought not affect
their handling of IETF-100. If they even said that they planned to
revisit their level of open-ness more generally after sorting out
IETF-100, that'd help.

At no time did I make any statement about critical paths, but it is
fair to ask about that. It seems to be not fair to assert that I was
"putting it into the critical path" as you've done, but then again
perhaps part of the magical thinking you detected was me thinking
things I'd not said:-)

S.