IETF Logo Mail Archive

Re: [rfc-i] archiving outlinks in RFCs

Alexis Rossi <rsce@rfc-editor.org> Thu, 27 April 2023 17:54 UTC

Return-Path: <rsce@rfc-editor.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 4A5F6C1519B2 for <rfc-interest@ietfa.amsl.com>; Thu, 27 Apr 2023 10:54:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=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 4OJ5C38O8iUs; Thu, 27 Apr 2023 10:54:09 -0700 (PDT)
Received: from smtpclient.apple (157-131-78-231.fiber.dynamic.sonic.net [157.131.78.231]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPSA id 01015C151536; Thu, 27 Apr 2023 10:54:08 -0700 (PDT)
From: Alexis Rossi <rsce@rfc-editor.org>
Message-Id: <BF0FCBF8-2315-4BF3-A5B2-5F48EA836D8E@rfc-editor.org>
Content-Type: multipart/alternative; boundary="Apple-Mail=_55431A2C-F35C-4FCF-B288-D9631413E159"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.120.41.1.3\))
Date: Thu, 27 Apr 2023 10:54:07 -0700
In-Reply-To: <6448E47C.9030101@btconnect.com>
Cc: rfc-interest@rfc-editor.org
To: tom petch <daedulus@btconnect.com>
References: <E024D9AC-2B92-4720-9713-519592D2362B@rfc-editor.org> <6448E47C.9030101@btconnect.com>
X-Mailer: Apple Mail (2.3696.120.41.1.3)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-interest/dM9acTMTe2wyEWWgs9C9-MGVfw8>
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: Thu, 27 Apr 2023 17:54:13 -0000


> On Apr 26, 2023, at 1:44 AM, tom petch <daedulus@btconnect.com> wrote:
> 
> On 25/04/2023 19:50, Alexis Rossi wrote:
>> 


>> 
>> The first thing I wanted to do was just make sure we were archiving these outlinks somewhere. This won’t fix a broken link in the RFC, but at least the resource can be saved elsewhere for someone curious enough to go look (and potentially we could fix links in some version of the RFC in future).
>> 
> 
> What is an 'outlink'?
> 
> Not a term I can recall seeing in an RFC or on a discussion list before.
> 
> Tom Petch
> 

An “outlink” would be any URL that goes to an external page (as opposed to an internal reference, like a table of contents link that takes you to a section of the same document). In practice at the moment I am ignoring these internal links as well as outlinks that go to other pages on rfc-editor.org, since I know those are archived already. So I’m archiving any outlink that goes to any domain other than rfc-editor.org <http://rfc-editor.org/>.

Alexis

v2.23.0 | Report a Bug | By Email