[routing-wg] ASN reference cleanup

Hi Aftab

It is quite a complex process to automate the removal of these 
references and old references may come back later looking like new 
policy but is still old policy, if the user did not handle the removal 
themselves. We will put some scenarios to you tomorrow and ask some 
questions, but we don't have many answers yet.

Regards
Denis Walker
Business Analyst
RIPE NCC Database Team


On 14/05/2014 11:09, Aftab Siddiqui wrote:
> Hi Denis,
> Just for my understanding. For such clean-ups is there any need to 
> have a policy to remove certain object references or this comes under 
> RIR housekeeping can be done once problem has been identified by the 
> community consensus.
>
> Regards,
>
> Aftab A. Siddiqui
>
>
> On Wed, May 14, 2014 at 1:33 PM, Denis Walker <denis at ripe.net 
> <mailto:denis at ripe.net>> wrote:
>
>     Hi all
>
>     In the DB WG session this afternoon we only touch on the fact that
>     this project is ongoing. I go into more details on the problems we
>     have with this project with my short presentation in the Routing
>     WG tomorrow.
>
>     Regards
>     denis
>
>     On 14/05/2014 10:28, Rob Evans wrote:
>>     Folks,
>>
>>     For any RPSL lovers among you that weren't at the Address Policy WG meeting
>>     this morning, the topic of cleaning up referenced AS numbers came up again.
>>     There are about ~2,000 16 bits ASNs that have been returned, but are still
>>     referenced in the import/export lines of other aut-num objects, either
>>     directly or via as-sets.
>>
>>     There will be more discussion of this in the Database WG this afternoon, but
>>     I thought I'd mention it here as it has implications for those on this list
>>     that use RPSL.
>>
>>     Cheers,
>>     Rob
>>
>>
>>
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: </ripe/mail/archives/routing-wg/attachments/20140514/3fc6e5ff/attachment.html>