Re: [rfc-i] Referencing Internet Drafts

Paul Kyzivat <paul.kyzivat@comcast.net> Fri, 16 June 2017 20:10 UTC

Return-Path: <rfc-interest-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-interest-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-interest-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2DF1C1293F2 for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Fri, 16 Jun 2017 13:10:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.892
X-Spam-Level:
X-Spam-Status: No, score=-3.892 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, FREEMAIL_FORGED_FROMDOMAIN=0.199, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_DKIM_INVALID=0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (2048-bit key) reason="fail (message has been altered)" header.d=comcast.net
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ikIuKUdZy7HE for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Fri, 16 Jun 2017 13:09:58 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9CDD7127078 for <rfc-interest-archive-eekabaiReiB1@ietf.org>; Fri, 16 Jun 2017 13:09:58 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 1FE5CB80A45; Fri, 16 Jun 2017 13:09:43 -0700 (PDT)
X-Original-To: rfc-interest@rfc-editor.org
Delivered-To: rfc-interest@rfc-editor.org
Received: from localhost (localhost [127.0.0.1]) by rfc-editor.org (Postfix) with ESMTP id 6C9E3B80A45 for <rfc-interest@rfc-editor.org>; Fri, 16 Jun 2017 13:09:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at rfc-editor.org
Authentication-Results: rfcpa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=comcast.net
Received: from rfc-editor.org ([127.0.0.1]) by localhost (rfcpa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5r82gn1DU26D for <rfc-interest@rfc-editor.org>; Fri, 16 Jun 2017 13:09:40 -0700 (PDT)
Received: from resqmta-ch2-08v.sys.comcast.net (resqmta-ch2-08v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:40]) by rfc-editor.org (Postfix) with ESMTPS id E43BAB80A44 for <rfc-interest@rfc-editor.org>; Fri, 16 Jun 2017 13:09:39 -0700 (PDT)
Received: from resomta-ch2-18v.sys.comcast.net ([69.252.207.114]) by resqmta-ch2-08v.sys.comcast.net with SMTP id LxYvd9WDpAfZsLxZ2d0Krv; Fri, 16 Jun 2017 20:09:52 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20161114; t=1497643792; bh=N1BngFrU3YO94mXIT/tWfl5TDH/6jWPVdBRnbhzsZ4w=; h=Received:Received:Subject:To:From:Message-ID:Date:MIME-Version: Content-Type; b=ooZUWfNonABWS3166O3LdQPnDi9dtl5vPr7BxdtH1C6ewLFSLyAfGAwFw2SUaYzI1 TLvxYOFcait5Nh94Rzqc9vsbEQI8jNy5ZBbJTgi1z2riAOhw2z1oIOOJvMB5bLLvv3 6bGssgKC2xmPJizQS0nT2vA1EVOTv78XT3teVasQf/Zdpc3ez8CIVVk6fTPKXldkYn A3yhKkRHRtGHdmD2eXgTJvc/uEECJqM/XyhwmHce5Bp1VQtiU+QngxP3YLvfQIQt5I ZIZkUG8HFtY0hRTTsAfU4xar6K1yIauIgYW4lsphIXy0JSojuJL0WjPEQNwnU5l3UO SzqwQnDluM1dA==
Received: from [192.168.1.110] ([24.62.227.142]) by resomta-ch2-18v.sys.comcast.net with SMTP id LxZ1dPNLPKn57LxZ1dr38N; Fri, 16 Jun 2017 20:09:52 +0000
To: rfc-interest@rfc-editor.org
References: <148916689952.6827.6792653811413720687.idtracker@ietfa.amsl.com> <383fa41c-e289-8045-7c1f-fcdcd8cc8445@rfc-editor.org> <eca0f643-0e06-0e9e-d972-47b76d5ef1bb@gmx.de> <1cd9c597-f945-6b22-d0fb-8623897b678d@gmx.de> <eff80e48-ff88-0516-9a46-072e88be3164@rfc-editor.org> <27887A7B-DD5A-4D10-B307-44AD342B4F74@tzi.org> <0c97b073-80ca-9dd8-3f3e-30cc874a2a9d@gmail.com> <bf937f01-ee6e-fd0e-1e58-1917ca786129@rfc-editor.org> <cad23c19-70a4-7bae-0b66-16cb55827842@gmx.de> <e9f4c563-15b7-b696-9d1c-af46b0cade2a@comcast.net> <97bf81f3-3cd0-cb17-750b-a12910e97413@rfc-editor.org>
From: Paul Kyzivat <paul.kyzivat@comcast.net>
Message-ID: <2f8405b7-1577-bde7-b88a-205ca4d03506@comcast.net>
Date: Fri, 16 Jun 2017 16:09:51 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:52.0) Gecko/20100101 Thunderbird/52.2.0
MIME-Version: 1.0
In-Reply-To: <97bf81f3-3cd0-cb17-750b-a12910e97413@rfc-editor.org>
Content-Language: en-US
X-CMAE-Envelope: MS4wfLpHwQzM/wk0/bvMZ9vHz0q3fG8n4ZmI0OQIuY8Qg60+ASrn8ZtyEkCwvpxzO9ZJZfLcpa0ysmevID1Bwq1Negi213L2QSoxbtcjjCDS5BES1PLfypXL YugLhfR80kS+DMpOlV0170N9CjGKI4qqfgLOFUX5ZkiaHe4EcWU/1KwZRfAACVWCtfUlzFe/oymj7Q==
Subject: Re: [rfc-i] Referencing Internet Drafts
X-BeenThere: rfc-interest@rfc-editor.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "A list for discussion of the RFC series and RFC Editor functions." <rfc-interest.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-interest/>
List-Post: <mailto:rfc-interest@rfc-editor.org>
List-Help: <mailto:rfc-interest-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Errors-To: rfc-interest-bounces@rfc-editor.org
Sender: rfc-interest <rfc-interest-bounces@rfc-editor.org>

