Randy Bush <randy@psg.com> schrieb:
If the ASN is already returned to the pool, it means that the RIPE had tried to communicate with the resource holder at least three times during at least 3 month.
the resource holder of a route: object owns the ip space, not necessarily the asn.
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. I mean, IPv4 is also reallocated pretty quickly, as my last /22 existed in my routing table announced from a London based ASN less than two months before it was allocated to my LIR. BTW: IMHO the database shall also be cleaned from route6 objects with invalid netmasks ... but that's a different topic ;) BR Jens
randy
!DSPAM:637,51cb0c70196951779145505!