Hi Randy I don't think anyone cares how much work a script has to do, whether it's the one that writes or reads the data. But keep in mind that the RIPE Database was designed to be, and still largely is, human readable. So for the poor humans who delve into the database manually it's probably better not to confuse them with extra, new tags on 95% of the data that has the same meaning as before, and just tag that little 5% (or so) that can now be interpreted differently. cheersdenisco-chair DB WG From: Randy Bush via db-wg <db-wg@ripe.net> To: job@instituut.net Cc: Nick Hilliard via db-wg <db-wg@ripe.net> Sent: Tuesday, 17 October 2017, 19:34 Subject: Re: [db-wg] Foreign ROUTE objects in RIPE Database - final decision?

...

...

2) Flag "route:" objects for non-RIPE-managed space with "source: RIPE-NONAUTH" to identify non-authoritative data.

why not go the other, more positive, direction, and identify authorised data with RIPE-AUTH or whatever?  no need to be pejorative.

This is not meant to be pejorative. "RIPE-NONAUTH" was brought up because that way we don't touch the majority of objects that actually are valid, and belong with RIPE.

ahh, the poor overworked script will have less to do so we will have to pay it less.  good plan.

If you have a different suggestion than "RIPE-NONAUTH" I think the group would be all ears. "RIPE-2", "RIPE-OTHER", all is fine with me.

for those old enough to remember, RARE