[db-wg] Foreign ROUTE objects in RIPE Database - final decision?

* denis1 at gmail.com (den is) [Tue 17 Oct 2017, 03:02 CEST]:
>3) Consider possible, simple options to allow non RIPE resource
>holders to 'approve' (if not authorise) the creation of a foreign
>ROUTE object.

This is cumbersome in practice already.  Options 1 and 2 would lessen
the administrative load of documenting permission of others to route
prefixes; option 3 wouldn't.


On 17 October 2017 at 01:23, William Sylvester wrote:

>1) Remove the "origin:" authorization requirement. RIPE is 
>currently the only RIR that requires this, the current 
>implementation creates data concurrency issues across Internet 
>databases by requiring the creation of duplicate autnums.
>
>2) Flag "route:" objects for non-RIPE-managed space with "source: 
>RIPE-NONAUTH" to identify non-authoritative data.

I support these two.  They would make things simpler that I encounter 
frequently.

Regards,


	-- Niels.