Dear Denis, On Wed, Jan 10, 2018 at 11:21:44PM +0000, denis walker via db-wg wrote:

In December I asked if we should continue to allow the creation of new ROUTE(6) objects in the RIPE Database (with the new source tag) for non RIPE address space. There were a few comments supporting the view NOT to allow any new object creations. There were no comments supporting the continued creation of any new objects. During the earlier, lengthy discussion on NWI-5 quite a few people supported the use of the RIPE Database for ROUTE(6) objects for non RIPE address space. With the plan to drop the ASN auth requirement are those people satisfied that we no longer need to create these ROUTE(6) objects in the RIPE Database?

So basically I am making a last call to see if anyone still feels there is any need to allow creation of any new ROUTE(6) objects in the RIPE Database for non RIPE address space?

I don't think there is a good case to continue to allow the creation of new ROUTE(6) objects in the RIPE DB for non RIPE address space. I'm seeing quite some abuse of this 'feature', where spammers/hijackers register out-of-region prefixes to sneak them into people's prefix-list filters. It would be good if that hole can be plugged. Separately, a study should be done on how to deal with the existing non-RIPE-managed ROUTE(6) objects in the DB. Maybe some cleanup can be done for at least for a subset of those objects. Kind regards, Job