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]/
[members-discuss] Draft Activity Plan 2021 - RPKI development
- Next message (by thread): [members-discuss] Draft Activity Plan 2021 - RPKI development
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Fredrik Korsbäck
fredrik.korsback at gmail.com
Thu Oct 1 14:28:25 CEST 2020
+1 on this aswell. I have been operating validators for a few years now in production at various companies, and I see no point to keep the RIPE Validator stack alive. Even with significant improvements to the code i don't see that we can "save" it and make it a viable choice going forward for real production enviroements, i dont think that RIPE is the right place to develop a replacement either.. Discontinue the support for the software as suggested on Jan 1st 2021. And then move the full suggested budget over to the operational department of RIPE NCC, strengthen the operations and scale around the RPKI CA. The RPKI CA, for RIPE and for others, plays a MAJOR role as critical internet infrastructure. This is services that needs Oncall 24/7 support, testing-enviroments, scaled out infrastructure, thoughtful crypto-implementations and other such things, nothing of this comes cheap and we might even need more budget allocated for this in the future. ------------ Best Regards Fredrik Korsbäck Amazon Web Services (but speaking for myself in this context) On Mon, Sep 28, 2020 at 6:01 PM Aaron A. Glenn <ripe at aagico.com> wrote: > > > On Fri, Sep 25, 2020, at 16:21, Gert Doering wrote: > > Hi, > > > > On Mon, Sep 21, 2020 at 01:33:43PM +0000, Erik Bais wrote: > > > I would like to see further development of the RIPE NCC RPKI Validator > discontinued as of Jan. 1st 2021. > > > > This. > > > > When we looked at possible software options for our RPKI validator, we > > compared performance, memory, robustness, agility of development, and > > this all concluded in "this was nice as a demonstration vehicle, but I > do > > not want to run it near a any production system, ever". > > This is a common refrain I have heard and experienced first hand. I would > like to also add my voice to the suggestion of discontinuing (significant) > software development costs in relation to the RPKI validator. > > --- > Aaron A. Glenn > > +1 (877) 926-5767 > AAGlenn Internetworking Company > Cheyenne, WY 82001 | +1 (307) 316-5767 > > _______________________________________________ > members-discuss mailing list > members-discuss at ripe.net > https://mailman.ripe.net/ > Unsubscribe: > https://lists.ripe.net/mailman/options/members-discuss/fredrik.korsback%40gmail.com > -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://www.ripe.net/ripe/mail/archives/members-discuss/attachments/20201001/4cdc3e67/attachment.html>
- Next message (by thread): [members-discuss] Draft Activity Plan 2021 - RPKI development
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]