IETF Logo Mail Archive

[Tools-discuss] Stronger references to rfc-editor.org pages?

Michael Richardson <mcr+ietf@sandelman.ca> Thu, 23 June 2022 16:49 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 34764C13CD99 for <tools-discuss@ietfa.amsl.com>; Thu, 23 Jun 2022 09:49:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.709
X-Spam-Level:
X-Spam-Status: No, score=-1.709 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=neutral reason="invalid (public key: not available)" 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 i0TL2gkKa5Pf for <tools-discuss@ietfa.amsl.com>; Thu, 23 Jun 2022 09:48:56 -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 16E6EC15D86F for <tools-discuss@ietf.org>; Thu, 23 Jun 2022 09:48:55 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id CB73538E09 for <tools-discuss@ietf.org>; Thu, 23 Jun 2022 13:05:09 -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 YWGw3lPsi7rj for <tools-discuss@ietf.org>; Thu, 23 Jun 2022 13:05:09 -0400 (EDT)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id 2EDE438E07 for <tools-discuss@ietf.org>; Thu, 23 Jun 2022 13:05:09 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=sandelman.ca; s=mail; t=1656003909; bh=oS6I3oTtO8iA2JjCqc1UU9RYJFTwEh6A0WgcN0Fm+i8=; h=From:To:Subject:Date:From; b=tf9NaV8FKbQraSAfQXFBx/j0FLy1ccEWua+n9jAml9Qmp0h2VAeWvILQpSMCcHhFW 6pSxXUW6dPkXluda8iYbKrdWKchcy0V7jNKTpeJH6U4DI9gx1ahxUARntWLisiZjRE fbTva7SKibqWLriLyNu6YAwcSt1CBkeMSSWUeo2KIe+l60JmrD+e0oxRjo3inpIoSK LxS4gLlewYytw1TQ3/0IiCB48mpmHW8rUVfvFXZdenCnbcv3NCY4CtbVM9VoZ2HW+u 2vuRUiLqlyILUz2uIaSzT93wL2O2/yJykIgi3a+c+8hgaSAkHX0iQTzu2y3s5zUvyz rf4P1b4O4Xe0g==
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id D0F3B118 for <tools-discuss@ietf.org>; Thu, 23 Jun 2022 12:48:53 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: tools-discuss@ietf.org
X-Attribution: mcr
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: Thu, 23 Jun 2022 12:48:53 -0400
Message-ID: <16583.1656002933@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-discuss/xwpGG2J9QM4CZILIHy0qSy7KNU4>
Subject: [Tools-discuss] Stronger references to rfc-editor.org pages?
X-BeenThere: tools-discuss@ietf.org
X-Mailman-Version: 2.1.39
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: Thu, 23 Jun 2022 16:49:00 -0000

from, for instance:
https://datatracker.ietf.org/doc/rfc7959/

what thing leads me to:
  https://www.rfc-editor.org/info/rfc7959
  ??

All of the Formats lead to https://www.rfc-editor.org/rfc/rfc7959.html,
etc. which is good.
The IESG state item says: RFC 7959 , but leads to the DT info page.
(which is a self-reference, but of course, on ID copies of that page it
wouldn't be)

I wonder if a link to the info/ page might be added to...
Formats?  (kinda wrong)
Stream?	  Internet Engineering Task Force (IETF) __RFC7959__

Document Type?
(says: "Was..."
could have: "Now __RFC7959__"
even better: "Now __RFC7959 (with errata)_"
)

The with errata boolean would involve the DT doing some API call to the
RFC-editor periodically.


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

v2.23.0 | Report a Bug | By Email