Bob, A noticed a few editorial updates are needed: Page 2: “CK_FUNCTION_LIST_3_2 is a structure which contains the same function pointers as in CK_FUNCTION_LIST and …”. Shouldn’t we refer to CK_FUNCTION_LIST_3.0 instead of CK_FUNCTION_LIST, as CK_FUNCTION_LIST_3.0 already has extensions to CK_FUNCTION_LIST ? Page 4: at the end of the function list table, right before section 1.1.1: CK_FUNCTION_LIST_3.0 -> CK_FUNCTION_LIST_3.2 Section 1.3.2, in paragraph starting with “C_Encapulates creates …”, in sentence “The CKA_ENCAPSULATE attribute of the private key, which indicates whether the key supports decapsulation, MUST be CK_TRUE.” replace “private key” by “public key”, and “supports decapsulation” by “supports encapsulation”. Same paragraph, last sentence “The values … for the base key …” What is the base key here? Can it be that this sentence is left over from a copy-paste but doesn’t apply here, or has to be rephrased? Example in section 1.3.2: change “CK_ATTRIBUTE derivedKeyTemplate[]” to “CK_ATTRIBUTE keyTemplate[]”; add hpubKey as 3 rd argument to function call C_EncapsulateKey With that, the document is good for me. Thanks and best regards, Dieter From:
pkcs11@lists.oasis-open.org <
pkcs11@lists.oasis-open.org> On Behalf Of Robert Relyea Sent: Friday, May 5, 2023 11:21 PM To:
pkcs11@lists.oasis-open.org Subject: [pkcs11] Groups - Add KEM APIs to PKCS #11 uploaded Submitter's message I've tried to pick up the latest comments. Still outstanding: C_Encapsulate and C_Decapsulate or C_EncapsulateKey and C_DecapsulateKey -- Mr. Robert Relyea Document Name : Add KEM APIs to PKCS #11 Description Draft to of the KEM API proposal Download Latest Revision Public Download Link Submitter : Mr. Robert Relyea Group : OASIS PKCS 11 TC Folder : Working Drafts Date submitted : 2023-05-05 14:21:26 Utimaco IS GmbH Germanusstr. 4, D.52080 Aachen, Germany, Tel: +49-241-1696-0,
www.utimaco.com Seat: Aachen – Registergericht Aachen HRB 18922 VAT ID No.: DE 815 496 496 Managementboard: Stefan Auerbach, Martin Stamm, Hacan Tiwemark This communication is confidential. If you are not the intended recipient, any use, interference with, disclosure or copying of this material is unauthorised and prohibited. Please inform us immediately and destroy the email.