It is a broken situation imho.. I would like to see this fixed by setting a path forward along the following lines : - Communicate (via the INETNUM IRR’s) contact the legitimate holder and inform them that the route objects will be removed by date X (or sooner once there is a newer Route Object in the valid IRR DB. ) - And I would like to get some notification remarks in the current objects that these are incorrect objects that can’t be ‘updated’ anymore in the RIPE DB.. only in the actual INETNUM DB.. and can only be deleted. Any date / time is from my perspective up for debate, if it is less than 18 months … That should be more than enough to get this fixed or re-write whatever code is required imho. Just my 2cp. Erik Bais On 18/07/2017, 17:51, "Tim Bruijnzeels" <tim@ripe.net> wrote: > On 18 Jul 2017, at 17:03, Sander Steffann via db-wg <db-wg@ripe.net> wrote: > > > From: Sander Steffann <sander@steffann.nl> > Subject: Re: [db-wg] out of region routing in the RIPE Database > Date: 18 July 2017 at 16:10:09 GMT+2 > To: George Michaelson <ggm@algebras.org> > Cc: Nick Hilliard <nick@foobar.org>, Database WG <db-wg@ripe.net>, denis walker <ripedenis@yahoo.co.uk> > > > Hi George, > >> I think the previously stated position from APNIC region is clear: we >> have problems with the logistics which permit resources from our >> region to be included in IRR statements in the RIPE DB, when no formal >> check is made of permission or integrity, and we do not see any clear >> path to a deployable mechanism to provide authorization checks over >> resources from out of region. >> >> its a broken process. it inherently permits things to be said, which >> should not have been said. > > Time to set up a joint IRR database where only authoritative data from participating RIRs is stored? Thanks sander, we will certainly look into the options and report back to the wg group. Tim