Re: [pkcs11] Text for motion to move Working Draft to Committee Specific

Subject: Re: [pkcs11] Text for motion to move Working Draft to Committee Specification

On Tue, Jan 25, 2022 at 5:57 AM Greg Scott <greg.scott@cryptsoft.com> wrote:

Bob,

I took an action item to get the appropriate motion text together to move the latest working draft to Committee Specification for PKCS11 3.1. The current approved template motion text for this action is:

"I move that the TC approve <Working Draft title, version number and revision number> and all associated artifacts packaged together in <URL to ZIP file in TC's Kavi document repository> as a Committee Specification Draft and designate Âthe <format> version of the specification as authoritative.â

Noting the above:

- The working draft is currently "PKCS#11 specification v3.1 working draft 10â however if we make any further changes this will need to be updated.

- I believe we may need to produce a ZIP file of the document (.docx, .html, .pdf) and any header files and other documents in the git repository and upload these into the document repository as part of the motion text;

- The <format> of the document to be the authoritative version should be a PDF.

This is based on the standard OASIS motion and ballot language template atÂhttps://www.oasis-open.org/committees/download.php/53768Âand is the process we have been using for the SAM and KMIP TCs.

Going back through the meetings from memory we have used the wording of "link to be providedâ in the meeting, the URL of the file is then added in the minutes Âand then when the TC reviews the minutes of that meeting and approves them then TC Admin can take the required action.

So as long as WD 10 is reviewed and there are no further changes then we can use this as the basis of the document to move from Working Draft to Committee Specification.

Regards
Greg

â
Greg Scott
E: greg.scott@cryptsoft.com
M: +61 406 255 166

pkcs11 message

ChetÂEnsign