Re: [Tools-discuss] Setting replaced-by

Robert Sparks <> Tue, 23 February 2021 17:29 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 77F5A3A0C3A for <>; Tue, 23 Feb 2021 09:29:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.079
X-Spam-Status: No, score=-2.079 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_BLOCKED=0.001, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id DUjBFrfDB5iB for <>; Tue, 23 Feb 2021 09:29:11 -0800 (PST)
Received: from ( [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 29CE93A0C33 for <>; Tue, 23 Feb 2021 09:29:11 -0800 (PST)
Received: from unformal.localdomain ([]) (authenticated bits=0) by (8.16.1/8.16.1) with ESMTPSA id 11NHT86D070238 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Tue, 23 Feb 2021 11:29:08 -0600 (CST) (envelope-from
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple;; s=default; t=1614101349; bh=tYdSOqu1b9vXHNSO5ZFqDI9AMByLPg9T2njsXx2Oc0s=; h=Subject:To:Cc:References:From:Date:In-Reply-To; b=VfSlbB8jdS6uiaIcInd8oeTMuFFwLHIaztfSJzKcKSAXZgHuzz+zdC74VUbFNHsiA d2BIS5qcsPuF9dg2H164W6WwLke9AhGZJT7uHGxuVuALAAroNnFQb7KBY8zkBEGLZ1 k9n9iQCKsQq5Oze2shpV4sdxvQyhwl1TOK+SK6bA=
X-Authentication-Warning: Host [] claimed to be unformal.localdomain
To: Carsten Bormann <>
References: <> <> <> <>
From: Robert Sparks <>
Message-ID: <>
Date: Tue, 23 Feb 2021 11:29:03 -0600
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.7.1
MIME-Version: 1.0
In-Reply-To: <>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <>
Subject: Re: [Tools-discuss] Setting replaced-by
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF Tools Discussion <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 23 Feb 2021 17:29:12 -0000

On 2/23/21 11:19 AM, Carsten Bormann wrote:
> On 2021-02-23, at 16:29, Robert Sparks <> wrote:
>> On 2/23/21 8:40 AM, Russ Housley wrote:
>>> Carsten:
>>> The Datatracker has both replaces and replaced-by pointers.
>> The datatracker only stores replaces pointers - it computes replaced-by.
>> Editing the relationship is only currently possible at the document that does the replacing. And I think that's right. Carsten, for the use case you're talking about, you will almost certainly be able to operate on the document that is doing the replacing or know someone who can.
> My use case actually was as an author of the replaced document.
> So I’ll have to talk to the author of the replacing document, and it’s still somehow hard for them to get this status in there (for good reasons!).
> Gets the whole thing in the “not worth the effort” category too easily.
>> Replaces is many-to-many. A document can replace several other documents. A document can be replaced by several other documents. Keeping a clear understanding of authority for replaces requires careful attention.
> I agree.
> I was just trying to make it easier for the author of a replaced document to acknowledge that their work has been superseded.
> (If we need a rendezvous here to make the relationship happen, that’s fine too.)
How about "suggests has been replaced by" that sends a note to the 
> Grüße, Carsten