<html><head></head><body><div class="ydpc419dfc4yahoo-style-wrap" style="font-family:Helvetica Neue, Helvetica, Arial, sans-serif;font-size:16px;"><div></div>
<div dir="ltr" data-setdir="false">Colleagues</div><div dir="ltr" data-setdir="false"><br></div><div dir="ltr" data-setdir="false">We need to take some action on these old NWIs. Either we move forward with them or we cancel them. It is difficult to draw a consensus on 2 comments. Can you please give us a couple of minutes of your time and let us know if this NWI-1 is needed, useful or a waste of time.</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="ydp2b326c98yahoo_quoted_1587858958" class="ydp2b326c98yahoo_quoted">
<div style="font-family:'Helvetica Neue', Helvetica, Arial, sans-serif;font-size:13px;color:#26282a;">
<div>----- Forwarded message -----</div>
<div><b>From:</b> ripedenis--- via anti-abuse-wg <anti-abuse-wg@ripe.net></div><div><b>To:</b> anti-abuse-wg@ripe.net <anti-abuse-wg@ripe.net></div><div><b>Sent:</b> Tuesday, 22 September 2020, 22:50:52 CEST</div><div><b>Subject:</b> [anti-abuse-wg] NWI reviews: NWI-1 staying on top of abuse contact changes</div><div><br></div>
<div><div id="ydp2b326c98yiv3995894601"><div><div class="ydp2b326c98yiv3995894601yahoo-style-wrap" style="font-family:Helvetica Neue, Helvetica, Arial, sans-serif;font-size:16px;"><div dir="ltr">Colleagues</div><div dir="ltr"><br></div><div dir="ltr">This is now a very old NWI that never got out of the starting blocks. I am posting this to the AA-WG as I think the discussion is more relevant to this community given the impact of not properly managing this data.</div><div><br></div><div dir="ltr"><a href="https://www.ripe.net/ripe/mail/archives/db-wg/2016-May/005234.html" class="ydp2b326c98yiv3995894601" rel="nofollow" target="_blank">https://www.ripe.net/ripe/mail/archives/db-wg/2016-May/005234.html</a><br></div><div><br></div><div><br></div><div dir="ltr">Since I raised this point the world has moved on and the situation is now even more complex. The "abuse-c:" attribute can be added to:</div><div dir="ltr">-the resource holders primary ORGANISATION object</div><div dir="ltr">-any secondary ORGANISATION object referenced from any point in the address hierarchy</div><div dir="ltr">-any resource object at any point in the address hierarchy</div><div dir="ltr">-all, or any combination, of the above</div><div dir="ltr"><br></div><div dir="ltr">These (multiple) "abuse-c:" attributes can reference the same or multiple ROLE objects.</div><div dir="ltr"><br></div><div dir="ltr">These (multiple) ROLE objects can include "abuse-mailbox:" attributes referencing <span><span style="color:rgb(0, 0, 0);font-family:Helvetica, Arial, sans-serif;font-size:16px;">the same or multiple email addresses.</span></span></div><div dir="ltr"><span><span style="color:rgb(0, 0, 0);font-family:Helvetica, Arial, sans-serif;font-size:16px;"><br></span></span></div><div dir="ltr"><span><span style="color:rgb(0, 0, 0);font-family:Helvetica, Arial, sans-serif;font-size:16px;">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.</span></span></div><div dir="ltr"><span><span style="color:rgb(0, 0, 0);font-family:Helvetica, Arial, sans-serif;font-size:16px;"><br></span></span></div><div dir="ltr"><span><span style="color:rgb(0, 0, 0);font-family:Helvetica, Arial, sans-serif;font-size:16px;">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.</span></span></div><div dir="ltr"><span><span style="color:rgb(0, 0, 0);font-family:Helvetica, Arial, sans-serif;font-size:16px;"><br></span></span></div><div dir="ltr"><span><span style="color:rgb(0, 0, 0);font-family:Helvetica, Arial, sans-serif;font-size:16px;">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.</span></span></div><div dir="ltr"><span><span style="color:rgb(0, 0, 0);font-family:Helvetica, Arial, sans-serif;font-size:16px;"><br></span></span></div><div dir="ltr"><span><span style="color:rgb(0, 0, 0);font-family:Helvetica, Arial, sans-serif;font-size:16px;">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.</span></span></div><div dir="ltr"><span><span style="color:rgb(0, 0, 0);font-family:Helvetica, Arial, sans-serif;font-size:16px;"><br></span></span></div><div dir="ltr"><span><span style="color:rgb(0, 0, 0);font-family:Helvetica, Arial, sans-serif;font-size:16px;">Would this be useful, is it necessary or a waste of time? Please discuss....</span></span></div><div dir="ltr"><span><span style="color:rgb(0, 0, 0);font-family:Helvetica, Arial, sans-serif;font-size:16px;"><br></span></span></div><div dir="ltr"><span><span style="color:rgb(0, 0, 0);font-family:Helvetica, Arial, sans-serif;font-size:16px;">cheers</span></span></div><div dir="ltr"><span><span style="color:rgb(0, 0, 0);font-family:Helvetica, Arial, sans-serif;font-size:16px;">denis</span></span></div><div dir="ltr"><span><span style="color:rgb(0, 0, 0);font-family:Helvetica, Arial, sans-serif;font-size:16px;"><br></span></span></div><div dir="ltr"><span><span style="color:rgb(0, 0, 0);font-family:Helvetica, Arial, sans-serif;font-size:16px;">co-chair DB-WG</span></span></div><div dir="ltr"><span><span style="color:rgb(0, 0, 0);font-family:Helvetica, Arial, sans-serif;font-size:16px;"><br></span></span></div></div></div></div></div>
</div>
</div></body></html>