Re: [rfc-i] Referencing Internet Drafts

"Heather Flanagan (RFC Series Editor)" <rse@rfc-editor.org> Fri, 16 June 2017 19:49 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 E633B13183B for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Fri, 16 Jun 2017 12:49:45 -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 9DmGYN2-8_Kr for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Fri, 16 Jun 2017 12:49:44 -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 2471E131618 for <rfc-interest-archive-eekabaiReiB1@ietf.org>; Fri, 16 Jun 2017 12:49:44 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 8A960B80D78; Fri, 16 Jun 2017 12:49:28 -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 1C6EAB80D78 for <rfc-interest@rfc-editor.org>; Fri, 16 Jun 2017 12:49:27 -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 emkI7MmU0r34 for <rfc-interest@rfc-editor.org>; Fri, 16 Jun 2017 12:49:26 -0700 (PDT)
Received: from mail.amsl.com (c8a.amsl.com [4.31.198.40]) by rfc-editor.org (Postfix) with ESMTPS id 15752B80D77 for <rfc-interest@rfc-editor.org>; Fri, 16 Jun 2017 12:49:26 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 250A81CA532; Fri, 16 Jun 2017 12:49:28 -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 YKgI-x6x_snd; Fri, 16 Jun 2017 12:49:28 -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 E5E091CA42D; Fri, 16 Jun 2017 12:49:27 -0700 (PDT)
To: Bob Hinden <bob.hinden@gmail.com>
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> <e86fff04-6fa6-8f32-7ee6-cf74873576ff@gmx.de> <030DC553-3338-476F-A077-529F0193BEF1@gmail.com> <5aa0cab7-d5cc-a8e0-1b1e-465067d5fa13@rfc-editor.org> <2F061E95-0D7D-478C-8CCB-4B501F157F61@gmail.com>
From: "Heather Flanagan (RFC Series Editor)" <rse@rfc-editor.org>
Message-ID: <923e7dca-2394-f17a-50cc-f4bd21a7e4d5@rfc-editor.org>
Date: Fri, 16 Jun 2017 12:49:39 -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: <2F061E95-0D7D-478C-8CCB-4B501F157F61@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>
Cc: rfc-interest@rfc-editor.org
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/16/17 12:37 PM, Bob Hinden wrote:
> Heather,
>
>> On Jun 16, 2017, at 11:16 AM, Heather Flanagan (RFC Series Editor) <rse@rfc-editor.org> wrote:
>>
>> On 6/15/17 11:38 AM, Bob Hinden wrote:
>>>> On Jun 15, 2017, at 1:37 AM, Julian Reschke <julian.reschke@gmx.de> wrote:
>>>>
>>>> On 2017-06-15 02:03, Brian E Carpenter wrote:
>>>>> ...
>>>>> 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.
>>>>> ...
>>>> +1
>>>>
>>> I tend to agree as well.  Though I am not sure “unpublished draft” is exactly right since the draft is available online.  We treat Internet Drafts as temporary, and at the same time permanent.  Starting to seem more like the later.
>>>
>>> Why don’t we include a link to the Internet Draft in the reference like we do for RFCs?
>>>
>>>
>> Historically, it's to enforce the face that I-Ds are not equal to RFCs,
>> and because I-D URLs were ephemeral (since I-Ds would disappear after
>> six months). The latter is no longer true. How do you feel about the former?
> Certainly I-Ds are not equal to RFCs, though there are a bunch of sub cases depending on if the ID is just an individual submission w/ no review, an active w.g. document, or approved by a stream for publication.  I conclude that calling them “work in progress” may or may not be correct when an RFC is published with a reference to an ID, and certainly not true 10 years later.
>
> I don’t think we want to have labels for each stage of an IDs life because it changes over time.  Perhaps calling them something like “working draft” or similar might be better than “work in progress”.  It doesn’t imply it is changing.

Process question: Does this suggest we need to do something special to
update RFC 2026 (which is where the "Work in Progress" term for I-Ds
comes from)? (See Section 2.2).

>
> Since they don’t appear to be ephemeral any longer, including a link in the reference might be useful.

I'm fine with that.

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