Re: [rfc-i] Citing internet drafts

Paul Kyzivat <pkyzivat@alum.mit.edu> Tue, 03 September 2019 15:01 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 15844120019 for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Tue, 3 Sep 2019 08:01:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.951
X-Spam-Level:
X-Spam-Status: No, score=-4.951 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=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 PHUZi43HkQ3m for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Tue, 3 Sep 2019 08:01:42 -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 740E1120018 for <rfc-interest-archive-eekabaiReiB1@ietf.org>; Tue, 3 Sep 2019 08:01:42 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id A6B5FB80B36; Tue, 3 Sep 2019 08:01:21 -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 A58FEB80B36 for <rfc-interest@rfc-editor.org>; Tue, 3 Sep 2019 08:01:19 -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 MgJq0-GPBeCe for <rfc-interest@rfc-editor.org>; Tue, 3 Sep 2019 08:01:18 -0700 (PDT)
Received: from outgoing-alum.mit.edu (outgoing-alum.mit.edu [18.7.68.33]) by rfc-editor.org (Postfix) with ESMTPS id 23FD6B80B2F for <rfc-interest@rfc-editor.org>; Tue, 3 Sep 2019 08:01:16 -0700 (PDT)
Received: from Kokiri.localdomain (c-24-62-227-142.hsd1.ma.comcast.net [24.62.227.142]) (authenticated bits=0) (User authenticated as pkyzivat@ALUM.MIT.EDU) by outgoing-alum.mit.edu (8.14.7/8.12.4) with ESMTP id x83F1XG6018042 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT) for <rfc-interest@rfc-editor.org>; Tue, 3 Sep 2019 11:01:35 -0400
To: rfc-interest@rfc-editor.org
References: <9dca07bd-293c-7f1e-0cbc-c0a9907d09c2@gmx.de>
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
Message-ID: <f9792cff-da1c-a779-629b-cd8b1480e63c@alum.mit.edu>
Date: Tue, 03 Sep 2019 11:01:33 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:60.0) Gecko/20100101 Thunderbird/60.8.0
MIME-Version: 1.0
In-Reply-To: <9dca07bd-293c-7f1e-0cbc-c0a9907d09c2@gmx.de>
Content-Language: en-US
Subject: Re: [rfc-i] Citing internet drafts
X-BeenThere: rfc-interest@rfc-editor.org
X-Mailman-Version: 2.1.29
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: base64
Content-Type: text/plain; charset="utf-8"; Format="flowed"
Errors-To: rfc-interest-bounces@rfc-editor.org
Sender: rfc-interest <rfc-interest-bounces@rfc-editor.org>

IIUC the restriction that references to drafts must be informational 
only applies to *RFC*s? It is important that *drafts* be able to 
normatively reference other drafts as they progress in parallel, with 
the limitation that they will be forced to progress together, at which 
point they will become references to RFCs. Right?

	Thanks,
	Paul

On 9/2/19 9:37 AM, Julian Reschke wrote:
> Hi there,
> 
> I just saw
> <https://trac.tools.ietf.org/tools/xml2rfc/trac/changeset/3263>, which
> in turn mentions draft-flanagan-7322bis-03.
> 
> <https://tools.ietf.org/html/draft-flanagan-7322bis-03#section-4.8.6.4>
> says:
> 
>> 4.8.6.4.  Referencing Internet-Drafts
>>
>>    References to Internet Drafts may only appear as informative
>>    references.  Given that several revisions of an I-D may be produced
>>    in a short time frame, references must include the posting date
>>    (month and year), the full Internet-Draft file name (including the
>>    version number), and the phrase "Internet Draft".  Authors may
>>    reference multiple versions of an I-D.  If the referenced I-D was
>>    also later published as an RFC, then that RFC must also be listed.
>>
>>    [SYMBOLIC-TAG]  Last name, First initial., Ed. (if applicable) and
>>    First initial.  Last name, Ed. (if applicable), "I-D Title", Internet
>>    Draft, draft-string-NN, Month Year.
>>
>>    Example:
>>
>>    [RFC-STYLE] Flanagan, H. and S.  Ginoza, "RFC Style Guide", Internet
>>    Draft, draft-flanagan-style-01, June 2013.
> 
> This is a change from 7322, which had
> (<https://tools.ietf.org/html/rfc7322#section-4.8.6.4>):
> 
>> 4.8.6.4.  Referencing Internet-Drafts
>>
>>    References to Internet-Drafts may only appear as informative
>>    references.  Given that several revisions of an I-D may be produced
>>    in a short time frame, references must include the posting date
>>    (month and year), the full Internet-Draft file name (including the
>>    version number), and the phrase "Work in Progress".  Authors may
>>    reference multiple versions of an I-D.  If the referenced I-D was
>>    also later published as an RFC, then that RFC must also be listed.
>>
>>       [SYMBOLIC-TAG]  Last name, First initial., Ed. (if applicable)
>>                       and First initial. Last name, Ed. (if
>>                       applicable), "I-D Title", Work in Progress,
>>                       draft-string-NN, Month Year.
>>
>>      Example:
>>
>>       [RFC-STYLE] Flanagan, H. and S. Ginoza, "RFC Style Guide",
>>                   Work in Progress, draft-flanagan-style-01,
>>                   June 2013.
> 
> I personally find this an improvement, but two questions come to mind:
> 
> 1.) When is this change supposed to go in effect?
> 
> 2.) Isn't this in conflict with today's Internet Draft boilerplate, wich
> clearly says: 'It is inappropriate to use Internet-Drafts as reference
> material or to cite them other than as "work in progress."'. Is that
> clause going to change as well?
> 
> Best regards, Julian
> _______________________________________________
> 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