IETF Logo Mail Archive

Re: [rfc-i] archiving outlinks in RFCs

Michael Richardson <mcr+ietf@sandelman.ca> Wed, 26 April 2023 17:12 UTC

Return-Path: <mcr+ietf@sandelman.ca>
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 57C3DC14CE4F for <rfc-interest@ietfa.amsl.com>; Wed, 26 Apr 2023 10:12:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.397
X-Spam-Level:
X-Spam-Status: No, score=-4.397 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, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=sandelman.ca
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 Fyuh3-jHUe7U for <rfc-interest@ietfa.amsl.com>; Wed, 26 Apr 2023 10:12:11 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 739FDC14CE2C for <rfc-interest@rfc-editor.org>; Wed, 26 Apr 2023 10:12:11 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id A937638994; Wed, 26 Apr 2023 13:30:05 -0400 (EDT)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id IPnPvz4Btv9Q; Wed, 26 Apr 2023 13:30:05 -0400 (EDT)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id 0AF053898E; Wed, 26 Apr 2023 13:30:05 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sandelman.ca; s=mail; t=1682530205; bh=IUAONQhW6BJISxhhAK4X1ONX2xI3KPRXDy0hTe3XkO4=; h=From:To:Subject:In-Reply-To:References:Date:From; b=CY+fT3nO9EmGx5azpGhYQiBrXearo7N47szVFppKVxrH5elyxou8HJgqfsJh1StZw TCBjROxeNGspZHybM0LyypOGiT/0EkS2gDeNU9ezxxUOKTC/GJYOCGy5xlKdDJYzNK 5zf6jfH8pT5ZD8R0Awfx+BnVwHXBVnfDQ+8ijayrcNCKK+UNplIdRJcr9XC1ThtSs4 ZFH52lBSFdMmc46zy3yjlvDlfLY3wyw3xqpQ+0H7DrlXWzV1cEJwlfEbUDtVipGXB7 fMP3LM9eLkCX6O6UMDgdBlFy3bLFA27r2TAQIZc5fOwjLOhKmcvAju1zWCtf+S0FLW C+FmhiCtLfOaQ==
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id E1C51755; Wed, 26 Apr 2023 13:12:09 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Ted Hardie <ted.ietf@gmail.com>, rfc-interest@rfc-editor.org
In-Reply-To: <CA+9kkMBVMTG7Zku4gt_DwCNWArYTauR_O0u70zceCMtN2GNN_Q@mail.gmail.com>
References: <E024D9AC-2B92-4720-9713-519592D2362B@rfc-editor.org> <30c30c2f-4e96-560a-73dd-a51ba8d04714@comcast.net> <771B7586-FFBB-49E4-9B99-5578863FBD8B@rfc-editor.org> <CABcZeBOevOj8cWY7dacWxzwZS82+iAjf1p+DZWF=7WZ9JydnrQ@mail.gmail.com> <48de4d92-e279-4c26-ab3c-15dd854b56f8@betaapp.fastmail.com> <CABcZeBPqePQwPAq5pWda1pGaY_=kLkcOxCjZWmOv9yRZ_MNb7g@mail.gmail.com> <CA+9kkMBVMTG7Zku4gt_DwCNWArYTauR_O0u70zceCMtN2GNN_Q@mail.gmail.com>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 27.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Wed, 26 Apr 2023 13:12:09 -0400
Message-ID: <796.1682529129@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-interest/kKfZQtS3cDzbi_TekxK6F1OS-4c>
Subject: Re: [rfc-i] 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: Wed, 26 Apr 2023 17:12:16 -0000

Ted Hardie <ted.ietf@gmail.com> wrote:
    > I agree with Ekr that this is problematic, but my concern is with external
    > links to other standards.  If I replace a link to https://ieee.example/876.1
    > to an archive link like
    > https://archivesite.example/see?https_ieee_example/876.1_retrieved_the_day_of_publication
    > then ieee.example has no chance to use its own redirects or tombstones to

It also keeps ieee.example from replacing the link that we were using with a
link that goes through a paywall.

(Which, btw, DOES HAPPEN regularly)

--
Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 IøT consulting )
           Sandelman Software Works Inc, Ottawa and Worldwide

v2.29.0 | Report a Bug | By Email | System Status