On 06/25/13 18:47, Nick Hilliard wrote:
On 25/06/2013 14:02, Andrea Cima wrote:
A. Not reassign referenced AS numbers B. Reassign AS numbers even if referenced C. Clean up the RIPE Database from references and then reassign the AS numbers C.1. "Silent" update; or C.2. Informing the object holder of the update My preference would be for C.1, and that the process of reassignment should not be delayed by replies or a lack of replies from object holders who are referencing the ASNs.
As this is an operational issue, is there a need for a policy proposal?
Nick
Fully agree with Nick Communication with resource holders that referenced to unused ASN is the way to waste time. 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. So, there's no necessity to provide additional time to communicate with someone. Moreover: the ASN assigned to no one, so clearing the database from the erroneous reference will not affect to any resource holder (it's because there's no the ASN holder any more) and all references may be cleared as soon the ASN is returned to the pool. All the RIPE may to do - is to notify a holder of the resource that was silently cleared (but after the object was cleared) So, C.1 - is the good choice -- Best wishes, Andrey Semenchuk Trifle Internet Service Provider (056) 731-99-11 www.trifle.net