On Fri 16/Nov/2012 07:06:42 +0100 Florian Weimer wrote:
* Kaveh Ranjbar:
None of the objects in the chain, "inetnum/inet6num/aut-num", "organisation" and "role" are provisioned as, or designed to be private data holders.
Are you sure? After all, you anonymize these objects in the database dumps, citing data protection concerns: [...] admin-c: DUMY-RIPE tech-c: DUMY-RIPE
I worry that most LIRs put quite a bit of effort into updating the contact information, and then RIPE NCC decides to hide it because it's considered personal data, like all the other contact information currently in the database.
It may be necessary to contact a "person", sometimes. However, machines are not allowed to do that. I believe mechanisms better than the existing CAPTCHA are being considered, but that seems to be tied to a different implementation plan, as it is not entirely within RIPE. *Tools for searching* are mentioned in the Implementation Details page that Kaveh posted. Other pages are obsolete; for example, the Refinements to the RIPE Database Query API is of 23 Aug 2010, and has a broken link for the RIPE Database Web Services. The specification of RESTful web services for retrieving registration data involves all RIRs and most names registries, so it doesn't depend on RIPE only. Even so, I hope Kaveh will be able to keep us informed about those developments' timeline.