[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Proposal: Standing Rule for Identifier Allocation
Hi folks! Here is my rough draft of a standing rule proposal. PKCS11 Technical Committee Standing Rule on Identifier AllocationThe PKCS11 technical specifications have several constants defined throughout the standard. Those constants are then used to create the header files for each version of the standard. There is a need for these values to be stable in order to maintain compatibility between various versions of the standard, and interoperability between various vendors and applications.
To assist developers who are working on testing new additions to the standard and for interoperability testing, it is important to stabilize the identifiers used for these constants as early in the process as possible.
After a proposal has gone through its review process, but before it goes to ballot or voice vote, the proposal author(s) should seek identifier values for all of their constants from the technical committee co-chairs before the ballot is opened.
If a proposal is not approved by the technical committee, it will be the co-chairs discretion whether or not to reuse those constant identifier values for a future proposal.
Section 2.9 of the TC process covers these rules, see this link for more details: https://www.oasis-open.org/policies-guidelines/tc-process#procedure Thank you for your review! Valerie -- Note: I am using voice recognition software. Forgive any strange words. Valerie Fenwick, http://bubbva.blogspot.com/ @bubbva Solaris Cryptographic & Key Management Technologies, Manager Oracle Corporation: 4180 Network Circle, Santa Clara, CA, 95054.