The Key Management Interoperability Protocol (KMIP) is a single, comprehensive protocol for communication between clients and servers to manage a wide range of encryption keys. By replacing redundant, incompatible key management protocols, KMIP provides better data security while at the same time reducing expenditures on multiple products.
KMIP Specification v1.4 is intended for developers and architects who wish to design systems and applications that interoperate using the Key Management Interoperability Protocol Specification. The TC received 3 Statements of Use from Cryptsoft Pty Ltd, P6R Inc. and Hewlett Packard Enterprise [2].
This is a call to the Organizational Members of OASIS to consent or object to this approval. You are welcome to register your consent explicitly on the ballot; however your consent is assumed unless you register an objection [3]. To register an objection, you must:
1. Indicate your objection on this ballot, and
2. Provide a reason for your objection and/or a proposed remedy to the TC.
You may provide the reason in the comment box or by email to the Technical Committee on its comment mailing list or, if you are a member of the TC, to the TC's mailing list [4]. If you provide your reason by email, please indicate in the subject line that this is in regard to the Call for Consent. Note that failing to provide a reason and/or remedy may result in an objection being deemed invalid.
URIs:
The prose specification document and related files are available here:
Key Management Interoperability Protocol Specification Version 1.4
Candidate OASIS Standard 01
09 August 2017
Editable source (Authoritative):
http://docs.oasis-open.org/kmip/spec/v1.4/cos01/kmip-spec-v1.4-cos01.docx
HTML:
http://docs.oasis-open.org/kmip/spec/v1.4/cos01/kmip-spec-v1.4-cos01.html
PDF:
http://docs.oasis-open.org/kmip/spec/v1.4/cos01/kmip-spec-v1.4-cos01.pdf
Please contact OASIS TC Administration at tc-admin@lists.oasis-open.org with any questions you may have about this ballot.
--- Additional information ---
[1] OASIS Key Management Interoperability Protocol (KMIP) TC
https://www.oasis-open.org/committees/kmip/
[2] Statements of use:
- Cryptsoft Pty Ltd - https://www.oasis-open.org/apps/org/workgroup/kmip/download.php/60994/KMIP-SOU-Cryptsoft-18-Jun-2017.pdf
- P6R Inc. - https://www.oasis-open.org/apps/org/workgroup/kmip/download.php/61007/KMIP-SOU-P6R-18-June-2017-R2.pdf
- Hewlett Packard Enterprise - https://www.oasis-open.org/apps/org/workgroup/kmip/download.php/61016/HPE-SOU-19-June-2017.pdf
[3] https://www.oasis-open.org/policies-guidelines/tc-process-2017-05-26#OScallForConsent
[4] If you are not a member of the KMIP TC, you may submit an objection to the KMIP comment mailing list following the instructions at https://www.oasis-open.org/committees/comments/index.php?wg_abbrev=kmip.
If you are a member of the TC, you may submit an objection to the TC mailing list. |
