IETF Logo Mail Archive

Re: [rfc-i] archiving outlinks in RFCs

Eliot Lear <lear@lear.ch> Thu, 27 April 2023 20:42 UTC

Return-Path: <lear@lear.ch>
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 82219C14CEF9 for <rfc-interest@ietfa.amsl.com>; Thu, 27 Apr 2023 13:42:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.889
X-Spam-Level:
X-Spam-Status: No, score=-0.889 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_ALL=0.8, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, NICE_REPLY_A=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SPF_HELO_PERMERROR=0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=lear.ch
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 kWPj5bobpQZc for <rfc-interest@ietfa.amsl.com>; Thu, 27 Apr 2023 13:42:10 -0700 (PDT)
Received: from upstairs.ofcourseimright.com (upstairs.ofcourseimright.com [IPv6:2a00:bd80:aa::2]) (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 1BEA6C14F5E0 for <rfc-interest@rfc-editor.org>; Thu, 27 Apr 2023 13:42:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=lear.ch; s=upstairs; t=1682628125; bh=8qmpq7SB1mJE6fWZlarEC7A4DW21yK1qIrqkwzv8Ijc=; h=Date:To:References:From:Subject:In-Reply-To:From; b=Vud++sb+lJ4RYRqnd0cD+3DQrMhPPda0CjfM6DQJBXb7CJykONAGt7l8K6BqAKmIt Kx4XqbW1cCY+mgUi494X1pl5u6ruVyQD9nvCzP8lB1WSRjZ996HkZoXgBKNX7mFzd2 CA4imlLEApq0+hUlNHTHCbiV5b1DYEKlCqJlDVYI=
Received: from [IPV6:2001:420:c0c0:1011::4] ([IPv6:2001:420:c0c0:1011:0:0:0:4]) (authenticated bits=0) by upstairs.ofcourseimright.com (8.15.2/8.15.2/Debian-22ubuntu3) with ESMTPSA id 33RKg3S6306825 (version=TLSv1.3 cipher=TLS_AES_128_GCM_SHA256 bits=128 verify=NO); Thu, 27 Apr 2023 22:42:04 +0200
Message-ID: <aee31b38-793c-c1fc-d211-285636701779@lear.ch>
Date: Thu, 27 Apr 2023 22:42:00 +0200
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:102.0) Gecko/20100101 Thunderbird/102.10.0
Content-Language: en-US
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, rfc-interest@rfc-editor.org
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> <796.1682529129@localhost> <CA+9kkMBiqZCqbDviOVQFmjROYJtViz=S7ZsW6T41mv4XGbZ3=g@mail.gmail.com> <04BE48FA-322D-457A-9D7B-A9DA8FCE8E50@rfc-editor.org> <3e70ec52-8a7c-02f8-884c-94e42997588d@gmail.com>
From: Eliot Lear <lear@lear.ch>
In-Reply-To: <3e70ec52-8a7c-02f8-884c-94e42997588d@gmail.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-interest/jOOQscYXnKfmbSimnVF69i0hipY>
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 20:42:15 -0000

On 27.04.23 22:20, Brian E Carpenter wrote:
> I think that automating the errata creation is a good idea. The point 
> is to trigger human intervention when it's appropriate, and that 
> should be a stream choice rather than an RPC choice. In many cases an 
> automated redirect to an archive copy will be all that's needed.

I am not ready to say that.  I would like to see if there is a generic 
policy that could apply to all RFCs.  That will provide the reader with 
a consistent experience.

Eliot

v2.23.0 | Report a Bug | By Email