[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [kmip] Issue with KMIP SoUs/conformance vs. Use Cases
Usecase 3.1.5 gives the instance of Opaque (Key Format Type). Thanks -- Shyam -----Original Message----- From: Wierenga, Steven [mailto:steve.wierenga@hp.com] Sent: Thursday, June 03, 2010 12:24 PM To: Griffin, Robert; kmip@lists.oasis-open.org Subject: [kmip] Issue with KMIP SoUs/conformance vs. Use Cases 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 --------------------------------------------------------------------- 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
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]