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

Blake Ramsdell <blaker@gmail.com> Wed, 19 January 2011 05:56 UTC

Return-Path: <blaker@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 72BC43A6DA2 for <datatracker-rqmts@core3.amsl.com>; Tue, 18 Jan 2011 21:56:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.985
X-Spam-Level:
X-Spam-Status: No, score=-102.985 tagged_above=-999 required=5 tests=[AWL=0.387, BAYES_00=-2.599, 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 yn7zLgiplbFD for <datatracker-rqmts@core3.amsl.com>; Tue, 18 Jan 2011 21:56:46 -0800 (PST)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by core3.amsl.com (Postfix) with ESMTP id 408553A6C42 for <datatracker-rqmts@ietf.org>; Tue, 18 Jan 2011 21:56:46 -0800 (PST)
Received: by wyf23 with SMTP id 23so503943wyf.31 for <datatracker-rqmts@ietf.org>; Tue, 18 Jan 2011 21:59:24 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=bL0fneT074nmA7MXHd1JqJoZpLmhXAa0bzOIo11P6AA=; b=RZge9DoanSdCG/S5m98Bps+6YgW8CAhy+QLY6Vd+CT/ndWa41vW3oB9V+cZBLzaFN8 I0Yk6K2nQNyJxNLZjXBSaiWk9aLBya7185zW7w6TSIOs+1yHWMv1NY7tGdx0xlNmfUKA 8ImDLZAazqCRQTmC/nDBPeqGBowHYvp/Kdiew=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=ftbKC1xYeXEHreGjD7C3mVq2Pr5yca8fMzjlXChGYHQhxhhNtSvhOZov/HNMEd6ZiL rqqq8bf8+YtIu92K2YPfEeib7X5gc6RbVDjTcyz1Bv8TkewjmiAGwhzmgmPyVmzlefT3 5VX7su98oyi9z50mu70a4CsP6h5i0KvhGMsBM=
MIME-Version: 1.0
Received: by 10.216.30.81 with SMTP id j59mr251633wea.39.1295416764881; Tue, 18 Jan 2011 21:59:24 -0800 (PST)
Received: by 10.216.2.8 with HTTP; Tue, 18 Jan 2011 21:59:24 -0800 (PST)
In-Reply-To: <AANLkTi=4veGVEyxNd1tSLDT653z2ELZ02-R+A81STdSa@mail.gmail.com>
References: <4D35E4F4.2030603@vpnc.org> <AANLkTi=4veGVEyxNd1tSLDT653z2ELZ02-R+A81STdSa@mail.gmail.com>
Date: Tue, 18 Jan 2011 21:59:24 -0800
Message-ID: <AANLkTi=+N8RDUr5=4vg9Y-KQgsuuN1QaqYqcEFTxhbPG@mail.gmail.com>
From: Blake Ramsdell <blaker@gmail.com>
To: Barry Leiba <barryleiba@computer.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: datatracker-rqmts@ietf.org, Paul Hoffman <paul.hoffman@vpnc.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 05:56:47 -0000

On Tue, Jan 18, 2011 at 8:45 PM, Barry Leiba <barryleiba@computer.org>; wrote:
> 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.)

I agree with Barry. I have implemented a protocol defined by an RFC. I
want to know anything that might affect my implementation.

I was not aware of errata for RFCs before I became a WG chair. I
imagine many other implementors are in the same boat.

Blake