Proposal: CKM_SHA512_224, CKM_SHA512_256, CKM_SHA512_T [AMENDED]

[Dina Kurktchi <dina.kurktchi@oracle.com>]

Proposal: CKM_SHA512_224, CKM_SHA512_256, CKM_SHA512_T
[AMENDED]

I've attached an amended version of the same proposal,
posted last week Aug 2, with these modifications based
on comments:

- clarify FIPS 180-4, *section 5.3.6* as the source

- clarify that these are digests *based on SHA-512 but
  with distinct initial hash values*, in addition to
  truncation

- state that CKM_SHA512_224 = CKM_SHA512_T, t=224 and
  CKM_SHA512_256 = CKM_SHA512_T, t=256

- fixed a significant error that the parameter to
  CKM_SHA512_T is the *value of t in bits*, not the
  length of the digest t/8 in bytes; and that the
  digest output length is still (t/8) bytes, but it
  should be *ceil(t/8) bytes*

- the "missing" references in the Word version should
  resolve themselves when inserted into the main body
  of the spec from which I cut this out

I did not make the change wherein the SHA-512/t section
is the main section, and the special cases SHA-512/224
and SHA-512/256 are subsections.  The nesting of the
sections seemed to make it less readable as it got
deeper.

Thanks again,
D.

On 08/02/13 16:12, Dina Kurktchi wrote:
> Proposal: CKM_SHA512_224, CKM_SHA512_256, CKM_SHA512_T
>
>
> Addition of new hash algorithms defined in FIPS 180-4:
> SHA-512/224, SHA-512/256, and general case SHA-512/t.
>
> FIPS PUB 180-4, "Secure Hash Standard (SHS)", March 2012
> http://www.nist.gov/manuscript-publication-search.cfm?pub_id=910977
>
>
> The text attached can be inserted immediately after what
> is now section 2.21 in "PKCS #11 Cryptographic Token
> Interface Current Mechanisms Specification Version 2.40".
> The general case SHA-512/t is included for completeness.
>
> This proposal is independent of Robert Burns' "Proposal:
> Update references to FIPS PUB 180". The two ought to be
> complementary though.
>
>
> Thanks,
> D.
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this mail list, you must leave the OASIS TC that
> generates this mail.  Follow this link to all your TCs in OASIS at:
> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php

Attachment: sha512t-amended.pdf
Description: Adobe PDF document

Attachment: sha512t-amended.doc
Description: MS-Word document