[Tools-discuss] Re: documents by WG --- RFCs and related documents -- are there APIs
Jennifer Richards <jennifer@staff.ietf.org> Wed, 30 July 2025 16:10 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 D2F134D638E8 for <tools-discuss@mail2.ietf.org>; Wed, 30 Jul 2025 09:10:51 -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 nPxlOpGFxJza for <tools-discuss@mail2.ietf.org>; Wed, 30 Jul 2025 09:10:51 -0700 (PDT)
Received: from mail-qk1-x734.google.com (mail-qk1-x734.google.com [IPv6:2607:f8b0:4864:20::734]) (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 66C754D638E3 for <tools-discuss@ietf.org>; Wed, 30 Jul 2025 09:10:51 -0700 (PDT)
Received: by mail-qk1-x734.google.com with SMTP id af79cd13be357-7e1d89fcc31so665685a.1 for <tools-discuss@ietf.org>; Wed, 30 Jul 2025 09:10:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=staff-ietf-org.20230601.gappssmtp.com; s=20230601; t=1753891851; x=1754496651; darn=ietf.org; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=6ywvbOJY+8dgY7atWbTqkZP2GaUbw+5HJW4R0zPJGNk=; b=hT5oPBPJS1qjBxvn00b348HNHUrOE2dx8VFPQmIqecrG9ky6SGLXEQXDbQ3PnbDjyk aA9mQ9IfIABcctj0ejpo6KM4sYPwp6e1p3rvASTcI4Y/NneSxZX331+OQ78Rs2EFnrVF xhWQNDZnKnHc4cxW1VoP4vUJW6WTkxs7gBaW1+/3BUSjqHKfsCEWhIxKx9QGtfo9WtdX OKEeFoBFdtNlS6slPrUm5YVvq6waivj0qunjZyu43SIwqAW7Y400GMuQMC8nHYhS7Iq8 Ji7i66Ie57PwirTVdKuIFXYRMq0uwvijimISXwz9BcMIh9ZIgXAYYcvDMQIrdFl+OPJ1 gxfg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1753891851; x=1754496651; h=content-transfer-encoding:in-reply-to:from:references:cc: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=6ywvbOJY+8dgY7atWbTqkZP2GaUbw+5HJW4R0zPJGNk=; b=u0cQ/SU1PKIziMW42IpmMz3Io4hCETRziwv5DQ7Uq9HUQuOhO7IekPELtfaUofW80U hKiMMhuUESAktSUNFMzYAz3dvW2g9elvDwFdsqEa+nIwGA3kG3/k4EYtdswyVrhLg/By +r/b/27SQYGthZl2HTzcVcYEJF9op/WnMziTz6+iow6Ds0wPplufGQiFRM5qmjD1GwJ4 iLLeNtYcOGpx7D4Nr0v9LxTjMtBPqkVfQJQrvEb5hL8SLSjOFUIdsN7mvtNv6jRB/6lr gw7P7NAcdXeb5S6zrySJG+zknF3l2QgJB7I2XEMcnKwm5UuTx9R/h+TKxtrFJK2TF64+ ZvQg==
X-Forwarded-Encrypted: i=1; AJvYcCVI8iF9v3Vo/5gkjIQJqNX+o6uVTddMHulikvuMxqal8wYOJhg2aJkXM9mebzWKqpdt3VppP5ssXa0B0YT9@ietf.org
X-Gm-Message-State: AOJu0Yz1yDlBS6ZBEjsDk0EUbMXEiUIK7mqaSD5SwlzqbatykJXdE5zm WA32e1ix899Rpikk5SkiFDy/XCadELc2lMbdCBpm+L0QqQNZ9ptimXuiyqbHlVSjggLJdQ==
X-Gm-Gg: ASbGncsLQB71qZo8Vk7VigwEkERwO3B+Z0bDw4Rvqzd3C+9bsYmqzxyat4kRPIkTjTN Stiy0W2tqeFWx3X5GhdQ5hnk9vUmU+cT+F+gEiK0gMNUfaCB4ev42JKfNxJ/g5ibC/y+Q8ct0lQ jBXlHFmxC4qSKxlPMdF3HosQGP0UsFgRsOahZdgHTmPcDtqLr1KDhzz8Zw2myVuxEw1INcYungw DYb/bufARVFqpN9tfAkJM7ZQPyZvC2eMxAWe31MjcF5Y80gA0kUgDehBl/+evXEaC5AiTXqsgno wqJzuEndMnPXfyICGJZnf31D2ma2qbzpUvQJo7cAH4WnYzEn1bnqMX3l7Ii0jDImMLEE80YulIP SPEFx6NhVMtte6qXZVIxqrOQHh5fdn1GOXHMV80wL+DcqIc+mNR5sQsaOcz+ZmGct6Icn9Q6N9t +Bxky0ztKSOCOcbFBoa8yj8ctb3DSrhRTs7PAPAqyppSeHo1Vm8CQ1
X-Google-Smtp-Source: AGHT+IFYR8oEu98WRFb9pS5sgcI8oD64zAq4zhENk95at9Cth1OpCLYX4/O59opL7v4cC0RQ+QFYEQ==
X-Received: by 2002:a05:620a:284b:b0:7e3:3276:99f with SMTP id af79cd13be357-7e66f38ef9cmr571395185a.53.1753891850719; Wed, 30 Jul 2025 09:10:50 -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-7e64327a929sm591899685a.16.2025.07.30.09.10.50 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 30 Jul 2025 09:10:50 -0700 (PDT)
Message-ID: <23025517-b37c-491d-85f6-43b35a5fe159@staff.ietf.org>
Date: Wed, 30 Jul 2025 13:10:49 -0300
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Content-Language: en-CA
To: Tom Pusateri <pusateri@bangj.com>
References: <523a3640-feab-4eeb-9b98-09eb6438923c@staff.ietf.org> <9215E610-26BC-4110-A319-66C85E7C2A4F@bangj.com>
From: Jennifer Richards <jennifer@staff.ietf.org>
In-Reply-To: <9215E610-26BC-4110-A319-66C85E7C2A4F@bangj.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Message-ID-Hash: F3P4AMY4ZULJTT3RZ2ZHW7YCUMDXQKIR
X-Message-ID-Hash: F3P4AMY4ZULJTT3RZ2ZHW7YCUMDXQKIR
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: Michael Richardson <mcr+ietf@sandelman.ca>, 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/78jubwj5dz1Jw98zBGr1eU64kas>
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>
On 2025-07-30 12:19 PM, Tom Pusateri wrote: > Hopefully, the v1 API won’t change. Isn’t that the point of versioning? If the models were to change, then you should define a new v2 API so that you don’t break all the existing v1 users. Assuming tastypie, which is what provides the v1 API, remains stable, the structure of that API won't change. That API is, and has always been as far as I'm aware, a thin layer over (almost all of) the Datatracker's internal models. For better or worse, the meaningful version number for that API is the datatracker's version number. Introducing the kind of long-term stable API you're getting at would be a substantial new project. It's possible, but it's a much bigger ask than just bumping a version number on the API. 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