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/members-discuss@ripe.net/
[members-discuss] Draft Activity Plan 2021 - RPKI development
- Previous message (by thread): [members-discuss] Draft Activity Plan 2021 - RPKI development
- Next message (by thread): [members-discuss] [ncc-announce] [GM] Draft RIPE NCC Activity Plan and Budget 2021
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Robert Scheck
robert.scheck at etes.de
Mon Sep 28 13:48:41 CEST 2020
Hello Hans Petter and fellow members, On Mon, 21 Sep 2020, Erik Bais wrote: > I would like to argue that further development of Proof of Concept software (the RPKI validator) isn't required anymore now that there are multiple open source tools available on the market. > > The RIPE NCC isn't a software development house .. and I don't recall the RIPE NCC has the planning to become one ... > I would like to see further development of the RIPE NCC RPKI Validator discontinued as of Jan. 1st 2021. I completely agree. On Fri, 25 Sep 2020, Gert Doering wrote: > 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". Yes, I agree with that, too. And: When looking to the current RIPE NCC RPKI Validator status, the average time of about 87+ days to fix security issues (based on #158, #159, #162, #232, #255 from ticket opening till closure) is not what I would like to see near a production system either...as of this moment some of the security issues are still unresolved! Even if one of the current alternative RPKI validators would disappear for whatever reason, I would nowadays not consider switching to the RIPE NCC RPKI Validator, sorry. I'm aware that I might not give enough credits to the RIPE NCC's internal development team while there was a lack of other software...and I really appreciate their past work, but I definitely would like to see the RIPE NCC shift the focus from the validator software development towards the RPKI infrastructure as soon as possible. Kind regards Robert Scheck -- Robert Scheck Mail: robert.scheck at etes.de ETES GmbH Fon : +49 (7 11) 48 90 83 - 12 Talstraße 106 Fax : +49 (7 11) 48 90 83 - 50 D-70188 Stuttgart Web : http://www.etes.de/ Registergericht: Amtsgericht Stuttgart HRB 721182 Geschäftsführender Gesellschafter: Markus Espenhain Sitz der Gesellschaft: Stuttgart USt.-Id.Nr.: DE814767446 Folgen Sie uns auch bei Facebook (https://www.facebook.com/ETES.IT) und Twitter (https://twitter.com/systemhaus). Wir würden uns freuen, wenn Sie unseren Newsletter (1x pro Monat) abonnieren würden. (https://www.etes.de/blog/newsletter/) -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 4121 bytes Desc: S/MIME Cryptographic Signature URL: <https://www.ripe.net/ripe/mail/archives/members-discuss/attachments/20200928/7133414f/attachment.p7s>
- Previous message (by thread): [members-discuss] Draft Activity Plan 2021 - RPKI development
- Next message (by thread): [members-discuss] [ncc-announce] [GM] Draft RIPE NCC Activity Plan and Budget 2021
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]