[connect-wg] BCOP for the use of IRR DBs in IXP RS - Last call

Difficult but not impossible, right?

Maybe a reasonable counter-proposal would be to delay the removal of RADB for an extra year until a common API is adopted or a proxy tool is developed ?

Technical solutions exist, is a matter of willingness and I would love to see initiatives into that direction rather seeing ourselves rely on convenient solutions.


Kind Regards
Stavros

From: connect-wg <connect-wg-bounces at ripe.net> on behalf of Arturo Servin via connect-wg <connect-wg at ripe.net>
Date: Friday, 7 June 2024 at 09:51
To: Barry O'Donovan (Open Solutions) <barry at opensolutions.ie>
Cc: Connect-WG <connect-wg at ripe.net>
Subject: Re: [connect-wg] BCOP for the use of IRR DBs in IXP RS - Last call


On Thu, Jun 6, 2024 at 11:21 PM Barry O'Donovan (Open Solutions) <barry at opensolutions.ie<mailto:barry at opensolutions.ie>> wrote:
Hi all,



One comment I did make was that it was paradoxical, on one hand, to
bemoan the depeering of large network(s) from route servers and discuss
how IXPs could engage to bring them back while, on the other hand,
trying to implement a practice which would dictate how and where they
should register their routing objects.


And this will definitely won't help to bring them back (and probably nothing will but we can try ... )

As I mentioned in my previous email, as stated in the MARNS for CDN/Cloud providers their approach for the same problem is different and possibly incompatible.

In a perfect world where all RIR support and have the same APIs to manage IRR objects, this could have an opportunity, but in the current state of affairs for IRR management in RIRs, I think it is difficult.

Regards
as



-------------- next part --------------
An HTML attachment was scrubbed...
URL: </ripe/mail/archives/connect-wg/attachments/20240609/6f5d4686/attachment.html>