Re: [regext] using subdomains in RDAP bootstrap

["Andrew Newton (andy)" <[e-mail]>]

Hi Dmitry,

You can use redirects as described by section 5.2 of RFC 7480:

https://datatracker.ietf.org/doc/html/rfc7480#section-5.2

Redirects are commonly used in the RIR/INR space for IP addresses and 
ASNs and, as you have pointed out, the domain space for zones below the 
TLD level.

I hope this helps.

-andy

On 4/8/24 11:09, Dmitry Kohmanyuk wrote:
> Hello everyone,
>
> As a long-time lurker on regext@ and an infrequent participant in IETF meetings, I apologize if I missed something.  We have a practical issue with RDAP.
>
> My registry, Hostmaster.UA have implemented RDAP for UA (URL: https://rdap.hostmaster.ua/, as included into IANA bootstrap.) Similarly to say UK we have multiple public suffixes where domains are registered, such as com.ua net.ua odesa.ua etc.
>
> The trouble is, some of these domains are not managed by us;  let’s say that alice.ua would have rdap.alice.ua,  and bob.ua, rdap.bob.ua whereas com.ua would use IANA bootstrap element. Now, I want RDAP service to be as seamless as possible.
>
> How can we implement this?  IANA JSON registry only has TLDs.  I can of course create my own bootstrap file but I cannot imagine practical way of informing RDAP clients of it’s existence.  I can use HTTP codes “moved permanently” when answering RDAP queries on our server.  (I can query the other server myself and serve the response; bad idea.)
>
> Is there a most effective way to do it? Thanks!
>
>
> _______________________________________________
> regext mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/regext