[proto-team] Re: PROTO - proceeding on adding PROTO shepherds to the tracker
Brian E Carpenter <brc@zurich.ibm.com> Sun, 14 May 2006 14:03 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FfHBy-0001Px-CA; Sun, 14 May 2006 10:03:30 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FfHBw-0001Pp-Kj; Sun, 14 May 2006 10:03:28 -0400
Received: from mtagate2.de.ibm.com ([195.212.29.151]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FfHBw-0001Ur-4Z; Sun, 14 May 2006 10:03:28 -0400
Received: from d12nrmr1607.megacenter.de.ibm.com (d12nrmr1607.megacenter.de.ibm.com [9.149.167.49]) by mtagate2.de.ibm.com (8.13.6/8.13.6) with ESMTP id k4EE3Rlf120658; Sun, 14 May 2006 14:03:27 GMT
Received: from d12av04.megacenter.de.ibm.com (d12av04.megacenter.de.ibm.com [9.149.165.229]) by d12nrmr1607.megacenter.de.ibm.com (8.12.10/NCO/VER6.8) with ESMTP id k4EE4p5i153384; Sun, 14 May 2006 16:04:52 +0200
Received: from d12av04.megacenter.de.ibm.com (loopback [127.0.0.1]) by d12av04.megacenter.de.ibm.com (8.12.11/8.13.3) with ESMTP id k4EE3QCj022515; Sun, 14 May 2006 16:03:26 +0200
Received: from sihl.zurich.ibm.com (sihl.zurich.ibm.com [9.4.16.232]) by d12av04.megacenter.de.ibm.com (8.12.11/8.12.11) with ESMTP id k4EE3QwC022512; Sun, 14 May 2006 16:03:26 +0200
Received: from zurich.ibm.com (sig-9-145-254-21.de.ibm.com [9.145.254.21]) by sihl.zurich.ibm.com (AIX4.3/8.9.3p2/8.9.3) with ESMTP id QAA30794; Sun, 14 May 2006 16:03:24 +0200
Message-ID: <446738AB.2070900@zurich.ibm.com>
Date: Sun, 14 May 2006 16:03:23 +0200
From: Brian E Carpenter <brc@zurich.ibm.com>
Organization: IBM
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113
X-Accept-Language: en, fr, de
MIME-Version: 1.0
To: mankin@psg.com
References: <E1FdpF4-0007xU-Fk@megatron.ietf.org>
In-Reply-To: <E1FdpF4-0007xU-Fk@megatron.ietf.org>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cd26b070c2577ac175cd3a6d878c6248
Cc: Aaron Falk <falk@isi.edu>, Ray Pelletier <rpelletier@isoc.org>, proto-team@ietf.org, iesg@ietf.org, henrik@levkowetz.com
Subject: [proto-team] Re: PROTO - proceeding on adding PROTO shepherds to the tracker
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
[resend due to address problem the first time] Thanks. Here are my comments on the two drafts. One general question: has Michael Lee reviewed them for gotchas? One general suggestion: let's not waste time in the RFC queue with these. Once they're agreed, just do it. You can post <?rfc private ?> versions on the PROTO site for the record. Brian draft-ietf-proto-wgchair-tracker-ext-00 > 2. I-D Tracker Write Access ... > * Identification of the actions and information which may not be > accessed by all users (R-002). Such actions and information will > be called 'restricted features' in the following. Some known > restricted features are: It would be good to see an updated and marked-up state table and state diagram, with the restricted features clearly identified. > 3.1. WG Document States ... > > * WG Document Awaiting Reviews > This document needs reviews (possibly a certain number of reviews, > at a minimum) before a WG last call will be done. > > Possible next states: "Active WG Document", "Parked WG Document", > "Publication Requested", "In WG Last Call", "Dead" > > Permitted sub-states: "0 reviews", "1 reviews", "2 reviews", "3 > reviews", "4 reviews", "5 reviews", "Awaiting MIB Doctor Review", > *** More special review states *** > (R-008) This will be very useful for the proposed early cross-area review mechanism. (Since the recent IESG retreat, Lisa owns that topic.) Can we have a substate "Awaiting cross-area review"? Linked to that, what happens about state change notifications? For example, the dispatcher for cross-area reviews needs to get a trigger when the sub-state "Awaiting cross-area review" is set. > 5. Modification of Existing States > > One existing sub-state in the tracker should be modified to reflect > the role of the WG document shepherds. > > The sub-state "AD Followup" is defined as generic and may be used for > many purposes by an Area Director. However, the tracker > automatically assigns this sub-state when a document which has been > in the "Revised ID Needed" sub-state is updated. The "AD Followup" > sub-state shall continue to exist for the first purpose, but when a > document is in "IESG Evaluation - Revised ID Needed" and an update > arrives, it shall receive an automatic state change to a new sub- > state instead: "Doc Shepherd Followup" (R-022). But not for non-WG documents, which should still get "AD Followup." draft-ietf-proto-iab-irtf-tracker-ext-00 You don't mention access control. I'm surprised you don't expect "Revised ID Needed" to be used. Brian _______________________________________________ proto-team mailing list proto-team@ietf.org https://www1.ietf.org/mailman/listinfo/proto-team
- [proto-team] PROTO - proceeding on adding PROTO s… Allison Mankin
- Re: [proto-team] PROTO - proceeding on adding PRO… Bill Fenner
- Re: [proto-team] PROTO - proceeding on adding PRO… Henrik Levkowetz
- [proto-team] Re: PROTO - proceeding on adding PRO… Brian E Carpenter
- [proto-team] Re: PROTO - proceeding on adding PRO… Henrik Levkowetz
- [proto-team] Re: PROTO - proceeding on adding PRO… Brian E Carpenter
- [proto-team] Re: PROTO - proceeding on adding PRO… Brian E Carpenter
- [proto-team] Re: PROTO - proceeding on adding PRO… Brian E Carpenter
- Re: [proto-team] Re: PROTO - proceeding on adding… Henrik Levkowetz
- Re: [proto-team] Re: PROTO - proceeding on adding… Henrik Levkowetz
- Re: [proto-team] Re: PROTO - proceeding on adding… Brian E Carpenter
- Re: [proto-team] Re: PROTO - proceeding on adding… Henrik Levkowetz
- Re: [proto-team] Re: PROTO - proceeding on adding… Brian E Carpenter
- Re: [proto-team] Re: PROTO - proceeding on adding… Lisa Dusseault
- Re: [proto-team] Re: PROTO - proceeding on adding… Henrik Levkowetz
- Re: [proto-team] Re: PROTO - proceeding on adding… Lisa Dusseault
- Re: [proto-team] Re: PROTO - proceeding on adding… Henrik Levkowetz
- Re: [proto-team] Re: PROTO - proceeding on adding… Bill Fenner
- Re: [proto-team] Re: PROTO - proceeding on adding… Henrik Levkowetz
- Re: [proto-team] Re: PROTO - proceeding on adding… Brian E Carpenter
- Re: [proto-team] Re: PROTO - proceeding on adding… Lisa Dusseault
- Re: [proto-team] Re: PROTO - proceeding on adding… Bill Fenner
- [proto-team] Re: PROTO - proceeding on adding PRO… Lisa Dusseault
- [proto-team] Re: PROTO - proceeding on adding PRO… Henrik Levkowetz