[Iasa20] Call for volunteers: IASA 2.0 design team

Alissa Cooper <alissa@cooperw.in> Tue, 09 May 2017 20:56 UTC

Return-Path: <alissa@cooperw.in>
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 6743412EB2A for <iasa20@ietfa.amsl.com>; Tue, 9 May 2017 13:56:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.021
X-Spam-Level:
X-Spam-Status: No, score=-0.021 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=cooperw.in header.b=GG/UODNe; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=T3It9rgo
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 7hLDtch2dq8k for <iasa20@ietfa.amsl.com>; Tue, 9 May 2017 13:56:53 -0700 (PDT)
Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0C94C1296B3 for <iasa20@ietf.org>; Tue, 9 May 2017 13:56:53 -0700 (PDT)
Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 1BC3920CA5 for <iasa20@ietf.org>; Tue, 9 May 2017 16:56:52 -0400 (EDT)
Received: from frontend1 ([10.202.2.160]) by compute7.internal (MEProxy); Tue, 09 May 2017 16:56:52 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cooperw.in; h= content-transfer-encoding:content-type:date:from:message-id :mime-version:subject:to:x-me-sender:x-me-sender:x-sasl-enc :x-sasl-enc; s=fm1; bh=5ysGIamw/Rd8Q7vGy78wimsqPH+dfLVPnCYlLTPSc sM=; b=GG/UODNeBbZFhhbWsghCTRHQzY/jKsFgHtUtNaLi4+T2EbwIZGFIC+MM8 IocJJOlOawNOtu5hEJwZsz89VFLiwQZtqM6UJwToespAfTj2uJhEGgdZZtET5dAA OikkKINC/2hHVItODGSrILjpNvL0eqDpkookPpFa4SZYTh4LglInMtDZQ+uw0DeJ fIR8QVKHPM3BYiDyQ82P7L9QrPvj5eBW4A8a6Dwh9HFvV6m2wO+LKDDBtJ0aKeDP 9rzUASoTEbG2Wl6seTmuW6F8gALUdgL1AwyDlO7qSu14Au0J5g5N9PaW9fUv54tg 6I0vP3+x+6SN46T7EoApT5pyRiH5g==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:message-id:mime-version:subject:to:x-me-sender :x-me-sender:x-sasl-enc:x-sasl-enc; s=fm1; bh=5ysGIamw/Rd8Q7vGy7 8wimsqPH+dfLVPnCYlLTPScsM=; b=T3It9rgohow0RNAD+JAX/AtDnZhpsDVpoP xQM6W5V3DFyK5bmoMt3XrI4txCGUevRbGRvHjmp3sKHKv4SwOj29Dt4t5MasPw56 QBS4IGWFryWNzCO6nB77agwhi8AFW06KQWFJtbWAeo8MQHnnKQEpWhMFna4/4zAR 6t14worFf2x05ZD/haRoIAdXT6yEdMU1EiWmQ5UDcyY2MqGt/hz4TOEMEBcAJGbf tyglhT7B+PgW6Bb2gY1kPeHiKDRAisFSOVPguGvdv7SYeDiI0wBmDaBJmdNLimwr h1SGQLfU56FPqY062iMh4zVVP0gguiHr6Mmg1HupjdgHgfv0KYNA==
X-ME-Sender: <xms:FC0SWTrQw2GUL09qUmkf1HepTYNvDbKCAjtVzQmXTs3llZjDraKXUA>
X-Sasl-enc: aScPl/Z4Z2IRl4pcEoD/NiXYTgmI6n+BdrAfb9VZUG/N 1494363411
Received: from [10.24.41.93] (unknown [128.107.241.167]) by mail.messagingengine.com (Postfix) with ESMTPA id B391D7E876 for <iasa20@ietf.org>; Tue, 9 May 2017 16:56:51 -0400 (EDT)
From: Alissa Cooper <alissa@cooperw.in>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Message-Id: <76E736E8-E7F5-45D4-ABA3-3E1766450865@cooperw.in>
Date: Tue, 09 May 2017 13:56:50 -0700
To: iasa20@ietf.org
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/iasa20/5gzzFAJcmLsJq25SVZcXif29_08>
Subject: [Iasa20] Call for volunteers: IASA 2.0 design team
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, 09 May 2017 20:56:54 -0000

I think the community is at a point in the IASA 2.0 discussions where we are ready to form a design team to start evaluating options for the path forward. We have a good articulation of the set of problems we are facing in draft-hall-iasa20-workshops-report and draft-daigle-iasa-retrospective. We have some sense of the outcome properties that people are looking for here, based on list discussion. So I'd like to task a design team to go examine potential solutions to the problem set that fit the outcome properties, and come back to the community with recommended solutions. The scope of the solutions to be explored would include:

- Structural and organizational changes, both externally (with ISOC and contractors) and internally (within the IAOC and subcommittees)
- Changes to personnel resources, both volunteer and paid
- Transparency changes

For now, changes to the funding model would be out of scope to the extent they fall outside the categories above, although the design team's work should be informed by the prior discussion of funding challenges. The IAOC sponsorship committee is currently in the process of getting off the ground and I think it would make sense to have some of that discussion start there before merging it back in with the administrative discussion. And I think the administrative problems are articulated well enough for a team to get going with that focus.

My hope is that the design team would have something (even an interim something) ready for community discussion around the time frame of IETF 99. From there we can figure out what a logical next step would be.

If you’re interested in volunteering and willing to dedicate time to this work over the next several months, please send me email off-list by May 17, 2017 and I’ll sort out the team composition. 

Thanks,
Alissa