IETF Logo Mail Archive

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

Carsten Bormann <cabo@tzi.org> Fri, 28 April 2023 16: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 [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 175C2C1BED29; Fri, 28 Apr 2023 09:01:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rNv7eSILjZY1; Fri, 28 Apr 2023 09:01:01 -0700 (PDT)
Received: from smtp.zfn.uni-bremen.de (smtp.zfn.uni-bremen.de [134.102.50.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 30235C1BE894; Fri, 28 Apr 2023 09:01:00 -0700 (PDT)
Received: from [192.168.217.124] (p548dc9a4.dip0.t-ipconnect.de [84.141.201.164]) (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 4Q7HQL2cqfzDCcF; Fri, 28 Apr 2023 18:00:58 +0200 (CEST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <644BE7BD.4020004@btconnect.com>
Date: Fri, 28 Apr 2023 18:00:58 +0200
Cc: Alexis Rossi <rsce@rfc-editor.org>, rfc-interest@rfc-editor.org
X-Mao-Original-Outgoing-Id: 704390457.901183-b27256179f0341615bf49cac96e3c073
Content-Transfer-Encoding: quoted-printable
Message-Id: <1D73D198-D0B0-4B33-B523-077A0DD82FD2@tzi.org>
References: <E024D9AC-2B92-4720-9713-519592D2362B@rfc-editor.org> <79E6CBE7-FC51-468A-B3F7-AC16FDCAC489@tzi.org> <644BE7BD.4020004@btconnect.com>
To: tom petch <daedulus@btconnect.com>
X-Mailer: Apple Mail (2.3608.120.23.2.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-interest/O11hMGF_ZEFx6x73-i-C6_xlDvQ>
Subject: Re: [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 16:01:06 -0000

On 2023-04-28, at 17:35, tom petch <daedulus@btconnect.com> wrote:
> 
>> I think we also should look at targets for links used in IANA registries.
> 
> Why?
> 
> When I review and I-D, I always encourage the authors to insert a URL to the registry since the choice of name for the registry is sometimes, often, not chosen with ease of use in mind.  I see such URL in documents approved by the IESG.

I wasn’t talking about links to IANA registries (which are also interesting, but more like under our control), but about the links in the registries.  All 6412 of them.

http://standard.pictel.com/ftp/avc-site/0206_Bru/AVD-2198.zip
http://standards.ieee.org/regauth/ethertype/eth.txt
http://www.sil.org/iso639-3/cr_files/639-3_ChangeRequests_2011_Summary.pdf

The first one is now an empty HTML page.
The second one now points to general information and no longer to the actual document, so it is not sufficient to check them from a bot (unless that alerts to major changes).
Some of these, like the third, are amazingly still working!
Obviously, I haven’t checked all of them.

Grüße, Carsten

v2.23.0 | Report a Bug | By Email