Bob, all, Looking for some simplifications, I ’ ve spotted this: - The conditions 1 and 2 can be combined. An implementation is either a consumer or a provider, there is no third option. For both, the conditions required by the PKCS #11 Authentication Token Clause (Section 3.6.2) must be supported. Thus, these conditions have to be supported always. - And condition 5 is the same as condition 6a and can, therefore, be removed. Finally, what ’ s the CKA_USER attribute mentioned in condition 6.b.iii.? Best regards, Daniel From:
pkcs11@lists.oasis-open.org [mailto:
pkcs11@lists.oasis-open.org] On Behalf Of Robert Relyea Sent: Mittwoch, 24. Mai 2017 22:06 To:
pkcs11@lists.oasis-open.org Subject: [pkcs11] Groups - Publicly Readable Cert Profile uploaded Document Name : Publicly Readable Cert Profile Description New Profile of type Authentication token for Authentication tokens that have publicly readable certificates. Download Latest Revision Public Download Link Submitter : Mr. Robert Relyea Group : OASIS PKCS 11 TC Folder : Working Drafts Date submitted : 2017-05-24 13:05:51 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: Malte Pollmann (Chairman) CEO, Dr. Frank J. Nellissen CFO This communication is confidential. We only send and receive email on the basis of the terms set out at
https://www.utimaco.com/en/e-mail-disclaimer/