[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Fw: question on Statements of Use for KMIP V1.1
----- Original Message ----- From: Chet Ensign [mailto:chet.ensign@oasis-open.org] Sent: Monday, June 18, 2012 05:11 PM To: Griffin, Robert Cc: Subhash.Sankuratripati@netapp.com <Subhash.Sankuratripati@netapp.com> Subject: Re: question on Statements of Use for KMIP V1.1 Hi Bob, I interpret the TC Process to mean the second: the SoU need not have used every conformance clause, it just has to identify those that it did. Also, I don't see that limiting their use for your OS vote. Best, /chet On Mon, Jun 18, 2012 at 12:19 PM, <robert.griffin@rsa.com> wrote: > Hi Chet – > > > > As we prepare our request for a vote on promoting KMIP V1.1 to an OASIS > standard, we’ve had a bit of confusion about Statements of Use. I believe we > have 2 different readings of the relevant clause from > http://www.oasis-open.org/policies-guidelines/tc-process > > "Statement of Use", with respect to a Committee Specification, is a written > statement by an OASIS Organizational Member stating that it is successfully > using or implementing that specification in accordance with the conformance > clauses specified in Section 2.18, identifying those clauses that apply, and > stating whether its use included the interoperation of multiple independent > implementations. A Statement of Use must be endorsed by the Organizational > Member's Primary Representative. > > These two interpretations are: > > > > - Only those organizations that have exercised all the profiles > defined for KMIP V1.1 can submit a Statement of Use. The conformance clause > in the KMIP Specification references the profiles as the mechanism for > establishing conformance claims. > > > > or > > - Any organization that has implemented one or more of the profiles > can contribute a Statement of Use, as long as they stipulate which profiles > they have exercised. Such an SoU, however, would not considered as one of > the 3 required for consideration of KMIP V1.1 as an OASIS standard. > > > > It seems to me it’s worthwhile to take the second approach, to show a > greater breadth of support for KMIP. It seems to me that this is in > accordance with the policy above. But if that is not the case, we want to be > sure we conform to the process! > > > > Please give us your guidance on this question? > > > > Thanks! > > > > Bob > > > > 1 KMIP Server and Client Implementation Conformance > > 1.1 KMIP Server Implementation Conformance > > An implementation is a conforming KMIP Server if the implementation meets > the conditions specified in one or more server profiles specified in > [KMIP-Prof]. > > A KMIP server implementation SHALL be a conforming KMIP Server. > > If a KMIP server implementation claims support for a particular server > profile, then the implementation SHALL conform to all normative statements > within the clauses specified for that profile and for any subclauses to each > of those clauses. > > 1.2 KMIP Client Implementation Conformance > > An implementation is a conforming KMIP Client if the implementation meets > the conditions specified in one or more client profiles specified in > [KMIP-Prof]. > > A KMIP client implementation SHALL be a conforming KMIP Client. > > If a KMIP client implementation claims support for a particular client > profile, then the implementation SHALL conform to all normative statements > within the clauses specified for that profile and for any subclauses to each > of those clauses. > > -- /chet ---------------- Chet Ensign Director of Standards Development and TC Administration OASIS: Advancing open standards for the information society http://www.oasis-open.org Primary: +1 973-996-2298 Mobile: +1 201-341-1393 TC Administration information and support is available at http://www.oasis-open.org/resources/tcadmin Follow OASIS on: LinkedIn: http://linkd.in/OASISopen Twitter: http://twitter.com/OASISopen Facebook: http://facebook.com/oasis.open
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]