On Mon, Mar 11, 2019 at 04:49:19PM -0400, Marc Blanchet wrote: > Hello, > this draft just posted is the result of discussions that happened in ICANN > RDAP profile discussions, where a missing piece was found in the use case of > thin domain registries. However, the proposal in the draft is generic and > may apply to other use cases in the future if necessary. The draft is not > fully baked but more than enough to have a discussion on the issue and the > proposed solution. > > Looking for comments and reviews,
A couple of comments: 1. Why is a new bootstrap registry being created? This seems to be doing the same thing as the object tag registry, except this only applies to RDAP entities. 2. The do-this-or-that of step 4 in section 3 is far from ideal. There should only be one step, and that should be to use the referral URL in 4A. The servers that, for reasons that escape me, do not know the URLs for the registrars can use the bootstrap to formulate the referral URL on behalf of the client thus keeping client complexity to a minimum. -andy _______________________________________________ regext mailing list regext@ietf.org https://www.ietf.org/mailman/listinfo/regext
