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

Stephen Farrell <stephen.farrell@cs.tcd.ie> Sun, 09 July 2017 20:52 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 D492412EC18 for <iasa20@ietfa.amsl.com>; Sun, 9 Jul 2017 13:52:04 -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 BYpKaHhrrwlu for <iasa20@ietfa.amsl.com>; Sun, 9 Jul 2017 13:52:02 -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 2A9CB12F280 for <iasa20@ietf.org>; Sun, 9 Jul 2017 13:52:01 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id B3382BE55; Sun, 9 Jul 2017 21:51:59 +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 eIHATVJNjQu5; Sun, 9 Jul 2017 21:51:55 +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 5B31FBE53; Sun, 9 Jul 2017 21:51:55 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; s=mail; t=1499633515; bh=F6A1mnQriFuAX3yWWyKswGemzU9our3k1Oc9bwaWS0M=; h=Subject:To:References:From:Date:In-Reply-To:From; b=n2VSC4W2tfZroJ9B1574p3jom9HpoW2DjFPsIpC7FUkBDB0WM7aSMAyfriaATaA5w D3fpsbh36RvksPkDnCIZ2MM5X5nn7ffEdPna6E32FcdYRah4ePhE+GRzses3WgdctB HMNKTdn8HjZJ0cxx4Y/XrB9FxKcSq2RDKFBAsIdY=
To: Joseph Lorenzo Hall <joe@cdt.org>, "iasa20@ietf.org" <iasa20@ietf.org>
References: <CABtrr-VtbzvTuBxV1y8910m8zPNi53CWVKd9NGpvAfprwc8iEA@mail.gmail.com>
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Openpgp: id=D66EA7906F0B897FB2E97D582F3C8736805F8DA2; url=
Message-ID: <4f2cced5-be6c-0a9d-9d72-e559dccdd90f@cs.tcd.ie>
Date: Sun, 09 Jul 2017 21:51:51 +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-VtbzvTuBxV1y8910m8zPNi53CWVKd9NGpvAfprwc8iEA@mail.gmail.com>
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="qxpnAVfaS8WSU91LHdugaMcuTDiHuWbrf"
Archived-At: <https://mailarchive.ietf.org/arch/msg/iasa20/PcwNC-Vc5CtFWMNsAXecXX1ViEg>
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: Sun, 09 Jul 2017 20:52:05 -0000

Thanks for the DT's efforts on this.

I guess I understand how the DT got there, but I'm a bit
disappointed that so far, we only seem to have addressed
the "should the IETF incorporate" aspect of the iasa2
work.

Anyway, my initial take on the draft is:

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

- I didn't find section 6 clear or convincing but
  it's also hard to see how one might document
  such an analysis at this point. Maybe when I
  read it more closely or we see a presentation in
  Prague, it'll be clearer, but as of now, the DT's
  analysis isn't that clear to me. It could be that
  I change my opinion about IASA++ if/when I do
  understand the DT's analysis better, but I'd be
  surprised if that were the case.

Cheers,
S.

On 07/07/17 17:29, Joseph Lorenzo Hall wrote:
> Greetings IASA 2.0 enthusiasts!
> 
> The design team has just published a preliminary -00 draft in terms of
> analysis of three options. Find it below.
> 
> We will have a one-hour meeting at the beginning of the IASA 2.0 slot
> (3:50-4:50 local time) on Tuesday of IETF week. Jon Peterson will chair and
> send along an agenda. (We are reserving the second hour of that slot for an
> in-person design team meeting.)
> 
> Note that this is very early work, but far along enough that we would like
> to focus the discussion during the meeting as follows:
> 
> Feedback on the set of identified possible paths forward or options is the key
> question. Are any potential missed options? Also, feedback on the implications
> of options being considered would be welcome.
> 
> Best wishes, Joe
> 
> ---------- Forwarded message ---------
> From: <internet-drafts@ietf.org>
> Date: Fri, Jul 7, 2017 at 12:21
> Subject: New Version Notification for draft-haberman-iasa20dt-recs-00.txt
> To: Jari Arkko <jari.arkko@piuha.net>, Leslie Daigle <
> ldaigle@thinkingcat.com>, Brian Haberman <brian@innovationslab.net>, Jason
> Livingood <Jason_Livingood@comcast.com>, Eric Rescorla <ekr@rtfm.com>,
> Joseph Lorenzo Hall <joe@cdt.org>
> 
> 
> 
> A new version of I-D, draft-haberman-iasa20dt-recs-00.txt
> has been successfully submitted by Cindy Morgan and posted to the
> IETF repository.
> 
> Name:           draft-haberman-iasa20dt-recs
> Revision:       00
> Title:          IASA 2.0 Design Team Recommendations
> Document date:  2017-07-07
> Group:          Individual Submission
> Pages:          23
> URL:
> https://www.ietf.org/internet-drafts/draft-haberman-iasa20dt-recs-00.txt
> Status:
> https://datatracker.ietf.org/doc/draft-haberman-iasa20dt-recs/
> Htmlized:       https://tools.ietf.org/html/draft-haberman-iasa20dt-recs-00
> Htmlized:
> https://datatracker.ietf.org/doc/html/draft-haberman-iasa20dt-recs-00
> 
> 
> Abstract:
>    The arrangements relating to administrative support for the IETF were
>    created more than ten years ago.  Since then, there has been
>    considerable change in the tasks and in our own expectations.  The
>    IETF community has discussed these changes and the problems they
>    cause.  The community has some sense of the properties they expect
>    from future arrangements, including structural and organizational
>    changes, changes to volunteer and staff personnel resources, and
>    transparency changes.
> 
>    This document is a product of a design team, focused on providing
>    additional information to the community about solution options, as
>    well as supporting analysis of the implications of those options.  To
>    be clear, the community is responsible for adopting any
>    recommendations or making any final decisions.
> 
> 
> 
> 
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
> 
> The IETF Secretariat
> 
> 
> 
> _______________________________________________
> iasa20 mailing list
> iasa20@ietf.org
> https://www.ietf.org/mailman/listinfo/iasa20
>