As you can see, the call for consent to approve 4 Candidate OASIS Standards has closed and passed. Each of the 4 COSs received 16 affirmative votes and no objections.Â
TC Admin will now publish and announce the OASIS Standards. TC Admin JIRA ticketsÂhttps://issues.oasis-open.org/browse/TCADMIN-3757ÂthroughÂhttps://issues.oasis-open.org/browse/TCADMIN-3760Âhave been opened to track the work.Â
We will let you know when the OSs are published. Meanwhile, our congratulations to you on achieving this milestone.Â
Best,Â
/chetÂ
---------- Forwarded message ---------
From: <tc_admin@oasis-open.org>
Date: Mon, Jun 15, 2020 at 8:11 PM
Subject: Email sent to voters re: [voting] Groups - Ballot closed: "Call for consent for 4 PKCS #11 specifications as OASIS Standards"
To: <chet.ensign@oasis-open.org>
From: <tc_admin@oasis-open.org>
Date: Mon, Jun 15, 2020 at 8:11 PM
Subject: Email sent to voters re: [voting] Groups - Ballot closed: "Call for consent for 4 PKCS #11 specifications as OASIS Standards"
To: <chet.ensign@oasis-open.org>
Call for consent for 4 PKCS #11 specifications as OASIS Standards has closed.
|
Ballot Title: Call for consent for 4 PKCS #11 specifications as OASIS Standards Question Please make four selections below to indicate whether the named PKCS #11 Candidate OASIS Standards should become OASIS Standards. Voting Results 16 of 197 eligible companies cast their vote before the deadline. - PKCS #11 Cryptographic Token Interface Base Specification Version 3.0 - consent received 16 Votes - PKCS #11 Cryptographic Token Interface Base Specification Version 3.0 - object received 0 Votes - PKCS #11 Cryptographic Token Interface Profiles Version 3.0 - consent received 16 Votes - PKCS #11 Cryptographic Token Interface Profiles Version 3.0 - object received 0 Votes - PKCS #11 Cryptographic Token Interface Current Mechanisms Specification Version 3.0 - consent received 16 Votes - PKCS #11 Cryptographic Token Interface Current Mechanisms Specification Version 3.0 - object received 0 Votes - PKCS #11 Cryptographic Token Interface Historical Mechanisms Specification Version 3.0 - consent received 16 Votes - PKCS #11 Cryptographic Token Interface Historical Mechanisms Specification Version 3.0 - object received 0 Votes The ballot received 1 comment. Description These PKCS #11 specifications define a platform-independent API to cryptographic tokens, such as hardware security modules and smart cards. The API itself is named "Cryptoki" (from "cryptographic token interface" and pronounced as "crypto-key"). - "Base Specification" defines data types, functions and other basic components of the PKCS #11 Cryptoki interface. - "Profiles" is intended for developers and architects who wish to design systems and applications that conform to the PKCS #11 Cryptographic Token Interface standard. - "Current Mechanisms" defines mechanisms that are anticipated for use with the current version of PKCS #11. - "Historical Mechanisms" defines mechanisms for PKCS #11 that are no longer in general use. Three Statements of Use were received from Cryptsoft, Information Security Corporation, and Utimaco [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: ********************* PKCS #11 Cryptographic Token Interface Base Specification Version 3.0 Candidate OASIS Standard 01 27 March 2020 Editable source (Authoritative): https://docs.oasis-open.org/pkcs11/pkcs11-base/v3.0/cos01/pkcs11-base-v3.0-cos01.docx HTML: https://docs.oasis-open.org/pkcs11/pkcs11-base/v3.0/cos01/pkcs11-base-v3.0-cos01.html PDF: https://docs.oasis-open.org/pkcs11/pkcs11-base/v3.0/cos01/pkcs11-base-v3.0-cos01.pdf PKCS #11 header files: https://docs.oasis-open.org/pkcs11/pkcs11-base/v3.0/cos01/include/ ********************* PKCS #11 Cryptographic Token Interface Profiles Version 3.0 Candidate OASIS Standard 01 27 March 2020 Editable source (Authoritative): https://docs.oasis-open.org/pkcs11/pkcs11-profiles/v3.0/cos01/pkcs11-profiles-v3.0-cos01.docx HTML: https://docs.oasis-open.org/pkcs11/pkcs11-profiles/v3.0/cos01/pkcs11-profiles-v3.0-cos01.html PDF: https://docs.oasis-open.org/pkcs11/pkcs11-profiles/v3.0/cos01/pkcs11-profiles-v3.0-cos01.pdf PKCS #11 header files: https://docs.oasis-open.org/pkcs11/pkcs11-profiles/v3.0/cos01/include/ ********************* PKCS #11 Cryptographic Token Interface Current Mechanisms Specification Version 3.0 Candidate OASIS Standard 01 27 March 2020 Editable source (Authoritative): https://docs.oasis-open.org/pkcs11/pkcs11-curr/v3.0/cos01/pkcs11-curr-v3.0-cos01.docx HTML: https://docs.oasis-open.org/pkcs11/pkcs11-curr/v3.0/cos01/pkcs11-curr-v3.0-cos01.html PDF: https://docs.oasis-open.org/pkcs11/pkcs11-curr/v3.0/cos01/pkcs11-curr-v3.0-cos01.pdf PKCS #11 header files: https://docs.oasis-open.org/pkcs11/pkcs11-curr/v3.0/cos01/include/ ********************* PKCS #11 Cryptographic Token Interface Historical Mechanisms Specification Version 3.0 Candidate OASIS Standard 01 27 March 2020 Editable source (Authoritative): https://docs.oasis-open.org/pkcs11/pkcs11-hist/v3.0/cos01/pkcs11-hist-v3.0-cos01.docx HTML: https://docs.oasis-open.org/pkcs11/pkcs11-hist/v3.0/cos01/pkcs11-hist-v3.0-cos01.html PDF: https://docs.oasis-open.org/pkcs11/pkcs11-hist/v3.0/cos01/pkcs11-hist-v3.0-cos01.pdf PKCS #11 header files: https://docs.oasis-open.org/pkcs11/pkcs11-hist/v3.0/cos01/include/ Additional information about the specification and the PKCS 11 TC may be found at the TC's public home page [1]. 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 PKCS 11 TC https://www.oasis-open.org/committees/pkcs11/ [2] Statements of use - Cryptsoft: https://www.oasis-open.org/committees/download.php/66459 - Information Security Corporation https://www.oasis-open.org/committees/download.php/66711 - Utimaco https://www.oasis-open.org/committees/download.php/66584 [3] https://www.oasis-open.org/policies-guidelines/tc-process-2017-05-26#OScallForConsent View Results Group: OASIS organizational voting Date Opened: Tuesday, 2 June 2020 @ 12:00 am UTC Date Closed: Monday, 15 June 2020 @ 11:59 pm UTC This email has been sent to 279 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Â