SHA-1 and SHA2 information in v2.40

["Mr. Darren Johnson" <darren.johnson@safenet-inc.com>]

Hi,
This is related to David Gascon's email about the SHA3 proposal.  I decided to start a separate thread to keep the v2.40 conversation separate from the SHA3 proposal discussion.

The same issues that Dave brought up also exists in 2.40 for SHA-1 and SHA2.  So it looks like it was a simple copy-paste error when the data was propagated to the SHA3 proposal.
 
In the 2.40 spec, the sections for SHA-1, SHA224 and SHA256 all have tables defining function/key-type/data-length/signature-length the for the general length HMAC, but all of the other SHA2 sections for general length HMAC do not have this table.  And the key type field in the table only lists "generic secret" instead of both "generic secret" as well as the mechanisms specific HMAC key type as described in the text above each table.

Is there an official way we should report small changes like this for content in the existing standard so that they get cleaned up in the next revision?  Or does an email suffice and it can be discussed on the next call?  I suspect that a proposal is over kill for this type of change?

Somewhat related to that, is there any specific reason there are no key generation mechanisms for the CKK_SHA_1_HMAC (and the SHA2 equivalent) key types?  Were they just not needed at the time so they were not added to the spec?  Or are they buried in the spec somewhere and I just didn't notice them?

Thanks
Darren