Re: [xml2rfc] referencing an old ID as expired

Carsten Bormann <cabo@tzi.org> Tue, 05 May 2020 21:16 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7F99D3A0B7C for <xml2rfc@ietfa.amsl.com>; Tue, 5 May 2020 14:16:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, 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 9VDhVoHtT1P2 for <xml2rfc@ietfa.amsl.com>; Tue, 5 May 2020 14:16:38 -0700 (PDT)
Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 22DE33A0B7D for <xml2rfc@ietf.org>; Tue, 5 May 2020 14:16:37 -0700 (PDT)
Received: from [172.16.42.112] (p548DCD70.dip0.t-ipconnect.de [84.141.205.112]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 49Gswh0LGSzyXV; Tue, 5 May 2020 23:16:35 +0200 (CEST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <dcd5faae-3c1d-0d40-ed1f-5a172e08bb50@gmail.com>
Date: Tue, 05 May 2020 23:16:35 +0200
Cc: Robert Moskowitz <rgm@htt-consult.com>, xml2rfc@ietf.org
X-Mao-Original-Outgoing-Id: 610406195.231038-e3798b0d28f92268d960c356cf2853b1
Content-Transfer-Encoding: quoted-printable
Message-Id: <F7B64D08-A659-4D4D-83B1-79FF2CE0FC6F@tzi.org>
References: <781a50a7-5faa-1043-56b2-f52b5ac91a80@htt-consult.com> <0ba7aad8-05c2-ad91-9c36-20d58ad5c082@gmx.de> <04138b58-b7cb-b6b7-7d31-8025a5720902@alum.mit.edu> <fa59152b-76cc-9335-66b9-c3160d740d81@htt-consult.com> <dcd5faae-3c1d-0d40-ed1f-5a172e08bb50@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.3608.80.23.2.2)
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/i1sIXynYJzzMqn_aU89ceykgIPk>
Subject: Re: [xml2rfc] referencing an old ID as expired
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xml2rfc/>
List-Post: <mailto:xml2rfc@ietf.org>
List-Help: <mailto:xml2rfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 May 2020 21:16:43 -0000

On 2020-05-05, at 22:55, Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
> 
> On 06-May-20 08:05, Robert Moskowitz wrote:
>> 
>> 
>> On 5/5/20 3:35 PM, Paul Kyzivat wrote:
>>> On 5/5/20 11:12 AM, Julian Reschke wrote:
>>>> On 05.05.2020 16:49, Robert Moskowitz wrote:
>>>>> I want to reference an old ID for various reasons.  The ID is expired
>>>>> and no xml.  So I created my own ref section:
>>> 
>>> I don't see much point in highlighting the fact that it is expired in 
>>> the reference. *Any* time you reference a draft, even if it is active 
>>> at the time you publish your document then it can eventually become 
>>> expired. In some sense it remains a work in progress after it expires, 
>>> it simply isn't making very much progress.
>>> 
>>> And after a draft has expired you can still post a next version of it.
>>> 
>>> Seems to be a distinction without a difference.
>> 
>> One draft had a feature which was later removed and never made it into 
>> the rfc.  I wanted to reference the last draft with that feature for 
>> discussion purposes.
> 
> That's fine, but doesn't change the rule that I-Ds are cited as "work
> in progress", which is as old as the hills and has been re-asserted
> several times by the RFC Editor.

The place that cites the reference will need to provide the information whether the referenced draft is considered by the authors of the current draft to be

* active [it might still be expired, because the update period increased to over 6 months, and it may expire while the current draft is sitting in the repo]
* abandoned (no successor)
* superseded (we try to capture this in the datatracker as “replaced”, but that is manual work, it also doesn’t quite cover all the ways of superseding a previous draft)

The bibliography entry itself is agnostic of this view (*).

“Work in Progress” is a bit like “Proposed Standard”: 
It means something very different in the IETF than outside in normal English.

> I can't remember why, but I once needed to cite two different versions
> of the same I-D; that required some contortions in the xml, but they were
> certainly both listed as "work in progress".

Yeah, that is a misfeature of the bibxml library.  Easily worked around with kramdown-rfc.

Grüße, Carsten

(*) Ceterum censeo, not about the reference but about the place it appears in: It would really be useful to have a third category of references in RFCs that identifies *why* something is referenced, beyond normative and informative: historical.  But that is yet another dimension.  Yes, I know that historical can be lumped under informative, but this structure has more meaning to it than being used by the RFC editor to quarantine an RFC in the queue while its normative references aren’t done yet.

> 
> Stay well,
> 
>    Brian
> 
>> 
>> The other draft is dead and not going to restart.  However, it also 
>> presented this feature and thus part of the feature discussion.
>> 
>> 
>> _______________________________________________
>> xml2rfc mailing list
>> xml2rfc@ietf.org
>> https://www.ietf.org/mailman/listinfo/xml2rfc
>> 
> 
> _______________________________________________
> xml2rfc mailing list
> xml2rfc@ietf.org
> https://www.ietf.org/mailman/listinfo/xml2rfc