<html><head><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Dear Job, all,<br class=""><div><br class=""><blockquote type="cite" class=""><div class="">Op 20 sep. 2021, om 15:37 heeft Job Snijders <<a href="mailto:job@fastly.com" class="">job@fastly.com</a>> het volgende geschreven:</div><br class="Apple-interchange-newline"><div class=""><div class="">Dear Nathalie, group,<br class=""><br class="">On Mon, Sep 20, 2021 at 03:11:22PM +0200, Nathalie Trenaman wrote:<br class=""><blockquote type="cite" class="">Please be aware that the roadmap you mentioned just shows the roadmap<br class="">for the current quarter and not for a longer period. <br class=""></blockquote><br class="">Ah, thank you for the clarification.<br class=""><br class="">Are there any other items that predate the existence of the "Community<br class="">Input on Planning" table on [1]?<br class=""></div></div></blockquote><div><br class=""></div><div>No, not formally at least. In the past I received some feature requests to my direct e-mail address. Some from individual community members, some through different fora. </div><div>This is why we decided to go for a more transparent framework. Also, because it was hard to read the demand for these features. </div><div>To give the WG some examples from the last 12 months:</div><div><br class=""></div><div>-Route object integration in the RPKI Dashboard of <a href="http://my.ripe.net" class="">my.ripe.net</a> (similar as APNIC) [2]</div><div>-Mandatory 2FA for the RPKI Dashboard</div><div>-API session timeouts</div><div><br class=""></div><div>It would be good, in a separate thread maybe, to discuss if the working group sees these features as useful.</div><br class=""><blockquote type="cite" class=""><div class=""><div class=""><br class="">As some RPKI projects are multi-quarter or even multi-year projects,<br class="">it might be good to expand the community's visibility into the list of<br class="">RPKI-related work items which RIPE NCC to some degree has accepted, but<br class="">not yet scheduled.<br class=""></div></div></blockquote><div><br class=""></div><div>At RIPE82, I published the rough time lines for the work in 2021 on slide 12 and 13. [3] As you can see, the quarterly roadmap follows this time line (approximately). I intend to do the same for 2022 as soon as the budget and activity plan are approved. </div><br class=""><blockquote type="cite" class=""><div class=""><div class=""><br class="">Kind regards,<br class=""><br class="">Job<br class=""><br class="">[1]: <a href="https://www.ripe.net/manage-ips-and-asns/resource-management/rpki/rpki-planning-and-roadmap" class="">https://www.ripe.net/manage-ips-and-asns/resource-management/rpki/rpki-planning-and-roadmap</a><br class=""></div></div></blockquote><br class=""></div><div>Kind regards,</div><div><br class=""></div><div>Nathalie Trenaman</div><div>RIPE NCC</div><div><br class=""></div><br class=""><div class="">[2] <a href="https://www.apnic.net/wp-content/uploads/2017/01/route-roa-management-guide.pdf" class="">https://www.apnic.net/wp-content/uploads/2017/01/route-roa-management-guide.pdf</a> (PDF)</div><div class="">[3] <a href="https://ripe82.ripe.net/presentations/81-Routing-WG-RIPE82-Nathalie.pdf" class="">https://ripe82.ripe.net/presentations/81-Routing-WG-RIPE82-Nathalie.pdf</a> (PDF)</div><div class=""><br class=""></div><div class=""><br class=""></div></body></html>