Re: [Cfrg] What crypto algorithm is referenced most in RFCs?

[Jon Callas <[e-mail]>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

> 
> Jon, I'm sorry for not being more clear. What I was implicitly referring
> to was the lists of active drafts, not RFCs. I agree that for RFCs it is
> more important to look at implementations.
> 
> But the drafts has not yet become the map. Fixing errors in the map to
> be before it is printed isn't that better than waiting until it has been
> printed and in use?
> 
> We basically have two different problems:
> (1) Help implemementations to migrate from algorithms we don't trust
> anymore to the algorithms we trust, algorithms specified in updated
> versions of the map.
> 
> (2) Help map developers avoid specifying use of the bad algorithms so
> that new implementations don't end up using bad algorithms in the first
> place.

Absolutely!

These days it's very easy to pick a good set of building blocks. There are also plenty of things that are mostly okay, but you shouldn't use for new protocols. In the protocol process, it's relatively easy to make sure you're only using the good ones, and for anyone who isn't, we can point out what to do.

	Jon


-----BEGIN PGP SIGNATURE-----
Version: PGP Universal 2.10.0 (Build 554)
Charset: us-ascii

wj8DBQFN+jkWsTedWZOD3gYRAhbPAKDIPfun9JMoLcvFpipR7Zr7cQa+AgCgwECs
mx3l7q0yjofbfBkz+0Bx4TE=
=a+WE
-----END PGP SIGNATURE-----