[ARIN-consult] NEW Consultation: Available Methods of Reporting Network Sub-Delegation Information
bill at herrin.us
Thu Oct 12 18:16:44 EDT 2017
On Mon, Oct 2, 2017 at 11:19 AM, ARIN <info at arin.net> wrote:
> ARIN expects to continue offering Method 1 (SWIP) into the foreseeable
> future. As previously described, we are acting on a formal suggestion to
> consult with the community about the future of RWhois support, and also
> have potential options with RDAP.
> - Question (general):
> Of the three sub-delegation reporting methods listed (SWIP,
> RWhois, RDAP), which should ARIN support in the future?
The main problem I had with rwhois, way back when I ran rwhois, was that
the software would crash after a few weeks and since nothing noticeable
broke, I wouldn't realize it for a few months. Even if the software is now
rock solid, something on the server hosting it will break. It's just not a
first class element of the system.
On the other hand, SWIP is push-style database replication involving
mismatched and custom pieces of software plus manual submissions. The
probability of data synchronization problems approaches 1.
RDAP at least operates as an HTTP web app that can presumably be managed
the same way you maintain availability of your other web servers.
In the far future, I think ARIN should support RDAP. Period. Getting from
here to there in the intermediate term is another matter.
> - Question (SWIP/RESTful API specific):
> The existing RESTful API allows users to report (SWIP) one
> sub-delegation at a time to be added to ARIN Whois. Should ARIN add
> bulk-upload features to the RESTful API?
Not necessary. If changes are happening in enough bulk for that to be
needful, there's a programmer who needs a spanking.
On the other hand, if it's not available now then there should be a
facility for a registrant to **bulk-download** all their SWIP entries at
once for comparison with their local database. Otherwise data
synchronization requires a nasty dance.
> - Question (RWhois specific):
> As noted, RWhois servers are not referred to in an automated
> fashion when users query ARIN Whois. Should ARIN automate referrals to
> RWhois servers from ARIN's Whois service?
If you keep rwhois then yes, of course. Caveat that by "automate" I mean
publish the referral in a machine-readable form in the rwhois response,
expect rwhois client software to follow it and make sure your own rwhois
clients (e.g. on your web site) follow it. Last I checked (which was a very
long time ago) ARIN did this brokenly: published both the referral and
contradictory SWIP data which really confused things.
> - Question (RDAP specific):
> If ARIN was to allow the reporting of network sub-delegation
> information using RDAP, associated enabling software would be required.
> Should ARIN enable this method by creating an RDAP software suite that
> would allow ARIN registrants to run RDAP service locally?
No. JSON over HTTP is easy enough to work with and writing appropriate
interface modules should be the responsibility of the folks vending IPAM
On the other hand, curl --head http://rdap.org/ip/22.214.171.124 lands at
http://whois.arin.net/rest/ip/126.96.36.199 which does not output RDAP
formatted results (XML != JSON), so there's some work to be done on ARIN's
side just to report RDAP correctly with ARIN's own data.
William Herrin ................ herrin at dirtside.com bill at herrin.us
Dirtside Systems ......... Web: <http://www.dirtside.com/>
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the ARIN-consult