Re: Post-hoc working group chartering
Dave Crocker <dcrocker@bbiw.net> Wed, 22 July 2015 09:18 UTC
Return-Path: <dcrocker@bbiw.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 009D61A1A10 for <ietf@ietfa.amsl.com>; Wed, 22 Jul 2015 02:18:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
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 fdEE03ZIfbcj for <ietf@ietfa.amsl.com>; Wed, 22 Jul 2015 02:18:27 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 525371ACF5E for <ietf@ietf.org>; Wed, 22 Jul 2015 02:18:27 -0700 (PDT)
Received: from [10.0.0.33] (168.208.broadband18.iol.cz [109.81.208.168]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id t6M9INIR022949 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Wed, 22 Jul 2015 02:18:25 -0700
Subject: Re: Post-hoc working group chartering
To: Dave Cridland <dave@cridland.net>
References: <55AF413D.1060102@dcrocker.net> <CAKHUCzy2nXQUXTJDifHxNnZMjGE-QAFE-QeREGvhJMm_Ca3buw@mail.gmail.com>
From: Dave Crocker <dcrocker@bbiw.net>
X-Enigmail-Draft-Status: N1110
Organization: Brandenburg InternetWorking
Message-ID: <55AF5FDF.6040203@bbiw.net>
Date: Wed, 22 Jul 2015 11:18:23 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.1.0
MIME-Version: 1.0
In-Reply-To: <CAKHUCzy2nXQUXTJDifHxNnZMjGE-QAFE-QeREGvhJMm_Ca3buw@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Wed, 22 Jul 2015 02:18:25 -0700 (PDT)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/gq1mFDfcn8KkkmiPfILYV6oaLIM>
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Jul 2015 09:18:29 -0000
Dave, Thanks for the thoughtful response. Comments inline... Meta point: BOFs serve multiple purposes and therefore are appropriate at different times. So the model I'm proposing doesn't cite BOFs explicitly as part of the sequence. That's not to deny their use but rather means "do a BOF whenever it makes sense to do one"... > Firstly, the prerequisites for working group formation under those > rules are going to be based on - essentially - forming a stealth > working It is already reasonably easy to get a non-working group IETF mailing list. I like that and suggest that that should be the usual entry point for nascent wg efforts. So: not stealth and not outside the IETF. > group, which somewhat implies gathering people who know how this > works, and I'm not entirely sure that an external group would figure > this out. Required familiarity with IETF process is a basic and long-standing issue, independent of my proposal. There's been a theory of having one of the co-chairs be IETF-savvy, but that's probably later in the sequence than we need. So I'll trivially suggest that when a non-wg mailing list is created, it should be assigned an IETF-savvy mentor. (This would carry no implication that the mentor would become a co-chair, should the effort get chartered.) > Secondly, just as I-D is the new Proposed, I worry we're in danger > of "left-shifting" our process again, to paraphrase Scott Bradner. I > make Certainly a fair concern, since I share your view on the overly-high bar for Proposed. (And I'm thankful we were, at least, able to make the criteria for full Standard be simpler and more pragmatic.) So, yes, I'm suggesting a higher bar for chartering. But note that I am /not/ suggesting any change in what it takes to get a mailing list. I think that it should be pretty easy, requiring no more than a basic Statement of Purpose and passing a basic 'smell' test with the sponsoring AD. So the basic ability to conduct an Internet technical discussion in the IETF and start doing work would not change. To me, that's the important step. In fact, I claim this /lowers/ the bar for getting work done. Here's my logic: right now, a group has to focus first on getting chartered. That tends to take months. Eventually they get to focus on the work. But with my suggestion, they are expected to focus on the work immediately. One of the current wg efforts /refused/ to pursue substantive technical work prior to chartering. This led to months of problematic technical proposals being circulated, with no effort to deal with the problems. (The problems did get attention, many months later.) With my suggestion, the expectation would be that substantive technical concerns would be addressed immediately. > Thirdly, it's not actually clear to me that there is a problem with > taking on work - and even creating working groups - and then later > dropping it if the supposed interest doesn't materialize. We tend to ignore the economics of unsuccessful or problematic efforts, essentially treating working groups as a cost-free entity. And we frequently produce useless specifications. The reality is that these are extremely expensive. They consume expensive engineer time, scarce management resources, and scarce IETF meeting time. They often also impose an opportunity cost, while the world thinks that something productive is being done about a relevant problem, when in fact progress is not being made. Alternatives are not pursued, based on the mistaken belief that the problem is being worked on. Successful IETF work requires clarity about the topic being pursued, meaningful market need for pursuing it, and people willing to work on it. Currently, the IETF criteria for chartering a working group pretends to approximate measuring these, but in reality does not. Rather it takes only the vaguest expressions of interest as sufficient. Expressing interest is not the same as doing work. I am suggesting fixing this disconnect by requiring at least substantive, sustained demonstrations of interest in the topic and an ability to make progress with it. d/ -- Dave Crocker Brandenburg InternetWorking bbiw.net
- Re: Post-hoc working group chartering Dave Crocker
- Post-hoc working group chartering Dave Crocker
- Re: Post-hoc working group chartering Dave Cridland
- Re: Post-hoc working group chartering Eliot Lear
- Re: Post-hoc working group chartering Eggert, Lars
- Re: Post-hoc working group chartering Ofer Inbar
- Re: Post-hoc working group chartering Eric Burger
- Re: Post-hoc working group chartering John C Klensin
- Re: Post-hoc working group chartering Melinda Shore
- Re: Post-hoc working group chartering John C Klensin