<div dir="ltr">Hi Denis,<div>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. </div>
</div><div class="gmail_extra"><br clear="all"><div>Regards,<br><br>Aftab A. Siddiqui</div>
<br><br><div class="gmail_quote">On Wed, May 14, 2014 at 1:33 PM, Denis Walker <span dir="ltr"><<a href="mailto:denis@ripe.net" target="_blank">denis@ripe.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF">
<font size="+1"><tt>Hi all<br>
<br>
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.<br>
<br>
Regards<span class="HOEnZb"><font color="#888888"><br>
denis<br>
<br>
</font></span></tt></font><div><div class="h5">
<div>On 14/05/2014 10:28, Rob Evans wrote:<br>
</div>
<blockquote type="cite">
<pre>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
</pre>
</blockquote>
<br>
</div></div></div>
</blockquote></div><br></div>