Subject: Re: [weirds] bootstrap json registry proposal

From: Naoki Kambe <[email-masked]>
Date: Tue, 03 Jun 2014 10:51:54 +0900 (JST)

Hello,

Thank you for the bootstrap proposal. Here are my quick comments.

From: Marc Blanchet <[email-masked]>
Date: Sat, 31 May 2014 11:01:00 -0400
> ===================================
> IANA RDAP DOMAIN BOOTSTRAP REGISTRY
> ===================================
> {
>   “rdap.bootstrap”: {
>     “domain": {
>       “myexampletld.”: {
>         "host": "rdap.example.org",
>       },
>       "myexample2tld.": {
>         "host": "rdap.example.net",
>         "protos": [ "http" ],
>         "proto": [ "http" ],
>         "prefix": "",
>       },
>     },
>   },
> }

I think a multiple hosts choice might be preferred.  Some TLD
registries might want to provide a RDAP service at different names.
For example,

  "hosts": [
    "rdap1.example.net",
    "rdap2.example.net"
  ], ..

How can we represent a URL templete when specifying an arbitrary port
number in this bootstrap? For example, if we provide a RDAP service at

  http://rdap.example.tld:8080/rdap

How do we distribute these bootstrap registries?  For example, is an
IANA URL like this?

  http://example.iana.org/rdap/domain
  => {
       "rdap.bootstrap": {
         "domain": {
           ..
         }
       }
     }

Regards,

Naoki Kambe