Re: [weirds] I-D Action: draft-blanchet-weirds-bootstrap-ianaregistries-00.txt

["John Levine" <[e-mail]>]

>How would a client bootstrap a query for 29.12.202.in-addr.arpa ?

It would look at arpa.domains.rdap.arpa to get the name of the RDAP
server for .arpa, if there were one.  I expect that's not the answer
to the question you meant to ask.

If you're asking how to bootstrap a query for 202.12.29.0/24, or
2001:0400::/22, my proposal is that the numbers bootstraps are built
into the clients, with informal advice to update them every year or
two, sort of like the root zone hints in a DNS cache.  Given how
slowly the IANA numbers tables change, I think that's more workable
than something that tries to boostrap the rather irregular numbers
assignments on the fly.

>I would prefer to see an approach that minimises variance in bootstrap
>complexity between names and numbers: making numbers bootstrap too complex
>increases the likelihood of an unofficial solution arising, such as an
>HTTP(S) request to rdap.org or rdap.arin.net.

Indeed.  But do keep in mind that there are some rather basic operational
differences between names and numbers that won't change.

* Numbers assignments move among RIRs, so the RIRs have a history of
cooperation and awareness of each other's assignments.  

* Names never move from one TLD to another, and there's no need for
operational cooperation between different TLDs.

R's,
John