OASIS members and other interested parties,
OASIS and the OASIS Key Management Interoperability Protocol (KMIP) TC [1] are pleased to announce that KMIP Specification v2.1 Committee Specification 01 and KMIP Profiles v2.1 Committee Specification 01 are now available for public review and comment.
The TC members approved submitting these Committee Specifications to the OASIS membership for consideration as Candidate OASIS Standards, as described in the OASIS TC Process [6]. This is a 60-day public review, after which they may be submitted to a membership-wide call for consent to promote the specifications to OASIS Standards.
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.
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 has received 3 Statements of Use. They are from Cryptsoft, Primekey, and Utimaco [3].
The candidate specifications and related files are available here:
Key Management Interoperability Protocol Specification Version 2.1
Committee Specification 01
07 May 2020
Editable source (Authoritative):
https://docs.oasis-open.org/kmip/kmip-spec/v2.1/cs01/kmip-spec-v2.1-cs01.docxHTML:
https://docs.oasis-open.org/kmip/kmip-spec/v2.1/cs01/kmip-spec-v2.1-cs01.htmlPDF:
https://docs.oasis-open.org/kmip/kmip-spec/v2.1/cs01/kmip-spec-v2.1-cs01.pdfFor your convenience, OASIS provides a complete package of the prose document and related files in a ZIP distribution file. You can download the ZIP file here:
https://docs.oasis-open.org/kmip/kmip-spec/v2.1/cs01/kmip-spec-v2.1-cs01.zipKey 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.docxHTML:
https://docs.oasis-open.org/kmip/kmip-profiles/v2.1/cs01/kmip-profiles-v2.1-cs01.htmlPDF:
https://docs.oasis-open.org/kmip/kmip-profiles/v2.1/cs01/kmip-profiles-v2.1-cs01.pdfTest cases:
https://docs.oasis-open.org/kmip/kmip-profiles/v2.1/cs01/test-cases/ZIP file:
https://docs.oasis-open.org/kmip/kmip-profiles/v2.1/cs01/kmip-profiles-v2.1-cs01.zipPublic Review Period:
The 60-day public review starts immediately and ends 26 October 2020 at 23:59 UTC.
This is an open invitation to comment. OASIS solicits feedback from potential users, developers and others, whether OASIS members or not, for the sake of improving the interoperability and quality of its technical work.
Comments may be submitted to the TC by any person through the use of the OASIS TC Comment Facility as explained in the instructions located via the button labeled "Send A Comment" at the top of the TC public home page, or directly at:
https://www.oasis-open.org/committees/comments/index.php?wg_abbrev=kmipComments submitted by TC non-members for this work and for other work of this TC are publicly archived and can be viewed at:
http://lists.oasis-open.org/archives/kmip-comment/All comments submitted to OASIS are subject to the OASIS Feedback License, which ensures that the feedback you provide carries the same obligations at least as the obligations of the TC members. In connection with this public review of KMIP Specification v2.1 and KMIP Profiles v2.1, we call your attention to the OASIS IPR Policy [4] applicable especially [5] to the work of this technical committee. All members of the TC should be familiar with this document, which may create obligations regarding the disclosure and availability of a member's patent, copyright, trademark and license rights that read on an approved OASIS specification.
OASIS invites any persons who know of any such claims to disclose these if they may be essential to the implementation of the above specifications, so that notice of them may be posted to the notice page for this TC's work.
Additional information related to this public review can be found at:
-
https://docs.oasis-open.org/kmip/kmip-spec/v2.1/cs01/kmip-spec-v2.1-cs01-public-review-metadata.html-
https://docs.oasis-open.org/kmip/kmip-profiles/v2.1/cs01/kmip-profiles-v2.1-cs01-public-review-metadata.html==============
[1] OASIS Key Management Interoperability Protocol (KMIP) TC
https://www.oasis-open.org/committees/kmip/[2] Approval ballot:
https://www.oasis-open.org/committees/ballot.php?id=3516[3] Statements of Use:
- Cryptsoft:
https://lists.oasis-open.org/archives/kmip/202008/msg00004.html- PrimeKey:
https://lists.oasis-open.org/archives/kmip/202007/msg00000.html- Utimaco:
https://lists.oasis-open.org/archives/kmip/202008/msg00005.html[4]
https://www.oasis-open.org/policies-guidelines/ipr[5]
http://www.oasis-open.org/committees/kmip/ipr.phphttps://www.oasis-open.org/policies-guidelines/ipr#RF-on-RAND-ModeRF on RAND Terms Mode
[6] TC Process for OASIS Standard
https://www.oasis-open.org/policies-guidelines/tc-process-2017-05-26#OASISstandard