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]/
Fw: [db-wg] Foreign ROUTE objects in RIPE Database - final decision?
- Previous message (by thread): [db-wg] RIPE Access Account: Cannot change registered e-mail address back to previously one
- Next message (by thread): DB signatures
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
denis walker
ripedenis at yahoo.co.uk
Fri Oct 13 13:43:15 CEST 2017
Second attempt to get through the mailing system.... ----- Forwarded Message ----- From: denis walker <ripedenis at yahoo.co.uk> To: Sascha Luck [ml] <dbwg at c4inet.net> Cc: Database WG <db-wg at ripe.net> Sent: Wednesday, 11 October 2017, 19:40 Subject: Re: [db-wg] Foreign ROUTE objects in RIPE Database - final decision? Hi Sascha, all I see this as a real possibility for the longer term. But realistically it is not going to help with the situation in the near future. I see some think that RADB is already a 'central DB' whereas others in this thread have said they would not use RADB (don't know it that is for technical, political or reliability issues). Just to throw a wild idea into the pot on this. If we were to look into the possibility of a centralised database, at least for the three RIRs who use a common database root RIPE, APNIC, Afrinic, then to me it makes sense to have a common, public database for operational data not only for routing information but also for number resource information. Then such a common database could do proper authentication. Almost certainly the personal data referenced by the operational data would need to remain in separate regional databases for privacy and data protection reasons. From the point of view of managing globally unique resources it makes perfect sense. But I suspect there would be lots of opposition to such a suggestion for political and self preservation reasons from many directions. Bearing in mind that any such suggestion would takes years from an idea to reality, I don't think we should get too bogged down in discussing this as part of this thread. However, several people have mentioned the idea of proper management of global resources. So perhaps if someone feels the desire to raise the issue in Dubai and formally call for the start of a serious investigation process that could lead to a common operational database, then the ball will at least start rolling.... cheersdenisco-chair DB WG From: Sascha Luck [ml] via db-wg <db-wg at ripe.net> To: denis walker <ripedenis at yahoo.co.uk> Cc: Database WG <db-wg at ripe.net> Sent: Wednesday, 11 October 2017, 16:21 Subject: Re: [db-wg] Foreign ROUTE objects in RIPE Database - final decision? 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: </ripe/mail/archives/db-wg/attachments/20171013/b55d85f2/attachment.html>
- Previous message (by thread): [db-wg] RIPE Access Account: Cannot change registered e-mail address back to previously one
- Next message (by thread): DB signatures
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]