Re: [pkcs11] We need you to re-approve the PKCS11 Specification v3.1 - the current one is incomplete

[Greg Scott <greg.scott@cryptsoft.com>]

Chet,

Probably my mistake as the comments which were raised were only in relation to the document and so when I went through the template text from the TC process and there was no reference to other objects being required I did not add them into the text.Â

This has two causes then, the first issue was mine, being new in this role in the TC I was trying to follow closely the sample text to avoid such an error, the second is that the sample text has no example for this type of issue and if there was a previous problem with a TC as in V3.0 then adding an item clarifying this would have been helpful. Perhaps now is a time to update so you donât have this problem again.

I will get the files together and run it all past you when I get to the office, considering my time zone and as there is little overlap with our locations, there may be a slight delay

Greg

â

Greg Scott

E: greg.scott@cryptsoft.com

M: +61 406 255 166

On 21 July 2022 at 6:06:13 am, Chet Ensign (chet.ensign@oasis-open.org) wrote:

Members of the PKCS11 TC,Â

Paul started work on publishing the PKCS 11 Specification v3.1 files but realized that only the DOCX file was approved. The approval did not include the header files that were previously a part of the spec. This also happened on V3.0 and we had to do a kludge - a red alert on the cover page telling people that the header files included were out of date.Â

Please put together a new ZIP file containing all the component parts that have to be published together as the CS. I will run a new SMV to approve it and then we can return to its publication.Â

Thanks for your help,Â

/chet

ChetÂEnsign

Chief Technical Community Steward

OASIS Open

Â

Â

Â

	+1 201-341-1393
	chet.ensign@oasis-open.org
	www.oasis-open.org