[rpp] Re: RPP -05 feedback

[Jasdip Singh <[e-mail]>]

Hi,

On Wed, Mar 18, 2026 at 03:30:08PM +0100, Pawel Kowalik wrote:

> 1) Bootstrapping = finding where is the server for .xx TLD. I agree this is
> likely of limited value today.

Just a small warning: RPP is not limited to TLD. There are many public
(accepting domain name registrations from a wide public) registries
which are not TLD.

RDAP bootstrap is not limited to TLD (RFC 9224 "If a domain RDAP query
for a.b.example.com matches both com and example.com entries in the
registry, then the longest match applies and the example.com entry is
used by the client.")

Also, RDAP relies on HTTP redirection and, currently,
draft-wullink-rpp-core-05 seems silent about redirection (should a RPP
client follow it?)

[JS] On further thought, with the RPP ecosystem growing over time, having an IANA RPP registry (emulating IANA RDAP Bootstrap registry) containing each RPP registry’s service (and .well-known ?) URIs by domains that registry serves might be a decent idea. But more from service discovery perspective (like SVCB/HTTPS RRs) rather than helping dynamically bootstrap a registrar. In other words, an organized place to see which RPP registry serves which domain. I could be wrong about this not helping much with dynamically bootstrapping a registrar. (Numbers side could follow on this if/when needed.)

However, not sure if an RPP redirection service based on such IANA data would be needed since RPP would primarily be a provisioning protocol where redirecting provisioning requests seems a bit odd/risky, unlike RDAP (a query protocol) where query redirections make sense.


Jasdip