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

Joseph Lorenzo Hall <joe@cdt.org> Fri, 07 July 2017 16:30 UTC

Return-Path: <jhall@cdt.org>
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 2FCD0131665 for <iasa20@ietfa.amsl.com>; Fri, 7 Jul 2017 09:30:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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=cdt.org
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 6earOiO_7Z0h for <iasa20@ietfa.amsl.com>; Fri, 7 Jul 2017 09:30:05 -0700 (PDT)
Received: from mail-ua0-x232.google.com (mail-ua0-x232.google.com [IPv6:2607:f8b0:400c:c08::232]) (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 B68CA131613 for <iasa20@ietf.org>; Fri, 7 Jul 2017 09:30:04 -0700 (PDT)
Received: by mail-ua0-x232.google.com with SMTP id w19so23428296uac.0 for <iasa20@ietf.org>; Fri, 07 Jul 2017 09:30:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cdt.org; s=google; h=mime-version:from:date:message-id:subject:to; bh=z5qqBQ3ZFK31eDxfBku09Y9SMWuFcGCsvXEJTyK7gmc=; b=Bh8lSjRstXDokubj69WrOLu3O6wWVlxb6MezAeHCKDxRoyF4dcAS9jGF2WFqJM09n0 XyYHSVnDbdIHZP5srsHGI4G51w8kudL5SE70R6tpHq4eAZmm9Xv9y0S5kbhDuQ2Gxz14 iYJBgzDtDECQB3IDi6TQEzHcpqSdG6SYawiKY=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=z5qqBQ3ZFK31eDxfBku09Y9SMWuFcGCsvXEJTyK7gmc=; b=LnXT4TN4wRKxJjYufVM5n4byDq+cqh9fav27qUohGlvn23SjUCRDLKqdmhHCJ7cX3U c9PDPEUx0iFhzoDTwlhmKtNYhwM5Xl5oh+8lyEE/iWLHk18UJ7M9TYty09ogPhiHyBHy mqfSYdefrMvY2yXEZVs1Kyu8Smy4PbRDh7OhwGlx5GqoJjEkUuTG8HGHzepoBA7rjwCZ FhbLb+TocWcylFN5Fxlcj6XGiDZFOzTWqnTA+1qT07aT0hUgszrPwYqkZjtGWYaaG1KE 0acbHQEcfu9/2/Hqs1rHIVGd3a3G5EivQfKRujgvDUs2nYyPTGwByrFuZJbVbb95dKTK JqAQ==
X-Gm-Message-State: AIVw1111P98Hpu/9+JTuL52DwJ/rq34z/TzjbN/EWEv0B7u2ZRvUQQIX jxvWuvU2XjPeeM0YlKXwyIHq+XxWtPKKPVg=
X-Received: by 10.176.65.41 with SMTP id j38mr1069627uad.112.1499445003509; Fri, 07 Jul 2017 09:30:03 -0700 (PDT)
MIME-Version: 1.0
From: Joseph Lorenzo Hall <joe@cdt.org>
Date: Fri, 07 Jul 2017 16:29:53 +0000
Message-ID: <CABtrr-VtbzvTuBxV1y8910m8zPNi53CWVKd9NGpvAfprwc8iEA@mail.gmail.com>
To: "iasa20@ietf.org" <iasa20@ietf.org>
Content-Type: multipart/alternative; boundary="94eb2c123592cb7ab60553bcbef4"
Archived-At: <https://mailarchive.ietf.org/arch/msg/iasa20/co2ebgKVhhtGju795jP-Ds6kIsk>
Subject: [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: Fri, 07 Jul 2017 16:30:07 -0000

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

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