Issue with KMIP SoUs/conformance vs. Use Cases

["Wierenga, Steven" <steve.wierenga@hp.com>]

Hello Bob and all,

While doing due diligence preparing the HP Statement of Use, I noticed some discrepancies between the Profiles document and the Use Cases which make it problematic to claim or corroborate conformance and interop based on the Use Cases:

1. The Secret Data Profile requires - Enumerated Objects - Key Format Type - Opaque.  However there is no instance of Opaque in the Use Cases document.

2. The Basic Symmetric Key Store and Server Profile requires - Enumerated Objects - Key Format Type - Transparent Symmetric Key.  However there is no instance of Transparent Symmetric Key in the Use Cases document. 

3.  Likewise, the Basic Symmetric Key Foundry and Server Profile requires - Enumerated Objects - Key Format Type - Transparent Symmetric Key.  Again, there is no instance of Transparent Symmetric Key in the Use Cases document. 

This is not just an editorial issue, if conformance/interop have not been fully verified or are not verifiable under the current Use Cases.  Either the Profiles or the Use Cases need to be amended to match.

Thanks,
--Steve Wierenga
HP