Heart of his argument is this, with which I absolutely agree:<p>"The moral is the need for cryptographic agility. It’s not enough to implement a single standard; it’s vital that our systems be able to easily swap in new algorithms when required. We’ve learned the hard way how algorithms can get so entrenched in systems that it can take many years to update them: in the transition from DES to AES, and the transition from MD4 and MD5 to SHA, SHA-1, and then SHA-3."<p>Although, personally, I am more supportive of the OpenVPN model (many standards to choose from, including older algos, maybe too much choice) compared to the Wireguard model (one set of well thought of defaults, no choice), one has to ask -- aren't they both wrong? Isn't the correct model high flexibility, while relentlessly deprecating and <i>removing</i> older standards, and, maybe, a clear nudge towards sensible default choices ("X recommends the following algos in 2022...").<p>Obviously crypto is super hard. But the 'problem of agility' seems like a software engineering problem not a hard crypto theoretical or implementation issue.