[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 at instituut.net
job at instituut.net
Tue Oct 17 19:31:36 CEST 2017
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
- 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 ]