Re: Last Call: <draft-turner-md5-seccon-update-07.txt> (Updated Security Considerations for the MD5 Message-Digest and the HMAC-MD5 Algorithms) to Informational RFC

[Francis Dupont <[e-mail]>]

I have a concern about no security usages of MD5 for practical reasons:
in some environments, including US Gov, crypto implementations (e.g.,
FIPS 140-2 HSMs) are required to not support MD5 so you can have to
choose between a compliant application and a conformant crypto,
for instance for DNS TSIG...

So IMHO it is still a good idea to avoid MD5 in any uses, even when
it is still far to have been proved insecure or for an use which is
not about security.

This could be caught by the "DEPRECATED" keyword in the registry
but this registry doesn't seem to have usage entries?!

To conclude I am fine with the implicit conclusion of the I-D to
not use MD5 or HMAC-MD5 in new protocols.

Thanks

[e-mail]

PS: I am the gen-art reviewer for this document too.