On Wed, Dec 15, 2021, at 12:45, Thomas Corte (TANGO support) wrote:
> All of this is correct; however, for registrars seeking to keep their
> inventory up-to-date with such a feature, it seems rather awkward having
> to implement *two* instead of one real-time connection to the registry.
I don't think this should be what drives protocol design.
Because that same argument could then be applied to many other things,
basically barring any innovation.
I see really nothing "awkward" by just using the proper tool for each job.
EPP for provisioning, other interfaces (they exist already: custom resports
through
FTP/SFTP/SCP, or registry website, etc.) for other needs not related to
provisioning.
The constraints are completely different: EPP is a "real-time" "always on"
kind of interface, as you need live results.
Synchronizing a portfolio or doing searches is something not needing real-time
and which (for synchronization) shouldn't happen "often".
The SLAs and rate-limits will be wildly different between the two features.
Trying to cram everything inside EPP basically just because EPP exists
(both as protocol and as connection for registrars) seems the wrong direction
to me.
Also, I do recall that often/sometimes (and that was the case for EPP itself),
there is first a draft of the requirements/contraints/desires, without any
technical stuff, and only when that is agreed upon, the technical work on
finding the correct protocol and way to reach that goal is started.
Using EPP just because it is there seems to me to go too quickly to the
"solution".
> Right now, registrars have little to no reason to include an RDAP client
> implementation in their software at all, as everything they need to do in
> terms of domain/contact/host inventory management can/must be done via
> EPP,
Which is not/was not already true. Think FOAs in gTLDs (not all registry
allow domain:info on domain you don't sponsor, even with the correct authInfo)
for one thing.
> and EPP provides more information about sponsored objects than RDAP
> anyway.
In what sense?
And even if true, what prohibits to add more data to RDAP?
> As such, IF e.g. a "list my domains" feature shall be made available in a
> real-time interface,
Why? Registrars certainly don't need that often/in real time.
> IMHO it would make more sense to add it to EPP, as
> registrars can then handle all of their business with the registry over
> their existing EPP connection,
First not all registries use EPP.
Second, it could be good to hear from more registrars and registries in fact
to know if that is really a factor for them.
Third, for any registrar stack, adding a new "client" for RDAP stuff
may be easier than changing their EPP stack to add yet one more extension.
--
Patrick Mevzek
p...@dotandco.com
_______________________________________________
regext mailing list
regext@ietf.org
https://www.ietf.org/mailman/listinfo/regext
