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

Daniel Shaw via db-wg wrote:
> On 17/10/2017, 03:24, William Sylvester via db-wg	typed:
>> > 
>> > 
>> > 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’d like to seek input from the group;
>> > 
>> > - Do you feel these options are straight forward and easy to understand?
>> > - Does this provide a reasonable security posture?
>> > - Will this make a positive impact for RIPE DB and the greater Internet?
>> > - Do you support these concepts?
>> > 
> 
> Yes. There isn't really any downside to these. There are clear benefits to both.

Agreed.  This sounds like a sensible thing to do.

Nick