Hi Somesh,
To add to the conversation, we did identify that there may be ID
clashes within the reserved vendor mechanisms space however we are
biting this off in chunks. for V3.0 we ring-fenced the reserved
space. For v3.1 the TC has already agreed that a key focus will be
on on testing which requires greater levels of interoperability
and as such, I am expecting that we will tighten up on how we
handle vendor-specific content.
That said, as Valerie mentioned, if you have some specific
requirements - we'd love to see them.
Best Regards,
2017-02-24T20:38:00Z
1
19
191
1
1
209
14.00
X-NONE
X-NONE
MicrosoftInternetExplorer4
Tony Cox
VP
Partners,
Alliances & Standards
Cryptsoft
P:Â +61 7 3103 0321, US:Â +1 (650) 918 4307
On 22/05/2019 3:40 am, Fenwick, Valerie
wrote:
Hi Somesh â
Â
We donât
reserve ranges of vendor defined mechanisms, other than what
range they can be in. That is, 2 separate vendors may use
the same IDs, which require the applications to understand
what libraries they are calling into and the expected
behavior.
Â
What are the
mechanisms for? We have many new mechanisms coming out in
PKCS#11 v3.0 and you may find your needs are already met by
the standard.
Â
Thank you,
Â
Valerie
Â
From:
<>
On Behalf Of Chakrabarti, Somesh
Sent: Monday, May 20, 2019 4:23 PM
To:
Subject: [pkcs11-comment] Request for vendor
defined mechanism allocation
Â
Dear PKCS11
committee and members,
Â
We want to
reserve a block of vendor defined mechanism codes for AWS
CloudHSM. Can you please let us know what is required to do
this?
Â
Thank you,
Somesh
Chakrabarti
Sr Security
Engineer, AWS CloudHSM
