Members of the OASIS Key Management Interoperability Protocol (KMIP) TC [1] approved advancing KMIP Specification v2.1 CS02 and KMIP Profiles v2.1 CS01 to the membership as candidates for OASIS Standard.
The Key Management Interoperability Protocol (KMIP) is a single, comprehensive protocol for communication between clients that request any of a wide range of encryption keys and servers that store and manage those keys. By replacing redundant, incompatible key management protocols, KMIP provides better data security while at the same time reducing expenditures on multiple products.
The KMIP Specification v2.1 is intended for developers and architects who wish to design systems and applications that interoperate using the Key Management Interoperability Protocol Specification. Note that Committee Specification 02 was produced to correct non-material changes discovered during the 60-day public review. This was done in accordance with the procedures outlined in section 2.8.2 of the TC Process (https://www.oasis-open.org/policies-guidelines/tc-process-2017-05-26/#OSpublicRev).
KMIP Profiles v2.1 specifies conformance clauses that define the use of objects, attributes, operations, message elements and authentication methods within specific contexts of KMIP server and client interaction.
The TC received 3 Statements of Use from Cryptsoft, Utimaco, and PrimeKey [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 [3]. 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 2.1
Committee Specification 02
16 November 2020
Editable source (Authoritative):
https://docs.oasis-open.org/kmip/kmip-spec/v2.1/cs02/kmip-spec-v2.1-cs02.docx
HTML:
https://docs.oasis-open.org/kmip/kmip-spec/v2.1/cs02/kmip-spec-v2.1-cs02.html
PDF:
https://docs.oasis-open.org/kmip/kmip-spec/v2.1/cs02/kmip-spec-v2.1-cs02.pdf
ZIP file:
https://docs.oasis-open.org/kmip/kmip-spec/v2.1/cs02/kmip-spec-v2.1-cs02.zip
* Key Management Interoperability Protocol Profiles Version 2.1
Committee Specification 01
07 May 2020
Editable source (Authoritative):
https://docs.oasis-open.org/kmip/kmip-profiles/v2.1/cs01/kmip-profiles-v2.1-cs01.docx
HTML:
https://docs.oasis-open.org/kmip/kmip-profiles/v2.1/cs01/kmip-profiles-v2.1-cs01.html
PDF:
https://docs.oasis-open.org/kmip/kmip-profiles/v2.1/cs01/kmip-profiles-v2.1-cs01.pdf
Mandatory test cases:
https://docs.oasis-open.org/kmip/kmip-profiles/v2.1/cs01/test-cases/kmip-v2.1/mandatory/
Optional test cases:
https://docs.oasis-open.org/kmip/kmip-profiles/v2.1/cs01/test-cases/kmip-v2.1/optional/
ZIP file:
http://docs.oasis-open.org/kmip/kmip-profiles/v2.1/cs01/kmip-profiles-v2.1-cs01.zip
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 - https://www.oasis-open.org/apps/org/workgroup/kmip/download.php/67196/KMIP-2.1-SOU-Cryptsoft-18May2020.pdf
- Utimaco - https://www.oasis-open.org/apps/org/workgroup/kmip/download.php/67265/OASIS%20Key%20Management%20Interoperability%20Protocol%20J
- PrimeKey - https://www.oasis-open.org/apps/org/workgroup/kmip/download.php/67373/Statement-of-use-KMIP-2.1-PrimeKey-22Jun2020.pdf
[3] https://www.oasis-open.org/policies-guidelines/tc-process-2017-05-26#OScallForConsent |
