[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: question regarding conformance statement for KMIP
I agree there should be additions to the conformance section. I have included several proposed changes (as requested a few meetings ago) as a place to start. They include conformance claims, a table of required vs. optional items for both client and server (to be filled in), reference guidelines when claiming conformance by another standard and usage guidelines when using KMIP without claiming conformance.
Not sure if this is what you were looking for from me Bob & Tony when you asked but this is what I have so far. Looking for feedback.
From: email@example.com [firstname.lastname@example.org]
Sent: Wednesday, May 13, 2009 5:35 PM
Subject: [kmip] question regarding conformance statement for KMIP
Rather than convening a meeting on conformance (as I'd suggested a
couple of meetings ago), I'd like to pose the question I've been
wondering about and see if there is an issue or not:
- Should we modify the language in Section 5 of the Usage Guide to
clarify what "support all objects etc" means? In particular, do we need
to clarify whether this means a) the server has to implement all
mandatory objects etc or b) the server has to understand requests
related to all mandatory objects etc (but can return back an "object not
In drafting the conformance language currently included in the Usage
Guide, I followed the advice expressed in the Conformance Testing
document available at http://xml.coverpages.org/conform20000112.html:
that is, "the requirements or criteria for conformance must be specified
in the standard or specification. This is usually in a conformance
clause or conformance statement..."
The conformance statement in section 5 of the KMIP Usage Guide
distinguishes between conformance requirements for KMIP servers and
"Server implementations of the KMIP protocol must support all objects,
attributes, operations and profiles not specified as "optional" in the
KMIP Specification in order to be conformant to the specification.
Server implementations that do not support objects, attributes,
operations and profiles defined as "optional" can claim KMIP
conformance, though they may be limited in terms of interoperability
with other KMIP implementations.
Client implementations of the KMIP protocol may implement any subset of
the KMIP protocol. For example, a client may implement only the Get and
Locate operations for symmetric keys. In order to claim conformance,
however, such a client must implement all aspects of any elements of the
protocol (objects, attributes, operations, profiles) that it claims to
support. In the example of Get/Locate support for symmetric keys,
therefore, a conforming client implementation must support all required
attributes for symmetric keys."
In re-reading the conformance statement for server implementations, it
looks to me that I made it more restrictive than I intended - that the
language should perhaps have been something like:
"Server implementations of the KMIP protocol shall accept and respond to
client requests for all objects, operations and profiles not specified
as 'optional' in the KMIP Specification in order to be conformant to the
specification; a conformant response can be 'this object etc is not
But perhaps it's better to have the more restrictive language, after
I'd appreciate your thoughts!
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:
The information contained in this e-mail is confidential. It may also be privileged. It is only intended for the stated addressee(s) and access to it by any other person is unauthorised. If you are not an addressee or the intended addressee, you must not disclose, copy, circulate or in any other way use or rely on the information contained in this e-mail. Such unauthorised use may be unlawful. If you have received this e-mail in error please delete it (and all copies) from your system, please also inform us immediately on +1 (781) 994 4000 or email email@example.com. Commercial matters detailed or referred to in this e-mail are subject to a written contract signed for and on behalf of nCipher Inc.
Proposal for modification to Conformance Setion(Conformance_Clause_Proposal.doc)- Includes several proposals onmodifications and movement of the conformance section and a"simple" to use table of requirements for claiming confor....url