Access to the database is up to Chris, since it resides on his machine and he's responsible for its design and maintenance. It might be that an API is more appropriate than direct access.
We had discussed adding additional attributes to the DB to hold whois information so that the portal could be used to edit the info, but that hasn't been done because we never came up with a spec for those attributes. It's complicated by the fact that we have about 60 directly routed subnets and about 475 tunneled, all of which need to be in the rwhois DB. If you could work with Chris on that as his time permits, it would be good.
Negotiating with ARIN has been complicated in the past because we have to be very careful not to endanger our legacy status. - Brian
On Thu, Jun 18, 2015 at 01:18:42PM -0700, Tim Osburn wrote:
The rwhois server project I built has been idle since the next step requires work from your side. (I've added a few blocks at peoples request)
whois -h 44.4.64.10 -p 4321 <ip block in question here>
- If you can allow the 44.4.64.10 IP SQL access to your db so that I
can write the software that can translate whats in the DB into rwhois records that will allow me to populate the server. It doesn't need to reside on the amprgw server for that access.
- We also need you to add a referral whois entry for the 44/8 block to
point to the rwhois server so that anyone who does a whois will ultimately get forwarded to the server to resolve the request.
https://www.arin.net/resources/request/reassignments_rwhois.html