IETF Logo Mail Archive

Re: [xml2rfc] referencing an old ID as expired

Robert Moskowitz <rgm@htt-consult.com> Tue, 05 May 2020 20:07 UTC

Return-Path: <rgm@htt-consult.com>
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 5B9AB3A099C for <xml2rfc@ietfa.amsl.com>; Tue, 5 May 2020 13:07:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-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 hxXgoHt2WooV for <xml2rfc@ietfa.amsl.com>; Tue, 5 May 2020 13:07:01 -0700 (PDT)
Received: from z9m9z.htt-consult.com (z9m9z.htt-consult.com [23.123.122.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C47A53A099A for <xml2rfc@ietf.org>; Tue, 5 May 2020 13:07:01 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by z9m9z.htt-consult.com (Postfix) with ESMTP id 5157E62300; Tue, 5 May 2020 16:06:02 -0400 (EDT)
X-Virus-Scanned: amavisd-new at htt-consult.com
Received: from z9m9z.htt-consult.com ([127.0.0.1]) by localhost (z9m9z.htt-consult.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id urKjlqcxWdMj; Tue, 5 May 2020 16:05:52 -0400 (EDT)
Received: from lx140e.htt-consult.com (unknown [192.168.160.12]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by z9m9z.htt-consult.com (Postfix) with ESMTPSA id 046E1622FA; Tue, 5 May 2020 16:05:50 -0400 (EDT)
To: Paul Kyzivat <pkyzivat@alum.mit.edu>, xml2rfc@ietf.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>
From: Robert Moskowitz <rgm@htt-consult.com>
Message-ID: <fa59152b-76cc-9335-66b9-c3160d740d81@htt-consult.com>
Date: Tue, 05 May 2020 16:05:45 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.5.0
MIME-Version: 1.0
In-Reply-To: <04138b58-b7cb-b6b7-7d31-8025a5720902@alum.mit.edu>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/BXBRPa1fVwsMjOHSPZywcf_Ju5o>
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 20:07:05 -0000


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.

The other draft is dead and not going to restart.  However, it also 
presented this feature and thus part of the feature discussion.

v2.23.0 | Report a Bug | By Email