Subject: RE: [pkcs11] Review before next meeting
All, here are my comments. Updated AEAD Proposal (not repeating what other people already commented) * Page 2, bottom, "For most mechanisms, C_EncryptMessage is equivalent to C_EncryptMessageBegin followed by a sequence of C_EncryptMessageNext operations. " : It would be useful to mention in which cases C_EncryptMessage is NOT equivalent to C_EncryptMessageBegin followed by a sequence of C_EncryptMessageNext operations, if any. Idem for decryption (page 7), signing (page 13) . * Page 6, line 8: continues o rfinishes -> continues or finishes * Page 6, line 14: dot at the end of the line. * Page 11, line 7: signs as ingle-part -> signs a single-part * Page 11, line 18: MessagedSignInit -> MessageSignInit * Page 13, lines 14 and 19: insert space in pParameterand, ulParameterLenspecify and pParametermay * Page 17, line 13: for for -> for * Page 19, line 18: .. -> . * Page 20, lines 4-8: insert space between parameter type and name * Page 20, line 15: pSignatureargument -> pSignature argument * Page 21, table 8: CKF_MULTI_MESSGE -> CKF_MULTI_MESSAGE. * Page 22: C_SignRecover is possibly a left-over from the original table 30? * Throughout the whole document : Consistently use Courier font for parameter names inside the text. AES GCM Changes: * I have added my feedback using track changes (only up to and including page 11) * Page 3 and 5: The meaning of the following section is not clear to me: " The key type for K must be compatible with CKM_AES_ECB and the C_EncryptInit/C_DecryptInit calls shall behave, with respect to K, as if they were called directly with CKM_AES_ECB, K and NULL parameters. " Thanks, Dieter On May 31, 2016, at 2:45 PM, Valerie Fenwick <email@example.com> wrote: > Hi folks- > > We want to really start moving forward on 3.0, and we have a few items that are approaching readiness for ballot. But, we really don't want to take things to ballot if they need changes before they can be approved :-) to that end, please take time before our next meeting to review and give feedback to the authors on. > > I have provided the public links as well, if you find that useful: > > * New function proposal draft 3(Bob R): > WG link: > https://www.oasis-open.org/apps/org/workgroup/pkcs11/document.php?docu > ment_id=58225 PUblic Link: > https://www.oasis-open.org/committees/document.php?document_id=58225 > > * Updated AEAD Proposal (Bob R.): > WG Link: > https://www.oasis-open.org/apps/org/workgroup/pkcs11/document.php?docu > ment_id=57976 Public Link: > https://www.oasis-open.org/committees/document.php?document_id=57976 > > * AES GCM Changes form AEAD API (Bob R.): > WG Link: > https://www.oasis-open.org/apps/org/workgroup/pkcs11/document.php?docu > ment_id=57637 Public Link: > https://www.oasis-open.org/committees/document.php?document_id=57637 > > * PKCS11 Wrapping with templates - v2 (Graham S): > WG Link: > https://www.oasis-open.org/apps/org/workgroup/pkcs11/document.php?docu > ment_id=58092 Public link: > https://www.oasis-open.org/committees/document.php?document_id=58092 > > > * Adding attributes to wrapped keys - (Graham S): > WG Link: > https://www.oasis-open.org/apps/org/workgroup/pkcs11/document.php?docu > ment_id=58091 Public Link: > https://www.oasis-open.org/committees/document.php?document_id=58091 > > > > Please complete your review by Monday, June 6, to give the author time to incorporate your suggested changes and have a moment for you to we review that they got them right before our next meeting on June 8. > > Thank you so much! There is a lot here, but once we start knocking > some of these things off, there will be less :-) > > > If I missed one of the documents we're currently reviewing, please let > me know. I know documents like the DSA one are awaiting further updates. > > I hope to have my proposal for constant identifier allocation out shortly. > > 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. > > --------------------------------------------------------------------- > To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail. Follow this link to all your TCs in OASIS at: > https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php --------------------------------------------------------------------- To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail. Follow this link to all your TCs in OASIS at: https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php ________________________________ Utimaco IS GmbH Seat: Aachen – Registergericht Aachen HRB 18922 VAT ID No.: DE 815 496 496 Managementboard: Malte Pollmann (Chairman) CEO, Dr. Frank J. Nellissen CFO Wichtiger Hinweis: Diese E-Mail kann Betriebs- und Geschäftsgeheimnisse oder sonstige vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrtümlich erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine Vervielfältigung oder Weitergabe der E-Mail ausdrücklich untersagt. Bitte benachrichtigen Sie uns und vernichten Sie die E-Mail. Der Absender hat alle erdenklichen Vorsichtsmaßnahmen getroffen, dass die Anlagen dieser E-Mail frei von Computerviren o. Ä. sind. Gleichwohl schließen wir die Haftung für jeden Schaden aus, der durch Computerviren o. Ä. verursacht wurde, soweit wir nicht vorsätzlich oder grob fahrlässig gehandelt haben. Wir raten Ihnen, dass Sie in jedem Fall Ihre eigene Virenprüfung vornehmen, bevor Sie die Anlagen öffnen. Vielen Dank. Important Notice: The information contained in this email message may be confidential information. 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. We have taken every reasonable precaution to ensure that any attachment to this email has been swept for viruses. However, we cannot accept liability for any damage sustained as a result of software viruses and would advise that you carry out your own virus checks before opening any attachment. Thank you for your cooperation.