Re: [Iasa20] Call for volunteers: IASA 2.0 design team

Alissa Cooper <alissa@cooperw.in> Fri, 26 May 2017 00:42 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 D1116129B8D for <iasa20@ietfa.amsl.com>; Thu, 25 May 2017 17:42:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.821
X-Spam-Level:
X-Spam-Status: No, score=-0.821 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, 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, URIBL_BLOCKED=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=LUC5Sj9d; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=Rv1FDdb8
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 dWblCDDCX4Gs for <iasa20@ietfa.amsl.com>; Thu, 25 May 2017 17:42:21 -0700 (PDT)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 30539129B74 for <iasa20@ietf.org>; Thu, 25 May 2017 17:42:21 -0700 (PDT)
Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 98EA42094F for <iasa20@ietf.org>; Thu, 25 May 2017 20:42:20 -0400 (EDT)
Received: from frontend1 ([10.202.2.160]) by compute7.internal (MEProxy); Thu, 25 May 2017 20:42:20 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cooperw.in; h= content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc:x-sasl-enc; s=fm1; bh=6CAURkYp13B7CFN/As WA5cZ5RH0PW3kSF/X+T/M1On0=; b=LUC5Sj9dWNF0VX2X9NpqHv+Sf4ZCrDkquy /ah+sO7Dq/ybGJ8y+XJm1t0Y9vNnwq6wfcwJLzBgwbU7udbDRpi6R/nQlyFSfdI3 QWGoOF3PhYB+GKHMmUM7JJncfSOn7qJd9fPYS0/3SsJOXDQMBxmHPS22j7Op+SUh CPmdxWpm/VAVdSy7pYNF4b9j+jMz7JEIt8Df+oXrFgAaIQ6wuFKxKdIoHiBpR4Ot LC8vEVMQdywfO9l7prJXj8LUSoiqx4fnNrthaLMJ9OsjWhN5kFu51EkPMH1ivuMw P3OxLuYsatgh8yZJsTl29AeO+SblOINOhjLhv+AoESCfbMLQoxjg==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc:x-sasl-enc; s= fm1; bh=6CAURkYp13B7CFN/AsWA5cZ5RH0PW3kSF/X+T/M1On0=; b=Rv1FDdb8 +Fv9uOiepl68G3qrSzHXfKN4e/PKUKeSNv5BYl2eR7EW2xMmxNdCb5o1FV+Z1LbT gzyPw5h9s+56W1MdKAia8oV96XuXv5lqi6kow09+pCGg66s0cDMVUn8jiojEQkGD yhf2x1k9O4VGz8yhMgw0iJDXKsK752YH601GJotX5iq7OHwpYn0qnXzTqQIfQMAo bHBZ+pQIN+9E7TH8DsS22cvt13I5nMxupuhUncMMeT6Ecz8I2BVewdGKs23ouvKD GuLHhb8yPQ0cljPPgqM0jy53TKTJmcVXwq1bpdXtbNJZevUJxABauNNdW8hM+v0X eIfiE+ImZfFxZw==
X-ME-Sender: <xms:7HknWW4DsMxFYpNOwQZqw8lBC0vcAR2FPxWzlyxw0bkoWuuWkxufVA>
X-Sasl-enc: SHUHstsSd7j8bERMiLmXLxRU9oVZi+I/fBmF4iiwlevw 1495759340
Received: from sjc-alcoop-8813.cisco.com (unknown [128.107.241.164]) by mail.messagingengine.com (Postfix) with ESMTPA id 14A2A7E84B for <iasa20@ietf.org>; Thu, 25 May 2017 20:42:19 -0400 (EDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Alissa Cooper <alissa@cooperw.in>
In-Reply-To: <76E736E8-E7F5-45D4-ABA3-3E1766450865@cooperw.in>
Date: Thu, 25 May 2017 20:42:18 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <8CBEB49D-6AF6-4469-99B7-8F048F6528CC@cooperw.in>
References: <76E736E8-E7F5-45D4-ABA3-3E1766450865@cooperw.in>
To: iasa20@ietf.org
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/iasa20/cCT7z3mDJtldxGIxMQCphp5qcV8>
Subject: Re: [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: Fri, 26 May 2017 00:42:23 -0000

Many thanks to all those who volunteered to participate on this design team. To keep the group focused and at a somewhat manageable size, I’ve gotten confirmation from the following volunteers to serve on the team:

Brian Haberman
Eric Rescorla
Jari Arkko
Jason Livingood
Joe Hall
Leslie Daigle

They are in the process of getting organized now and I hope/expect they’ll have more info for the community soon about how they plan to work and interface back with this list.

Alissa


> On May 9, 2017, at 4:56 PM, Alissa Cooper <alissa@cooperw.in> wrote:
> 
> 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
> _______________________________________________
> iasa20 mailing list
> iasa20@ietf.org
> https://www.ietf.org/mailman/listinfo/iasa20