Ah. The ARIN service is just another RDAP server. Is there a special
meaning behind "bootstrap server"?

I'm able to parse the bootstrap files fine, but some of the downstream RDAP
servers seem to be returning errors.



On Wed, May 16, 2018 at 10:22 PM, Andrew Newton <a...@hxr.us> wrote:

> I don't think I understand. That is a bootstrap server, and sends
> redirects for information found in the IANA bootstrap files:
>
> $ curl -v https://rdap.arin.net/bootstrap/ip/45.56.121.172
> *   Trying 199.5.26.160...
> ...
> > GET /bootstrap/ip/45.56.121.172 HTTP/1.1
> > Host: rdap.arin.net
> > User-Agent: curl/7.47.0
> > Accept: */*
> >
> < HTTP/1.1 302 Found
> < Date: Thu, 17 May 2018 03:14:14 GMT
> < Server: WildFly/10
> < X-Powered-By: Undertow/1
> < Location: https://rdap.arin.net/registry/ip/45.56.121.172
> < Content-Length: 0
> < Access-Control-Allow-Origin: *
>
> Are you looking for the bootstrap files themselves?
> http://data.iana.org/rdap/asn.json
> http://data.iana.org/rdap/ipv4.json
> http://data.iana.org/rdap/ipv6.json
> http://data.iana.org/rdap/dns.json
>
> RFC 7884 covers the bootstrap files. RFC 7483 covers the JSON returned
> by RDAP servers.
>
> -andy
>
> On Wed, May 16, 2018 at 6:47 PM, Adam Shannon <adamkshan...@gmail.com>
> wrote:
> > Thanks, but I'm not seeing records which follow RFC 7484 in the ARIN
> > bootstrap server. There are notices, but nothing parsing.
> >
> >
> >
> > On Wed, May 16, 2018 at 4:27 PM, Andy Newton <a...@hxr.us> wrote:
> >>
> >> Try the ARIN bootstrap server:
> >> http://rdap.arin.net/bootstrap/
> >>
> >> -andy
> >>
> >> Sent from my iPhone
> >>
> >> On May 16, 2018, at 11:04 PM, Gavin Brown <gavin.br...@centralnic.com>
> >> wrote:
> >>
> >> Hi Adam,
> >>
> >> I run rdap.org (in a personal capacity). Unfortunately it has not
> >> received the attention it needs: it does not consume the IANA bootstrap
> >> file, so its map of prefixes to RIRs may not be complete. My apologies.
> >>
> >> If you're writing a client implementation I suggest you consume the
> >> bootstrap file directly, as per RFC 7484.
> >>
> >> Gavin.
> >>
> >> On 16/05/2018 13:24, Adam Shannon wrote:
> >>
> >> Hi all,
> >>
> >>
> >> I'm working on a client implementation of RDAP and running into some
> >>
> >> problems.
> >>
> >>
> >> Are all IPv4 ranges covered? It doesn't appear so, and servers from
> >>
> >> about.rdap.org <http://about.rdap.org> don't seem to be responding to
> >>
> >> domains they're said to serve.
> >>
> >>
> >> $ curl -L -v -H "Accept: application/json" https://rdap.org/ip/$(dig
> >>
> >> +short code.jobs <http://code.jobs>)
> >>
> >> ...
> >>
> >> GET /ip/45.56.121.172 <http://45.56.121.172> HTTP/2
> >>
> >> Host: rdap.org <http://rdap.org>
> >>
> >> Accept: application/json
> >>
> >>
> >> < content-type: application/rdap_error+json
> >>
> >>
> >> {"errorCode":404,"title":"No RDAP service could be found for
> >>
> >> '45.56.121.172'"}
> >>
> >>
> >> Also, I tried another example and am seeing a different response format
> >>
> >> than what I saw in the RFC's.
> >>
> >>
> >> $ curl -L -v -H "Accept: application/json"
> https://rdap.org/ip/192.0.2.0
> >>
> >> {
> >>
> >>     "net": {
> >>
> >>         // ...
> >>
> >>         "registrationDate": {
> >>
> >>             "$": "2009-06-29T11:15:30-04:00"
> >>
> >>         },
> >>
> >>         "ref": {
> >>
> >>             "$": "https://whois.arin.net/rest/net/NET-192-0-2-0-1";
> >>
> >>         },
> >>
> >>         "endAddress": {
> >>
> >>             "$": "192.0.2.255"
> >>
> >>         },
> >>
> >>         "handle": {
> >>
> >>             "$": "NET-192-0-2-0-1"
> >>
> >>         },
> >>
> >>         // ...
> >>
> >>         "version": {
> >>
> >>             "$": "4"
> >>
> >>         }
> >>
> >>     }
> >>
> >> }
> >>
> >>
> >>
> >> _______________________________________________
> >>
> >> regext mailing list
> >>
> >> regext@ietf.org
> >>
> >> https://www.ietf.org/mailman/listinfo/regext
> >>
> >>
> >>
> >> --
> >> Gavin Brown
> >> Chief Technology Officer
> >> CentralNic Group plc (LSE:CNIC)
> >> Innovative, Reliable and Flexible Registry Services
> >> for ccTLD, gTLD and private domain name registries
> >> https://www.centralnic.com/
> >> +44.7548243029
> >>
> >> CentralNic Group plc is a company registered in England and Wales with
> >> company number 8576358. Registered Offices: 35-39 Moorgate, London,
> >> EC2R 6AR.
> >>
> >> _______________________________________________
> >> regext mailing list
> >> regext@ietf.org
> >> https://www.ietf.org/mailman/listinfo/regext
> >
> >
>
_______________________________________________
regext mailing list
regext@ietf.org
https://www.ietf.org/mailman/listinfo/regext

Reply via email to