Re: [proto-team] Re: PROTO - proceeding on adding PROTO shepherds to the tracker

Henrik Levkowetz <henrik@levkowetz.com> Wed, 17 May 2006 08:29 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FgHPJ-0007hS-QA; Wed, 17 May 2006 04:29:25 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FgHPI-0007hB-0V; Wed, 17 May 2006 04:29:24 -0400
Received: from av8-2-sn3.vrr.skanova.net ([81.228.9.184]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FgHPG-0008WF-NW; Wed, 17 May 2006 04:29:23 -0400
Received: by av8-2-sn3.vrr.skanova.net (Postfix, from userid 502) id EEC7237FB3; Wed, 17 May 2006 10:29:21 +0200 (CEST)
Received: from smtp3-1-sn3.vrr.skanova.net (smtp3-1-sn3.vrr.skanova.net [81.228.9.101]) by av8-2-sn3.vrr.skanova.net (Postfix) with ESMTP id DD25637F12; Wed, 17 May 2006 10:29:21 +0200 (CEST)
Received: from shiraz.levkowetz.com (81-232-110-214-no16.tbcn.telia.com [81.232.110.214]) by smtp3-1-sn3.vrr.skanova.net (Postfix) with ESMTP id AAB9937E4D; Wed, 17 May 2006 10:29:21 +0200 (CEST)
Received: from localhost ([127.0.0.1]) by shiraz.levkowetz.com with esmtp (Exim 4.61) (envelope-from <henrik@levkowetz.com>) id 1FgHPE-0003vQ-3f; Wed, 17 May 2006 10:29:21 +0200
Message-ID: <446ADEE0.3090301@levkowetz.com>
Date: Wed, 17 May 2006 10:29:20 +0200
From: Henrik Levkowetz <henrik@levkowetz.com>
User-Agent: Thunderbird 1.5.0.2 (Macintosh/20060308)
MIME-Version: 1.0
To: Bill Fenner <fenner@research.att.com>
Subject: Re: [proto-team] Re: PROTO - proceeding on adding PROTO shepherds to the tracker
References: <E1FdpF4-0007xU-Fk@megatron.ietf.org> <446715D7.7080701@zurich.ibm.com> <446726DE.8040904@levkowetz.com> <44673AB3.2050002@zurich.ibm.com> <4467436E.2060400@levkowetz.com> <A9A5C496-4C40-43F8-86C7-8EC882AF85D9@osafoundation.org> <4468F2AA.60707@levkowetz.com> <446980AD.7030200@zurich.ibm.com> <44699905.1090405@levkowetz.com> <93BF5579-D718-4C3E-A3E1-A44F04C87769@osafoundation.org> <446A0AD0.9020007@levkowetz.com> <200605161848.k4GImF4i005235@bright.research.att.com>
In-Reply-To: <200605161848.k4GImF4i005235@bright.research.att.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Mail-From: henrik@levkowetz.com
X-SA-Exim-Scanned: No (on shiraz.levkowetz.com); SAEximRunCond expanded to false
X-Spam-Score: 0.1 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Cc: iesg@ietf.org, proto-team@ietf.org
X-BeenThere: proto-team@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Process and Tools Team <proto-team.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/proto-team>, <mailto:proto-team-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:proto-team@ietf.org>
List-Help: <mailto:proto-team-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/proto-team>, <mailto:proto-team-request@ietf.org?subject=subscribe>
Errors-To: proto-team-bounces@ietf.org

Hi Bill,

on 2006-05-16 20:48 Bill Fenner said the following:
> Here's a question:
> 
> Will the WG want to use the "in WG" states when the
> IESG has said "Revise this document to address these
> concerns" (e.g., AD Evaluation/Revised ID Needed, or
> IESG Evaluation/Revised ID Needed)?
> 
> I think the answer could be "Yes", meaning that this is
> actually a parallel state machine, not an extension to
> the existing state machine.

Mmm.  Either that (but then the two state machines are
bound together by constraints, for the WG states are
only meaningful in some IESG states) or we add WG states
for the cases you mention, which are different from the
pre-pub-request states.

Preferences?  I think I'd prefer the latter, to avoid
having to think about imposing constraints on two bound
state sets.


	Henrik

_______________________________________________
proto-team mailing list
proto-team@ietf.org
https://www1.ietf.org/mailman/listinfo/proto-team