<html><head></head><body><div class="ydpefd96e9fyahoo-style-wrap" style="font-family:Helvetica Neue, Helvetica, Arial, sans-serif;font-size:16px;"><div></div>
<div dir="ltr" data-setdir="false">Hi Leo</div><div dir="ltr" data-setdir="false"><br></div><div dir="ltr" data-setdir="false">I was proposing a tool to help the registrant manage their data. If you want to find the abuse contact you just query the resource and the abuse contact is returned.</div><div dir="ltr" data-setdir="false"><br></div><div dir="ltr" data-setdir="false">cheers</div><div dir="ltr" data-setdir="false">denis</div><div dir="ltr" data-setdir="false"><br></div><div dir="ltr" data-setdir="false">co-chair DB-WG</div><div><br></div>
</div><div id="ydpd4fde1d2yahoo_quoted_1640460148" class="ydpd4fde1d2yahoo_quoted">
<div style="font-family:'Helvetica Neue', Helvetica, Arial, sans-serif;font-size:13px;color:#26282a;">
<div>
On Tuesday, 22 September 2020, 23:13:02 CEST, Leo Vegoda <leo@vegoda.org> wrote:
</div>
<div><br></div>
<div><br></div>
<div><div dir="ltr">Hi Denis,<br clear="none"><div class="ydpd4fde1d2yqt9593998006" id="ydpd4fde1d2yqtfd37207"><br clear="none">On Tue, Sep 22, 2020 at 1:51 PM ripedenis--- via anti-abuse-wg<br clear="none"><<a shape="rect" href="mailto:anti-abuse-wg@ripe.net" rel="nofollow" target="_blank">anti-abuse-wg@ripe.net</a>> wrote:<br clear="none"><br clear="none">[...]<br clear="none"><br clear="none">> Over time, with large hierarchies, we could end up with very complex arrangements with objects, attributes and values that have been overlooked and forgotten about. Even though they may have been forgotten about they are still 'active' and queries will return the most appropriate abuse contact details, even if it is the wrong contact.<br clear="none">><br clear="none">> There is no simple query that will return the details of such a complex structure of abuse contact data in the RIPE Database. So there is no easy way for a resource holder to review or manage these abuse contacts. Although most resources will only ever have one abuse contact for the whole hierarchy, over several years we could end up with the kind of data swamp we had before we introduced the "abuse-c:" attribute for the larger networks.<br clear="none">><br clear="none">> Any user could write their own script to do more specific queries, parse the returned objects and work out the abuse contact data structure for their resource. It would require detailed knowledge of the RIPE Database structure, the abuse contact rules and would involve multiple queries just to get the data, which you then have to visualise.<br clear="none">><br clear="none">> My reason for this NWI-1 was to suggest the RIPE NCC creates a tool or RIPEstat widget that would take in a resource and map out the abuse contact details for the whole hierarchy including that resource.<br clear="none">><br clear="none">> Would this be useful, is it necessary or a waste of time? Please discuss....</div><br clear="none"><br clear="none">Should I understand this as a proposal for a tool that is used to keep<br clear="none">the registrant informed about changes related to resources for which<br clear="none">they are responsible, or a tool to help other network operators and<br clear="none">users find the right place to send an abuse report?<br clear="none"><br clear="none">Many thanks,<br clear="none"><br clear="none">Leo</div></div>
</div>
</div></body></html>