Re: Broken SHA-1

I suggest the following approach...

Someone (or more) write a W3C Note that defines the "obvious" URI's 
(i.e., in the DSIG namespace) for sha-256, sha-512, and ripemd-160.
In the note say something like
	while not a formal recommendation or standards track RFC, 
implementations complying with this note MUST implement sha256 and 
sha512 and MAY implement RIPEMD160."

Then work to get the W3C Note used as the basis for an XML DSIG errata 
and an IETF RFC.

	/r$

-- 
Rich Salz, Chief Security Architect
DataPower Technology                           http://www.datapower.com
XS40 XML Security Gateway   http://www.datapower.com/products/xs40.html

Received on Friday, 18 February 2005 15:38:39 UTC