On 6/16/17 3:13 PM, Heather Flanagan (RFC Series Editor) wrote:
> On 6/16/17 11:42 AM, Paul Kyzivat wrote:
>> On 6/16/17 2:33 PM, Julian Reschke wrote:
>>> On 2017-06-16 20:19, Heather Flanagan (RFC Series Editor) wrote:
>>>> ...
>>>> Who would make the call as to whether an I-D is a work in progress or a
>>>> [stale|historic|overtaken by events|your favorite term here] I-D? It's
>>>> not a simple case of time, and the author of the I-D being referenced
>>>> might have a difference of opinion than the author doing the
>>>> referencing.
>>>> ...
>>>
>>> There'll be edge cases, right. But if an ID hasn't been updated in
>>> years, it's likely abandoned, right?
>>
>> Isn't it sufficient to define that an ID that is the most recent version
>> and hasn't expired is a work in progress, and that others are historic?
>>
> 
> I don't think it's quite that tidy. For example, there are drafts that
> are expired but which are in one of the stream manager's queue for
> consideration (e.g.,
> https://datatracker.ietf.org/doc/draft-young-entity-category/).

*That* is a whole different issue. IMO those should not expire!

> There's also a certain consideration about how useful it is to make this
> distinction when someone reads the RFC referencing these I-Ds in a year;
> all the I-Ds may be historic, or may be revised, or may be replaced, or
> a mix of all the above. Unless the author of the RFC doing the
> referencing is careful to explain the context in which he or she is
> referencing the I-D (which they should do regardless) I'm not sure we're
> helping the reader with an "the I-D being referenced was older than six
> months at the time this RFC was published".

Yeah, guess so.

If change description from "Work in Progress" to "Working Draft" then it 
ages better, and maybe no need to make a distinction for historic.

	Thanks,
	Paul
_______________________________________________
rfc-interest mailing list
rfc-interest@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-interest