OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

members message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Call for Consent for KMIP Specification v2.0 and KMIP Profiles v2.0 as OASIS Standards

OASIS Members:

The OASIS Key Management Interoperability Protocol (KMIP) TC members [1] have approved submitting the following Candidate OASIS Standards to the OASIS Membership in a call for consent for OASIS Standard:

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

This Call for Consent is taking place under the TC Process rules [2]. This is a call to the primary or alternate representatives of OASIS Organizational Members 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.

This Committee Specification was approved by the Technical Committee and was submitted for the required 60-day public review [4]. All requirements of the OASIS TC Process having been met [5][6], the Candidate OASIS Standard is now submitted to the voting representatives of OASIS Organizational Members.

-- Details --

The Call for Consent opens at 18 October 2019 00:00 UTC and closes on 31 October 2019 23:59 pm timezone. You can access the ballot at:

Internal link for voting members: https://www.oasis-open.org/apps/org/workgroup/voting/ballot.php?id=3437

Publicly visible link: Âhttps://www.oasis-open.org/committees/ballot.php?id=3437

OASIS members should ensure that their organization's voting representative responds according to the organization's wishes. If you do not know the name of your organization's voting representative is, go to the My Account page at


then click the link for your Company (at the top of the page) and review the list of users for the name designated as "Primary".

-- Information about the Candidate OASIS Standards and the KMIP TC --

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.

The TC received three Statements of Use from Cryptsoft, P6R, and Semper Fortis [6].
The prose specification document and related files are available here:

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

Editable source (Authoritative):



ZIP file:

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

Editable source (Authoritative):



Test cases:

ZIP file:

-- Additional information --

[1] OASIS Key Management Interoperability Protocol (KMIP) TC

TC IPR page

[2] https://www.oasis-open.org/policies-guidelines/tc-process-2017-05-26#OScallForConsent

[3] KMIP TC comment mailing list: kmip-comment@lists.oasis-open.org Â
(You must be subscribed to send to this list. To subscribe, see https://www.oasis-open.org/committees/comments/index.php?wg_abbrev=kmip.)

KMIP TC main mailing list: kmip@lists.oasis-open.org

[4] Candidate OASIS Standard Special Majority Vote:

[5] Public reviews:
- 60-day public review, 17 August 2019:
 Comment resolution logs:
 - http://docs.oasis-open.org/kmip/kmip-spec/v2.0/csprd01/kmip-spec-v2.0-csprd01-comment-resolution-log.txt
 - http://docs.oasis-open.org/kmip/kmip-profiles/v2.0/csprd01/kmip-profiles-v2.0-csprd01-comment-resolution-log.txt

- 30-day public review, 26 April 2019:
 Comment resolution logs:
 - http://docs.oasis-open.org/kmip/kmip-spec/v2.0/csprd01/kmip-spec-v2.0-csprd01-comment-resolution-log.txt
 - http://docs.oasis-open.org/kmip/kmip-profiles/v2.0/csprd01/kmip-profiles-v2.0-csprd01-comment-resolution-log.txt

[6] Statements of Use:

Cryptsoft: https://www.oasis-open.org/committees/download.php/65609/KMIP-SOU-Cryptsoft-10-Jul-2019.pdf

P6R: https://www.oasis-open.org/committees/download.php/65613/KMIP-SOU-P6R-12-July-2019.pdf

Semper Fortis: https://www.oasis-open.org/committees/download.php/65652/KMIP%20SOU-SFS-17-July-2019.pdf


Chet Ensign
Chief Technical Community Steward
OASIS: Advancing open source & open standards for the information society

Mobile: +1 201-341-1393Â

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]