Re: Evaluation: draft-nesser-otp-sha-256-384-512 - AES Companion Hash Definitions (SHA256, SHA384, SHA512) for OTP to Proposed Standard

[Harald Tveit Alvestrand <harald@alvestrand.no>]

I think I have not written up my DISCUSS - at least it did not make it to 
the ballot. Here it is.

--On 2. juni 2003 11:52 -0400 IESG Secretary <iesg-secretary@ietf.org> 
wrote:

> Harald Alvestrand   [   ]     [   ]       [ X ]      [   ]
The document uses C code fragments to specify its algorithms, but uses 
libraries the functionality of which is not defined in the document (the 
sha functions and structures).

This violates the IESG guidelines on use of formal languages:
<http://www.ietf.org/IESG/STATEMENTS/pseudo-code-in-specs.txt>

If the libraries are completely specified in the FIPS document referenced, 
a sentence saying that is sufficient.
NOTE: The FIPS document is a normative reference.