[rpp] Re: Listing and filtering objects in RPP
Maarten Wullink <ietf@wullink.nl> Mon, 02 November 2026 13:39 UTC
Received: from mo4-p00-ob.smtp.rzone.de (mo4-p00-ob.smtp.rzone.de [81.169.146.218]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange x25519 server-signature ECDSA (prime256v1) server-digest SHA256) (No client certificate requested) by mx.ietf.org (Postfix) with ESMTPS id 1EFC646 for <rpp@ietf.org>; Mon, 02 Nov 2026 13:39:26 +0000 (UTC)
Authentication-Results: mx.ietf.org; dkim=pass header.d=wullink.nl header.s=strato-dkim-0002 header.b=D5uSJSZQ; dkim=pass header.d=wullink.nl header.s=strato-dkim-0003 header.b=CQNAcm31; spf=none (mx.ietf.org: domain of ietf@wullink.nl has no SPF policy when checking 81.169.146.218) smtp.mailfrom=ietf@wullink.nl; dmarc=pass (policy=reject) header.from=wullink.nl; arc=pass ("strato.com:s=strato-dkim-0002:i=1")
ARC-Seal: i=1; a=rsa-sha256; t=1793626758; cv=none; d=strato.com; s=strato-dkim-0002; b=JqxHu75PtQH0kvAE8iWXFziwQAvwOYVanpODGkEcX09/Clm9kX3QgDyI1V4UNTCrC6 u03VCh5tdjGnh3WgAdQT8fCDSh3u9fZ2g9ZjRVaxPDV0oKiXcZN0plaguIQN5EyPaEJB NkvHL2EnvcSpfpZc2c8LUbwBZ3ulsPH8KHWXmYzryw/JyEZF+y/kAfnGdRKUuE7D/1C9 xxsg/p6JqMpt6oJVsNtFdgMz6Nuy2u1TzFH7hTsvxm/5br38ZxBG4eA+LW7uO5oc/HnJ Q75u3vI/OdtGzOGTNN2ejYkgaPxDnmOdFD4FVe24MEx2+KbLWBPd3LemwZfX+DVafNvs sDLQ==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; t=1793626758; s=strato-dkim-0002; d=strato.com; h=To:References:Message-Id:Cc:Date:In-Reply-To:From:Subject:Cc:Date: From:Subject:Sender; bh=/JM0AOUx2AqcvCkGUp2QWO/bbKGj6mUCWJpzN9UtpRk=; b=o91B5UL9/6h7/ufvzvBkK1Naa3QiYPUa9SRa79NCAacHJr1cheaBqr1Alp01mUghD5 mWmkHP4/hHuZsClyKMmDzsDXgW4I9pCYFCvbffFC53xQ3/omN1rsIaVrtnRIQ4q2xU/h h3La/eoAF99+Ct9nZ51aOjWpnOX63+Q6Y3qtEA+1frZBiRJo520OjljmJrYRCT89U5Jy Y2HmlX4p6eNkX0Bv3jP9YkTWlotPlOKQ4o6KgRlQGd82gVE9DRHLciulBKH/ysw/r2r6 73lUT0HUvDlsVrTXFx+GN7MQ/reK02PR/pQhpnceBA2iyhINgRLLLlGbSN/wkljnofvk zilg==
ARC-Authentication-Results: i=1; strato.com; arc=none; dkim=none
X-RZG-CLASS-ID: mo00
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1793626758; s=strato-dkim-0002; d=wullink.nl; h=To:References:Message-Id:Cc:Date:In-Reply-To:From:Subject:Cc:Date: From:Subject:Sender; bh=/JM0AOUx2AqcvCkGUp2QWO/bbKGj6mUCWJpzN9UtpRk=; b=D5uSJSZQs7PHYY9i1EtMZ4HiJ/M9Fk4PRagOok2VzRwVAXy1CLSBbha6XTX3doXjj5 cT9jY7UcJckjfOHjpCeA7dDLCIqsDofDxi3mXvdcPgfOfS6wHAFeC6k7iR84p5Hrn71i JEG1NqhNaJEMtuKOA7Zx7qris1KjgzsOemRrxgFPmjJ0crvjo52HmUKNrZeta6z0OnWK xqhY4PctsN1ce47lIVNIDRUiEqvHMM4T7lnG82qIq/Qa+o7lzZG/UE5/BF5s4dC1aeRz r4pH2LZfuQQWP4Wv0ZRL/fvm1OWYJBAYxkZbDZmQ0lOQ9JcVIXatXz8x8gMYKP4SlVqN 9apA==
DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; t=1793626758; s=strato-dkim-0003; d=wullink.nl; h=To:References:Message-Id:Cc:Date:In-Reply-To:From:Subject:Cc:Date: From:Subject:Sender; bh=/JM0AOUx2AqcvCkGUp2QWO/bbKGj6mUCWJpzN9UtpRk=; b=CQNAcm31i6nKjJDVRee28x8Rogr98VQGAx95ghwh3G1VVUKaRSaH2f8vpktLEiJwuv cMoQ0GGS3Y7vGa1GroAw==
X-RZG-AUTH: ":JWkQc2C/bvP3tODnPr76mjCXe1iI8gOyM6Quzqr/H+EtjuLEcV0opwXB/KZrnKE="
Received: from smtpclient.apple by smtp.strato.com (RZmta 55.6.3 AUTH) with ESMTPSA id 4b53cb2A2DdIrfu (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (curve X9_62_prime256v1 with 256 ECDH bits, eq. 3072 bits RSA)) (Client did not present a certificate); Mon, 2 Nov 2026 14:39:18 +0100 (CET)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3901.100.1.1.12\))
From: Maarten Wullink <ietf@wullink.nl>
In-Reply-To: <170D181B-0189-4BB7-994A-4595D5821A88@dns.business>
Date: Mon, 02 Nov 2026 14:39:06 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <CAFEA198-02FF-428F-9E36-A69EA688C3AD@wullink.nl>
References: <170D181B-0189-4BB7-994A-4595D5821A88@dns.business>
To: David Kinnes <david@dns.business>
X-Mailer: Apple Mail (2.3901.100.1.1.12)
X-Spamd-Bar: -------------------------
Message-ID-Hash: H5MXZJ23P4ISH3ECSXCZDWV2LBJRCPRU
X-Message-ID-Hash: H5MXZJ23P4ISH3ECSXCZDWV2LBJRCPRU
X-MailFrom: ietf@wullink.nl
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: rpp@ietf.org
X-Mailman-Version: 3.3.10
Precedence: list
Subject: [rpp] Re: Listing and filtering objects in RPP
List-Id: "This list discusses a provisioning protocol based on RESTful principles and corresponding data representations using JSON." <rpp.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/rpp/MEeNfVojp4SrrnTkYGU_gMPYeMU>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rpp>
List-Help: <mailto:rpp-request@ietf.org?subject=help>
List-Owner: <mailto:rpp-owner@ietf.org>
List-Post: <mailto:rpp@ietf.org>
List-Subscribe: <mailto:rpp-join@ietf.org>
List-Unsubscribe: <mailto:rpp-leave@ietf.org>
Hi David,
>
> Some background: alongside EPP, we run a JSON REST API for our registry
> platform. Registrars use it, as do our own portal and operator console.
> Registrars depend on it heavily to list and search the objects they
> sponsor. Typical uses are portfolio management, reconciliation against
> their own records, and finding domains by status or upcoming expiry.
thanks for this info, it’s good to learn that there already are real world implementations for this type of functionality.
especially the options for getting list of domains by status or with upcoming expiry is something i like.
>
> In the current drafts, Table 2 of core (Section 16.1.2) maps a "query"
> operation to GET /{collection}. However, as far as we can see, the
> data-objects draft does not define a query or list operation for domain
> names, contacts, hosts or organisations. The only filter-like parameter is
> hostsFilter on a single-domain read. Rule 7 (Section 16.1.7) requires
> servers to reject unknown query parameters, and Section 2.6.3 of
> data-objects says other operations must have their input and output fully
> specified. Together, these seem to leave no compliant way for a server to
> offer listing or filtering today.
today we will release, the -02 version of the rpp-data-objects draft.
in this version there is a query operation, currently its only applied to the messages data object.
>
> We would be grateful to know the group's thinking:
>
> 1. Is listing intentionally out of scope for the core, or is it expected
> to come in a later revision or an extension?
Actually, bulk operations such as objects listing has been captured as a rpp requirement
see requirements:
- R12.2
- D2.4
- H2.2
- C2.3
in https://datatracker.ietf.org/doc/html/draft-ietf-rpp-requirements-04
However, the opinions are somewhat divided on how far we should take this.
we do want to be careful to prevent us just reinventing rdap as part of rpp.
If there are good arguments and use cases (such as yours) for including it, then i would be in favor of this.
> 2. If it is planned, is the HTTP QUERY method (mentioned as future work in
> Section 16.10.1 for messages) the intended direction for filtering more
> generally, or would plain GET with query parameters be preferred?
>
no plans yet, but if the listing functionality is something the wg decides is useful to add (either in core or as extension)
then depending on the complexity of the query request, use of the http query method may be an option.
> In case it is useful, our API currently supports:
>
> - Listing scoped to the objects the authenticated registrar sponsors
> - Pagination (limit/offset)
> - Filtering by status, expiry date range, linked contact or host, and
> creation date
> - Ordering, simple text search, and a bulk export (CSV)
>
It is very useful to know that registries already offer similar functionality, or would like rpp to include this functionality.
> Based on that, a minimal common definition might cover the scope (the
> caller's sponsored objects), pagination (for example a cursor with a
> Link rel="next" header), a small agreed set of filters, a sort order, and
> a response shape made up of a list of short summaries with links to the
> full objects.
>
> Apologies if this has already been discussed on the list or in an earlier
> meeting and I have missed it. If so, I would be grateful for a pointer to
> the thread or issue.
i think this topic was discussed during the requirements phase, i cannot find the discussion, but the outcome was captured in the requirements mentioned above.
Best,
Maarten
- [rpp] Listing and filtering objects in RPP David Kinnes
- [rpp] Re: Listing and filtering objects in RPP Maarten Wullink
- [rpp] Re: Listing and filtering objects in RPP Pawel Kowalik
- [rpp] Re: Listing and filtering objects in RPP Andy Newton