[Tools-discuss] documents by WG --- RFCs and related documents -- are there APIs

Michael Richardson <mcr+ietf@sandelman.ca> Sun, 27 July 2025 15:33 UTC

Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: tools-discuss@mail2.ietf.org
Delivered-To: tools-discuss@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id E92BC4BDA737 for <tools-discuss@mail2.ietf.org>; Sun, 27 Jul 2025 08:33:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=sandelman.ca
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wuaW5CVaXjqd for <tools-discuss@mail2.ietf.org>; Sun, 27 Jul 2025 08:33:54 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256)) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 74A584BDA72F for <tools-discuss@ietf.org>; Sun, 27 Jul 2025 08:33:54 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 10BFD38D8C for <tools-discuss@ietf.org>; Sun, 27 Jul 2025 11:33:54 -0400 (EDT)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavis, port 10024) with LMTP id mB86nRBrurPP for <tools-discuss@ietf.org>; Sun, 27 Jul 2025 11:33:53 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sandelman.ca; s=mail; t=1753630433; bh=6dXyTS2mlKyW0hwmQBfg1UQwLVWJLBhimHSzfkhMnb8=; h=From:To:Subject:Date:From; b=ZqvO5R7LncyxBFZN4lPEmzuQYDDemJsucCPuxGSxxV/NbKUYBCJ9qhAKvZcuTQEM9 Jy7rqUholpQKhVArTFM2L0TsJ7PIiWaORC3JFDL0ZmOKWnITMyePJmonc28tgiQNDM 2cCdVuhSNojGgF4FyAWXLXlYGqdu4Xamkyivx1WLnOajagIDSAoQjoqp4zbYyCIWWr mHjUfQ1bHeMPNzLHaopiRXxUE40aLd8sDkY5WfoTvqhwucsuUr8VVmLFM0N6H/6QsP Xjz13p4TRBurmyrJ1C1ZKe/vhw674Yi0jZF6jUHxwpJ96pdX/ZwHYR+ot1bn+aCtjU mAP+7GTZUZ7Gw==
Received: from sandelman.ca (unknown [IPv6:2607:f0b0:f:2:b241:6fff:fe09:a92b]) by tuna.sandelman.ca (Postfix) with ESMTP id 2D1F138D8B for <tools-discuss@ietf.org>; Sun, 27 Jul 2025 11:33:53 -0400 (EDT)
Received: from obiwan.sandelman.ca (obiwan.sandelman.ca [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 261741AE for <tools-discuss@ietf.org>; Sun, 27 Jul 2025 11:33: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.8+dev; GNU Emacs 28.2
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: Sun, 27 Jul 2025 11:33:53 -0400
Message-ID: <26738.1753630433@obiwan.sandelman.ca>
Message-ID-Hash: UKYUIXIPKUHSNMJ2YSU27I7VCFACXHPN
X-Message-ID-Hash: UKYUIXIPKUHSNMJ2YSU27I7VCFACXHPN
X-MailFrom: mcr+ietf@sandelman.ca
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-tools-discuss.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [Tools-discuss] documents by WG --- RFCs and related documents -- are there APIs
List-Id: IETF Tools Discussion <tools-discuss.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-discuss/Ovt2a3iZU8VXl00IEtKj6WW_Z7w>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tools-discuss>
List-Help: <mailto:tools-discuss-request@ietf.org?subject=help>
List-Owner: <mailto:tools-discuss-owner@ietf.org>
List-Post: <mailto:tools-discuss@ietf.org>
List-Subscribe: <mailto:tools-discuss-join@ietf.org>
List-Unsubscribe: <mailto:tools-discuss-leave@ietf.org>

For some years (decades?) I have, like many others, rsync'ed IDs and RFCs to desktop and laptop.
{I remember when the ~1G, now ~5G of space was a huge commitment for disk
sizes of the time}

I run a script on the internet-drafts directory that sorts/hardlinks:
  draft-ietf-foo-bar-00.txt -> ietf/foo/bar-00.txt
  draft-author-foo-bar-00.txt -> ietf/author/foo-bar-00.txt
  (and ditto irtf)
And I tend not to clean the hard links out very often, so I have more history
than perhaps I need.

On WGs that I work a lot with, I often then hard link the RFCxxxx into that directory.
I have in the past suggested that maybe this view could benefit others.

Now I am thinking that I want to automate bring RFCxxxx into each directory.

1. Is there an API that would return a WG's "RFC list"?
2. Is there an API that would return a WG's Related Documents list?

Yes, I can read the DT source code, but asking here would tell me if the API
contract is stable, or if someone is considering changing it.

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