[Tools-discuss] Re: documents by WG --- RFCs and related documents -- are there APIs
Jennifer Richards <jennifer@staff.ietf.org> Wed, 30 July 2025 15:16 UTC
Return-Path: <jennifer@staff.ietf.org>
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 E2FC14D58ACB for <tools-discuss@mail2.ietf.org>; Wed, 30 Jul 2025 08:16:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, 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=staff-ietf-org.20230601.gappssmtp.com
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 vjn8C5Q1ySQT for <tools-discuss@mail2.ietf.org>; Wed, 30 Jul 2025 08:16:02 -0700 (PDT)
Received: from mail-qk1-x732.google.com (mail-qk1-x732.google.com [IPv6:2607:f8b0:4864:20::732]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id E04214D58AC6 for <tools-discuss@ietf.org>; Wed, 30 Jul 2025 08:16:02 -0700 (PDT)
Received: by mail-qk1-x732.google.com with SMTP id af79cd13be357-7e1d89fcc31so641208385a.1 for <tools-discuss@ietf.org>; Wed, 30 Jul 2025 08:16:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=staff-ietf-org.20230601.gappssmtp.com; s=20230601; t=1753888562; x=1754493362; darn=ietf.org; h=content-transfer-encoding:in-reply-to:cc:from:references:to :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=Uru946bNFYnSPXfNvPHEEq6zmB6bQEsAyFt5kLnQo+8=; b=F1rcyFAH92432uGk8kG7dxpPHUIj0mN8BGPj9dY3EUFf1+G5Iq7LPq3JGmHN4y0ZLU z70gR4hL37ALfqhJ+4/LhkKeOV3TSkmqLmBAhKrY9wQV7UUXR66j5FkMwXzoz0Oirjui 7uvnlLf9fW9aewj3HaPNWZYZV8UGVqlwzcL+u+bTPQZPs1IyzH4+ejK8I5+7zdPELcEL EWa7trqKeExTDCHh4UfR9yqMnAl+8JqyPgYLjtDEwjmj2QH98H7Bila/NY1gE9oagsvl qdMq5ufeW5WS7fUweoZpa1L7rkueIF+ZvEOOtgHi1MashOTy0lQJFy/0ojNX+Q3ruQfp zurQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1753888562; x=1754493362; h=content-transfer-encoding:in-reply-to:cc:from:references:to :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=Uru946bNFYnSPXfNvPHEEq6zmB6bQEsAyFt5kLnQo+8=; b=Qqf1kCOcHclTb3xUZ6gALnp8hnuNYeacx2Twz9vEYdr0G78xdP5hQZyzWVDWuLR15z upJDU/SpX7NbRBAiLZw53Bwh3woRiehSgULcnnloQTF7gAinHZoXy3R1LSljIe0xhgkl 5dSuwXXp0o51vTMih+e1N3uEAK5xIzZgT3DNPpv4TxYLV0gYP5xMlEf96iHTlvbkX7bi kRBuWadePYDIyTZcG7CShMDXbAkuHL13G5GX/8sTK5K4Bh6jqe/UcqazgAID5k/hFwOr uzg15A7XDGyfO/0Pvjuqg/NTbYN+2C/evGB6iZ69zNjvvb4bNZyNQt/7przuAwUwuVZI Phdg==
X-Gm-Message-State: AOJu0Yy6GsYzx7/IDcGQqpqxhZ2bGfUL6yS9lRTs7RSZ353az041cf5B e8FRHaDgu38DMkXO92Qtpk2jCfmfcgJsTepOBxN/+7zNdsR5W7W2syyPqDfK9C27gDw6eA==
X-Gm-Gg: ASbGncu55evBNRuL0+I+7oJdGqIEQfKQKoE0kjjjXks+1ToOlEvX5CQgHfW0Hv2SAYd AHWg0IUUD37MZDQB/mKcAA1Bu92MC6SduZRHvRakCQVDjMJKYQTDLcma4L7sTljrw6ISI9+5p3G KzfkBmLnaafEYy1FNs9Lr3Kyf2mZyg6k9uVskwT1T1MqXKAyfTIBkdnvbYMlzPbevb0Omwa7jQD L5yFvckmGY4da+zB36RSwe6u64kplB2gM+o5YlGXasO1jWM5qzjdhQbgHX3LbFhpmqTy6qL39ta Exx2ilPwfNoQyYZQ71KLVdc3Pmhxjb331nvLP8TxMwnmLexQDMEA+AjV7XFHlF5yTbZJv6W8+3Q msLVy3UpoFnCO99CAfqEKui5TAXEzflt2bG79HWrVe70R9JjFBTeJgbhHp3on6m+YjLXo5kO7/G XGzf1yFxuvTP7LLi1P/7ZHIVVTxqEJR1WRBzsyd5b/4H49xsJ1B5qF
X-Google-Smtp-Source: AGHT+IHD5WlqeF6Lfxxmnd6RDooKdFmH26+0gE42uQ9OyvyQ8jZTaxw3ruDiJOHNBBtn61eu7f59xA==
X-Received: by 2002:a05:620a:a812:b0:7d0:9be0:2e35 with SMTP id af79cd13be357-7e66ef7f782mr485187785a.10.1753888562264; Wed, 30 Jul 2025 08:16:02 -0700 (PDT)
Received: from [192.168.53.91] (hlfxns018gw-134-41-51-94.dhcp-dynamic.fibreop.ns.bellaliant.net. [134.41.51.94]) by smtp.gmail.com with ESMTPSA id af79cd13be357-7e64387c9absm592743485a.65.2025.07.30.08.16.01 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 30 Jul 2025 08:16:01 -0700 (PDT)
Message-ID: <523a3640-feab-4eeb-9b98-09eb6438923c@staff.ietf.org>
Date: Wed, 30 Jul 2025 12:16:00 -0300
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Content-Language: en-CA
To: Michael Richardson <mcr+ietf@sandelman.ca>
References: <26738.1753630433@obiwan.sandelman.ca>
From: Jennifer Richards <jennifer@staff.ietf.org>
In-Reply-To: <26738.1753630433@obiwan.sandelman.ca>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Message-ID-Hash: JTB2RYQEEU7JH7D7CZVFPYLCSJJAPO27
X-Message-ID-Hash: JTB2RYQEEU7JH7D7CZVFPYLCSJJAPO27
X-MailFrom: jennifer@staff.ietf.org
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
CC: tools-discuss@ietf.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [Tools-discuss] Re: 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/4XHEkG3w_ab9LSOXlt48D4yh6ow>
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>
Hi Michael, On 2025-07-27 12:33 PM, Michael Richardson wrote: > 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. You can do this with the v1 (tastypie) API for RFCs: $ curl -s 'https://datatracker.ietf.org/api/v1/doc/document/?type=rfc&group__acronym=httpapi' | jq -r '.objects[].name' rfc9512 rfc9264 rfc9457 rfc9652 rfc9745 rfc9727 The related documents is more difficult because it involves a configuratble list of search rules. You can get ones that were explicitly added to the document list starting with $ curl -s 'http://localhost:8000/api/v1/community/communitylist/?group__acronym=httpapi' | jq -r '.objects[].added_docs[]' /api/v1/doc/document/draft-pot-authentication-link/ which you can parse for the name or fetch as an API url to get more details. AFAIK there's no (reasonable) way to get the related documents that appear because of search rule matches. It might be technically possible, but you'd likely be happier looking these up manually. This API is stable, though closely reflects datatracker's models so may change if the modeling evolves. That's not likely to come up often. jennifer
- [Tools-discuss] documents by WG --- RFCs and rela… Michael Richardson
- [Tools-discuss] Re: documents by WG --- RFCs and … Jennifer Richards
- [Tools-discuss] Re: documents by WG --- RFCs and … Tom Pusateri
- [Tools-discuss] Re: documents by WG --- RFCs and … Jennifer Richards
- [Tools-discuss] Re: documents by WG --- RFCs and … Michael Richardson
- [Tools-discuss] Re: documents by WG --- RFCs and … Tom Pusateri
- [Tools-discuss] Re: documents by WG --- RFCs and … Jay Daley
- [Tools-discuss] Re: documents by WG --- RFCs and … Robert Sparks
- [Tools-discuss] Re: documents by WG --- RFCs and … Martin Thomson
- [Tools-discuss] Re: documents by WG --- RFCs and … Michael Richardson