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.1 and KMIP Profiles v2.1 as OASIS Standards

OASIS Members:

The KMIP TC members [1] have approved submitting the following Committee Specifications to the OASIS Membership as candidates for OASIS Standard:

Key Management Interoperability Protocol Specification Version 2.1
Committee Specification 02
16 November 2020

Key Management Interoperability Protocol Profiles Version 2.1
Committee Specification 01
07 May 2020

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 [2]. 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 candidates for OASIS Standard are now submitted to the voting representatives of OASIS Organizational Members.


The Call for Consent opens at 01 December 2020 at 00:00 UTC and closes on 14 December 2020 at 23:59 pm UTC. You can access the ballot at:

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

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

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 Standard 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.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 [6].

The specification documents and related files are available here:

Editable source (Authoritative):
ZIP file:

Editable source (Authoritative):
Mandatory test cases:
Optional 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 main mailing list: kmip@lists.oasis-open.org

[4] Candidate for OASIS Standard Special Majority Votes:
Original ballot: https://www.oasis-open.org/committees/ballot.php?id=3516
Vote to approve KMIP Spec Committee Specification 02 as a revised candidate for OASIS Standard: https://www.oasis-open.org/committees/ballot.php?id=3533

[5] Public reviews:
30-day public review, 13 February 2020:
 Comment resolution log:

60-day public review, 27 August 2020:
 Comment resolution log:

[6] 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



Chief Technical Community Steward


+1 201-341-1393

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