60-day Public Reviews for #PKCS #11 Cryptographic Token Interface Base Specification, Interface Profiles, Current Mechanisms Specification, and Historical Mechanisms Specification Versions 2.40 COS01 – end March 10th
Members of the OASIS PKCS 11 TC [1] have recently approved Special Majority Ballots [2] to advance four Committee Specifications as a Candidate OASIS Standards (COS). These COSs now enter a 60-day public review period in preparation for member ballots to consider their approvals as OASIS Standards.
PKCS #11 Cryptographic Token Interface Base Specification Version 2.40
Candidate OASIS Standard 01
23 December 2014
PKCS #11 Cryptographic Token Interface Profiles Version 2.40
Candidate OASIS Standard 01
23 December 2014
PKCS #11 Cryptographic Token Interface Current Mechanisms Specification Version 2.40
Candidate OASIS Standard 01
23 December 2014
PKCS #11 Cryptographic Token Interface Historical Mechanisms Specification Version 2.40
Candidate OASIS Standard 01
23 December 2014
Specification Overview:
The PKCS #11 Base Specification provides normative definition of PKCS #11 objects, attributes and operations.
The PKCS #11 Profiles document describes conformant profiles consisting of PKCS #11 objects, attributes, operations and mechanisms.
The PKCS #11 Current Mechanisms document describes the application of PKCS #11 objects, attributes and operations for specific mechanisms currently in general use.
The PKCS #11 Historical Mechanisms document describes the application of PKCS #11 objects, attributes and operations for specific mechanisms that have been but are no longer in general use.
Four Statements of Use were received for all four Committee Specifications from Cryptsoft, Feitian, P6R and Thales [3].
The OASIS PKCS 11 Technical Committee develops enhancements to improve the PKCS #11 standard for ease of use in code libraries, open source applications, wrappers, and enterprise/COTS products: implementation guidelines, usage tutorials, test scenarios and test suites, interoperability testing, coordination of functional testing, development of conformance profiles, and providing reference implementations.
Public Review Period:
The 60-day public review starts 10 January 2015 at 00:00 UTC and ends 30 March 2015 at 23:59 UTC.
This is an open invitation to comment. OASIS solicits feedback from potential users, developers and others, whether OASIS members or not, for the sake of improving the interoperability and quality of its technical work.
URIs:
The prose specification document and related files are available here:
– PKCS #11 Cryptographic Token Interface Base Specification Version 2.40
Editable source (Authoritative):
http://docs.oasis-open.org/pkcs11/pkcs11-base/v2.40/cos01/pkcs11-base-v2.40-cos01.doc
HTML:
http://docs.oasis-open.org/pkcs11/pkcs11-base/v2.40/cos01/pkcs11-base-v2.40-cos01.html
PDF:
http://docs.oasis-open.org/pkcs11/pkcs11-base/v2.40/cos01/pkcs11-base-v2.40-cos01.pdf
– PKCS #11 Cryptographic Token Interface Profiles Version 2.40
Editable source (Authoritative):
http://docs.oasis-open.org/pkcs11/pkcs11-profiles/v2.40/cos01/pkcs11-profiles-v2.40-cos01.doc
HTML:
http://docs.oasis-open.org/pkcs11/pkcs11-profiles/v2.40/cos01/pkcs11-profiles-v2.40-cos01.html
PDF:
http://docs.oasis-open.org/pkcs11/pkcs11-profiles/v2.40/cos01/pkcs11-profiles-v2.40-cos01.pdf
– PKCS #11 Cryptographic Token Interface Current Mechanisms Specification Version 2.40
Editable source (Authoritative):
http://docs.oasis-open.org/pkcs11/pkcs11-curr/v2.40/cos01/pkcs11-curr-v2.40-cos01.doc
HTML:
http://docs.oasis-open.org/pkcs11/pkcs11-curr/v2.40/cos01/pkcs11-curr-v2.40-cos01.html
PDF:
http://docs.oasis-open.org/pkcs11/pkcs11-curr/v2.40/cos01/pkcs11-curr-v2.40-cos01.pdf
– PKCS #11 Cryptographic Token Interface Historical Mechanisms Specification Version 2.40
Editable source (Authoritative):
http://docs.oasis-open.org/pkcs11/pkcs11-hist/v2.40/cos01/pkcs11-hist-v2.40-cos01.doc
HTML:
http://docs.oasis-open.org/pkcs11/pkcs11-hist/v2.40/cos01/pkcs11-hist-v2.40-cos01.html
PDF:
http://docs.oasis-open.org/pkcs11/pkcs11-hist/v2.40/cos01/pkcs11-hist-v2.40-cos01.pdf
ZIP distribution files (complete):
For your convenience, OASIS provides complete packages of each prose specification and related files in ZIP distribution files. You can download the ZIP files here:
– PKCS #11 Cryptographic Token Interface Base Specification:
http://docs.oasis-open.org/pkcs11/pkcs11-base/v2.40/cos01/pkcs11-base-v2.40-cos01.zip
– PKCS #11 Cryptographic Token Interface Profiles Version: http://docs.oasis-open.org/pkcs11/pkcs11-profiles/v2.40/cos01/pkcs11-profiles-v2.40-cos01.zip
– PKCS #11 Cryptographic Token Interface Current Mechanisms Specification: http://docs.oasis-open.org/pkcs11/pkcs11-curr/v2.40/cos01/pkcs11-curr-v2.40-cos01.zip
– PKCS #11 Cryptographic Token Interface Historical Mechanisms Specification: http://docs.oasis-open.org/pkcs11/pkcs11-hist/v2.40/cos01/pkcs11-hist-v2.40-cos01.zip
Additional information about the specification and the OASIS PKCS 11 TC may be found at the TC’s public home page:
https://www.oasis-open.org/committees/pkcs11/
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 by TC non-members for this work and for other work of this TC are publicly archived and can be viewed at:
http://lists.oasis-open.org/archives/pkcs11-comment/
All comments submitted to OASIS are subject to the OASIS Feedback License, which ensures that the feedback you provide carries the same obligations at least as the obligations of the TC members. In connection with the public reviews of these Candidate OASIS Standards, we call your attention to the OASIS IPR Policy [4] applicable especially [5] to the work of this technical committee. All members of the TC should be familiar with this document, which may create obligations regarding the disclosure and availability of a member’s patent, copyright, trademark and license rights that read on an approved OASIS specification.
OASIS invites any persons who know of any such claims to disclose these if they may be essential to the implementation of the above specification, so that notice of them may be posted to the notice page for this TC’s work.
==============
[1] OASIS PKCS 11 TC
https://www.oasis-open.org/committees/pkcs11/
[2] Candidate OASIS Standard ballots:
1) PKCS #11 Cryptographic Token Interface Base Specification
https://www.oasis-open.org/committees/ballot.php?id=2721
2) PKCS #11 Cryptographic Token Interface Profiles V2.40
https://www.oasis-open.org/committees/ballot.php?id=2724
2) PKCS #11 Cryptographic Token Interface Current Mechanisms Specification
https://www.oasis-open.org/committees/ballot.php?id=2722
3) PKCS #11 Cryptographic Token Interface Historical Mechanisms
Specification
https://www.oasis-open.org/committees/ballot.php?id=2723
[3] 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
[4] http://www.oasis-open.org/policies-guidelines/ipr
[5] http://www.oasis-open.org/committees/pkcs11/ipr.php
https://www.oasis-open.org/policies-guidelines/ipr#s10.2.2
RF on RAND