All, you might be interested in this, it is how the RIPE NCC plan to deal with removing references to reclaimed ASNs in database objects (e.g. RPSL routing policies). Cheers, Rob Begin forwarded message:
From: Ingrid Wijte <ingrid@ripe.net> Subject: [address-policy-wg] Draft proposal: Guidance Requested: Reassigning Referenced ASNs Date: 14 August 2013 09:47:37 BST To: address-policy-wg@ripe.net, db-wg@ripe.net
Dear colleagues,
Thank you for your feedback on this issue. Based on the input we have received we propose taking the following action:
- The RIPE NCC will send an email to the maintainer and contacts of the RIPE Database objects in which the returned AS numbers are referenced, asking for the reference to be removed. - The RIPE NCC will send three additional reminders, at intervals of three weeks from each other, for a total of four emails. - If after four emails the reference is still in place, the RIPE NCC will update the RIPE Database object itself, removing the reference. - If the reference is being recreated within one month from deletion (possibly due to automatic updates), the RIPE NCC will contact the organisation through means of communication other than email.
The total number of RIPE Database objects that reference returned AS numbers is currently about 2000. All references are in the policy attributes of aut-num objects. No route(6) objects are involved.
Thank you again and best regards,
Ingrid Wijte RIPE NCC