60-day Public Review for #KMIP Specification v2.0 and KMIP Profiles v2.0 COS01 - ends 15 October

Members of the OASIS Key Management Interoperability Protocol (KMIP) TC [1] have recently approved a Special Majority Ballot [2] to advance KMIP Specification v2.0 and KMIP Profiles v2.0 as Candidate OASIS Standards (COS). These COS now enter a 60-day public review period in preparation for a member ballot to consider their approval as OASIS Standards.

Key Management Interoperability Protocol Specification Version 2.0
Candidate OASIS Standard 01
09 August 2019

Key Management Interoperability Protocol Profiles Version 2.0
Candidate OASIS Standard 01
09 August 2019

What is KMIP and why is it important?

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

Three Statements of Use were received from Cryptsoft, P6R, and Semper Fortis [3].

Public Review Period:

The 60-day public review starts 17 August 2019 at 00:00 UTC and ends 15 October 2019 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.

The prose specification document and related files are available here:

Key Management Interoperability Protocol Specification Version 2.0
Editable source (Authoritative):
https://docs.oasis-open.org/kmip/kmip-spec/v2.0/cos01/kmip-spec-v2.0-cos...
HTML:
https://docs.oasis-open.org/kmip/kmip-spec/v2.0/cos01/kmip-spec-v2.0-cos...
PDF:
https://docs.oasis-open.org/kmip/kmip-spec/v2.0/cos01/kmip-spec-v2.0-cos...
For 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.0/cos01/kmip-spec-v2.0-cos...

Key Management Interoperability Protocol Profiles Version 2.0
Editable source (Authoritative):
https://docs.oasis-open.org/kmip/kmip-profiles/v2.0/cos01/kmip-profiles-...
HTML:
https://docs.oasis-open.org/kmip/kmip-profiles/v2.0/cos01/kmip-profiles-...
PDF:
https://docs.oasis-open.org/kmip/kmip-profiles/v2.0/cos01/kmip-profiles-...
Test cases:
https://docs.oasis-open.org/kmip/kmip-profiles/v2.0/cos01/test-cases/
ZIP file:
https://docs.oasis-open.org/kmip/kmip-profiles/v2.0/cos01/kmip-profiles-...

Additional information about the specifications and the KMIP TC may be found at the TC's public home page:
https://www.oasis-open.org/committees/kmip/

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=kmip

Comments submitted by TC non-members for this work and for other work of this TC are publicly archived and can be viewed at:
https://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.0 and KMIP Profiles v2.0, 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 specification, so that notice of them may be posted to the notice page for this TC's work.

==============

[1] OASIS Key Management Interoperability Protocol (KMIP) TC
https://www.oasis-open.org/committees/kmip/

[2] https://www.oasis-open.org/committees/ballot.php?id=3421

[3] Statements of Use:
Cryptsoft: https://www.oasis-open.org/committees/download.php/65609/KMIP-SOU-Crypts...
P6R: https://www.oasis-open.org/committees/download.php/65613/KMIP-SOU-P6R-12...
Semper Fortis: https://www.oasis-open.org/committees/download.php/65652/KMIP%20SOU-SFS-...

[4] https://www.oasis-open.org/policies-guidelines/ipr

[5] https://www.oasis-open.org/committees/kmip/ipr.php
https://www.oasis-open.org/policies-guidelines/ipr#RF-on-RAND-Mode
RF on RAND Terms Mode

Associated TC: 
Key Management Interoperability Protocol (KMIP)
Associated MS: 
IDtrust