The OASIS KMIP TC works to define a single, comprehensive protocol for communication between encryption systems and a broad range of new and legacy enterprise applications, including email, databases, and storage devices.
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. Six Statements of Use for the Committee Specifications were received from Cryptsoft, IBM, P6R, Fortenix, HP and Thales.
Key Management Interoperability Protocol Profiles Version 1.2 define a set of normative constraints for employing KMIP within a particular environment or context of use. They may, optionally, require the use of specific KMIP functionality or in other respects define the processing rules to be followed by profile actors.
URIs
The prose specification document and related files are available here:
Editable source (Authoritative):
http://docs.oasis-open.org/kmip/profiles/v1.2/cos01/kmip-profiles-v1.2-cos01.doc
HTML:
http://docs.oasis-open.org/kmip/profiles/v1.2/cos01/kmip-profiles-v1.2-cos01.html
PDF:
http://docs.oasis-open.org/kmip/profiles/v1.2/cos01/kmip-profiles-v1.2-cos01.pdf
--- Additional information ---
[1] OASIS Key Management Interoperability Protocol (KMIP) TC
https://www.oasis-open.org/committees/kmip/ |
