Re: [Tools-discuss] BCP links to multiple RFCs broken (in inconsistent ways)

Michael Richardson <mcr+ietf@sandelman.ca> Tue, 16 March 2021 21:27 UTC

Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: tools-discuss@ietfa.amsl.com
Delivered-To: tools-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8782B3A0FEC for <tools-discuss@ietfa.amsl.com>; Tue, 16 Mar 2021 14:27:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SEN6QNb2R3FU for <tools-discuss@ietfa.amsl.com>; Tue, 16 Mar 2021 14:27:04 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9124A3A0FED for <tools-discuss@ietf.org>; Tue, 16 Mar 2021 14:27:04 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 2EF51389AC for <tools-discuss@ietf.org>; Tue, 16 Mar 2021 17:32:31 -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 GVaah2sqyBoQ for <tools-discuss@ietf.org>; Tue, 16 Mar 2021 17:32:30 -0400 (EDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id BE3D6389A3 for <tools-discuss@ietf.org>; Tue, 16 Mar 2021 17:32:30 -0400 (EDT)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 26752D5 for <tools-discuss@ietf.org>; Tue, 16 Mar 2021 17:27:03 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: tools-discuss@ietf.org
In-Reply-To: <C625B11D-7158-45DE-AD93-3BF684B5133B@vigilsec.com>
References: <834d516-4c99-c8d-aedd-cd843de3fe5@w3.org> <35d1f7ae-df08-590d-9245-96e20f32ee66@nostrum.com> <C625B11D-7158-45DE-AD93-3BF684B5133B@vigilsec.com>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.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, 16 Mar 2021 17:27:03 -0400
Message-ID: <9155.1615930023@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-discuss/sTGFGG7lxLYr6JOXVWYnVvuG5YA>
Subject: Re: [Tools-discuss] BCP links to multiple RFCs broken (in inconsistent ways)
X-BeenThere: tools-discuss@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF Tools Discussion <tools-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tools-discuss>, <mailto:tools-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tools-discuss/>
List-Post: <mailto:tools-discuss@ietf.org>
List-Help: <mailto:tools-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tools-discuss>, <mailto:tools-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 16 Mar 2021 21:27:07 -0000

Russ Housley <housley@vigilsec.com> wrote:
    > Why doesn't the datatracker serve the .html file for the BCP from the RFC Editor?

That's a good question!

I think that aside from reducing duplication, it would also raise the SEO of
that copy, and I think that we want to point more to rfc-editor.org, where errata,
etc. are best available.

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