RE: Last Call: AES Companion Hash Definitions (SHA256, SHA384, SHA512) for OTP to Proposed

["Philip J. Nesser II" <phil@Nesser.COM>]

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

NOTE TO IANA:

The only IANA issue is to reserve the algorithm identifiers:

	 sha256	NIST Secure Hash Algorithm 256-bit output
	 sha384	NIST Secure Hash Algorithm 384-bit output
	 sha512	NIST Secure Hash Algorithm 512-bit output

So updates to the page: 
http://www.iana.org/assignments/otp-parameters  must be made.

NOTE TO IESG:

There was a cut/paste error in the code snippets.  I have corrected
them and resubmitted a -01 version of the draft.  I have also put the
official reference to the FIPS standard for SHS now that it has been
finalized.  Since this does not in any material way effect the
contents of the document, I would like to consider this an issue
similar to typographical changes and not need a new last call issued.

Thanks,

- ---> Phil


> -----Original Message-----
> From: IANA [mailto:iana@iana.org]
> Sent: Tuesday, January 21, 2003 11:23 AM
> To: iesg@ietf.org
> Cc: phil@nesser.com
> Subject: RE: Last Call: AES Companion Hash Definitions (SHA256,
> SHA384, SHA512) for OTP to Proposed
> 
> IESG:
> 
> The IANA has reviewed the following Internet-Draft which
> is in Last Call: <draft-nesser-otp-sha-256-384-512-00.txt>,
> and has the following comments with regards to the publication
> of this document:
> 
> We understand there to be no IANA Actions for this document.
> 
> Please respond to the IANA if we have misunderstood this
> document.  Failing to do so may cause delay of the approval
> and publication of your document.
> 
> Thank you.
> 
> Michelle S. Cotton
> (on behalf of the IANA)

-----BEGIN PGP SIGNATURE-----
Version: PGPfreeware 6.5.8 for non-commercial use <http://www.pgp.com>

iQA/AwUBPi5uwA6aViIxlRuuEQLcNACg86xwgLRTVj/sIUVWYgHsQpxPd4cAoOK1
hvmkMQMcptwfQ4hb5GwYa21N
=k75o
-----END PGP SIGNATURE-----