Re: [regext] EPP Extension Object Search

"Thomas Corte (TANGO support)" <Thomas.Corte@knipp.de> Tue, 14 December 2021 16:24 UTC

Message-ID: <5d4e3a97-2f09-2a85-8193-54de66d87eef@knipp.de>
Date: Tue, 14 Dec 2021 17:24:08 +0100
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Thunderbird/91.4.0
Content-Language: en-US
To: regext@ietf.org
References: <9DC8EEDB-36A3-406F-80E3-C521B5C6D876@tobiassattler.com>
From: "Thomas Corte (TANGO support)" <Thomas.Corte@knipp.de>
Organization: Knipp Medien und Kommunikation GmbH
In-Reply-To: <9DC8EEDB-36A3-406F-80E3-C521B5C6D876@tobiassattler.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/auQqeLVsSNV5SlvTuttLN_JLeM8>
Subject: Re: [regext] EPP Extension Object Search
Precedence: list

Hello,

On 12/14/21 15:29, Tobias Sattler wrote:

> Dear Working Group,
> 
> Jody and I wrote a draft on EPP Extension called Object Search.
> 
> We want to spin this idea with this group because using EPP for searching 
> is more secure than RDAP by reducing a threat vector.
> 
> https://github.com/seitsu/epp-object-search/blob/main/draft-sattler-epp-object-search.txt 
> <https://github.com/seitsu/epp-object-search/blob/main/draft-sattler-epp-object-search.txt>
> 
> Please note that this is an early draft that is not submitted yet. 
> Therefore, the approach used in this document is only to illustrate the 
> idea, not necessarily the final approach.
> 
> We are looking forward to hearing your feedback.

As a (registrar) EPP client developer, I'd surely actually welcome a way 
to obtain ad-hoc lists of sponsored objects via EPP (rather than having 
to rely on out-of-band reports, which aren't really standardized yet, see 
below).

However, as a (registry) EPP server developer, I'm wary of the extra 
stress that could be caused by excessive list queries (with search 
filters) hitting the main SRS database, especially if registrars took the 
availability of this feature as an incentive to neglect their local 
inventory management.

This is one of the reasons why our own TANGO registry system is using a 
dedicated reporting server that offers daily inventory reports, 
pre-generated from a local, partial copy of the registry's data.

The registration reporting draft at

https://datatracker.ietf.org/doc/draft-ietf-regext-simple-registration-reporting/

seems to be aiming at standardizing such registry reports, which at this 
point seems to be the preferable option to get inventory information IMHO 
- registrars could use them to easily get full inventory data, allowing 
them to filter them offline in any way they see fit (compared to the 
simple filtering options the object search branch offers right now). 
Also, the standardized reports are supposed to also include data about 
transactions, RGP, reserved names, premium names etc.; the EPP object 
search would really only offer a small subset of this data.

By the way, the text and examples don't seem to be aligned with the XSD 
in the draft; for example, "type" and "filter" are defined as XML 
elements, while they occur as XML attributes in the examples.

Best regards,

Thomas

-- 
TANGO REGISTRY SERVICES®
Knipp Medien und Kommunikation GmbH                    Thomas Corte
Technologiepark                             Phone: +49 231 9703-222
Martin-Schmeisser-Weg 9                       Fax: +49 231 9703-200
D-44227 Dortmund                      E-Mail: Thomas.Corte@knipp.de
Germany

[regext] EPP Extension Object Search Tobias Sattler
Re: [regext] EPP Extension Object Search Thomas Corte (TANGO support)
Re: [regext] EPP Extension Object Search Patrick Mevzek
Re: [regext] EPP Extension Object Search Mario Loffredo
Re: [regext] EPP Extension Object Search Thomas Corte (TANGO support)
Re: [regext] EPP Extension Object Search Patrick Mevzek