RPKI planning @ RIPE (Was: Support for "Publish in Parent" [RPKI RFC 8181]?)
Dear Nathalie, group, On Mon, Sep 20, 2021 at 03:11:22PM +0200, Nathalie Trenaman wrote:
Please be aware that the roadmap you mentioned just shows the roadmap for the current quarter and not for a longer period.
Ah, thank you for the clarification. Are there any other items that predate the existence of the "Community Input on Planning" table on [1]? As some RPKI projects are multi-quarter or even multi-year projects, it might be good to expand the community's visibility into the list of RPKI-related work items which RIPE NCC to some degree has accepted, but not yet scheduled. Kind regards, Job [1]: https://www.ripe.net/manage-ips-and-asns/resource-management/rpki/rpki-plann...
Dear Job, all,
Op 20 sep. 2021, om 15:37 heeft Job Snijders <job@fastly.com> het volgende geschreven:
Dear Nathalie, group,
On Mon, Sep 20, 2021 at 03:11:22PM +0200, Nathalie Trenaman wrote:
Please be aware that the roadmap you mentioned just shows the roadmap for the current quarter and not for a longer period.
Ah, thank you for the clarification.
Are there any other items that predate the existence of the "Community Input on Planning" table on [1]?
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. This is why we decided to go for a more transparent framework. Also, because it was hard to read the demand for these features. To give the WG some examples from the last 12 months: -Route object integration in the RPKI Dashboard of my.ripe.net <http://my.ripe.net/> (similar as APNIC) [2] -Mandatory 2FA for the RPKI Dashboard -API session timeouts It would be good, in a separate thread maybe, to discuss if the working group sees these features as useful.
As some RPKI projects are multi-quarter or even multi-year projects, it might be good to expand the community's visibility into the list of RPKI-related work items which RIPE NCC to some degree has accepted, but not yet scheduled.
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.
Kind regards,
Job
[1]: https://www.ripe.net/manage-ips-and-asns/resource-management/rpki/rpki-plann...
Kind regards, Nathalie Trenaman RIPE NCC [2] https://www.apnic.net/wp-content/uploads/2017/01/route-roa-management-guide.... <https://www.apnic.net/wp-content/uploads/2017/01/route-roa-management-guide.pdf> (PDF) [3] https://ripe82.ripe.net/presentations/81-Routing-WG-RIPE82-Nathalie.pdf <https://ripe82.ripe.net/presentations/81-Routing-WG-RIPE82-Nathalie.pdf> (PDF)
Thanks Nathalie, On Mon, Sep 20, 2021 at 04:18:09PM +0200, Nathalie Trenaman wrote:
-Route object integration in the RPKI Dashboard of my.ripe.net <http://my.ripe.net/> (similar as APNIC) [2] -Mandatory 2FA for the RPKI Dashboard -API session timeouts
It would be good, in a separate thread maybe, to discuss if the working group sees these features as useful.
Discussion in separate threads sounds good. Kind regards, Job
participants (2)
-
Job Snijders -
Nathalie Trenaman