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

Denis,

On Mon, Oct 09, 2017 at 02:49:39PM +0100, denis walker via db-wg wrote:
>Question - Should the RIPE Database allow creation of ROUTE
>objects for non RIPE resources?
>
>A: Yes the RIPE Database should allow creation of ROUTE objects
>for non RIPE resources. If this is the answer then we can look
>at how to make the data more trusting in the short term (and
>there may be ways to do that).
>
>B: No the RIPE Database should not allow creation of ROUTE
>objects for any non RIPE resource. If this is the answer then
>maybe we need to look at a project to remove all non RIPE
>resource related ROUTE(6)/AUT-NUM objects from the RIPE Database
>and disable the feature. But that needs to look at what to do
>with ROUTE objects for prefixes from one region and ASNs from a
>different region.
>
>C: Just leave things as they are. Don't promote the service but
>no projects to remove any data from the RIPE Database either.
>Just drift along on the principle "if it ain't broken, don't fix
>it". This also means document this as the answer to this
>question and no more discussions. Of course any problems
>associated with this feature don't go away.

Either A or C, insofar as they are different. Not allowing
"foreign" resources in the ripedb denies the reality that there
will always be RIPE-allocated prefixes originated from
non-RIPE-assigned ASNs and vice versa.

One could make an argument for not allowing route: objects where
both the prefix and ASN are from outside RIPE. This would
complicate (or make impossible) any attempt at automating
acceptance filters, unless and until this information is
available from other (trusted?) sources. As it currently stands,
this would, on balance, be worse for the "good of the internet".

cheers,
Sascha Luck