[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Fwd: Email sent to voters re: [voting] Groups - Ballot closed: "Call for consent of PKCS 11 Specification V3.1 and PKCS #11 Profiles V3.1 from the PKCS 11 TC as OASIS Standards"
Ballot Title: Call for consent of PKCS 11 Specification V3.1 and PKCS #11 Profiles V3.1 from the PKCS 11 TC as OASIS Standards Question PKCS 11 Specification V3.1 and PKCS #11 Profiles V3.1 have been presented by the PKCS 11 TC [1] as Candidates for OASIS Standard. Do you consent or object to their approval as OASIS Standards? Voting Results 14 of 182 eligible companies cast their vote before the deadline. - PKCS #11 Specification V3.1 - approve received 14 Votes - PKCS #11 Specification V3.1 - object received 0 Votes - PKCS #11 Profiles V3.1 - approve received 14 Votes - PKCS #11 Profiles V3.1 - object received 0 Votes The ballot received 0 comments. Description The documents describe the public-key cryptography standards maintained and enhanced by the OASIS PKCS 11 Technical Committee. The Specification defines 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 "crypto-key". The specification defines data types, functions and other basic components of the interface and also defines mechanisms that are anticipated for use with the current version of PKCS #11. Profiles define the use of PKCS#11 data types, objects, functions and mechanisms within specific contexts of provider and consumer interaction. These profiles define a set of normative constraints for employing PKCS#11 within a particular environment or context of use. The TC received 3 Statements of Use from from Utimaco, Information Security Corp (ISC), and Cryptsoft [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 OP. You may provide the reason in the comment box or by email to the TC's comment 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. URIs: The prose specification document and related files are available here: - PKCS #11 Specification Version 3.1 Committee Specification 01 11 August 2022 Editable source (Authoritative): https://docs.oasis-open.org/pkcs11/pkcs11-spec/v3.1/cs01/pkcs11-spec-v3.1-cs01.docx HTML: https://docs.oasis-open.org/pkcs11/pkcs11-spec/v3.1/cs01/pkcs11-spec-v3.1-cs01.html PDF: https://docs.oasis-open.org/pkcs11/pkcs11-spec/v3.1/cs01/pkcs11-spec-v3.1-cs01.pdf Header files: - pkcs11.h: https://docs.oasis-open.org/pkcs11/pkcs11-spec/v3.1/cs01/include/pkcs11-v3.1/pkcs11.h - pkcs11f.h: https://docs.oasis-open.org/pkcs11/pkcs11-spec/v3.1/cs01/include/pkcs11-v3.1/pkcs11f.h - pkcs11t.h: https://docs.oasis-open.org/pkcs11/pkcs11-spec/v3.1/cs01/include/pkcs11-v3.1/pkcs11t.h ZIP distribution file: https://docs.oasis-open.org/pkcs11/pkcs11-spec/v3.1/cs01/pkcs11-spec-v3.1-cs01.zip - PKCS #11 Profiles Version 3.1 Committee Specification 01 14 July 2022 Editorial source (Authoritative): https://docs.oasis-open.org/pkcs11/pkcs11-profiles/v3.1/cs01/pkcs11-profiles-v3.1-cs01.docx HTML: https://docs.oasis-open.org/pkcs11/pkcs11-profiles/v3.1/cs01/pkcs11-profiles-v3.1-cs01.html PDF: https://docs.oasis-open.org/pkcs11/pkcs11-profiles/v3.1/cs01/pkcs11-profiles-v3.1-cs01.pdf Test cases: https://docs.oasis-open.org/pkcs11/pkcs11-profiles/v3.1/cs01/test-cases/ ZIP distribution file: https://docs.oasis-open.org/pkcs11/pkcs11-profiles/v3.1/cs01/pkcs11-profiles-v3.1-cs01.zip --- Additional information --- [1] OASIS PKCS 11 TC https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=pkcs11 [2] Statements of Use: - Utimaco: https://www.oasis-open.org/apps/org/workgroup/pkcs11/download.php/70709/PKCS11v3.1-SOU-Utimaco-Jan2023.pdf - Information Security Corp (ISC): https://www.oasis-open.org/apps/org/workgroup/pkcs11/download.php/70708/ISC%20PKCS%2011%20v3.1%20Statement%20of%20Use%20v103.pdf - Cryptsoft: https://www.oasis-open.org/apps/org/workgroup/pkcs11/download.php/70712/PKCS11v3.1-SOU-Cryptsoft-31-Jan-2023.pdf [3] https://www.oasis-open.org/policies-guidelines/tc-process-2017-05-26#OScallForConsent Comments may be submitted to the TC by any person through the use of the OASIS TC Comment Facility as explained in the instructions located via the button labeled "Send A Comment" at the top of the TC public home page, or directly at: https://www.oasis-open.org/committees/comments/index.php?wg_abbrev=pkcs11 Comments submitted for this work and for other work of this TC/OP are publicly archived and can be viewed at: https://lists.oasis-open.org/archives/pkcs11-comment View Results Group: OASIS organizational voting Date Opened: Monday, 10 July 2023 @ 12:00 am UTC Date Closed: Sunday, 23 July 2023 @ 11:59 pm UTC This email has been sent to 243 members of OASIS Open. Here is a list of members who were notified:
Referenced Items
|
ChetÂEnsignChief Technical Community Steward OASIS Open | Â | Â | Â |
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]