This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/

[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 ]

Daniel Shaw daniel at afrinic.net
Tue Oct 17 09:06:15 CEST 2017

On 11/10/2017, 17:48, Nick Hilliard via db-wg	typed:
> 
> 
> Job Snijders wrote:
>> I think this touches upon an incredibly important question: how do we
>> distinguish between garbage and properly authenticated "route:"
>> objects covering RIPE-managed space?
> 
> and more to the point: are there good reasons and community support for
> continuing not to distinguish between the two.

Quite so. I cannot see any.

Having a flag/label that makes it clear right away how much authentication a given route:/rotue6: object has associated with it can only be a good thing.

That doesn't change the existence or creation of any class of object. But clearly marking what is what seems a no brainer to me.

Thanks,
Daniel

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 ]