On 4 Aug 2020, at 15:47, Patrick Mevzek wrote:
PS: related but not directly, at least for domain registries, it would
be
nice to have an `SRV` record on `_rdap._tcp` or something to point to
relevant
RDAP server, even if that does not allow to encode the path (but maybe
a solution with .well-known/ and URI template could be found), it
allows at least
for nice failover and load balancing. It may be a problem for gTLDs as
they have
restrictions in content of their zone.
well, this has been debated at length during the WEIRDS working group
work. I actually wrote a sentence about this in the RFC (in the
acknowledgements section). I’m not sure we want to restart the debate
again…
Maybe the newly expected SCVB record could help...
A setup like that would allow for discoverability without
centralization of data,
which also removes IANA from the hot operational path when RDAP
clients do queries.
yes. this is the well-known caveat of this RFC and discussed and debated
during WEIRDS. But experience up to now has not shown any issue, at
least to my knowledge. (and as a developer of the RDAP Browser mobile
app, I haven’t seen any issue fetching that registry. I do have found
thousands of issues with the registry/registrars RDAP servers however,
but that is another story).
Marc.
--
Patrick Mevzek
p...@dotandco.com
_______________________________________________
regext mailing list
regext@ietf.org
https://www.ietf.org/mailman/listinfo/regext
