Re: [proto-team] Re: PROTO - proceeding on adding PROTO shepherds to the tracker
Henrik Levkowetz <henrik@levkowetz.com> Sun, 14 May 2006 14:49 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FfHuP-0005UK-JU; Sun, 14 May 2006 10:49:25 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FfHuO-0005UA-NI for proto-team@ietf.org; Sun, 14 May 2006 10:49:24 -0400
Received: from av10-2-sn2.hy.skanova.net ([81.228.8.182]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FfHuN-0004Rd-8Y for proto-team@ietf.org; Sun, 14 May 2006 10:49:24 -0400
Received: by av10-2-sn2.hy.skanova.net (Postfix, from userid 502) id 5868F37E48; Sun, 14 May 2006 16:49:22 +0200 (CEST)
Received: from smtp4-2-sn2.hy.skanova.net (smtp4-2-sn2.hy.skanova.net [81.228.8.93]) by av10-2-sn2.hy.skanova.net (Postfix) with ESMTP id 20C9337E44; Sun, 14 May 2006 16:49:22 +0200 (CEST)
Received: from shiraz.levkowetz.com (81-232-110-214-no16.tbcn.telia.com [81.232.110.214]) by smtp4-2-sn2.hy.skanova.net (Postfix) with ESMTP id 7AF0737E5D; Sun, 14 May 2006 16:49:20 +0200 (CEST)
Received: from localhost ([127.0.0.1]) by shiraz.levkowetz.com with esmtp (Exim 4.61) (envelope-from <henrik@levkowetz.com>) id 1FfHuJ-0001Ib-9R; Sun, 14 May 2006 16:49:20 +0200
Message-ID: <4467436E.2060400@levkowetz.com>
Date: Sun, 14 May 2006 16:49:18 +0200
From: Henrik Levkowetz <henrik@levkowetz.com>
User-Agent: Thunderbird 1.5.0.2 (Macintosh/20060308)
MIME-Version: 1.0
To: Brian E Carpenter <brc@zurich.ibm.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>
In-Reply-To: <44673AB3.2050002@zurich.ibm.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: f4c2cf0bccc868e4cc88dace71fb3f44
Cc: mankin@psg.com, Ray Pelletier <rpelletier@isoc.org>, Aaron Falk <falk@isi.edu>, 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 again, on 2006-05-14 16:12 Brian E Carpenter said the following: ... >>>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. >> >> >> If the tracker currently supports notification triggers, I'd add >> that here - but I don't think it does, > > It does for certain transitions - Michael can advise. Ok. I've asked about this in the email to Michael. I've also provisionally added this after the list of new states in -01.b : 3.2. Notifications Under the assumption that the tracker already has the ability to send email notifications when certain state transitions occur, the tracker should be able to send out notification to one or more email addresses when one of the followings states or sub-states are entered(R-012): * Awaiting MIB Doctor Review * Awaiting Cross-Area Review ... >>>draft-ietf-proto-iab-irtf-tracker-ext-00 >>> >>>You don't mention access control. >> >> >> Not sure I know exactly what you think of here - this document >> was only supposed to describe the additional IAB and IRTF states >> needed, and having little knowledge of their process, I expect >> someone else to provide the needed text adjustment for those. >> But I get the impression that you also expect special access >> control restrictions associated with the IAB and IRTF states > > Well, I hadn't really thought it through - but they presumably will > only have write access for IAB/IRTF drafts respectively. Ok. For now I've added this to the requirements in Section 2 of draft-ietf-proto-wgchair-tracker-ext: * There should at least be individual groups corresponding to 'ADs', 'Chairs', 'IAB' and 'IRTF', permitting per-group access control of actions and features with this granularity (R-011). Regards, Henrik _______________________________________________ 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