[rfc-i] IANA, too (Re: archiving outlinks in RFCs)

Carsten Bormann <cabo@tzi.org> Fri, 28 April 2023 09:01 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: rfc-interest@ietfa.amsl.com
Delivered-To: rfc-interest@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 65D56C151B24; Fri, 28 Apr 2023 02:01:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.888
X-Spam-Status: No, score=-6.888 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, T_SPF_TEMPERROR=0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id YB9hMv3JELu1; Fri, 28 Apr 2023 02:01:17 -0700 (PDT)
Received: from smtp.zfn.uni-bremen.de (smtp.zfn.uni-bremen.de [IPv6:2001:638:708:32::21]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0D877C151B13; Fri, 28 Apr 2023 02:01:15 -0700 (PDT)
Received: from [] (p548dc9a4.dip0.t-ipconnect.de []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4Q76611shszDChs; Fri, 28 Apr 2023 11:01:13 +0200 (CEST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <E024D9AC-2B92-4720-9713-519592D2362B@rfc-editor.org>
Date: Fri, 28 Apr 2023 11:01:12 +0200
Cc: rfc-interest@rfc-editor.org
X-Mao-Original-Outgoing-Id: 704365272.7359999-10bcb5312ac32ff9cde6cdff55d9b787
Content-Transfer-Encoding: quoted-printable
Message-Id: <79E6CBE7-FC51-468A-B3F7-AC16FDCAC489@tzi.org>
References: <E024D9AC-2B92-4720-9713-519592D2362B@rfc-editor.org>
To: Alexis Rossi <rsce@rfc-editor.org>
X-Mailer: Apple Mail (2.3608.
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-interest/RAaVYj2Q05mssOLyt3OvaOM-76w>
Subject: [rfc-i] IANA, too (Re: archiving outlinks in RFCs)
X-BeenThere: rfc-interest@rfc-editor.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "A list for discussion of the RFC series and RFC Editor functions." <rfc-interest.rfc-editor.org>
List-Unsubscribe: <https://mailman.rfc-editor.org/mailman/options/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfc-interest/>
List-Post: <mailto:rfc-interest@rfc-editor.org>
List-Help: <mailto:rfc-interest-request@rfc-editor.org?subject=help>
List-Subscribe: <https://mailman.rfc-editor.org/mailman/listinfo/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Apr 2023 09:01:23 -0000

> On 2023-04-25, at 20:50, Alexis Rossi <rsce@rfc-editor.org> wrote:
> The first thing I wanted to do was just make sure we were archiving these outlinks somewhere.

While we are discussing archiving link targets and making these targets accessible:

I think we also should look at targets for links used in IANA registries.

(Not an rfc-i issue, but probably a useful part of a solution.)

Grüße, Carsten