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/db-wg@ripe.net/

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

Sascha Luck [ml] dbwg at c4inet.net
Wed Oct 11 16:21:23 CEST 2017

On Mon, Oct 09, 2017 at 02:49:39PM +0100, denis walker via db-wg wrote:

> Question - Should the RIPE Database allow creation of ROUTE objects for non RIPE resources?

Is an option D: create a central IRRDB with authentication hooks
into all RIRs completely out of the question? It certainly sounds
like the technologically most elegant answer. Modulo legacy
resources, no unauthenticated irrdb objects should then have to
exist. The trust root could be shared between the RIRs as is
seemingly done with RPKI these days...

cheers,
Sascha Luck

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