Subject: draft motions and other information regarding the request for OASIS candidate standard ballot
Here is the draft motion for our PKCS 11 TC meeting and drafts of 2 additional paragraphs that I will need to submit with the request.
I move to approve the PKCS 11 TC co-chairs requesting that TC Administration hold a Special Majority Vote to approve submitting the following documents as Candidate OASIS Standards:
PKCS #11 Cryptographic Token Interface Base Specification v2.40 Committee Specification cs01 at http://docs.oasis-open.org/pkcs11/pkcs11-base/v2.40/cs01/pkcs11-base-v2.40-cs01.doc
PKCS #11 Cryptographic Token Interface Current Mechanisms Specification v2.40 Committee Specification cs01 at http://docs.oasis-open.org/pkcs11/pkcs11-curr/v2.40/cs01/pkcs11-curr-v2.40-cs01.doc
PKCS #11 Cryptographic Token Interface Historical Mechanisms Specification v2.40 Committee Specification cs01 at http://docs.oasis-open.org/pkcs11/pkcs11-hist/v2.40/cs01/pkcs11-hist-v2.40-cs01.doc
PKCS #11 Cryptographic Token Interface Profiles v2.40 Committee Specification cs01 at http://docs.oasis-open.org/pkcs11/pkcs11-profiles/v2.40/cs01/pkcs11-profiles-v2.40-cs01.zip
(d) A clear English-language summary of the specification
The PKCS #11 standard defines the data types and functions available to an application using the Cryptoki application programming interface (API). PKCS #11 isolates an application from the details of the specifics of a cryptographic device. The application does not have to change to interface to devices offering the same cryptographic functions or to be able to run in a different environment; thus, the application is portable between devices from different vendors and devices operating in different environments.
The PKCS #11 Base Specification provides the normative _expression_ of the application programming interface for the standard, including objects, attributes, operations and other elements.
The PKCS #11 Current Mechanisms Specification defines mechanisms that are anticipated for use with the current version of PKCS #11.
The PKCS #11 Historical Mechanisms Specification defines mechanisms for PKCS #11 that are no longer in general use.
The PKCS #11 Profiles document describes profiles that define a set of normative constraints for employing PKCS #11 within a particular environment or context of use for developers and architects who wish to design systems and applications that conform to the PKCS #11 Cryptographic Token Interface standard.
(e) A statement regarding the relationship of this specification to similar work of other OASIS TCs or other standards developing organizations;
PKCS #11 is one of the family of standards called Public-Key Cryptography Standards (PKCS), originally developed under the leadership of and published by RSA Laboratories. Minimal further development is anticipated at this time for the other standards within the PKCS family, some of which remain under RSA leadership and others of which have been transferred to IETF. Activity in support of cryptographic standardization is also occurring in a number of other venues, including OASIS Technical Committees such the Key Management Interoperability Protocol (KMIP). The PKCS 11 Technical Committee seeks to align its technical activities and deliverables with other standardization initiatives in order to support harmonized vocabularies, avoid unnecessary duplication of effort, and promote interoperability and integration with respect to cryptographic objects and operations. Toward this end, the OASIS PKCS 11 Technical Committee has established a formal TC Liaison relationship with OASIS KMIP TC.
(Should we mention other efforts as well, such as Technical Committee, JCA (Java Cryptography Architecture) and JCE (Java Cryptography Extension) frameworks and under vendor sponsorship such as the Microsoft CNG (Cryptography Next Generation) APIs. Other standards groups working on cryptography-related standards include IEEE (P1619), IETF (KeyProv), ANSI (X9.31) and ISO (ISO/IEC 9796)? )