Re: [rfc-i] Referencing Internet Drafts
"Heather Flanagan (RFC Series Editor)" <rse@rfc-editor.org> Fri, 16 June 2017 18:19 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 1C653129B48 for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Fri, 16 Jun 2017 11:19:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.203
X-Spam-Level:
X-Spam-Status: No, score=-4.203 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 YG2yw2gky7vR for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Fri, 16 Jun 2017 11:19:14 -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 5F4A0129A9C for <rfc-interest-archive-eekabaiReiB1@ietf.org>; Fri, 16 Jun 2017 11:19:14 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id E992FB80E0A; Fri, 16 Jun 2017 11:18:58 -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 E6861B80E09 for <rfc-interest@rfc-editor.org>; Fri, 16 Jun 2017 11:18:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at rfc-editor.org
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 bwvwRLH9IyxI for <rfc-interest@rfc-editor.org>; Fri, 16 Jun 2017 11:18:56 -0700 (PDT)
Received: from mail.amsl.com (c8a.amsl.com [4.31.198.40]) by rfc-editor.org (Postfix) with ESMTPS id 863B0B80E08 for <rfc-interest@rfc-editor.org>; Fri, 16 Jun 2017 11:18:56 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 970E11CA534 for <rfc-interest@rfc-editor.org>; Fri, 16 Jun 2017 11:18:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IJNZxuAR43_r for <rfc-interest@rfc-editor.org>; Fri, 16 Jun 2017 11:18:58 -0700 (PDT)
Received: from Heathers-MacBook-Pro.local (c-50-159-75-65.hsd1.wa.comcast.net [50.159.75.65]) by c8a.amsl.com (Postfix) with ESMTPSA id 6E4C91CA52A for <rfc-interest@rfc-editor.org>; Fri, 16 Jun 2017 11:18:58 -0700 (PDT)
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>
From: "Heather Flanagan (RFC Series Editor)" <rse@rfc-editor.org>
Message-ID: <bf937f01-ee6e-fd0e-1e58-1917ca786129@rfc-editor.org>
Date: Fri, 16 Jun 2017 11:19:10 -0700
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.1.1
MIME-Version: 1.0
In-Reply-To: <0c97b073-80ca-9dd8-3f3e-30cc874a2a9d@gmail.com>
Content-Language: en-US
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-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Errors-To: rfc-interest-bounces@rfc-editor.org
Sender: rfc-interest <rfc-interest-bounces@rfc-editor.org>
On 6/14/17 5:03 PM, Brian E Carpenter wrote: > On 14/06/2017 20:37, Carsten Bormann wrote: >> On Jun 13, 2017, at 23:02, Heather Flanagan (RFC Series Editor) <rse@rfc-editor.org> wrote: >>> >>> I can see a situation, in a purely historic context, where this might be >>> unnecessary. >> >> (Ceterum censeo:) >> >> I believe it would be a good thing to clearly identify “historical”(*) references (as in: here you can find out how this document came to be the way it is) as a separate class from other “informative” (as in: here is more information that helps in processing the technical content of this document) ones. >> >> The rule being discussed would then apply to informative, not to historical, references. > > This triggers one of my hobby-horses, I'm afraid. > > If I refer to an I-D because it's useful reading but not yet published, I'm happy with it being tagged as "Work in progress". A smart reader may even have the idea to look for a corresponding RFC. > > If I refer to an I-D because it has historical value, I would prefer it to be tagged as "Unpublished draft" and have an exact version number (and date). Calling it "Work in progress" is either inappropriate or simply untrue. > > Today we have no metadata to separate the two cases. > 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. -Heather _______________________________________________ rfc-interest mailing list rfc-interest@rfc-editor.org https://www.rfc-editor.org/mailman/listinfo/rfc-interest
- [rfc-i] Fwd: New Version Notification for draft-f… Heather Flanagan (RFC Series Editor)
- [rfc-i] Errata Reference Format Julian Reschke
- [rfc-i] Referencing Emails Julian Reschke
- [rfc-i] Placement of Index Julian Reschke
- [rfc-i] Referencing Internet Drafts Julian Reschke
- [rfc-i] Referencing RFCs Julian Reschke
- [rfc-i] Referencing STDs and BCPs Julian Reschke
- Re: [rfc-i] Referencing Internet Drafts Julian Reschke
- Re: [rfc-i] Referencing RFCs Julian Reschke
- Re: [rfc-i] Placement of Index Martin J. Dürst
- Re: [rfc-i] Fwd: New Version Notification for dra… Julian Reschke
- Re: [rfc-i] Fwd: New Version Notification for dra… Heather Flanagan (RFC Series Editor)
- Re: [rfc-i] Errata Reference Format Heather Flanagan (RFC Series Editor)
- Re: [rfc-i] Errata Reference Format Julian Reschke
- Re: [rfc-i] Errata Reference Format Heather Flanagan (RFC Series Editor)
- Re: [rfc-i] Referencing Emails Heather Flanagan (RFC Series Editor)
- Re: [rfc-i] Placement of Index Heather Flanagan (RFC Series Editor)
- Re: [rfc-i] Referencing RFCs Heather Flanagan (RFC Series Editor)
- Re: [rfc-i] Referencing STDs and BCPs Heather Flanagan (RFC Series Editor)
- Re: [rfc-i] Referencing Internet Drafts Heather Flanagan (RFC Series Editor)
- Re: [rfc-i] Referencing RFCs Heather Flanagan (RFC Series Editor)
- Re: [rfc-i] Referencing STDs and BCPs Julian Reschke
- Re: [rfc-i] Referencing RFCs Julian Reschke
- Re: [rfc-i] Referencing Internet Drafts Julian Reschke
- Re: [rfc-i] Referencing Emails Julian Reschke
- Re: [rfc-i] Referencing Internet Drafts Carsten Bormann
- Re: [rfc-i] Referencing Internet Drafts Brian E Carpenter
- Re: [rfc-i] Referencing Internet Drafts Julian Reschke
- Re: [rfc-i] Referencing Internet Drafts Bob Hinden
- Re: [rfc-i] Referencing STDs and BCPs Heather Flanagan (RFC Series Editor)
- Re: [rfc-i] Referencing RFCs Heather Flanagan (RFC Series Editor)
- Re: [rfc-i] Referencing Emails Heather Flanagan (RFC Series Editor)
- Re: [rfc-i] Referencing Internet Drafts Heather Flanagan (RFC Series Editor)
- Re: [rfc-i] Referencing Internet Drafts Heather Flanagan (RFC Series Editor)
- Re: [rfc-i] Referencing STDs and BCPs Julian Reschke
- Re: [rfc-i] Referencing RFCs Julian Reschke
- Re: [rfc-i] Referencing Emails Julian Reschke
- Re: [rfc-i] Referencing Internet Drafts Julian Reschke
- Re: [rfc-i] Referencing Internet Drafts Jim Schaad
- Re: [rfc-i] Referencing Internet Drafts Paul Kyzivat
- Re: [rfc-i] Referencing Internet Drafts Heather Flanagan (RFC Series Editor)
- Re: [rfc-i] Referencing STDs and BCPs Heather Flanagan (RFC Series Editor)
- Re: [rfc-i] Referencing Emails Carsten Bormann
- Re: [rfc-i] Referencing Internet Drafts Heather Flanagan (RFC Series Editor)
- Re: [rfc-i] Referencing Internet Drafts Bob Hinden
- Re: [rfc-i] Referencing Internet Drafts Heather Flanagan (RFC Series Editor)
- Re: [rfc-i] Referencing Internet Drafts Paul Kyzivat
- Re: [rfc-i] Referencing STDs and BCPs Julian Reschke
- Re: [rfc-i] Referencing Internet Drafts Brian E Carpenter
- Re: [rfc-i] Referencing Internet Drafts Andrew Sullivan
- Re: [rfc-i] Referencing Internet Drafts Brian E Carpenter
- Re: [rfc-i] Referencing Internet Drafts Bob Hinden
- Re: [rfc-i] Fwd: New Version Notification for dra… Julian Reschke
- Re: [rfc-i] Fwd: New Version Notification for dra… Heather Flanagan (RFC Series Editor)
- Re: [rfc-i] Errata Reference Format Martin Thomson
- Re: [rfc-i] Errata Reference Format Heather Flanagan (RFC Series Editor)
- Re: [rfc-i] Errata Reference Format Julian Reschke