Editorial changes, including the following:
2.2.6 & 2.2.7: merge the Template and Policy Template Objects into a single
Template Object. Added Initial Date, Archive Date, and Last Changed Date as
attributes that apply to the Template itself (similarly to Unique
Identifier and Name). Tags in 9.1.3.1 are updated. Object types
enumerations in 9.1.3.2.10 are updated. Appendices B & C are updated.
3.4, 3.5, 3.6: make Crypto Algorithm, Length, and Parameters applicable to
only Keys and Certs (not all Crypto Objects)
3.7, 3.8, 3.9: corrected description of Certificate Type, Issuer, and
Subject attributes as they cannot be set as a result of Create operation.
3.10: make Digest apply to Opaque Objects too (not only Crypto Objects)
3.13: make Lease Time apply to Crypto Objects (not only Keys)
3.18 & 3.19: corrected description of Process Start and Stop Dates
attributes as they cannot be set implicitly by Create Key Pair.
3.22, 3.23, 3.24: make Compromise Occurence Date, Compromise Date, and
Revocation Reason attributes apply to Certificates and Opaque Objects as
well.
3.27: make the Link attribute apply only Crypto Objects.
3.28: make Application-Specific Identification apply to all Objects (not
only Crypto Objects)
3.30: make Last Changed Date attribute always have a value, corrected
description when implicitly set/changed.
4.1: indicate that only symmetric keys are create with Create now.
4.1, 4.2, 4.3: added that only Template that are on-line (not archived) can
be used in these operations.
4.3: remove Object Type from the output parameters of the Register
operation as it is redundant.
4.5: remove Object Type from the output parameters of the Derive Key
operation as it is redundant.
4.19 & 4.20: allow Opaque Objects to be revoked/destroyed as well
4.20: allow Opaque Objects to be destroyed as well (not only Crypto
Objects).
4.19: include Opaque Objects as possible inputs to the Revoke operation
(to be consistent with 3.22, 3.23, 3.24)
6.4: rename Unique Message ID to Unique Batch Item ID
8: Indicate that client and server authentication features must be enabled
"unless otherwise specified in the operation (to be consistent with 4.24)
11.2, 11.3, 11.4, 11.14 (Create, Create Key Pair, Register, Add Attribute):
Add a new Result Reason of "Index Out of Bounds" if the client tries to set
more attribute instances than the server allows.
11.2, 11.3, 11.4: add an error in case a request Template is archived.
11.12 (Get Attributes): Add the Result Reason "Item Not Found" if the
requested attribute index does not exist
Appendix A: make the table consistent with the normative part of the spec.
Remove the "Note that" in the sentence "Note that this table is not
normative" (also in Appendices B & C).
-- Dr. Robert Haas
The document revision named kmip-1.0-spec-ed-0.98.doc has been submitted by
Dr. Robert Haas to the OASIS Key Management Interoperability Protocol
(KMIP) TC document repository. This document is revision #5 of
kmip-1.0-spec-ed-0.98.doc.
Document Description:
KMIP specification
View Document Details:
http://www.oasis-open.org/committees/document.php?document_id=33106
Download Document:
http://www.oasis-open.org/committees/download.php/33106/kmip-1.0-spec-ed-0.98.doc
Revision:
This document is revision #5 of kmip-1.0-spec-ed-0.98.doc. The document
details page referenced above will show the complete revision history.
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