PQC migration checkpoints of shared services
The checkpoints a post-quantum migration of a shared service goes through, who owns each one by role, what it waits for, the kind of each date and what a slip would delay. External prerequisites such as standards and industry rules carry their real status from recorded sources.
Reference model, not an agreed plan. No participant has agreed this plan and no coordination governance exists, so no checkpoint is agreed, no date is participant-agreed and no operational board is active. Participant checkpoints are proposed and undated. Owners are roles, never people. Not compliance advice.
Choose a reference service
Checkpoint boards
- Public website over TLS behind a CDN and a load balancer, with an HSM-backed certificate authority
- Site-to-site IPsec VPN (IKEv2) between two organisations
- SSH administration of servers, partly by an outsourced operator
- Code signing and firmware updates from a supplier to an operator's devices
- Qualified electronic signatures and seals with a qualified trust service provider
Kinds of date, kept apart
- Unknown: no date published or agreed
- Nothing published or agreed. Unknown dates stay unknown; the portal never fills them in.
- Vendor roadmap date
- A target a supplier announced for a release. A roadmap is not a release; shown only once an editor approved the vendor evidence in the product navigator.
- Official guidance target
- A date an authority sets as guidance, as the PQC migration timeline records it. Not a legal deadline and not agreed between the parties.
- Verified legal obligation
- A date a recorded legal act sets. None of the reference services has one.
- Participant-agreed date
- A date the parties of a service agreed. None exists: this is a reference model.