On 20 July 2026, RIPE Labs published Ties Dirksen’s research into independently operated RPKI publication servers. The work looks beyond the regional registries to the smaller organisations that publish routing authorisations. It draws attention to the people and services behind a security control often discussed mainly in terms of adoption.
RPKI allows address holders to publish authorisations for the origin of routes. Our operating perspective is that those records should be treated as maintained infrastructure, with an owner and a change process.
Connect the record to the change
A network migration may involve a new origin, a different announcement plan or a transfer of responsibility between teams. The routing authorisation needs to remain consistent with the intended network state throughout that work.
We would include the relevant records in the migration plan from the beginning. The plan should identify who can change them, who verifies the result and when each action occurs relative to the routing change. Discovering an access problem during the cutover is an avoidable dependency.
Document where responsibility sits
Using a third-party publication service changes how the work is performed. It does not remove the need to know who is responsible for account access, authorisation changes and escalation when publication fails.
The same principle applies to a self-operated service. A named technical owner needs a supported process, access to recovery material and another person capable of taking over. Independence can provide control, but it also creates maintenance obligations that should be understood before choosing the model.
Check the outcome after deployment
A completed configuration task should be followed by a check of the resulting routing and validation state. The review should cover expected announcements and any exceptions introduced for the migration. Temporary arrangements need an expiry or an explicit decision to retain them.
We would keep a concise record of the intended state, verification and rollback decision. That record helps the next team understand why a route is authorised and what must change if the network moves again.
A routing authorisation is part of the operating record of a network. Assigning it the same ownership and review discipline as other production configuration makes that record easier to trust.