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

Ted Hardie <ted.ietf@gmail.com> Tue, 09 May 2017 23:08 UTC

Return-Path: <ted.ietf@gmail.com>
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 9F26112711E for <iasa20@ietfa.amsl.com>; Tue, 9 May 2017 16:08:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 VUqV2A0W_j6d for <iasa20@ietfa.amsl.com>; Tue, 9 May 2017 16:08:41 -0700 (PDT)
Received: from mail-qk0-x235.google.com (mail-qk0-x235.google.com [IPv6:2607:f8b0:400d:c09::235]) (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 15F43124BFA for <iasa20@ietf.org>; Tue, 9 May 2017 16:08:41 -0700 (PDT)
Received: by mail-qk0-x235.google.com with SMTP id y201so14567618qka.0 for <iasa20@ietf.org>; Tue, 09 May 2017 16:08:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=TPgU5VDZ0Aq/iE2LzlBRpiA3iuDzOHIZcZjSIsn6+KE=; b=QMNlN/fZRrDLvoTtQebHe7scU6F4VDJE2D5gruKoMuOH9ek+dQoWlvHI5iomY90w5O yX4F20HG+5vyii2cPYCpiVNG9KG8yVhcsCr4Q59y/uCH2tdQVW28GQzv+HSgg5lj/+TP BF/P6nYuNZNpY2TVE9ADK/ISLydieugSvE6W12SE+QyNOzGM8jevqsxgWS83Dd9A51Wn xnwM2dNMDEME8OxLfOSovkOFCqKyNwwkzjp1RfFvobtzPztJdk77S/KDxY43xKU8KjaX l+2u++PVY1U+0Z7ULLcO8Omwto1OROPBmHus5KhXcUs+2herdSp2h28trMw8lU5Tfx9s oUnw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=TPgU5VDZ0Aq/iE2LzlBRpiA3iuDzOHIZcZjSIsn6+KE=; b=OUlNMnm9fU09cXN1JUDgFNJ2iDQBrpcyjG8xD+jqQhlZfBKKmVWb4gU+lKvBId3hEg +pdsj8eWlhrAoQ5ojXPBds/mymhX/y9FxsmD5pV2q37P3LjjmFoUY0t0bjCBy6ChNAxx gqubV+noHvbfPLXvWV2CzQLLoslylqy700JXiAZv2GVvS2j/tdNGQ1dTgsGZSk8bidUR uHyEf6pS1FyRBKOY17B5XuoS39zriKVmyF6U330BIN8mYW3CmGp/wIPDupbC7XbNwWr5 RLuPCtP/nd7NwNkrXqf83SNR+YqWjH6/AHPwvFOa05k5HEae3xCm+G+XmBmYahkrCU9m UvAg==
X-Gm-Message-State: AODbwcAW16foZYU1pVjn6Z+oTGa+x/R/JHk0ZqR9NSU3uQXLlf0v5lpS MRR9R5AafOyd0NOVJW4Rof1Rtd/6tw==
X-Received: by 10.55.72.143 with SMTP id v137mr2667421qka.222.1494371320263; Tue, 09 May 2017 16:08:40 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.237.63.45 with HTTP; Tue, 9 May 2017 16:08:09 -0700 (PDT)
In-Reply-To: <64B42F59-586B-4A03-BA87-23BB01C1A021@cooperw.in>
References: <76E736E8-E7F5-45D4-ABA3-3E1766450865@cooperw.in> <CA+9kkMBiB4v9aAdy6_C+YqhDp-gCJwxCkqTvKWL2MWrYtkGH=Q@mail.gmail.com> <64B42F59-586B-4A03-BA87-23BB01C1A021@cooperw.in>
From: Ted Hardie <ted.ietf@gmail.com>
Date: Tue, 09 May 2017 16:08:09 -0700
Message-ID: <CA+9kkMCxrdp=dnaJyyevkpTEo1v6kRV-L8OAM4E7xQeq5Nuu=g@mail.gmail.com>
To: Alissa Cooper <alissa@cooperw.in>
Cc: iasa20@ietf.org
Content-Type: multipart/alternative; boundary="001a114a8230b4fb50054f1f6f44"
Archived-At: <https://mailarchive.ietf.org/arch/msg/iasa20/gF_nZWke7huCzRrPYJ4tda0mxhA>
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: Tue, 09 May 2017 23:08:42 -0000

Howdy,

On Tue, May 9, 2017 at 3:50 PM, Alissa Cooper <alissa@cooperw.in> wrote:

> Hi Ted,
>
> Good questions. For a topic like this, I believe it’s premature to charter
> a working group. The problem list is well defined, but the space of
> considerations and solutions related to solving those problems is both very
> wide and potentially includes a number of topics that are outside the scope
> of your typical IETF working group (e.g., budget, personnel, legal issues).
> I’d like the design team to spend some time taking all of this under
> consideration as a means to help structure the next step of the community
> discussion around a focused approach/solution set.
>
> Ah, I see that I thoroughly misunderstood where you were; looking at the
community discussion you mentioned in IETF 99, I thought you meant
"community discussion to select among alternatives", when you said that the
design team would recommend solutions and the community would discuss next
steps.  I see now that this is a set of recommendations for how to proceed
from there.



> That next step might be writing a WG charter. Or it might be more plenary
> community discussion, or processing a document or two as AD-sponsored, or
> following some other process. My understanding is that IASA itself was
> created without a WG being formed, so while in my head it seems like a WG
> might be useful here down the line, I don’t want to presume at this point
> that that is the only option.
>

> Also, I’m a big fan of tightly focused WG charters, and I think we need
> this interim step if we do want to be able to write one, including being
> able to define precisely what the work of a potential WG would be covering
> and what its deliverables would be.
>
> The use of a design team was included in Jari’s original project plan, and
> I agree with him that it’s a useful tool. https://www.ietf.org/blo
> g/2016/11/proposed-project-ietf-administrative-support-2-0/
>

My mistake here was thinking you were at the design team mentioned in stage
4, not the one mentioned in stage 2; my apologies for the confusion.  I
note that his timeline also presumes that there is a working group set up
in stage 2, but I agree with you that some recommendations from a design
team might not require one ("do nothing" is a mighty short charter).

Thanks for the quick clarification,

Ted