Re: [datatracker-rqmts] Slides for the face-to-face BoF next week

Fred Baker <> Tue, 02 November 2010 16:15 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id CD0A43A68DB for <>; Tue, 2 Nov 2010 09:15:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -110.372
X-Spam-Status: No, score=-110.372 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, SARE_SUB_OBFU_Q1=0.227, USER_IN_WHITELIST=-100]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id faBScO+FKzdI for <>; Tue, 2 Nov 2010 09:15:20 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 099823A6883 for <>; Tue, 2 Nov 2010 09:15:20 -0700 (PDT)
Authentication-Results:; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAFvWz0yrR7Hu/2dsb2JhbAChVnGkW5wNhUUEhFeFfoMI
X-IronPort-AV: E=Sophos;i="4.58,283,1286150400"; d="scan'208";a="376706249"
Received: from ([]) by with ESMTP; 02 Nov 2010 16:15:10 +0000
Received: from Freds-Computer.local ([]) by (8.13.8/8.14.3) with ESMTP id oA2GF8ro011491; Tue, 2 Nov 2010 16:15:10 GMT
Received: from [] by Freds-Computer.local (PGP Universal service); Tue, 02 Nov 2010 09:15:10 -0700
X-PGP-Universal: processed; by Freds-Computer.local on Tue, 02 Nov 2010 09:15:10 -0700
Mime-Version: 1.0 (Apple Message framework v1081)
From: Fred Baker <>
In-Reply-To: <p0624088ac8f4ef10b46d@[]>
Date: Tue, 2 Nov 2010 09:15:00 -0700
Message-Id: <>
References: <p06240800c8ecfbb84168@[]> <p0624088ac8f4ef10b46d@[]>
To: Paul Hoffman <>
X-Mailer: Apple Mail (2.1081)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: Re: [datatracker-rqmts] Slides for the face-to-face BoF next week
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 02 Nov 2010 16:15:20 -0000

On Nov 1, 2010, at 3:28 PM, Paul Hoffman wrote:

> Greetings again. I have uploaded the proposed slides for the BoF to the IETF site; see <>.
> Of course, it would be swell if people wanted to talk about any of the topics in the draft or proposed in the slides before the meeting. :-)

Thanks for pointing out the slides.

One of the slides wonders what the rule is for identifying drafts associated with a working group. As I'm sure you know, there has been a convention for a long time in naming: draft-ietf-<wg>-*-nn.txt is a working group draft, and draft-<author>-<wg>-*-nn.txt is an individual submission to a working group. draft monikers that mention no working group are general submissions going nowhere in particular. I'm pretty sure that Henrik's existing tool looks for "draft-ietf-<wg>" and "anything containing <wg>" for the two areas.

I like the convention; I find it useful. I do go a little crazy with the set of people that don't choose to use it, though; I get people posting drafts and then wanting to discuss them for several meetings in my WG but not follow the convention, which means that I have to manually track things. Since a "convention" is not a "rule" (eg, I don't care to be a hard-ass about it), I put in the extra work, but there is a part of me that would like the tool to be able to remember for me in some sense. "documents that follow the convention plus those I add".

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/.