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]/
[routing-wg] RPKI planning @ RIPE (Was: Support for "Publish in Parent" [RPKI RFC 8181]?)
- Previous message (by thread): [routing-wg] RPKI planning @ RIPE (Was: Support for "Publish in Parent" [RPKI RFC 8181]?)
- Next message (by thread): [routing-wg] RPKI planning @ RIPE (Was: Support for "Publish in Parent" [RPKI RFC 8181]?)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Nathalie Trenaman
nathalie at ripe.net
Mon Sep 20 16:18:09 CEST 2021
Dear Job, all, > Op 20 sep. 2021, om 15:37 heeft Job Snijders <job at 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-planning-and-roadmap Kind regards, Nathalie Trenaman RIPE NCC [2] https://www.apnic.net/wp-content/uploads/2017/01/route-roa-management-guide.pdf <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) -------------- next part -------------- An HTML attachment was scrubbed... URL: </ripe/mail/archives/routing-wg/attachments/20210920/a50eb8cd/attachment.html>
- Previous message (by thread): [routing-wg] RPKI planning @ RIPE (Was: Support for "Publish in Parent" [RPKI RFC 8181]?)
- Next message (by thread): [routing-wg] RPKI planning @ RIPE (Was: Support for "Publish in Parent" [RPKI RFC 8181]?)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]