Re: [rfc-i] Referring to Internet Drafts -- retiring "Work in Progress"

Brian E Carpenter <brian.e.carpenter@gmail.com> Thu, 12 April 2018 23:46 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 158AC126CBF for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Thu, 12 Apr 2018 16:46:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.588
X-Spam-Level:
X-Spam-Status: No, score=-4.588 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, DKIM_SIGNED=0.1, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_DKIM_INVALID=0.01, URIBL_BLOCKED=0.001] 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 JsLgoZLede8F for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Thu, 12 Apr 2018 16:46:32 -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 6884A124D6C for <rfc-interest-archive-eekabaiReiB1@ietf.org>; Thu, 12 Apr 2018 16:46:32 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 4C505B8284E; Thu, 12 Apr 2018 16:46:29 -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 37C01B8284E for <rfc-interest@rfc-editor.org>; Thu, 12 Apr 2018 16:46:28 -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 arCkCFSZzeKY for <rfc-interest@rfc-editor.org>; Thu, 12 Apr 2018 16:46:26 -0700 (PDT)
Received: from mail-pf0-x22a.google.com (mail-pf0-x22a.google.com [IPv6:2607:f8b0:400e:c00::22a]) by rfc-editor.org (Postfix) with ESMTPS id B2301B8284D for <rfc-interest@rfc-editor.org>; Thu, 12 Apr 2018 16:46:26 -0700 (PDT)
Received: by mail-pf0-x22a.google.com with SMTP id p6so5165687pfn.4 for <rfc-interest@rfc-editor.org>; Thu, 12 Apr 2018 16:46:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:subject:to:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=uwcbARM/F6JxdAwqE6tQ8+SiLI/keCmy9v9O0Ng7oyQ=; b=k37nj2RB4Bs/xTt73vmaxkB+1jxD/llxgyhVKgRsudCbCPddXt5MZs3Rc9F7Upbl1q tJH6TT/oNUXdgganwlp9pFXobp2fu2dEQAQ2fBbbl0PrubGbaQzObghI7KNFdiEu4Muv eWXDO5sN/NrzadYqnkwlYgn8ItIylByMGombpC9PQ+UoWPPKjlLsdPuEYOlrEPI6+J/C eQZoPmN1D9JKNepTHYPQg1qY4OzZ/+Vw6oxit0xBfSIVzTBf5oPF8eSx+Y9y6n7zalou Q8OrQ26QBtgKUBbQzRI16c93/c1TOj+Bd2EM0ld8I3xP20MrO0LQQaPhRsdIswFbNvQ8 qR2w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:subject:to:references:from:message-id :date:user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=uwcbARM/F6JxdAwqE6tQ8+SiLI/keCmy9v9O0Ng7oyQ=; b=B0u2Ldx+RdP+CSBXkU8dWhj/x03A1Hu7gHO3v6jkXbf1AXZBwiL8EmzIi3bj+x9r/F 1+DTKIQ45usoc342Y211ASVe4fIGgW6uWSGfkIhkyk8ndm0pwJMn+UcU2Vv94fzyZ0bq fp0MOGqdUcb6ZUBcKYr6fy6j7wWfy6AkMGIYFYI9RMcTQM0gXb80y4MErFcOALrYTJNK e9HbPQaIOKsuTv49aCshIqRJid2KuiafqIrBfEjd7eDFLs/ooI29lBfdXFWZKAnarJqj 7qrhgHnMRVm5Ay4C/RH8csA3bXJSPkDDmXgfwqcdVaA6nVFJY1ZCK9vxRfSA4QmceeM2 ALKg==
X-Gm-Message-State: ALQs6tAJtK8pzjk23WOXNC9bG/GX1xEaO1DvUmNl69XAtM4A4SpJoP5+ biVtANfnfDuFuCHUmusnQV1IRw==
X-Google-Smtp-Source: AIpwx48dcPWMyF8jGr5uKCNj+wG06EkfdGPsDENU3hspLo1hYUrJVKRU+JbnjOGo6BdhMbDwl+Vc6w==
X-Received: by 10.98.210.7 with SMTP id c7mr9282584pfg.92.1523576787867; Thu, 12 Apr 2018 16:46:27 -0700 (PDT)
Received: from [192.168.178.26] ([118.148.68.60]) by smtp.gmail.com with ESMTPSA id a15sm8213771pgd.25.2018.04.12.16.46.24 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 12 Apr 2018 16:46:26 -0700 (PDT)
To: Adam Roach <adam@nostrum.com>, "rfc-interest@rfc-editor.org" <rfc-interest@rfc-editor.org>
References: <7adbf2cd-872c-2ebc-79d5-259c57bcc471@nostrum.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <1eafb781-8703-6fd0-fb98-c8e77a1ee9d7@gmail.com>
Date: Fri, 13 Apr 2018 11:46:30 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0
MIME-Version: 1.0
In-Reply-To: <7adbf2cd-872c-2ebc-79d5-259c57bcc471@nostrum.com>
Content-Language: en-US
Subject: Re: [rfc-i] Referring to Internet Drafts -- retiring "Work in Progress"
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="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-interest-bounces@rfc-editor.org
Sender: rfc-interest <rfc-interest-bounces@rfc-editor.org>

Hi,

I strongly support fixing this issue. But...

>    Note: It is acceptable to reference a standards-track specification
>    that may reasonably be expected to be published as an RFC using the
>    phrase "Internet Draft" without referencing an Internet-Draft.  This
>    may also be done in a standards track document itself as long as the
>    specification in which the reference is made would stand as a
>    complete and understandable document with or without the reference to
>    the "Internet Draft".

This doesn't cover all cases of "work in progress", unfortunately. Some of
the cases it doesn't cover are
a) A standards-track specification that is work in progress in another SDO.
b) A non-standards-track I-D of any kind, which is probably the
most common case today of "work in progress" citations.
c) Any other case where "work in progress" is in fact applicable.
Clearly, documents that are not I-Ds but are factually work in
progress should be cited as such.

Also, the first sentence doesn't need the phrase "without referencing an
Internet-Draft", which to my mind makes the sentence illogical.

I have an alternative suggestion. Leave the details to the RFC Editor
style guide. Then the new text only needs to say:

   Note: It is acceptable to reference a standards-track specification
   that may reasonably be expected to be published as an RFC.  This
   may also be done in a standards track document itself as long as the
   specification in which the reference is made would stand as a
   complete and understandable document with or without the reference.

(A more radical suggestion is to delete the paragraph completely.
I'm not sure we'd lose much.)

Regards
   Brian

On 13/04/2018 10:03, Adam Roach wrote:
> RFC 2026 (BCP 9) currently has the following text regarding the phrasing 
> that is to be used when referring to internet drafts:
> 
> 
>     Note: It is acceptable to reference a standards-track specification
>     that may reasonably be expected to be published as an RFC using the
>     phrase "Work in Progress"  without referencing an Internet-Draft.
>     This may also be done in a standards track document itself  as long
>     as the specification in which the reference is made would stand as a
>     complete and understandable document with or without the reference to
>     the "Work in Progress".
>   
> 
> In practice, not all internet drafts are still "in progress," although 
> there may still be value in referring to their contents. At the request 
> of the RFC Editor, I have put together a very small document that amends 
> RFC 2026 to allow referring to such documents using the more accurate 
> term "Internet Draft."
> 
> Please see <https://tools.ietf.org/html/draft-roach-id-cite-00>, and 
> provide feedback on this mailing list. Thanks!
> 
> /a
> 
> _______________________________________________
> 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