[db-wg] Solving the issue of rogue ROUTE objects in the RIPE Database

On Sat, Nov 07, 2015 at 06:49:07AM +0900, Randy Bush wrote:
> > STEP 1
> > 
> > Any ROUTE object submitted for creation in the RIPE Database involving
> > an out of region resource (address space and/or ASN) where that out of
> > region resource does not exist in the authoritative RIR database (has
> > not been allocated or assigned), reject the creation.
> > 
> > The RIPE NCC mirrors the operational data from all the other 4 RIRs.
> > These mirrors are updated daily as well as the RIRs daily stats. It is
> > easy to determine if a resource is registered in the authoritative
> > database.
> 
> most other rir irr instances are unused.  radb is used.  i think there
> is an altdb which is used.

The following RIR IRR's are in use today: RIPE, APNIC, AfriNIC, ARIN.
Three out of four apply a mechanism which ensures a high level of
certainty that the route-objects covering the respective RIR's managed
space are authenticated in a proper way. ARIN does not validate against
their RIR database at this moment. LACNIC has no IRR.

I do not agree with "most rir irr instances are unused".