[address-policy-wg] [db-wg] Guidance Requested: Reassigning Referenced ASNs

Gert Doering <gert at space.net> schrieb:

Hi,

On Wed, Jun 26, 2013 at 06:40:21PM +0200, Opteamax GmbH - RIPE-Team
wrote:
Actually I don't really understand the problem.  If the ASN is
back in the pool, this reads for me "it shall no longer appear in
the routing table". This includes for me that any object referencing
this ASN is illegal by definition. So these illegal objects may not
exist and *must* be removed asap from the DB. After removing all
illegal objects, they should stay in some "grace-period" - let's
say 3 month - and then there should be no problem reallocating the
asn.

The database currently has no mechanics to prevent someone from
entering
an import/export line that says:

aut-num: AS100000
remarks: have fun with Jens
export: to AS5539 announce AS48200


Got the point,  thanks for making it clearer to me (and maybe some others)

So this might also be a task for the database working group then ;)

Jens
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </ripe/mail/archives/address-policy-wg/attachments/20130626/92fd5b42/attachment.html>