<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Hi Daniel,<br class=""><div><br class=""><blockquote type="cite" class=""><div class="">Op 19 feb. 2021, om 09:33 heeft Daniel Suchy via routing-wg <<a href="mailto:routing-wg@ripe.net" class="">routing-wg@ripe.net</a>> het volgende geschreven:</div><br class="Apple-interchange-newline"><div class=""><div class="">Hi Nathalie,<br class=""><br class="">On 2/19/21 9:15 AM, Nathalie Trenaman wrote:<br class=""><blockquote type="cite" class="">We can do many things but our main concern is to implement what is<br class="">needed in a way that we can manage effectively and with input from all<br class="">the relevant stakeholders. You've provided a big list here and some of<br class="">these are already on our roadmap. For example, ROV in AS3333, we are<br class="">working on this, and we expect to come with an announcement soon.<br class=""></blockquote><br class="">Can you share your roadmap? I think also plans and timeline should be open. As these plans exists, you can just publish such document(s) for those who're interested.<br class="">I think community should be informed in advance about plans - not just ex-post by "marketing" announcements about done things.<br class=""></div></div></blockquote><div><br class=""></div><div>I shared the RPKI roadmap on RIPE Labs last year: <a href="https://labs.ripe.net/Members/nathalie_nathalie/where-were-at-with-rpki-resiliency" class="">https://labs.ripe.net/Members/nathalie_nathalie/where-were-at-with-rpki-resiliency</a></div><div>and the work plan for this year has recently been finalised and will first be presented to the Executive Board in March. After that, I will publish another RIPE Labs article with the work plan for this year and announce it in this working group as well. </div><div><br class=""></div><br class=""><blockquote type="cite" class=""><div class=""><div class=""><br class=""><blockquote type="cite" class="">Also, open-sourcing the RPKI core is on our roadmap, but this will take<br class="">a bit longer.<br class=""></blockquote><br class="">Can you explain in detail, where's problem with opensourcing RPKI core (publishing it's code)? Are there some legal reasons or there's something else blocking publishing code you're using? As above, how long we have to wait? I think (open) community review is important also from security perspective for this critical part of internet infrastructure.<br class=""><br class=""></div></div></blockquote><div><br class=""></div><div>I agree that open sourcing the RPKI core is important, and so are many other things that we are working on. Please be assured that this is on our radar and we’ll move forward with this as soon as we can. </div><br class=""><blockquote type="cite" class=""><div class=""><div class="">- Daniel<br class=""><br class=""></div></div></blockquote></div><br class=""><div class="">Kind regards,</div><div class="">Nathalie Trenaman</div><div class="">Routing Security Programme Manager</div><div class="">RIPE NCC</div></body></html>