OASIS PKCS 11 TC

 View Only

  • 1.  Motions for our next meeting

    Posted 03-03-2025 14:30
    Hi All 

    I can update this and add to the agenda once we have the final Zip with Header files and WD of spec available. 


    Motions for PKCS#11 Specification Version 3.2

    Motion 1a

    I move that the TC approve <Working Draft title, version number and revision number> and all associated artifacts packaged together in <URL to ZIP file in project's document repository> as a Committee Specification Draft and designate  the Word version of the specification as authoritative.

    Motion 1b if we decide to include CKR_PARAMETER_SET_NOT_SUPPORTED 
    I move that the TC approve <Working Draft title, version number and revision number> which includes the addition of CKR_PARAMETER_SET_NOT_SUPPORTED for ML-KEM, ML-DSA and SLH-DSA.and all associated artifacts packaged together in <URL to ZIP file in project's document repository> as a Committee Specification Draft and designate  the Word version of the specification as authoritative.

    Motions for Committee Note Drafts

    @Tim and @Dieter - please upload Zip files of these respective documents

    The Usage Guide and Profiles documents will be Committee Notes.

    Motion 2a:
    I move that the TC approve <working draft title and version number> and all associated artifacts packaged together at <URL to ZIP file in the TC's document repository> as a Committee Note. 

    If I understand the OASIS process correctly, committee needs to officially declare these as Committee Note drafts (which we may have done earlier?) before we can go to public review.  If we did this part already, then we can recommend the committee notes for public review:

    Motion 2b:
    I move that the TC approve submitting <Committee Note Draft title, version number and revision number> contained in <URL to CND on docs.oasis-open.org OR ZIP file in OASIS Project's document repository> for <number of days> public review.

    Thoughts and feedback welcome!

    Valerie


  • 2.  RE: Motions for our next meeting

    Posted 03-04-2025 07:27

    THALES GROUP LIMITED DISTRIBUTION to email recipients

     

    Hi,

    should we also add CKR_PARAMETER_SET_NOT_SUPPORTED to XMSS and XMSSMT as they also support a CKA_PARAMETER_SET attribute?

     

    Everything else looks good to me.

     

    Thanks

     




    Original Message


  • 3.  RE: Motions for our next meeting

    Posted 03-05-2025 08:37

    Hi Darren,

    I added the same comment about XMSS / XMSS MT just a few minutes ago to the discussion thread New error code for parameter set not supported | OASIS PKCS 11 TC . Thus yes, the motion should include XMSS and XMSS MT.



    ------------------------------
    Best regards,
    Dieter
    ------------------------------

    Original Message


  • 4.  RE: Motions for our next meeting

    Posted 03-06-2025 11:17

    Hi Valerie,

    I'm just preparing packages for public review and noticed that the Profiles document for PKCS#11 v3.1 and v3.0 have not been Committee Notes but OASIS standards. I thus assume that the Profiles document for PKCS#11 v3.2 will remain a standard, will it?

    There is no question about the Usage Guide being a Committee Note.



    ------------------------------
    Best regards,
    Dieter
    ------------------------------

    Original Message


  • 5.  RE: Motions for our next meeting

    Posted 03-06-2025 11:25
    The profiles remain a standard - which is required as that is where our conformance clauses are.
    The documents are "current" in that all the feedback has been applied long ago and we haven't extended the profiles (we could - but again that is too late for 3.2 in my view).

    Tim.




    Original Message


  • 6.  RE: Motions for our next meeting

    Posted 03-12-2025 14:39
    Apologies Dieter, yes, the profiles would also be a standard.

    I think our motions today will be: 

    1. I move to approve PKCS#11 v3.2 Committee Specification Working Draft 11 including the return code additions to message digest APIs per the email sent by Amine Najahi Extra return values for message-based APIs. | OASIS PKCS 11 TC , and the addition of CKR_PARAMETER_SET_NOT_SUPPORTED per the discussion thread by Tim Hudson New error code for parameter set not supported.
    2. I move that the TC approve PKCS#11 v3.2 Committee Specification Working Draft 11 and all associated artifacts packaged together in pkcs11-spec-v3.2-wd11.zip as a Committee Specification Draft and designate the Word version of the specification as authoritative.
    3. I move to approve PKCS#11 v3.2 Profiles Document Working Draft 03 and all associated artifacts packaged together in pkcs11-profiles-v3.2-wd03.zip as a Committee Specification Draft and designate the Word version of the specification as authoritative 
    4. I move  that the TC approve submitting PKCS#11 v 3.2 Usage Guide Working Draft 01 contained in pkcs11-ug-v3.2-wd01-clean.docx for 30 days public review.

    Valerie

    On Mar 6, 2025, at 8:17 AM, Dieter Bong via OASIS <Mail@mail.groups.oasis-open.org> wrote:





    Original Message


Related Content