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

On Wed, Jul 07, 2021 at 10:29:42PM +0100, Nick Hilliard wrote:
> Edward Shryane via db-wg wrote on 07/07/2021 15:05:
> > So 23456 is*not*  excluded, but it can be if the DB-WG agrees.
> 
> just to be clearer: AS23456 should be included in the list of ASNs which
> cannot be used as the origin.

Yes.

> Any objects which refer to it should be flagged for deletion.

Are you referring to RIPE or RIPE-NONAUTH?

In 'RIPE-NONAUTH' no references appear to 23456.

In 'RIPE' (the authoritative database) there are quite a few references
to 23456.

I would propose a "do not disturb existing objects" strategy for data
source 'RIPE'. Because if there are no route/route6 objects with 23456
as 'origin:' (as Cynthia indicated), then the key 'members: AS23456'
will be a NO-OP when doing reverse lookups through IRR AS-SETs to
generate a prefix filterlist.

Kind regards,

Job