[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [kmip] Groups - KMIP Server Conformance Proposal (KMIP ServerConformance Proposal.pdf) uploaded
Would the following vebiage work for the implemtation conformance statement on page 2 line 40 of your original proposal?
Is there any reason that we need to have the conformance profile as part of the specification itself? This would require servers to claim what profiles they support.
At the same time should there be verbiage about requirements for a profile defining how each element must be implemented including supported enumerations, extensions, etc..?
Robert A. (Bob) Lockhart
Senior Solutions Architect
THALES Information Systems Security
From: email@example.com [firstname.lastname@example.org]
Sent: Wednesday, September 02, 2009 4:36 PM
Subject: [kmip] Groups - KMIP Server Conformance Proposal (KMIP Server Conformance Proposal.pdf) uploaded
PDF version for easy viewing
-- Matthew Ball
The document revision named KMIP Server Conformance Proposal (KMIP Server
Conformance Proposal.pdf) has been submitted by Matthew Ball to the OASIS
Key Management Interoperability Protocol (KMIP) TC document repository.
This document is revision #1 of KMIP Server Conformance Proposal.doc.
This proposal is a subset of previous conformance proposals, aiming to do
the minimum work needed to meet the OASIS requirements for a Conformance
section. In particular, this proposal defines a 'baseline' Conformance
Clause for the KMIP Server Conformance Target.
View Document Details:
This document is revision #1 of KMIP Server Conformance Proposal.doc. The
document details page referenced above will show the complete revision
PLEASE NOTE: If the above links do not work for you, your email application
may be breaking the link into two pieces. You may be able to copy and paste
the entire link address into the address field of your web browser.
-OASIS Open Administration
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 unauthorized. 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 unauthorized 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 Thales.