Re: [kmip] Issue with KMIP SoUs/conformance vs. Use Cases

[Mary McRae <mary.mcrae@oasis-open.org>]

Disclaimer: This is just a question, and not any sort of TC Administration judgement, but:

Are the Use Cases and Usage Guide really intended to become a standard? Do they contain normative material that isn't in either the base spec or the profiles document? Isn't the Use Cases document a set of possibles, but not onlys (I think I just made up a word)? Both the Use Cases document and the Usage guide state that there are no conformance clauses associated with either. I would suggest that the UC and UG hold at the level of CS; it does not diminish their importance, and they can still be referenced by the main spec and profiles doc.

Regards,

Mary



On Jun 3, 2010, at 2:53 AM, Wierenga, Steven wrote:

> 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
>