Re: [rfc-i] Referring to Internet Drafts -- retiring "Work in Progress"
Martin Thomson <martin.thomson@gmail.com> Fri, 13 April 2018 00:09 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 373B61277BB for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Thu, 12 Apr 2018 17:09:55 -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 wqATByrh7NXd for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Thu, 12 Apr 2018 17:09:53 -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 5719E124D6C for <rfc-interest-archive-eekabaiReiB1@ietf.org>; Thu, 12 Apr 2018 17:09:53 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 1DD72B82880; Thu, 12 Apr 2018 17:09:51 -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 A228DB82880 for <rfc-interest@rfc-editor.org>; Thu, 12 Apr 2018 17:09:49 -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 GfcKuKIn4sm6 for <rfc-interest@rfc-editor.org>; Thu, 12 Apr 2018 17:09:48 -0700 (PDT)
Received: from mail-oi0-x22c.google.com (mail-oi0-x22c.google.com [IPv6:2607:f8b0:4003:c06::22c]) by rfc-editor.org (Postfix) with ESMTPS id 1DE6FB8287F for <rfc-interest@rfc-editor.org>; Thu, 12 Apr 2018 17:09:48 -0700 (PDT)
Received: by mail-oi0-x22c.google.com with SMTP id 188-v6so6868347oih.8 for <rfc-interest@rfc-editor.org>; Thu, 12 Apr 2018 17:09:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=+m7qId7SBYW/fNhiMEd/pw+y8Eyq+gQXyiMuzdQXlYg=; b=XHBJRzyPlm3S/KWC49Tyso2Er0uNYUNEEVJyxYbhBQRQMRHZSW3gvtSt5URR6Ozz+P 2hhfEK0dQPzWQPlH02+7hti5mja1VBH39Od3GsFbuouOBdJnO0pGDyT8HZoNoSsiAKoD 4qzBEH4BwONOk16ElDsTmju04oPDMd9wptcG0FsnXOTT8Jy/njKXditWxCoPBEvWZ+Gx lt536iaaOUgLUZJOMzun+e+cAp2arsfHCnDHT6ZMoMC++jXpd/rtpD9mWiK3mL0BwHoV hhDqn65K2lLPumcesOKF+UWIbOrWRHLNahZygTdhWvNy3/RSs0lVop+PsCq6XC8ltY/y IiRw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=+m7qId7SBYW/fNhiMEd/pw+y8Eyq+gQXyiMuzdQXlYg=; b=IobvSSTflT6aPqlLCcCaPZK2SWyyPYvYoKzcgx/f7goTTaN8JJSnCqIsWx72WBSo8c Io+tu/TIm022E/L/u/NbaTsGe3IjeLJ7GQXohAbxtzNZ6AjBS2MVbFc7SRxPL0DdfV4d d+mNZqYcnffuu1UN3dSqZFYVaY/c0pdSvxPhkEfrEC7x6WpHf+wp9RzO014RANZtdSA+ CeEafoPYqOCLCz29ZvYzF5du/KcebU3U9oqgaA/2PkbxezibLxIQwnaRCrfS3wzbHr+c /0yb4X64BwFLqJTE6+w0r62G988JkTYRtcqRT5XUETS8WyJ733HykOpp1z9ywsqirrcm CIjg==
X-Gm-Message-State: ALQs6tC7+NNzsM2a/Y1ljGOQma6z81KAHM7jNufcen7QMp39bh5naWkx sC8/gT6TqxngvKDZ6fW3LJ0w9se/G/pn1ZKwaoY=
X-Google-Smtp-Source: AIpwx491qMNz1+q4SFOrCEXC5QsofS0atiSTgwmImFpuwsM3i9zzBPCG3665ELb+Oa0GpqunlgqbiUkEDXREQL8UF7E=
X-Received: by 2002:aca:524c:: with SMTP id g73-v6mr6911953oib.144.1523578189324; Thu, 12 Apr 2018 17:09:49 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a9d:ac7:0:0:0:0:0 with HTTP; Thu, 12 Apr 2018 17:09:48 -0700 (PDT)
In-Reply-To: <1eafb781-8703-6fd0-fb98-c8e77a1ee9d7@gmail.com>
References: <7adbf2cd-872c-2ebc-79d5-259c57bcc471@nostrum.com> <1eafb781-8703-6fd0-fb98-c8e77a1ee9d7@gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
Date: Fri, 13 Apr 2018 10:09:48 +1000
Message-ID: <CABkgnnVvejj_VwPUraOw9ufumbOisR8h-5FiyR2iu0601Wy4yw@mail.gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
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>
Cc: "rfc-interest@rfc-editor.org" <rfc-interest@rfc-editor.org>
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>
The idea of lifting these sorts of things out of the rather-hard-to-change place they exist (BCPs) and into the style guide or locations more amenable to change is an improvement. On Fri, Apr 13, 2018 at 9:46 AM, Brian E Carpenter <brian.e.carpenter@gmail.com> wrote: > 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 _______________________________________________ rfc-interest mailing list rfc-interest@rfc-editor.org https://www.rfc-editor.org/mailman/listinfo/rfc-interest
- [rfc-i] Referring to Internet Drafts -- retiring … Adam Roach
- Re: [rfc-i] Referring to Internet Drafts -- retir… Brian E Carpenter
- Re: [rfc-i] Referring to Internet Drafts -- retir… Martin Thomson
- Re: [rfc-i] Referring to Internet Drafts -- retir… casperssidekick