[ietf-dkim] RFC4871bis - whether to drop -- SHA1 support

[Suresh Ramasubramanian]

On Tue, Jun 2, 2009 at 4:22 AM, Jon Callas<jon at callas.org> wrote:
> It is far more important for us to put SHA3 into 4871bis, as that will
> be finalized in 2012, and if you *can't* use it in DKIM, people would
> be justifiably miffed for us.

It'd actually be a good idea to delink specific encryption and hash
algorithms from 4871bis - so that people can use as strong an
algorithm as they like .. possibly specify an "at least sha256" with a
note that points to somewhere you can read up on a balance between
strong crypto and usability / scalability in large deployments.

srs