[apologies for duplicates] Dear colleagues, If you ever wished there would be an easier way to find all abuse-related contact information for a specific network in the RIPE Database, this new Abuse Finder tool might be interesting for you: http://labs.ripe.net/content/abuse-finder As always, please let us know what you think. We are also curious to find out if there are other more customised 'use case queries' you would find useful. We set up a forum to gather your feedback: http://labs.ripe.net/content/ripe-database-api-0 Kind Regards, Mirjam Kühne RIPE NCC
On Monday 26 April 2010 16.22, Mirjam Kuehne wrote:
[apologies for duplicates]
Dear colleagues,
If you ever wished there would be an easier way to find all abuse-related contact information for a specific network in the RIPE Database, this new Abuse Finder tool might be interesting for you:
the webforms seems to need userid/password. Where do i get this ? Also, i personallt would prefer scriptable stuff ( anything that generates text output that may be scripted) Any hope for that ?
As always, please let us know what you think. We are also curious to find out if there are other more customised 'use case queries' you would find useful. We set up a forum to gather your feedback:
http://labs.ripe.net/content/ripe-database-api-0
Kind Regards, Mirjam Kühne RIPE NCC
-- Peter Håkanson There's never money to do it right, but always money to do it again ... and again ... and again ... and again. ( Det är billigare att göra rätt. Det är dyrt att laga fel. )
Dear Peter, The "Abuse Finder" form doesn't need a UserID and Password. If you are referring to the Labs site, then I sugest you just register yourself and you'll be able to post to the forum. The "Abuse Finder" form actually uses an extension to the RIPE Database Query API, which is implemented in the form of a RESTful Web Service. The API allows you to write script against this search tool and responses can be received in either XML or JSON format for easy parsing. We will be updating the API documentation soon, but in the meantime you could try clicking the XML and JSON icons next to the response from the "Abuse Finder" form to see the original response from the web service. Regards, Paul Palse -- Database Group Manager at RIPE NCC http://www.ripe.net/info/ncc/contact.html On 26 Apr, 2010 Week: 18, at 18:06 PM, peter h wrote:
On Monday 26 April 2010 16.22, Mirjam Kuehne wrote:
[apologies for duplicates]
Dear colleagues,
If you ever wished there would be an easier way to find all abuse-related contact information for a specific network in the RIPE Database, this new Abuse Finder tool might be interesting for you:
the webforms seems to need userid/password. Where do i get this ?
Also, i personallt would prefer scriptable stuff ( anything that generates text output that may be scripted) Any hope for that ?
As always, please let us know what you think. We are also curious to find out if there are other more customised 'use case queries' you would find useful. We set up a forum to gather your feedback:
http://labs.ripe.net/content/ripe-database-api-0
Kind Regards, Mirjam Kühne RIPE NCC
-- Peter Håkanson
There's never money to do it right, but always money to do it again ... and again ... and again ... and again. ( Det är billigare att göra rätt. Det är dyrt att laga fel. )
Dear Colleagues, We received these suggestions in response to the Abuse Finder tool announced on RIPE Labs http://labs.ripe.net/content/abuse-finder - it would be helpful, if its noted in the output from wich object or field the abuse email address was extracted from (e.g. admin-c, tech-c, remarks, abuse-field aso) so output could look like: admin-c: noc@tester.de abuse-email: abuse@tester.de so that one can decide, wich one is really relevant for the own needs - what are the exact limits ? - is there a way of raising the limits for special cases (we maintain our own spam blcklist and do send about 30.000 reports, where there are about 5.000 to 8.000 reports originate from the RIPE region) daily - how can the finder be testes via other protocols (then just a webpage) We did think about applying some weighting to the email addresses returned. However, the abuse handling data is not structured within the RIPE Database. There are many places the abuse handling email can be put. This depends on where the network administrator thinks is the most appropriate place. It could be in an IRT object. Or in the admin-c of the maintainer of the INETNUM object. Because it is very subjective, one address is no more valuable or important than another. In most cases you are unlikely to receive a long list of email address options. So the actual objects they came from is less important. One of the main reasons for developing this tool is to reduce the need for users to query for personal data objects. In which case limits become less relevant. With the current data structure we cannot yet totally remove this need. Many abuse email addresses are contained in remarks, some of which are within personal data objects. We return links to the objects that contain remarks that may hold such an email address. If the tool does not return any "abuse-mailbox:" email addresses you will need to follow these links to the suggested objects with remarks. By pointing to those objects that have such remarks this tool avoids the need for users to directly query for all personal data objects referenced. The back end web service can be accessed via any HTTP client library. The response is available in XML or JSON. Regards Denis Walker Business Analyst RIPE NCC Database Group
participants (4)
-
Denis Walker -
Mirjam Kuehne -
Paul Palse -
peter h