Re: [Tools-discuss] Setting replaced-by

Carsten Bormann <> Tue, 23 February 2021 17:19 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 6428A3A0BEB for <>; Tue, 23 Feb 2021 09:19:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id fTCmo2Rp6W7M for <>; Tue, 23 Feb 2021 09:19:21 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 52B653A0BE9 for <>; Tue, 23 Feb 2021 09:19:18 -0800 (PST)
Received: from [] ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPSA id 4DlQl82FdjzyY6; Tue, 23 Feb 2021 18:19:16 +0100 (CET)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.\))
From: Carsten Bormann <>
In-Reply-To: <>
Date: Tue, 23 Feb 2021 18:19:15 +0100
X-Mao-Original-Outgoing-Id: 635793555.703537-44f07afd089b7d664de4333270fcbaed
Content-Transfer-Encoding: quoted-printable
Message-Id: <>
References: <> <> <>
To: Robert Sparks <>
X-Mailer: Apple Mail (2.3608.
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:19:23 -0000

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.)

Grüße, Carsten