Re: [rfc-i] Referencing Internet Drafts

Bob Hinden <bob.hinden@gmail.com> Fri, 16 June 2017 19:38 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 2DE75131833 for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Fri, 16 Jun 2017 12:38:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.891
X-Spam-Level:
X-Spam-Status: No, score=-3.891 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, 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=gmail.com
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 OiXMk04lTtzJ for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Fri, 16 Jun 2017 12:38:02 -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 27AE3131618 for <rfc-interest-archive-eekabaiReiB1@ietf.org>; Fri, 16 Jun 2017 12:38:02 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 92E5FB80D2A; Fri, 16 Jun 2017 12:37:46 -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 B837FB80D2A; Fri, 16 Jun 2017 12:37:45 -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=gmail.com
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 W3eQmowgKdpn; Fri, 16 Jun 2017 12:37:44 -0700 (PDT)
Received: from mail-pf0-x22f.google.com (mail-pf0-x22f.google.com [IPv6:2607:f8b0:400e:c00::22f]) by rfc-editor.org (Postfix) with ESMTPS id 1975FB80D29; Fri, 16 Jun 2017 12:37:44 -0700 (PDT)
Received: by mail-pf0-x22f.google.com with SMTP id 83so26637863pfr.0; Fri, 16 Jun 2017 12:37:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=Tyj3udFe/ZA/QlFDeFQqRrkQAf7rGktZuSMfdfGixhM=; b=K9OCwNx9jR7wmGkdiyL5qBK3CD0m2acIVz3MKpP0/vitO+CAgjsZANrMQ5pHGAqJKC aazJA9FFccVT1Bxt3/tAggrocm50P/VAqgXToXh+0KOq5l80dBRDO5u9JcD/+Jegzjuw ABPk9BsPZh16WjxAO/W4hguKm5E/hFYg0jBnNASK53NPMw12kILBb6lJ06vvc9qEOcM4 2E10UHTk/gk0hDDaSEA4dyr08pvJdyEH3f0n65YgggBjiFg/i82h+ogSAGZpBlHGpycg 5SD37Ht5mJVL3+L1aSlmtz4nv5NWjeFc9N+le8+vaL0K1OHucvxQr/M/g+wJcKafbVT7 YJnQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=Tyj3udFe/ZA/QlFDeFQqRrkQAf7rGktZuSMfdfGixhM=; b=NFKLcyyNNmdrY9WaEYjFKPoz7CSu4k3hxBYIhQPLdVHwXq7ATdPt/Ud/BjpgHL5jud BpYFPN0SDsIH2FNv1RWeAtQIWOUvOv4dhvwRYlJv3MCQcUTRVGyk1FECHYUuTpKCwMua KhkJVnFipN9V3dWed3t/fAtf2pXZulRenhg0E4otuqf5okvf/sc9kdIOXahxVWFykREZ hafaTI+PH6G6tgBF7hecvDSXhKQP2mdJVwia5xgeN38wD8duU396sXFkSEZSr7EnMnKB wvDdZX3Zf+YEkwbz//ZiFXrgshqCPA8uBXnxr71p8pxCOwEsx4x93wJdgRdTXVtaIDPT H72g==
X-Gm-Message-State: AKS2vOzb9gO1XNHPXzpE00E9K6JftiLV/lOlIyEVcqiRPO9Gd8WhTZ5s GoJT8gXSlZgoaqJZOHFX0g==
X-Received: by 10.84.229.79 with SMTP id d15mr5655270pln.4.1497641878173; Fri, 16 Jun 2017 12:37:58 -0700 (PDT)
Received: from [192.168.1.137] ([216.9.107.110]) by smtp.gmail.com with ESMTPSA id h71sm6741420pfk.126.2017.06.16.12.37.54 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 16 Jun 2017 12:37:56 -0700 (PDT)
From: Bob Hinden <bob.hinden@gmail.com>
Message-Id: <2F061E95-0D7D-478C-8CCB-4B501F157F61@gmail.com>
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Date: Fri, 16 Jun 2017 12:37:30 -0700
In-Reply-To: <5aa0cab7-d5cc-a8e0-1b1e-465067d5fa13@rfc-editor.org>
To: "Heather Flanagan (RFC Series Editor)" <rse@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> <e86fff04-6fa6-8f32-7ee6-cf74873576ff@gmx.de> <030DC553-3338-476F-A077-529F0193BEF1@gmail.com> <5aa0cab7-d5cc-a8e0-1b1e-465067d5fa13@rfc-editor.org>
X-Mailer: Apple Mail (2.3273)
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, Bob Hinden <bob.hinden@gmail.com>
Content-Type: multipart/mixed; boundary="===============0774388060360773228=="
Errors-To: rfc-interest-bounces@rfc-editor.org
Sender: rfc-interest <rfc-interest-bounces@rfc-editor.org>

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.

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

Bob



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

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