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

Hi,

I’ve read the document and in general agree with what is being said. Not really sure about the comparison criteria and how everything has been rated, but I’m sure we will be able to discuss this in the list and the next meeting and have many other inputs.

However, I’m missing some issues, that I think are key:

1) Despite the model chosen (IAOC for IASA++, board of directors for ISOC subsidiary/independent) and in addition to defining how the board/oversight committee is elected, we need to define how the committee members are elected. The actual model “they select the people that they feel more comfortable to work with” is absolutely against the IETF overall spirit and even an insult to all the participants.

2) Accountability of IAOC (or whatever replaces it). We need to make sure that they respond to the community and define strict deadlines for that (I can tell you that I’m still waiting responses from about a couple of years …, which again is an insult to a community member).

3) We also need to specify if anything is not going to be transparent. There is no sense to hide anything from the community, unless is clearly defined upfront.

Regards,
Jordi

-----Mensaje original-----
De: iasa20 <iasa20-bounces@ietf.org> en nombre de Joseph Lorenzo Hall <joe@cdt.org>
Responder a: <joe@cdt.org>
Fecha: viernes, 7 de julio de 2017, 18:29
Para: "iasa20@ietf.org" <iasa20@ietf.org>
Asunto: [Iasa20] draft-haberman-iasa20dt-recs-00.txt

    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 <http://tools.ietf.org>.

    The IETF Secretariat

    -- 

    Joseph Lorenzo Hall
    Chief Technologist, Center for Democracy & Technology [https://www.cdt.org]
    1401 K ST NW STE 200, Washington DC 20005-3497
    e: joe@cdt.org, p: 202.407.8825, pgp: https://josephhall.org/gpg-key
    Fingerprint: 3CA2 8D7B 9F6D DBD3 4B10  1607 5F86 6987 40A9 A871
    _______________________________________________
    iasa20 mailing list
    iasa20@ietf.org
    https://www.ietf.org/mailman/listinfo/iasa20

**********************************************
IPv4 is over
Are you ready for the new Internet ?
http://www.consulintel.es
The IPv6 Company

This electronic message contains information which may be privileged or confidential. The information is intended to be for the use of the individual(s) named above. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, including attached files, is prohibited.