Fwd: [TC Admin] [OASIS Issue Tracker] (TCADMIN-3692) Request a Special Majority Vote to proceed to Candidate OASIS Standard

[Chet Ensign <chet.ensign@oasis-open.org>]

Members of the PKCS 11 TC,Â

Your requests to open Special Majority Votes to approve 4 PKCS 11 Committee Specs as Candidate OASIS Standards have been received. TC Admin JIRA ticketsÂhttps://issues.oasis-open.org/browse/TCADMIN-3689ÂthroughÂhttps://issues.oasis-open.org/browse/TCADMIN-3691Âhave been opened to track this work. I expect to open them by end of day tomorrow.Â

Please feel free to contact me with any questions.Â

Best regards,Â

/chetÂ

---------- Forwarded message ---------
From: OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>
Date: Thu, Mar 19, 2020 at 12:28 AM
Subject: [TC Admin] [OASIS Issue Tracker] (TCADMIN-3692) Request a Special Majority Vote to proceed to Candidate OASIS Standard
To: <tc-admin@oasis-open.org>

Chet Ensign created TCADMIN-3692:
------------------------------------

      ÂSummary: Request a Special Majority Vote to proceed to Candidate OASIS Standard
        ÂKey: TCADMIN-3692
        ÂURL: https://issues.oasis-open.org/browse/TCADMIN-3692
      ÂProject: Technical Committee Administration
     Issue Type: Task
      Reporter: Chet Ensign
      Assignee: Chet Ensign


Submitted on Thursday, March 19, 2020 - 04:26
Submitted by user:
Submitted values are:

Your name: Tony Cox
TC name: PKCS#11 TC
TC email address: pkcs11@lists.oasis-open.org
Title: PKCS #11 Cryptographic Token Interface Base Specification Version 3.0
Committee Specification 01
Committee Specification URI:
http://docs.oasis-open.org/pkcs11/pkcs11-base/v3.0/cs01/
Committee Specification editable source URI(s):
http://docs.oasis-open.org/pkcs11/pkcs11-base/v3.0/cs01/pkcs11-base-v3.0-cs01.docx
Certification by the TC that all schema and XML instances are well-formed and
that expressions are valid: We so certify
Clear English-language summary of the specification: This document is
intended
for developers and architects who wish to design systems and applications
that
conform to the PKCS #11 Cryptographic Token Interface standard. The PKCS #11
Cryptographic Token Interface standard documents an API for devices that may
hold cryptographic information and may perform cryptographic functions.
Relationship of this specification to similar work: The PKCS#11 Suite of
documents maintains a liaison with the OASIS Key Management Interoperability
Protocol (KMIP) TC specifications in order to facilitate ease of integration
between the two specifications. The two pecification suites are
complimentary.
  Â--Statements of Use--
   ÂLink to Statement of Use #1:

https://www.oasis-open.org/apps/org/workgroup/pkcs11/download.php/66459/PKCS11v3.0-SOU-Cryptsoft-6-Jan-2020.pdf
   ÂLink to Statement of Use #2:

https://www.oasis-open.org/apps/org/workgroup/pkcs11/download.php/66584/PKCS11v3.0-SOU-Utimaco-Jan2020.pdf
   ÂLink to Statement of Use #3:

https://www.oasis-open.org/apps/org/workgroup/pkcs11/download.php/66711/ISC%20PKCS#11%20v3.0%20Statement%20of%20Use.pdf
   ÂAdditional Statements of Use:


  Â--Public Reviews--
   ÂFirst public review announcement URI:
   Âhttp://https//lists.oasis-open.org/archives/pkcs11/201906/msg00010.html
   ÂComment resolution log:

https://www.oasis-open.org/apps/org/workgroup/pkcs11/download.php/66357/PKCSk#11-v3.0-CSD-PR-Comments-TC%20Response-v4.pdf
   ÂAdditional public review announcement URIs:
   ÂAdditional comment resolution log URIs: http://


Approval link:
http://https//wiki.oasis-open.org/pkcs11/Meetingminutes/Minutes11032020
Earlier attempts to standardize: No
Sources of explanatory information:
Notes:


The results of this submission may be viewed at:
http://tools.oasis-open.org/issues/browse/TCADMIN



--
This message was sent by Atlassian Jira
(v8.3.3#803004)

--

/chetÂ
----------------

Chet Ensign

Chief Technical Community Steward
OASIS: Advancing open source & open standards for the information society
http://www.oasis-open.org

Mobile: +1 201-341-1393Â