[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 ]
Randy Bush
randy at psg.com
Tue Oct 17 19:34:13 CEST 2017
>>> 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
- 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 ]