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] IRRd re-write
- Previous message (by thread): [db-wg] IRRd re-write
- Next message (by thread): [db-wg] IRRd re-write
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Sascha Luck [ml]
dbwg at c4inet.net
Mon Jun 18 15:08:35 CEST 2018
On Mon, Jun 18, 2018 at 12:43:22PM +0000, denis walker via db-wg wrote: >Currently 4 of the 5 RIRs operate an IRR and they are all based on a version of the RIPE Database software. So we already have a common IRR database format. Add in this cross registry authorisation and we have a global IRR. I don't see the point of putting in the effort to develop a multitude of alternative/commercial IRRs when we can go the other way and have a single, authoritative, free IRR service. We have one internet, one DNS, why not one IRR? A single IRR is a single point of failure and a single point of attack. Much preferrable would be if all IRRs mirrored the authorisation data from all other (RIR?) IRRs. Am I correct in thinking that this is now done for RPKI data in order to address the SPOF problem? rgds, Sascha Luck
- Previous message (by thread): [db-wg] IRRd re-write
- Next message (by thread): [db-wg] IRRd re-write
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]