[anti-abuse-wg] 2016-01 New Policy Proposal (Include Legacy Internet Resource Holders in the Abuse-c Policy)

Hi Piotr,

Thank you for the formal proposal. 

> You can find the full proposal at:

>     https://www.ripe.net/participate/policies/proposals/2016-01

I've read the proposal and I have a question on it. 

You propose that you want to extend the Abuse-C  Contact management in the RIPE Database policy towards Legacy Internet Resource Holders. 

However ...  

That is already the case ... isn't it ?  ... 

If a Legacy holder changes his Organization Object to include the abuse-c object in the RIPE DB and links it to the inet num object .. it shows the abuse information.  

For instance :  
https://apps.db.ripe.net/search/lookup.html?source=ripe&key=144.2.240.0%20-%20144.2.255.255&type=inetnum 		( No Abuse contact, because no Org-ID. ) 
https://apps.db.ripe.net/search/lookup.html?source=ripe&key=144.2.168.0%20-%20144.2.171.255&type=inetnum 		( no Abuse Contact, Org ID present, but no abuse-c in the Org-ID. ) 
https://apps.db.ripe.net/search/lookup.html?source=ripe&key=144.2.176.0%20-%20144.2.191.255&type=inetnum 		( Abuse contact in the Org-ID. )  

From what I see is that the Abuse-C contact can be added, but it is org-id ( the link to the actual legitimate holder ) which holds the abuse-c, is the issue.  

So the question that would come to my mind is, do you want to enforce the inclusion of the Org-ID into the legacy ( or any type of inet-num) object .. and have the abuse-c as a mandatory field in the org-id. ? 
As for Legacy resource holders, that might be an issue to enforce, as the RIPE NCC can't reach out to all legacy holders that are 'incompliant' as we can't ask them to start guessing who are the actual legitimate holders.. 

So the mandatory database update needs to be done by the maintainer of the legacy resource (whenever they change their allocations/make changes).  That could be done by having the Org-ID field mandatory in the database for all parent inet-nums. 

Or am I missing something here ?  

Regards,
Erik Bais