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. randy
On Tue, Oct 17, 2017 at 05:18:55PM +0000, Randy Bush via db-wg wrote:
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. Since we are brownfielding, I see no other option than to continue using the historic tag for the main chunk of the database, and split out the non-authoritative data into a different tag. 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. Kind regards, Job
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
On Tue, Oct 17, 2017 at 05:34:13PM +0000, Randy Bush wrote:
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 it were just one script in one place, your snarky response would mean something.
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
http://bikeshed.com/ RIPE-NONAUTH is descriptive and accurate. Kind regards, Job
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 it were just one script in one place, your snarky response would mean something.
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
speaking of snark
RIPE-NONAUTH is descriptive and accurate.
sorry to step on your sensitive toes. randy
Randy Bush via db-wg wrote:
why not go the other, more positive, direction, and identify authorised data with RIPE-AUTH or whatever? no need to be pejorative.
s/RIPE-NONAUTH/RIPE-OTHERRIR/ Nick
why not go the other, more positive, direction, and identify authorised data with RIPE-AUTH or whatever? no need to be pejorative.
s/RIPE-NONAUTH/RIPE-OTHERRIR/
can there be cases where the source is not an rir? rfc1918 for example? s/RIPE-NONAUTH/JOB-HATES/ :) randy
participants (4)
-
Job Snijders -
job＠instituut.net
-
Nick Hilliard -
Randy Bush