[proto-team] Re: draft-proto-wgchair-tracker-ext-00.txt

Henrik Levkowetz <henrik@levkowetz.com> Mon, 15 May 2006 17:49 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FfhBl-0003hQ-RE; Mon, 15 May 2006 13:49:01 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FfhBl-0003hL-68 for proto-team@ietf.org; Mon, 15 May 2006 13:49:01 -0400
Received: from av6-2-sn3.vrr.skanova.net ([81.228.9.180]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FfhBj-0008Sk-NX for proto-team@ietf.org; Mon, 15 May 2006 13:49:01 -0400
Received: by av6-2-sn3.vrr.skanova.net (Postfix, from userid 502) id 018183813B; Mon, 15 May 2006 19:48:58 +0200 (CEST)
Received: from smtp3-1-sn3.vrr.skanova.net (smtp3-1-sn3.vrr.skanova.net [81.228.9.101]) by av6-2-sn3.vrr.skanova.net (Postfix) with ESMTP id E6D9437E8B; Mon, 15 May 2006 19:48:58 +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 3861337E48; Mon, 15 May 2006 19:48:58 +0200 (CEST)
Received: from localhost ([127.0.0.1]) by shiraz.levkowetz.com with esmtp (Exim 4.61) (envelope-from <henrik@levkowetz.com>) id 1FfhBL-0002DO-DF; Mon, 15 May 2006 19:48:57 +0200
Message-ID: <4468BEF4.3000007@levkowetz.com>
Date: Mon, 15 May 2006 19:48:36 +0200
From: Henrik Levkowetz <henrik@levkowetz.com>
User-Agent: Thunderbird 1.5.0.2 (Macintosh/20060308)
MIME-Version: 1.0
To: "Lee, Michael" <Michael.Lee@neustar.biz>
References: <C6402C6F0493AA4DBCB9E62F0911E1FC0159CDA2@stntexch06.cis.neustar.com>
In-Reply-To: <C6402C6F0493AA4DBCB9E62F0911E1FC0159CDA2@stntexch06.cis.neustar.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: cab78e1e39c4b328567edb48482b6a69
Cc: "Fuller, Barbara" <Barbara.Fuller@neustar.biz>, Allison Mankin <mankin@psg.com>, proto-team@ietf.org
Subject: [proto-team] Re: draft-proto-wgchair-tracker-ext-00.txt
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 Michael,

on 2006-05-15 18:04 Lee, Michael said the following:
> Hi Henrick,
> 
> I'll definitely read those documents and give you my feed back soon.
> To answer to you question, let me briefly explain how a notification
> gets automatically sent when the state of a document gets changed.
> Within the IESG I-D Tracker, there is field which contains a list of
> email addresses to which the I-D Tracker send out a notification when
> the state is changed. That field is populated automatically by the
> tracker when a document is entered to the tracker. Once populated, the
> list of email addresses in that field can be manually updated by ADs.
> 
> Of course, such a feature can be used in this new tracker for the WG
> chairs.

Ok.  From your description I get the impression that this is one
list of email addresses, for all notifications - it is not one list
per state/substate?

In that case, there's a potential additional feature which I'm not
at all sure should be part of the wgchair tracker package, which is
to add per-state/substate notification lists.  On the other hand,
this can be handled by the more general notification infrastructure
which I hope to have someone build over the summer.

One example where this kind of state-specific notification could be
appropriate is when a document enters "Awaiting MIB Review" - then
a message should go to the person who dispatches MIB reviews; but he
should not get notifications of all state transitions for all MIB
documents, before and after the MIB review point.

Anyway, I look forward to hearing your feedback on the documents.
The most recent versions are available at 

http://tools.ietf.org/wg/proto/

- I've done some updates after the -00 versions, based on other
comments received.


Best,

	Henrik

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