Hi Nigel and others Why are you only considering long term, complex solutions that seem to have no agreement? There is a simple and quick option. Let me say it again in a few lines. -Suppose we drop the requirement for ASN auth on ROUTE creation. -All duplicated AUT-NUM objects in the RIPE Database can then be deleted -When creating a ROUTE object for RIPE address space it will be authorised in the normal way by the resource holder -When creating a ROUTE for non RIPE address space, notify the resource holder and hold the creation pending acceptance -For any ROUTE creation notify the originating ASN holder as an FYI (from any RIR region) 90% of the software to do this already exists in the RIPE Database code base. The other 10% is finding the contacts for non RIPE resources in the authoritative RIR database and processing the acceptance from these non RIPE resource holders email notification. This could be implemented in a matter of weeks. All ROUTE objects in the RIPE Database will then be authorised by the authoritative address space resource holder and the originating ASN resource holder will be notified of it's creation. What else do you need right now from the RIPE IRR perspective? If you don't want to drop the ASN auth option simply extend the notification/acceptance process to the ASN resource holder for non RIPE ASNs. We still don't need copies in the RIPE Database. cheers Denis Walker Independent Netizen On 12/05/2015 19:35, Nigel Titley wrote:
Please find the rough notes that I took during this BOF attached
Nigel