By Julio Gomez,
Publication Date: 2026-09-28 17:47:00
I know, I know… I said I was done with the IPsec series, BUT what would this series say about me if I did not automate everything??
In the last few blog posts we reviewed the CLI story: classical baseline, PPK, ML-KEM hybrid, ML-DSA certificates, the atomic cutover. That’s how you LEARN a platform. But that is not how you RUN a fabric.
And if you’ve been hanging around DevNet for a while, you already know the next move. That was the point the whole time: enable the community on programmability so you can stop typing at boxes and start driving them through APIs. YANG, NETCONF, RESTCONF, Ansible: years of that work. API-driven automation was one of the main goals. Let’s now use those habits to configure Post-quantum IPsec!
Type the same IKEv2 profile on three boxes, change two addresses, and you’ll get two routers agreeing and one that doesn’t. You’ll find out a week later. The post-quantum posture is a decision: ML-KEM-768, optional or required, ML-DSA-65. You…
