As you see, the call for consent forÂKMIP Specification v2.0 and KMIP Profiles v2.0Âhas closed and passed. Congratulations on reaching this milestone.Â
TC Admin will now publish the OASIS Standards. TC Admin JIRA ticketsÂhttps://issues.oasis-open.org/browse/TCADMIN-3581ÂandÂhttps://issues.oasis-open.org/browse/TCADMIN-3582 have been opened to track the work.Â
Please let us know if you have any questions. And again, congratulations.Â
/chetÂ
---------- Forwarded message ---------
From: <tc_admin@oasis-open.org>
Date: Thu, Oct 31, 2019 at 8:11 PM
Subject: Email sent to voters re: [voting] Groups - Ballot closed: "Call for consent of KMIP Specification v2.0 and KMIP Profiles v2.0 as OASIS Standards"
To: <chet.ensign@oasis-open.org>
From: <tc_admin@oasis-open.org>
Date: Thu, Oct 31, 2019 at 8:11 PM
Subject: Email sent to voters re: [voting] Groups - Ballot closed: "Call for consent of KMIP Specification v2.0 and KMIP Profiles v2.0 as OASIS Standards"
To: <chet.ensign@oasis-open.org>
Call for consent of KMIP Specification v2.0 and KMIP Profiles v2.0 as OASIS Standards has closed.
|
Ballot Title: Call for consent of KMIP Specification v2.0 and KMIP Profiles v2.0 as OASIS Standards Question Please make 2 selections below to indicate whether the listed COSs should become OASIS Standards. Voting Results 15 of 216 eligible companies cast their vote before the deadline. - Key Management Interoperability Protocol Specification V2.0 _ Consent received 15 Votes - Key Management Interoperability Protocol Specification V2.0 _ Object received 0 Votes - Key Management Interoperability Protocol Profiles V2.0 _ Consent received 15 Votes - Key Management Interoperability Protocol Profiles V2.0 _ Object received 0 Votes The ballot received 0 comments. Description Members of the OASIS Key Management Interoperability Protocol (KMIP) TC [1] approved advancing KMIP Specification v2.0 and KMIP Profiles v2.0 to the membership as Candidate OASIS Standards (COS). 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 [2]. This is a call to the Organizational Members of OASIS 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. Note that failing to provide a reason and/or remedy may result in an objection being deemed invalid. URIs: 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): https://docs.oasis-open.org/kmip/kmip-spec/v2.0/cos01/kmip-spec-v2.0-cos01.docx HTML: https://docs.oasis-open.org/kmip/kmip-spec/v2.0/cos01/kmip-spec-v2.0-cos01.html PDF: https://docs.oasis-open.org/kmip/kmip-spec/v2.0/cos01/kmip-spec-v2.0-cos01.pdf ZIP file: https://docs.oasis-open.org/kmip/kmip-spec/v2.0/cos01/kmip-spec-v2.0-cos01.zip Key Management Interoperability Protocol Profiles Version 2.0 Candidate OASIS Standard 01 09 August 2019 Editable source (Authoritative): https://docs.oasis-open.org/kmip/kmip-profiles/v2.0/cos01/kmip-profiles-v2.0-cos01.docx HTML: https://docs.oasis-open.org/kmip/kmip-profiles/v2.0/cos01/kmip-profiles-v2.0-cos01.html PDF: https://docs.oasis-open.org/kmip/kmip-profiles/v2.0/cos01/kmip-profiles-v2.0-cos01.pdf 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-v2.0-cos01.zip Please contact OASIS TC Administration at tc-admin@lists.oasis-open.org with any questions you may have about this ballot. --- Additional information --- [1] OASIS Key Management Interoperability Protocol (KMIP) TC https://www.oasis-open.org/committees/kmip/ [2] 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 [3] https://www.oasis-open.org/policies-guidelines/tc-process-2017-05-26#OScallForConsent View Results Group: OASIS organizational voting Date Opened: Friday, 18 October 2019 @ 12:00 am UTC Date Closed: Thursday, 31 October 2019 @ 11:59 pm UTC This email has been sent to 295 members of OASIS Open. Here is a list of members who were notified:
Referenced Items
|
/chetÂ
----------------
Chet Ensign
Chief Technical Community Steward
OASIS: Advancing open source & open standards for the information society
http://www.oasis-open.org
OASIS: Advancing open source & open standards for the information society
http://www.oasis-open.org
Mobile: +1 201-341-1393Â