OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

pkcs11 message

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


Subject: FW: [pkcs11] Groups - Ballots opened: 4


Hi –

 

Please be sure to vote on all 4 ballots (using the drop down list in the upper right corner of the ballot=.

 

Thanks!

 

Bob

 

From: workgroup_mailer@lists.oasis-open.org [mailto:workgroup_mailer@lists.oasis-open.org] On Behalf Of tc_admin@oasis-open.org
Sent: Dienstag, 16. Dezember 2014 19:02
To: Griffin, Robert
Subject: [pkcs11] Groups - Ballots opened: 4

 

"Approve submitting PKCS #11 Cryptographic Token Interface Base Specification V2.40 as a Candidate OASIS Standard" has opened.

Ballot Title: Approve submitting PKCS #11 Cryptographic Token Interface Base Specification V2.40 as a Candidate OASIS Standard



Question
Do you approve submitting PKCS #11 Cryptographic Token Interface Base Specification V2.40 [1] with Designated Cross Reference changes [2] to the OASIS membership for consideration as a COS

Closing Date: Tuesday, 23 December 2014 @ 11:59 pm UTC

Description
The PKCS #11 Cryptographic Token Interface Base Specification Version 2.40 was approved as a Committee Specification on 16 November 2014. The TC has received 4 Statements of Use from Cryptsoft, Feitian, P6R and Thales [3]. Do you now approve submitting PKCS #11 Cryptographic Token Interface Base Specification V2.40 to the OASIS membership for consideration as a Candidate OASIS Standard?



Approving this ballot will result in a 60-day public review after which, if no comments are received, the COS will be submitted to a membership-wide ballot. If comments are received, the TC will be asked to vote by Special Majority Ballot on whether to continue to the membership vote. This is explained in TC Process section 3.4.2, Public Review of a Candidate OASIS Standard [4].



This ballot requires a Special Majority Vote [5]. The TC roster currently lists 20 voting members. In order to pass, at least 14 (2/3 x 20) members have to vote Yes and no more than 5 (1/4 x 20) members may vote No.



[1] URI to the Committee Specification:

http://docs.oasis-open.org/pkcs11/pkcs11-base/v2.40/pkcs11-base-v2.40.html



[2] Designated Cross Reference changes:



PKCS #11 Cryptographic Token Interface Profiles Version 2.40, 16-Sep-2014,

OASIS Committee Specification 01, http://docs.oasis-open.org/pkcs11/pkcs11-profiles/v2.40/cs01/pkcs11-profiles-v2.40-cs01.doc



PKCS #11 Cryptographic Token Interface Current Mechanisms Specification

Version 2.40, 16-Nov-2014, OASIS Committee Specification 02, http://docs.oasis-open.org/pkcs11/pkcs11-curr/v2.40/cs02/pkcs11-curr-v2.40-cs02.doc



PKCS #11 Cryptographic Token Interface Historical Mechanisms Specification

Version 2.40, 16-Nov-2014, OASIS Committee Specification 02, http://docs.oasis-open.org/pkcs11/pkcs11-hist/v2.40/cs02/pkcs11-hist-v2.40-cs02.doc



PKCS #11 Cryptographic Token Interface Usage Guide Version 2.40, 16-Sep-2014,

OASIS Committee Note 02, http://docs.oasis-open.org/pkcs11/pkcs11-ug/v2.40/cnd02/pkcs11-ug-v2.40-cnd02.doc



[3] Links to Statements of Use



Cryptsoft Pty Ltd: https://www.oasis-open.org/committees/download.php/54584/PKCS11-SOU-Cryptsoft-19-Nov-2014-final.pdf



Feitian Technologies Co., Ltd.: https://www.oasis-open.org/committees/download.php/54590/PKCS11-SOU-Feitian-20-November-2014-final.pdf



P6R Inc.: https://www.oasis-open.org/committees/download.php/54606/PKCS11-SOU-P6R-23-NOV-2014-final.pdf



Thales e-Security, Inc.: https://www.oasis-open.org/committees/download.php/54657/PKCS11-SOU-Thales-e-Security-01-Dec-2014.pdf



[3] http://www.oasis-open.org/policies-guidelines/tc-process#OASISstandard



[4] Special Majority Vote: http://www.oasis-open.org/committees/process-2010-07-28.php#dSpecialMajority

Vote

  • Yes
  • No
  • Abstain

Group: OASIS PKCS 11 TC
Date Opened: Wednesday, 17 December 2014 @ 12:00 am UTC


"Approve submitting PKCS #11 Cryptographic Token Interface Current Mechanisms Specification V2.40 as a Candidate OASIS Standard" has opened.

Ballot Title: Approve submitting PKCS #11 Cryptographic Token Interface Current Mechanisms Specification V2.40 as a Candidate OASIS Standard



Question
Do you approve submitting PKCS #11 Cryptographic Token Interface Current Mechanisms Specification V2.40 [1] with Designated Cross Reference changes [2] to the membership for consideration as a COS?

Closing Date: Tuesday, 23 December 2014 @ 11:59 pm UTC

Description
The PKCS #11 Cryptographic Token Interface Current Mechanisms Specification Version 2.40 was approved as a Committee Specification on 16 November 2014. The TC has received 4 Statements of Use from Cryptsoft, Feitian, P6R and Thales [3]. Do you now approve submitting PKCS #11 Cryptographic Token Interface Current Mechanisms Specification Version 2.40 to the OASIS membership for consideration as a Candidate OASIS Standard?



Approving this ballot will result in a 60-day public review after which, if no comments are received, the COS will be submitted to a membership-wide ballot. If comments are received, the TC will be asked to vote by Special Majority Ballot on whether to continue to the membership vote. This is explained in TC Process section 3.4.2, Public Review of a Candidate OASIS Standard [4].



This ballot requires a Special Majority Vote [5]. The TC roster currently lists 20 voting members. In order to pass, at least 14 (2/3 x 20) members have to vote Yes and no more than 5 (1/4 x 20) members may vote No.



[1] URI to the Committee Specification:

http://docs.oasis-open.org/pkcs11/pkcs11-curr/v2.40/pkcs11-curr-v2.40.html



[2] Designated Cross Reference changes:



PKCS #11 Cryptographic Token Interface Base Specification Version 2.40,

16-Nov-2014, OASIS Committee Specification 02, http://docs.oasis-open.org/pkcs11/pkcs11-base/v2.40/cs02/pkcs11-base-v2.40-cs02.doc



PKCS #11 Cryptographic Token Interface Profiles Version 2.40, 16-Sep-2014,

OASIS Committee Specification 01, http://docs.oasis-open.org/pkcs11/pkcs11-profiles/v2.40/cs01/pkcs11-profiles-v2.40-cs01.doc



PKCS #11 Cryptographic Token Interface Historical Mechanisms Specification

Version 2.40, 16-Nov-2014, OASIS Committee Specification 02,

http://docs.oasis-open.org/pkcs11/pkcs11-hist/v2.40/cs02/pkcs11-hist-v2.40-cs02.doc



PKCS #11 Cryptographic Token Interface Usage Guide Version 2.40, 16-Sep-2014,

OASIS Committee Note 02, http://docs.oasis-open.org/pkcs11/pkcs11-ug/v2.40/cnd02/pkcs11-ug-v2.40-cnd02.doc



[3] Links to Statements of Use



Cryptsoft Pty Ltd: https://www.oasis-open.org/committees/download.php/54584/PKCS11-SOU-Cryptsoft-19-Nov-2014-final.pdf



Feitian Technologies Co., Ltd.: https://www.oasis-open.org/committees/download.php/54590/PKCS11-SOU-Feitian-20-November-2014-final.pdf



P6R Inc.: https://www.oasis-open.org/committees/download.php/54606/PKCS11-SOU-P6R-23-NOV-2014-final.pdf



Thales e-Security, Inc.: https://www.oasis-open.org/committees/download.php/54657/PKCS11-SOU-Thales-e-Security-01-Dec-2014.pdf



[3] http://www.oasis-open.org/policies-guidelines/tc-process#OASISstandard



[4] Special Majority Vote: http://www.oasis-open.org/committees/process-2010-07-28.php#dSpecialMajority

Vote

  • Yes
  • No
  • Abstain

Group: OASIS PKCS 11 TC
Date Opened: Wednesday, 17 December 2014 @ 12:00 am UTC


"Approve submitting PKCS #11 Cryptographic Token Interface Historical Mechanisms V2.40 as a Candidate OASIS Standard" has opened.

Ballot Title: Approve submitting PKCS #11 Cryptographic Token Interface Historical Mechanisms V2.40 as a Candidate OASIS Standard



Question
Do you approve submitting PKCS #11 Cryptographic Token Interface Historical Mechanisms V2.40 [1] with Designated Cross Reference changes [2] to the OASIS membership for consideration as a COS?

Closing Date: Tuesday, 23 December 2014 @ 11:59 pm UTC

Description
The PKCS #11 Cryptographic Token Interface Historical Mechanisms Version 2.40 was approved as a Committee Specification on 16 November 2014. The TC has received 4 Statements of Use from Cryptsoft, Feitian, P6R and Thales [3]. Do you now approve submitting PKCS #11 Cryptographic Token Interface Historical Mechanisms Version 2.40 to the OASIS membership for consideration as a Candidate OASIS Standard?



Approving this ballot will result in a 60-day public review after which, if no comments are received, the COS will be submitted to a membership-wide ballot. If comments are received, the TC will be asked to vote by Special Majority Ballot on whether to continue to the membership vote. This is explained in TC Process section 3.4.2, Public Review of a Candidate OASIS Standard [4].



This ballot requires a Special Majority Vote [5]. The TC roster currently lists 20 voting members. In order to pass, at least 14 (2/3 x 20) members have to vote Yes and no more than 5 (1/4 x 20) members may vote No.



[1] URI to the Committee Specification:

http://docs.oasis-open.org/pkcs11/pkcs11-hist/v2.40/pkcs11-hist-v2.40.html



[2] Designated Cross Reference changes:



PKCS #11 Cryptographic Token Interface Base Specification Version 2.40,

16-Nov-2014, OASIS Committee Specification 02, http://docs.oasis-open.org/pkcs11/pkcs11-base/v2.40/cs02/pkcs11-base-v2.40-cs02.doc



PKCS #11 Cryptographic Token Interface Profiles Version 2.40, 16-Sep-2014,

OASIS Committee Specification 01, http://docs.oasis-open.org/pkcs11/pkcs11-profiles/v2.40/cs01/pkcs11-profiles-v2.40-cs01.doc



PKCS #11 Cryptographic Token Interface Current Mechanisms Specification

Version 2.40, 16-Nov-2014, OASIS Committee Specification 02,

http://docs.oasis-open.org/pkcs11/pkcs11-curr/v2.40/cs02/pkcs11-curr-v2.40-cs02.doc



PKCS #11 Cryptographic Token Interface Usage Guide Version 2.40, 16-Sep-2014,

OASIS Committee Note 02, http://docs.oasis-open.org/pkcs11/pkcs11-ug/v2.40/cnd02/pkcs11-ug-v2.40-cnd02.doc



[3] Links to Statements of Use



Cryptsoft Pty Ltd: https://www.oasis-open.org/committees/download.php/54584/PKCS11-SOU-Cryptsoft-19-Nov-2014-final.pdf



Feitian Technologies Co., Ltd.: https://www.oasis-open.org/committees/download.php/54590/PKCS11-SOU-Feitian-20-November-2014-final.pdf



P6R Inc.: https://www.oasis-open.org/committees/download.php/54606/PKCS11-SOU-P6R-23-NOV-2014-final.pdf



Thales e-Security, Inc.: https://www.oasis-open.org/committees/download.php/54657/PKCS11-SOU-Thales-e-Security-01-Dec-2014.pdf



[3] http://www.oasis-open.org/policies-guidelines/tc-process#OASISstandard



[4] Special Majority Vote: http://www.oasis-open.org/committees/process-2010-07-28.php#dSpecialMajority

Vote

  • Yes
  • No
  • Abstain

Group: OASIS PKCS 11 TC
Date Opened: Wednesday, 17 December 2014 @ 12:00 am UTC


"Approve submitting PKCS #11 Cryptographic Token Interface Profiles V2.40 as a Candidate OASIS Standard" has opened.

Ballot Title: Approve submitting PKCS #11 Cryptographic Token Interface Profiles V2.40 as a Candidate OASIS Standard



Question
Do you approve submitting PKCS #11 Cryptographic Token Interface Profiles V2.40 [1] with Designated Cross Reference changes [2] to the OASIS membership for consideration as a COS?

Closing Date: Tuesday, 23 December 2014 @ 7:00 am UTC

Description
The PKCS #11 Cryptographic Token Interface Profiles Version 2.40 was approved as a Committee Specification on 16 November 2014. The TC has received 4 Statements of Use from Cryptsoft, Feitian, P6R and Thales [3]. Do you now approve submitting PKCS #11 Cryptographic Token Interface Profiles Version 2.40 to the OASIS membership for consideration as a Candidate OASIS Standard?



Approving this ballot will result in a 60-day public review after which, if no comments are received, the COS will be submitted to a membership-wide ballot. If comments are received, the TC will be asked to vote by Special Majority Ballot on whether to continue to the membership vote. This is explained in TC Process section 3.4.2, Public Review of a Candidate OASIS Standard [4].



This ballot requires a Special Majority Vote [5]. The TC roster currently lists 20 voting members. In order to pass, at least 14 (2/3 x 20) members have to vote Yes and no more than 5 (1/4 x 20) members may vote No.



[1] URI to the Committee Specification:

http://docs.oasis-open.org/pkcs11/pkcs11-profiles/v2.40/pkcs11-profiles-v2.40.html



[2] Designated Cross Reference changes:



PKCS #11 Cryptographic Token Interface Profiles Version 2.40, 16-Sep-2014,

OASIS Committee Specification 01,

http://docs.oasis-open.org/pkcs11/pkcs11-profiles/v2.40/cs01/pkcs11-profiles-v2.40-cs01.doc



PKCS #11 Cryptographic Token Interface Current Mechanisms Specification

Version 2.40, 16-Nov-2014, OASIS Committee Specification 02,

http://docs.oasis-open.org/pkcs11/pkcs11-curr/v2.40/cs02/pkcs11-curr-v2.40-cs02.doc



PKCS #11 Cryptographic Token Interface Historical Mechanisms Specification

Version 2.40, 16-Nov-2014, OASIS Committee Specification 02,

http://docs.oasis-open.org/pkcs11/pkcs11-hist/v2.40/cs02/pkcs11-hist-v2.40-cs02.doc



PKCS #11 Cryptographic Token Interface Usage Guide Version 2.40, 16-Sep-2014,

OASIS Committee Note 02,

http://docs.oasis-open.org/pkcs11/pkcs11-ug/v2.40/cnd02/pkcs11-ug-v2.40-cnd02.doc



[3] Links to Statements of Use



Cryptsoft Pty Ltd: https://www.oasis-open.org/committees/download.php/54584/PKCS11-SOU-Cryptsoft-19-Nov-2014-final.pdf



Feitian Technologies Co., Ltd.: https://www.oasis-open.org/committees/download.php/54590/PKCS11-SOU-Feitian-20-November-2014-final.pdf



P6R Inc.: https://www.oasis-open.org/committees/download.php/54606/PKCS11-SOU-P6R-23-NOV-2014-final.pdf



Thales e-Security, Inc.: https://www.oasis-open.org/committees/download.php/54657/PKCS11-SOU-Thales-e-Security-01-Dec-2014.pdf



[3] http://www.oasis-open.org/policies-guidelines/tc-process#OASISstandard



[4] Special Majority Vote: http://www.oasis-open.org/committees/process-2010-07-28.php#dSpecialMajority

Vote

  • Yes
  • No
  • Abstain

Group: OASIS PKCS 11 TC
Date Opened: Wednesday, 17 December 2014 @ 12:00 am UTC

 



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