Hi, Erik On 06/26/13 23:16, Erik Bais wrote:
However ... there might be situations where someone would be using a certain BGP community in RPLS for internal reference still while the actual AS number isn't used anymore.
Any reference to the returned ASN that do not affect to the routing by itself should not prevent RIPE from reassigning this ASN. No one will prevent End User from placing some references inside his objects to ASNs that wasn't assigned ever. It's not the reason to not assign these ASNs. I think that some validation should be used even for import/export entries and RIPE's database should prevent End User from updating objects with erroneous information. In this case any existing reference inside object to the ASNs that are not assigned (or ASN that were returned to the pool) will make object that is referenced to them non up-to-date and notification may be sent to the resource holder. But my opinion that all references to unassigned objects should be removed by RIPE's software with notification message to the resource holder's contacts. We shouldn't wait any actions from anybody to reassign the resources. As long we talking about RIPE database all similar references may be found by the RIPE's software. Those references may be removed and the resource holders may be notified about this situations. I don't think that it's the problem - multiple regular expressions will do this work for us. -- Best wishes, Andrey Semenchuk Trifle Internet Service Provider (056) 731-99-11 www.trifle.net