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

Barry Leiba <barryleiba@computer.org> Wed, 19 January 2011 04:42 UTC

Return-Path: <barryleiba.mailing.lists@gmail.com>
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 855FC3A6F52 for <datatracker-rqmts@core3.amsl.com>; Tue, 18 Jan 2011 20:42:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.654
X-Spam-Level:
X-Spam-Status: No, score=-102.654 tagged_above=-999 required=5 tests=[AWL=0.096, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, SARE_SUB_OBFU_Q1=0.227, 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 8uXnpIfioiZY for <datatracker-rqmts@core3.amsl.com>; Tue, 18 Jan 2011 20:42:22 -0800 (PST)
Received: from mail-iw0-f172.google.com (mail-iw0-f172.google.com [209.85.214.172]) by core3.amsl.com (Postfix) with ESMTP id 9C79028C100 for <datatracker-rqmts@ietf.org>; Tue, 18 Jan 2011 20:42:22 -0800 (PST)
Received: by iwn40 with SMTP id 40so417057iwn.31 for <datatracker-rqmts@ietf.org>; Tue, 18 Jan 2011 20:45:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=bsd8llrn/yjHvdGz5N1m2iVXBwO+UA297PY4mf88coo=; b=a8DJlSAiOWikQEF7s0AvXjjHc0L4+M4PrYT6xj2scrOAYf4qGo9E5bfPey1/NH+HOK 1xWfcE7pazt0amvj9NkNnb8DF0y6bIIyrcrXWJ+QcGYEHZx+TGffMhChZuZyy+d+ny8v vurhWQPJggOu0S7+u2W26AjJOWPOkDwVAurR8=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; b=aRWivNEjEuVcYP5IKCDVKmx94B9f2K5nMV2P7h3CHxTOcnS3JNAu9X3k01Z0k4prj2 5m067fnV8RysVgkqNYIvEf/J8soJnGclbovcRajI7jq86/KOi7uBiaKLMqXllPwKv0uK 8QVjW3a8lXhV7VYISbgzAF7F3TqmwwA5N3N6c=
MIME-Version: 1.0
Received: by 10.42.180.194 with SMTP id bv2mr235742icb.152.1295412301646; Tue, 18 Jan 2011 20:45:01 -0800 (PST)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.42.227.193 with HTTP; Tue, 18 Jan 2011 20:45:01 -0800 (PST)
In-Reply-To: <4D35E4F4.2030603@vpnc.org>
References: <4D35E4F4.2030603@vpnc.org>
Date: Tue, 18 Jan 2011 23:45:01 -0500
X-Google-Sender-Auth: 13e-dDKncAEkQTKXPWfZiMgzYVI
Message-ID: <AANLkTi=4veGVEyxNd1tSLDT653z2ELZ02-R+A81STdSa@mail.gmail.com>
From: Barry Leiba <barryleiba@computer.org>
To: Paul Hoffman <paul.hoffman@vpnc.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: datatracker-rqmts@ietf.org
Subject: Re: [datatracker-rqmts] Tracking things other than drafts in lists
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: Wed, 19 Jan 2011 04:42:23 -0000

I'll review the draft as soon as I can, but just to answer this
question for now:

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

> b) Add just "RFC Status Changes and Errata"

My reasoning is that this should be part of tracking a document from
beginning to end.  You watch it as a draft, you continue watching as
it becomes an RFC, you see errata being posted, etc.

Also, what that says to me is that if I'm watching
draft-furbie-feedme-please, and that becomes RFC 6666, I should be
watching that, as well, without having to do it manually.  (Or perhaps
that should be an option when I start following it -- to specify
whether I want to keep following it as it's replaced by
draft-ietf-feedme-base-protocol and then by RFC 6666.)

Barry