-
Notifications
You must be signed in to change notification settings - Fork 30
MeetingMinutes20250312
Simo Sorce edited this page Mar 2, 2026
·
2 revisions
* Roll call taken by Bob R, quorum achieved. * Valerie F and Tim H took minutes.
* Attendance: Bob Relyea, Valerie Fenwick, Darren Johnson, Dieter Bong, Tim Hudson, Scott Marshall, Simo Sorce, Jonathan Schulze-Hewett
* Roll call * Review / approval of the agenda * Approve Minutes (February 26, 2025) * PKCS#11 v3.2 * Motions to approve committee notes and committee specification draft * Other 3.2 Discussion Items * PKCS#11 v3.3 * Logistics (wiki, markdown, etc) * New Business * Next Meeting * Call for late arrivals * Adjourn
* Motion: That the agenda for this meeting be approved. * Moved: Tim. Seconded: Simo. No objections, abstentions or comments. Agenda approved.
* Motion: That the minutes posted for [[https://wiki.oasis-open.org/pkcs11/MeetingMinutes20250226| February 26, 2025]] be approved. * Moved: Tim. Seconded: Dieter. No comments. No abstentions. No objections. Minutes approved.
* I move to approve PKCS#11 v3.2 Committee Specification Working Draft 11 including the return code additions to message digest APIs per the email sent by Amine Najahi [[https://groups.oasis-open.org/discussion/extra-return-values-for-message-based-apis|Extra return values for message-based APIs.]] | OASIS PKCS 11 TC , and the addition of CKR_PARAMETER_SET_NOT_SUPPORTED per the discussion thread by Tim Hudson [[https://groups.oasis-open.org/discussion/new-error-code-for-parameter-set-not-supported}|New error code for parameter set not supported | OASIS PKCS 11 TC ]]. * Moved: Tim. Seconded: Simo. No comments. No abstentions. No objections. Motion approved. * I move that the TC approve PKCS#11 v3.2 Committee Specification Working Draft 11 and all associated artifacts packaged together in [[https://groups.oasis-open.org/higherlogic/ws/public/document?document_id=72637&wg_id=922ef643-1e10-4d65-a5ea-018dc7d3f0a4|pkcs11-spec-v3.2-wd11.zip ]] as a Committee Specification Draft and designate the Word version of the specification as authoritative. * Moved: Tim. Seconded: Simo. No comments. No abstentions. No objections. Motion approved. * I move to approve PKCS#11 v3.2 Profiles Document Working Draft 03 and all associated artifacts packaged together in [[https://groups.oasis-open.org/higherlogic/ws/public/document?document_id=72620&wg_id=922ef643-1e10-4d65-a5ea-018dc7d3f0a4|pkcs11-profiles-v3.2-wd03.zip]] as a Committee Specification Draft and designate the Word version of the specification as authoritative * Moved: Tim. Seconded: Dieter. No comments. No abstentions. No objections. Motion approved. * I move that the TC approve submitting PKCS#11 v 3.2 Usage Guide Working Draft 01 contained in [[https://groups.oasis-open.org/higherlogic/ws/public/document?document_id=72619&wg_id=922ef643-1e10-4d65-a5ea-018dc7d3f0a4|pkcs11-ug-v3.2-wd01-clean.docx]] for 30 days public review. * Moved: Tim. Seconded: Dieter. No comments. No abstentions. No objections. Motion approved.
* Old: Email from: Robert Künnemann (shared by Darren Johnson) * Outstanding action: Valerie to add the substantive changes to 3.3 work item list.
* Logistics (wiki, markdown, etc)
* Wiki and markdown discussion. Migration of Wiki to GitHub : [[https://github.com/oasis-tcs/pkcs11/wiki/|https://github.com/oasis-tcs/pkcs11/wiki/]]
* Bob walked through how the migration and edit/update will be done.
* to do: Change Tony access to Valerie going forward.
* we could update via PRs.
* Motion to make old wiki just point to GitHub and update access to allow all co-chairs and editors to update.]
* Tim Moves. Bob seconds. No objections, abstentions or comments. Motion passed.
* What other features could we use in GitHub?
* Could we use projects for issues? You will get a way to access directly your working item. The projects don’t sit in the repo, but Tim said it is not hard to set up. Maybe leverage templates.
* Dieter: like have a Kanban board for each document? Tim suggests using milestones to generate the kanban.
* Here is what OpenSSL is doing: https://github.com/orgs/openssl/projects/20/views/13 and https://github.com/orgs/openssl/projects/20/views/11
* Can pick what the statuses are and what colors.
* Discussion of using MarkDown for our documents going forward
* Simo gave us an overview of first pass at moving the specifications to markdown with pandoc. Would we need to maintain the table numbering? Not necessarily. Creating tables require fine tuning lineups. Tim mentioned there are tools that can help with this.
* Markdown may make it simpler to make a “pull request” for a proposal for TC. Will require a learning curve for those of us used to working in Word, though with increased popularity of this type of editing, it will be useful to learn. Once the document is in markdown, can run a script to update format.
* Tim moves to make markdown authoritative from version 3.3 onward. Comments: OASIS would still need a PDF? Yes, and they would publish our markdown as well. Jonathan seconds. No objections, other comments, or abstentions. Motion approved.
* Tim & others share a big thank you for Simo for making the proof of concept
*
* None.
* Motion: That the meeting be adjourned. * Moved: Tim. Seconded: Dieter. No objections, abstentions, or comments. Meeting adjourned. * Meeting Adjourned 1:43 PM PT.