[db-wg] Foreign ROUTE objects in RIPE Database - final decision?
- Previous message (by thread): [db-wg] Foreign ROUTE objects in RIPE Database - final decision?
- Next message (by thread): [db-wg] Foreign ROUTE objects in RIPE Database - final decision?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Job Snijders
job at instituut.net
Tue Oct 17 19:48:37 CEST 2017
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
- Previous message (by thread): [db-wg] Foreign ROUTE objects in RIPE Database - final decision?
- Next message (by thread): [db-wg] Foreign ROUTE objects in RIPE Database - final decision?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]