Re: [datatracker-rqmts] Tracking things other than drafts in lists

Paul Hoffman <> Thu, 20 January 2011 18:21 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 092923A704B for <>; Thu, 20 Jan 2011 10:21:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -101.615
X-Spam-Status: No, score=-101.615 tagged_above=-999 required=5 tests=[AWL=0.204, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, SARE_SUB_OBFU_Q1=0.227, USER_IN_WHITELIST=-100]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id jnQj3Fg4um6a for <>; Thu, 20 Jan 2011 10:21:45 -0800 (PST)
Received: from (Hoffman.Proper.COM []) by (Postfix) with ESMTP id 5BED63A702F for <>; Thu, 20 Jan 2011 10:21:45 -0800 (PST)
Received: from MacBook-08.local ( []) (authenticated bits=0) by (8.14.4/8.14.3) with ESMTP id p0KIOSYk066388 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <>; Thu, 20 Jan 2011 11:24:28 -0700 (MST) (envelope-from
Message-ID: <>
Date: Thu, 20 Jan 2011 10:24:28 -0800
From: Paul Hoffman <>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv: Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
References: <>
In-Reply-To: <>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [datatracker-rqmts] Tracking things other than drafts in lists
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 20 Jan 2011 18:21:47 -0000

Thank you to Barry and Blake for responding. Other folks are strongly 
encouraged to do the same! :-)

On 1/18/11 11:07 AM, Paul Hoffman wrote:
> Greetings again. At the meeting in Beijing, many people in the room
> expressed interest in being able to track things other than just drafts.
> However, there was also a desire to keep the first round of this work
> simple. I would like to address those two now and see what folks on this
> list think should be done.
> Appendix A of the current draft lists the five non-draft things that I
> have heard requests to track:
> Tracking RFC Status Changes and Errata
> Tracking WG Charter Changes
> Tracking IANA Registry Changes
> Tracking Changes in the Liason Statement Directory
> Tracking Changes in Documents Outside the IETF Sphere
> We can add as many or as few of them as we want to the first round of
> the tool.
> I propose the following choices for the first round, although feel free
> to add your own:
> a) None of the above: just track drafts
> b) Add just "RFC Status Changes and Errata"
> c) Add them all
> In my mind, the logic behind (a) is "keep it as simple as possible", the
> logic behind (b) is "most IETFers care about RFC status and errata in
> their development work and their WG work", and the logic behind (c) is
> "this is all easy to do and people won't get confused if they have too
> many choices". You might have other reasons for preferring one over the
> others, or wanting some combination other than what is listed above.
> Comments are welcome.
> _______________________________________________
> datatracker-rqmts mailing list