[datatracker-rqmts] Lists not kept by the Datatracker

Paul Hoffman <paul.hoffman@vpnc.org> Tue, 02 November 2010 17:18 UTC

Return-Path: <paul.hoffman@vpnc.org>
X-Original-To: datatracker-rqmts@core3.amsl.com
Delivered-To: datatracker-rqmts@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0881128C132 for <datatracker-rqmts@core3.amsl.com>; Tue, 2 Nov 2010 10:18:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.274
X-Spam-Level:
X-Spam-Status: No, score=-100.274 tagged_above=-999 required=5 tests=[AWL=-0.087, BAYES_20=-0.74, HELO_MISMATCH_COM=0.553, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TV2fDqYOQxoN for <datatracker-rqmts@core3.amsl.com>; Tue, 2 Nov 2010 10:18:23 -0700 (PDT)
Received: from hoffman.proper.com (Hoffman.Proper.COM [207.182.41.81]) by core3.amsl.com (Postfix) with ESMTP id 5B1CB28C131 for <datatracker-rqmts@ietf.org>; Tue, 2 Nov 2010 10:18:23 -0700 (PDT)
Received: from [10.20.30.150] (75-101-30-90.dsl.dynamic.sonic.net [75.101.30.90]) (authenticated bits=0) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id oA2HIPPD085972 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 2 Nov 2010 10:18:27 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Mime-Version: 1.0
Message-Id: <p0624089ec8f5f7774360@[10.20.30.150]>
In-Reply-To: <E4EE6733-D741-4F31-9B4F-40B0212B3DC8@cisco.com>
References: <p06240800c8ecfbb84168@[10.20.30.249]> <p0624088ac8f4ef10b46d@[10.20.30.249]> <E4EE6733-D741-4F31-9B4F-40B0212B3DC8@cisco.com>
Date: Tue, 02 Nov 2010 10:18:24 -0700
To: Fred Baker <fred@cisco.com>
From: Paul Hoffman <paul.hoffman@vpnc.org>
Content-Type: text/plain; charset="us-ascii"
Cc: datatracker-rqmts@ietf.org
Subject: [datatracker-rqmts] Lists not kept by the Datatracker
X-BeenThere: datatracker-rqmts@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <datatracker-rqmts.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/datatracker-rqmts>, <mailto:datatracker-rqmts-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/datatracker-rqmts>
List-Post: <mailto:datatracker-rqmts@ietf.org>
List-Help: <mailto:datatracker-rqmts-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/datatracker-rqmts>, <mailto:datatracker-rqmts-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Nov 2010 17:18:24 -0000

At 9:15 AM -0700 11/2/10, Fred Baker wrote:
>Something else the slides note - there could be some pain in various forms regarding personal lists. There might be; I'm not sure why anyone would want to know what drafts I was tracking (it's not like we have drafts about specialized delivery of pornography or etc), but I could imagine someone trying to do corporate intelligence by tracking who is tracking what drafts. A simple solution would be to keep our private lists on our private computers. That might, for example, be a reasonable use of a cookie or some kind of local preferences file. If we're keeping the list on the machine, I would think that per-user lists would not be used in daily processing; they would be compiled into a set of rules of the form "if a draft whose name matches /<regex>/ changes, notify {list}". Individual draft names are an obvious special case, as are /draft-*-<wg>-*.txt/.

This is definitely a possibility for the tool. If people don't want to use the tool's list-making (such as if SM and Doug's proposal is accepted and someone has the concern you give above), the tool could have a mode of "give me your list and your preferences in an HTTP request and I'll give you a display like the one I would have done if you kept the list with me". I don't know how we could handle making an Atom feed or mail stream for those folks.

--Paul Hoffman, Director
--VPN Consortium