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 Quarterly Planning
- Previous message (by thread): [routing-wg] Fwd: Update on upcoming maintenance to ARIN’s RPKI infrastructure
- Next message (by thread): [routing-wg] RPKI Quarterly Planning
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Daniel Karrenberg
dfk at ripe.net
Mon Jul 12 10:23:20 CEST 2021
Good morning, Natanlie pointed us to https://www.ripe.net/manage-ips-and-asns/resource-management/rpki/rpki-planning-and-roadmap a while ago. Among other things this says: “In preparation for the improved RPKI repository architecture, the distributed nature of the RRDP repository is going to be implemented using containers and krill-sync that pulls data from the centralised on-premise repository. This greatly simplifies smooth transitioning between publication servers without any downtime. NOTE: We are not referring to cloud technologies here, just to our internal deployment technologies.” The silence here worries me. I would like to see some feedback from this group whether this is what you want to see happening. The RIPE Routing WG is the forum for giving guidance to the RIPE NCC about RPKI. I know other channels exist too and that is fine. I also know that individuals here seem to be happy with what is happening. However private channels and conversations are not the way RIPE does this. This group is where the RIPE NCC looks for guidance and where that guidance gets properly archived and responded to. Daniel
- Previous message (by thread): [routing-wg] Fwd: Update on upcoming maintenance to ARIN’s RPKI infrastructure
- Next message (by thread): [routing-wg] RPKI Quarterly Planning
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]