Hi everyone!
We have published Version 0.3.0 of the draft Chrome Quantum-resistant Root Program Policy. This update incorporates early operational feedback from Phase 2 participants, reorganizes major sections for clarity, and adds more granular guidance.
Why we’re sharing this now --
While participants in the earliest phases of our planned rollout have had direct visibility into these draft requirements as part of initial testing, we know that many others, including Phase 3 participants, are actively planning their own roadmaps.
Technical implementation decisions are tightly coupled to policy requirements. Key details, such as HSM requirements, active cosigner key limits, issuance log specifications, and synchronous cosigning expectations, carry lead time for engineering and infrastructure teams. Sharing our current draft policy openly gives everyone early insight into what’s ahead so you can factor these requirements into architecture and testing plans.
A core purpose of this group is community building, and we believe transparency is critical for building a resilient and secure post-quantum web.
Looking ahead --
This draft reflects what we believe best balances the security and safety of Chrome users with practical operational implementation considerations, grounded in feedback from early-phase participants. While different user agents and root programs may naturally arrive at different conclusions for their respective users, our goal with this share-out is to provide clarity and predictability on the direction Chrome is taking.
As always, you can track related specifications in the IETF PLANTS Working Group and follow our overarching Post-Quantum HTTPS Authentication Roadmap. Additionally, any organization currently operating either traditional root CAs or CT logs included in Chrome has the opportunity to be included in the Chrome MTC Testing and Validation Trust Store.
-Chris, on behalf of Chrome's MTCs team