[db-wg] RIPE NONAUTH route(6) objects using unregistered space cleanup - deployment *today*

Hi Cynthia,

> On 29 Jun 2021, at 15:00, Cynthia Revström <me at cynthia.re> wrote:
> 
> Hi Ed,
> 
> Thanks for implementing this :)
> 

Thanks for your feedback.

> I mainly wanted to give my initial take on the AS origin status part which is in short: I don't think we should clean up based on origin AS.
> This is as you do not need any technical authorization from the AS holder to create a route(6) object.
> Additionally, I don't think this is validated in RIPE AUTH, but I could be wrong on that part.
> 
> I might have a different opinion if it is a huge amount of objects that could be cleaned up or if it is such a tiny amount that maybe just contacting the maintainers manually would be enough.
> Summary: I don't think it is a good idea unless it is either a very large amount of objects, a very trivial task, or there is another good reason to do so.
> 
> -Cynthia
> 

I found 1,577 route objects (out of 55,960) and 43 route6 objects (out of 1,522) in the RIPE-NONAUTH database which reference an unregistered AS number (i.e. "available" or "reserved" in any RIRs delegated stats).

Of these, there are 169 distinct unregistered AS numbers referenced by route(6) objects in RIPE-NONAUTH.

As we don't validate the origin AS number in the RIPE database (apart from excluding bogon space according to: http://www.team-cymru.com/bogon-reference.html), I also checked route(6) objects there.

I found 72 routes and 20 route6 objects in the RIPE database which reference an unregistered AS number (41 distinct AS numbers).

Regards
Ed Shryane
RIPE NCC

-------------- next part --------------
An HTML attachment was scrubbed...
URL: </ripe/mail/archives/db-wg/attachments/20210630/c111da91/attachment.html>