OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

kmip message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: KMIP specification: proposed changes, mostly editorial (action item #17)



Hi All,
As promised, here is the list of changes that I propose to make to the specification. They are mostly editorial or resolve inconsistencies. I plan to review these proposed changes on the call today.
Regards,
-Robert


Section number: short description of the change.

2.2.6 & 2.2.7: merge the Template and Policy Template Objects into a single Template Object.

3.4 & 3.5: make Crypto Algorithm and Length applicable to only Keys and Certs (not all Crypto Objects)

3.13: make Lease Time apply to Crypto Objects (not only Keys)

3.28: make Application-Specific Identification apply to all Objects (not only Crypto Objects)

4.1: remove Object Type from the input and output parameters to Create operation as only Symmetric Keys can be created with this operation.

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

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]