Re: [Iasa20] draft-haberman-iasa20dt-recs-00.txt

Stephen Farrell <stephen.farrell@cs.tcd.ie> Tue, 11 July 2017 20:07 UTC

Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: iasa20@ietfa.amsl.com
Delivered-To: iasa20@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A537D1317BC for <iasa20@ietfa.amsl.com>; Tue, 11 Jul 2017 13:07:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.301
X-Spam-Level:
X-Spam-Status: No, score=-4.301 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.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 K1BtPlvMPIm3 for <iasa20@ietfa.amsl.com>; Tue, 11 Jul 2017 13:07:08 -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 98D16126DEE for <iasa20@ietf.org>; Tue, 11 Jul 2017 13:07:08 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 84793BECA; Tue, 11 Jul 2017 21:07:06 +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 6XZnzRpGPPQu; Tue, 11 Jul 2017 21:07:05 +0100 (IST)
Received: from [10.244.2.100] (95-45-153-252-dynamic.agg2.phb.bdt-fng.eircom.net [95.45.153.252]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 2DBE3BEC6; Tue, 11 Jul 2017 21:07:05 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; s=mail; t=1499803625; bh=gbX6pYOtlCXKnADyi01kfY6TKRwF6V0mTqi2Ub4Qlvo=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=PvIxUKlHdWgMvfZTqQ1x2u0POouGMOA6qyZZolyI+IE3hAjIaPUyshlpI4E1JFH9c IT6nic7CoZ7VKaK6XzW8mwl05YdP9RN1MC5i7oYFFfY6hSXcXjb8lH3W+2BpNbceBn AcS5+3NQe2ZQudQRVmGwM3Cn1SWizAPtQNEdUC7E=
To: Joseph Lorenzo Hall <joe@cdt.org>
Cc: "iasa20@ietf.org" <iasa20@ietf.org>
References: <CABtrr-VtbzvTuBxV1y8910m8zPNi53CWVKd9NGpvAfprwc8iEA@mail.gmail.com> <4f2cced5-be6c-0a9d-9d72-e559dccdd90f@cs.tcd.ie> <CABtrr-VCisPwwBLfTjTczQBn8gnvkKqqh-r7agqq+smvKsxgZQ@mail.gmail.com>
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Openpgp: id=D66EA7906F0B897FB2E97D582F3C8736805F8DA2; url=
Message-ID: <a63917be-2af6-43b1-159f-1173aad9d9a2@cs.tcd.ie>
Date: Tue, 11 Jul 2017 21:07:04 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <CABtrr-VCisPwwBLfTjTczQBn8gnvkKqqh-r7agqq+smvKsxgZQ@mail.gmail.com>
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="wsAKPxRkfKCNphcX2Dgv4SsvVTNoTX5cw"
Archived-At: <https://mailarchive.ietf.org/arch/msg/iasa20/bmqQ74ecgEYeV--DQOqWeOtWgR4>
Subject: Re: [Iasa20] draft-haberman-iasa20dt-recs-00.txt
X-BeenThere: iasa20@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Discussions relating to reorganising the IETF administrative structures in the so called “IASA 2.0” project. <iasa20.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/iasa20>, <mailto:iasa20-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/iasa20/>
List-Post: <mailto:iasa20@ietf.org>
List-Help: <mailto:iasa20-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/iasa20>, <mailto:iasa20-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Jul 2017 20:07:11 -0000


On 11/07/17 20:58, Joseph Lorenzo Hall wrote:
> On Sun, Jul 9, 2017 at 4:51 PM, Stephen Farrell
> <stephen.farrell@cs.tcd.ie> wrote:
>>
>> - IASA++ seems the obviously right option to me.
>>   The other two structures have either a "pro" or
>>   a "con" (depending on one's opinion) which is
>>   that the IETF becomes an incorporated entity.
>>   I think the effort to reach consensus on that
>>   topic could de-rail the iasa2 work and we'd risk
>>   losing the increased transparency etc. we want to
>>   get. So that'd just leave IASA++ as being the
>>   only feasible option.
> 
> 
> Hi Stephen!
> 
> Can you say a bit more why the two more legal separation/incorporation
> options are obviously not right to you?
> 
> The reason I ask is that we consciously tried to bound the solution
> space and having an enhanced status quo, some of the benefits of legal
> separation, and then full fledged legal separation seemed like the
> right way to do that.
> 
> If we are missing any gleans on the IASA++ options, it would be great
> to get that into list discussion if you are game. Thanks as always for
> wonderful feedback.

You're too nice:-)

As I kinda said in response to Jari, I fear that the
changes I'd most like to see (transparency++) would
get lost in the noise of all the added overhead of
the larger organisational changes.

I guess that's based on seeing how horrible the IANA
transition was - such a simple change required such
a huge effort. Of course, iasa/2 is much more IETF
internal, but I'd still fear that a lot of the same
cruft would accrue.

Cheers,
S.


> 
> best, Joe
>