Re: [rfc-i] archiving outlinks in RFCs

Michael Richardson <mcr+ietf@sandelman.ca> Tue, 02 May 2023 23:35 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 2F2C7C14CE5F; Tue, 2 May 2023 16:35:34 -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 RzxeIJXrux9C; Tue, 2 May 2023 16:35:29 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (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 BA494C151717; Tue, 2 May 2023 16:35:27 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 4ABDF3898E; Tue, 2 May 2023 19:53:44 -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 kgBtET5TJBks; Tue, 2 May 2023 19:53:43 -0400 (EDT)
Received: from sandelman.ca (unknown [IPv6:2607:f0b0:f:2:40a:34ff:fe10:f571]) by tuna.sandelman.ca (Postfix) with ESMTP id 831D23898D; Tue, 2 May 2023 19:53:43 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sandelman.ca; s=mail; t=1683071623; bh=Cn0gEbW0F8RZWysCeBVhlz2Oaq8b+v/Z6FAxbDdVeok=; h=From:To:Subject:In-Reply-To:References:Date:From; b=sQAxLv7khWGqsHiMquZOzubtk9bMK8V3r1+xipsVsYEiA3BJ5Ql72EXuGUpfTvQjT 7vzNL1hktGSPBwWud718I7sL/27WXPOTx+wWAejnzfAzPDRfLCPzUC0o22qUNFmCSO eYW9+8maWFE06TWA80lCCotSmH3HtHKFGo5i+19M9P1oyO3K+OOnNve58nU9RSsMcP aYYOOq8kq1rXPGD7m+516iM2CQgt2eqXK3ZgUgF6HVuIkIOyDqviHk1TZshzQW8WJC ofxhIIq0Pyqr/UayekMzh3wRx3FVy5VC4Df7Aq7FFz1dvWb7zLPGWg0h+Lz4mNmc36 /+3RDO/zGuhuQ==
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 27011E7; Tue, 2 May 2023 19:35:25 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Alexis Rossi <rsce@rfc-editor.org>, RFC Interest <rfc-interest@rfc-editor.org>
In-Reply-To: <BB283056-9CDA-4B3F-BEC7-BBAA036A3D29@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> <CA+9kkMCKM7A81+EU0OegtE5UbjLoVwsK7FVig8toddj-1APwxw@mail.gmail.com> <CANMZLAakmafNpe91TGG0eioR_yHt=n=ncV7nKLMCvCaQevoH8A@mail.gmail.com> <1718A586-7CFE-42CB-8206-DD7B18383BC9@ietf.org> <CA+9kkMCm1C762sTXiiP=MLLP9huuzdTbjJ-zROEXXJKGuwoGdg@mail.gmail.com> <93dd2fb8-f986-ed10-9369-529ab6bd320c@huitema.net> <BB283056-9CDA-4B3F-BEC7-BBAA036A3D29@rfc-editor.org>
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: Tue, 02 May 2023 19:35:25 -0400
Message-ID: <25312.1683070525@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-interest/Vo9paIYOawGOA7yU6pbw5PeQ218>
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: Tue, 02 May 2023 23:35:34 -0000

Alexis Rossi <rsce@rfc-editor.org> wrote:
    > Trying to steer clear of implementation details, I think these are the
    > goals from our discussion:

I'm with you.

    > - Update authors.ietf.org [1] and Web Portion of the Style Guide [2] to
    > provide guidance on choosing live vs archived URLs.  Suggested text:
    > “For URL references, consider whether the resource contains “live”
    > information that updates over time, or whether you are referencing
    > information that should not change. For live information we recommend
    > that you use the live URL in your reference.  For URLs where the

I'm unclear how one could really ever cite a "live URL", or maybe I don't see
the point.   It seems that we might want the result to be something like:

    <a href="https://archive.org/blah.example/page01">https://blah.example/page01</a>

with appropriate adjustments for references and the like in the .txt version.

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