OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

pkcs11 message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: RE: Approved and draft minutes

Hi Valerie,

 

thank you for the minutes. They look good to me.

 

Wrt to the starter documents, I thought I had seen mails about starter documents, and actually found them back., Please see attached mails.

 

Best regards,

Dieter

 

From: pkcs11@lists.oasis-open.org <pkcs11@lists.oasis-open.org> On Behalf Of Fenwick, Valerie
Sent: Donnerstag, 11. Juli 2019 06:12
To: pkcs11@lists.oasis-open.org
Subject: [pkcs11] Approved and draft minutes

 

HI folks

 

Today we approved the June 12 minutes: https://www.oasis-open.org/apps/org/workgroup/pkcs11/download.php/65600/20190612-minutes.pdf

 

Here are the draft from today: https://wiki.oasis-open.org/pkcs11/Meetingminutes/Minutes1072019

 

Inline below.

 

Valerie

 

 

July 10, 2019 Meeting Minutes

Meeting commenced 1:00 PM PST

  • Roll call (Valerie) - quorum achieved.
  • Valerie F. taking minutes.

Attendance

  • Attendance noted in KAVI

Proposed agenda

  • Roll call
  • Review / approval of the agenda
  • Approve Minutes (June 12, 2019)
  • V3.0 Items
  • V3.1
  • Comment regarding SetPIN
  • New business
  • Next meeting
  • Call for late arrivals
  • Adjourn

Motion to approve Agenda

  • Daniel moved, Gerry seconded. No objections, comments or abstentions. Agenda approved.

Motion to approve 12 June 2019 meeting minutes

  • Gerry moved, Dieter seconded. No objections, comments or abstentions. Minutes approved.

V3.0

  • Collected public review comments into an excel spreadsheet, and public review is closed.
  • A number of comments came through from TC members on the TC private list. not sure if we are required to address or if that will force a restart of our public review. Tony is reaching out to TC Admin to see what to address.
  • Reviewed public comment list. One item has been around for awhile, and some mismatches to header files. Another brought up a potential vulnerability in CKM_AES_GCM/CCM, in general we don't address vulnerabilities outside of our specification but should review the comment.

V3.1

  • Still waiting for starter documents.

Comment: C_SetPIN with multiple PINs; authenticated CKO_DATA handling

  • Pending action from Tony.

New business

  • none

Next meeting

  • Next meeting will be 24 July 2019.

Call for late arrivals

  • none noted.

Motion to adjourn today's meeting

  • Justin moved, Gerry seconded. No objections, comments or abstentions. Meeting adjourned.

Meeting Adjourned at 1:20 PM PST

 



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: Stefan Auerbach (Chairman) CEO, Malte Pollmann CSO, Dr. Frank J. Nellissen CFO

This communication is confidential. If you are not the intended recipient, any use, interference with, disclosure or copying of this material is unauthorised and prohibited. Please inform us immediately and destroy the email.
--- Begin Message ---
Per the TC's submission request [1], please find the attached starter document for:
PKCS #11 Profiles Version 3.1
WP-abbrev: pkcs11-profiles

When the TC first votes [6] to publish this Work Product in the OASIS Library, we expect it to be published at:
https://docs.oasis-open.org/pkcs11/pkcs11-profiles/v3.1/csprd01/pkcs11-profiles-v3.1-csprd01.docx
The permanent "Latest version" URI will be:
https://docs.oasis-open.org/pkcs11/pkcs11-profiles/v3.1/pkcs11-profiles-v3.1.docx

Please let me know if anything here fails to meet your expectations.
Further revisions to this Work Product must be maintained in Working Drafts, following procedures detailed in the OASIS TC Administration How-to Guide [2].
Working Drafts should be made available by uploading the document(s) to the TC's Kavi document repository, or (provisionally/temporarily) to the TC's Github or Subversion (SVN) repository, if it has been activated for your TC [3]. TCs are encouraged to use ZIP packaging when the WD releases contain multiple files (and directories).

For each WD revision, you will need to:
1) increment the Working Draft revision (number) from 01 to 02, 03, 04 etc., as successive Working Drafts are produced; the revision number needs to be updated at the top of the document in the stage identifier (Working Draft ##) and in the document identifier within the page footer.

2) supply the relevant publication/release/upload date for each successive Working Draft instance, using the prescribed date format: DD Month YYYY; the date needs to be updated at the top of the document (just below the stage identifier, Working Draft ##) and in the page footer.

3) provide suitable text for a document Abstract, updating this summary with successive revisions to provide an accurate description of the subject matter, goals, scope, etc.

4) keep the Acknowledgments (Appendix A) and Revision History (Appendix C) up-to-date with each WD revision.

5) consult the OASIS Naming Directives document when creating new artifacts that may be part of the Work Product (e.g., image files, XML schemas), observing the rules for name characters in files and proposed directories, and for proposed URIs/namespaces [4].

6) examine the instructions for construction of XML Namespace Identifiers (namespace URIs) and Namespace Documents [5] if your specification declares one or more XML namespaces or other namespace-related identifiers for (e.g.,) link relations, named properties, functions, dialects, faults, actions, or any named message types.  All such identifiers, if HTTP-scheme, must begin with: https://docs.oasis-open.org/[tc-shortname]/ns/xxxx

When the TC votes [6] to approve a Working Draft as a Committee Draft (CSD or CND), the Chair or other designated person must submit a "Committee Specification Draft Creation and Upload Request" accessible on the TC Administration Requests Page [7].

Upon receipt of this form, the TC Administrator will QC and process the Work Product for official publication in the OASIS Library (https://docs.oasis-open.org/) as a Committee Draft, including addition of the requisite cover page metadata and other boilerplate information.

=========== References:
[1] https://tools.oasis-open.org/issues/browse/TCADMIN-3475
[2] Developing Committee Specifications and Notes
https://www.oasis-open.org/resources/tcadmin/developing-committee-specifications-and-notes
Starting a Working Draft
https://www.oasis-open.org/resources/tcadmin/starting-a-working-draft
[3] Github and SVN Version control, via Tools
https://tools.oasis-open.org/
[4] OASIS Naming Directives
http://docs.oasis-open.org/specGuidelines/ndr/namingDirectives.html
[5] OASIS Naming Directives - Namespace Identifiers and Namespace Documents
http://docs.oasis-open.org/specGuidelines/ndr/namingDirectives.html#xml-namespaces
[6] Approval of a WD as a CD (CSD or CND)
https://www.oasis-open.org/resources/tcadmin/approving-a-committee-specification-or-note-draft
https://www.oasis-open.org/policies-guidelines/tc-process#committeeDraft
[7] TC Administration Requests Page, see Committee Specification Draft Creation / Upload Request
https://www.oasis-open.org/resources/tc-admin-requests

Best wishes,
Paul
--
Paul Knight....Document Process Analyst...mobile: +1 781-883-1783
OASIS - Advancing open standards for the information society

Attachment: pkcs11-profiles-v3.1-wd01.docx
Description: pkcs11-profiles-v3.1-wd01.docx

---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that 
generates this mail.  Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php

--- End Message ---
--- Begin Message ---
Per the TC's submission request [1], please find the attached starter document for:
PKCS #11 Historical Mechanisms Version 3.1
WP-abbrev: pkcs11-hist

When the TC first votes [6] to publish this Work Product in the OASIS Library, we expect it to be published at:
https://docs.oasis-open.org/pkcs11/pkcs11-hist/v3.1/csprd01/pkcs11-hist-v3.1-csprd01.docx
The permanent "Latest version" URI will be:
https://docs.oasis-open.org/pkcs11/pkcs11-hist/v3.1/pkcs11-hist-v3.1.docx

Please let me know if anything here fails to meet your expectations.
Further revisions to this Work Product must be maintained in Working Drafts, following procedures detailed in the OASIS TC Administration How-to Guide [2].
Working Drafts should be made available by uploading the document(s) to the TC's Kavi document repository, or (provisionally/temporarily) to the TC's Github or Subversion (SVN) repository, if it has been activated for your TC [3]. TCs are encouraged to use ZIP packaging when the WD releases contain multiple files (and directories).

For each WD revision, you will need to:
1) increment the Working Draft revision (number) from 01 to 02, 03, 04 etc., as successive Working Drafts are produced; the revision number needs to be updated at the top of the document in the stage identifier (Working Draft ##) and in the document identifier within the page footer.

2) supply the relevant publication/release/upload date for each successive Working Draft instance, using the prescribed date format: DD Month YYYY; the date needs to be updated at the top of the document (just below the stage identifier, Working Draft ##) and in the page footer.

3) provide suitable text for a document Abstract, updating this summary with successive revisions to provide an accurate description of the subject matter, goals, scope, etc.

4) keep the Acknowledgments (Appendix A) and Revision History (Appendix C) up-to-date with each WD revision.

5) consult the OASIS Naming Directives document when creating new artifacts that may be part of the Work Product (e.g., image files, XML schemas), observing the rules for name characters in files and proposed directories, and for proposed URIs/namespaces [4].

6) examine the instructions for construction of XML Namespace Identifiers (namespace URIs) and Namespace Documents [5] if your specification declares one or more XML namespaces or other namespace-related identifiers for (e.g.,) link relations, named properties, functions, dialects, faults, actions, or any named message types.  All such identifiers, if HTTP-scheme, must begin with: https://docs.oasis-open.org/[tc-shortname]/ns/xxxx

When the TC votes [6] to approve a Working Draft as a Committee Draft (CSD or CND), the Chair or other designated person must submit a "Committee Specification Draft Creation and Upload Request" accessible on the TC Administration Requests Page [7].

Upon receipt of this form, the TC Administrator will QC and process the Work Product for official publication in the OASIS Library (https://docs.oasis-open.org/) as a Committee Draft, including addition of the requisite cover page metadata and other boilerplate information.

=========== References:
[1] https://tools.oasis-open.org/issues/browse/TCADMIN-3474
[2] Developing Committee Specifications and Notes
https://www.oasis-open.org/resources/tcadmin/developing-committee-specifications-and-notes
Starting a Working Draft
https://www.oasis-open.org/resources/tcadmin/starting-a-working-draft
[3] Github and SVN Version control, via Tools
https://tools.oasis-open.org/
[4] OASIS Naming Directives
http://docs.oasis-open.org/specGuidelines/ndr/namingDirectives.html
[5] OASIS Naming Directives - Namespace Identifiers and Namespace Documents
http://docs.oasis-open.org/specGuidelines/ndr/namingDirectives.html#xml-namespaces
[6] Approval of a WD as a CD (CSD or CND)
https://www.oasis-open.org/resources/tcadmin/approving-a-committee-specification-or-note-draft
https://www.oasis-open.org/policies-guidelines/tc-process#committeeDraft
[7] TC Administration Requests Page, see Committee Specification Draft Creation / Upload Request
https://www.oasis-open.org/resources/tc-admin-requests

Best wishes,
Paul
--
Paul Knight....Document Process Analyst...mobile: +1 781-883-1783
OASIS - Advancing open standards for the information society

Attachment: pkcs11-hist-v3.1-wd01.docx
Description: pkcs11-hist-v3.1-wd01.docx

---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that 
generates this mail.  Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php

--- End Message ---
--- Begin Message ---
Per the TC's submission request [1], please find the attached starter document for:
PKCS #11 Current Mechanisms Version 3.1
WP-abbrev: pkcs11-curr

When the TC first votes [6] to publish this Work Product in the OASIS Library, we expect it to be published at:
https://docs.oasis-open.org/pkcs11/pkcs11-curr/v3.1/csprd01/pkcs11-curr-v3.1-csprd01.docx
The permanent "Latest version" URI will be:
https://docs.oasis-open.org/pkcs11/pkcs11-curr/v3.1/pkcs11-curr-v3.1.docx

Please let me know if anything here fails to meet your expectations.
Further revisions to this Work Product must be maintained in Working Drafts, following procedures detailed in the OASIS TC Administration How-to Guide [2].
Working Drafts should be made available by uploading the document(s) to the TC's Kavi document repository, or (provisionally/temporarily) to the TC's Github or Subversion (SVN) repository, if it has been activated for your TC [3]. TCs are encouraged to use ZIP packaging when the WD releases contain multiple files (and directories).

For each WD revision, you will need to:
1) increment the Working Draft revision (number) from 01 to 02, 03, 04 etc., as successive Working Drafts are produced; the revision number needs to be updated at the top of the document in the stage identifier (Working Draft ##) and in the document identifier within the page footer.

2) supply the relevant publication/release/upload date for each successive Working Draft instance, using the prescribed date format: DD Month YYYY; the date needs to be updated at the top of the document (just below the stage identifier, Working Draft ##) and in the page footer.

3) provide suitable text for a document Abstract, updating this summary with successive revisions to provide an accurate description of the subject matter, goals, scope, etc.

4) keep the Acknowledgments (Appendix A) and Revision History (Appendix C) up-to-date with each WD revision.

5) consult the OASIS Naming Directives document when creating new artifacts that may be part of the Work Product (e.g., image files, XML schemas), observing the rules for name characters in files and proposed directories, and for proposed URIs/namespaces [4].

6) examine the instructions for construction of XML Namespace Identifiers (namespace URIs) and Namespace Documents [5] if your specification declares one or more XML namespaces or other namespace-related identifiers for (e.g.,) link relations, named properties, functions, dialects, faults, actions, or any named message types.  All such identifiers, if HTTP-scheme, must begin with: https://docs.oasis-open.org/[tc-shortname]/ns/xxxx

When the TC votes [6] to approve a Working Draft as a Committee Draft (CSD or CND), the Chair or other designated person must submit a "Committee Specification Draft Creation and Upload Request" accessible on the TC Administration Requests Page [7].

Upon receipt of this form, the TC Administrator will QC and process the Work Product for official publication in the OASIS Library (https://docs.oasis-open.org/) as a Committee Draft, including addition of the requisite cover page metadata and other boilerplate information.

=========== References:
[1] https://tools.oasis-open.org/issues/browse/TCADMIN-3472
[2] Developing Committee Specifications and Notes
https://www.oasis-open.org/resources/tcadmin/developing-committee-specifications-and-notes
Starting a Working Draft
https://www.oasis-open.org/resources/tcadmin/starting-a-working-draft
[3] Github and SVN Version control, via Tools
https://tools.oasis-open.org/
[4] OASIS Naming Directives
http://docs.oasis-open.org/specGuidelines/ndr/namingDirectives.html
[5] OASIS Naming Directives - Namespace Identifiers and Namespace Documents
http://docs.oasis-open.org/specGuidelines/ndr/namingDirectives.html#xml-namespaces
[6] Approval of a WD as a CD (CSD or CND)
https://www.oasis-open.org/resources/tcadmin/approving-a-committee-specification-or-note-draft
https://www.oasis-open.org/policies-guidelines/tc-process#committeeDraft
[7] TC Administration Requests Page, see Committee Specification Draft Creation / Upload Request
https://www.oasis-open.org/resources/tc-admin-requests

Best wishes,
Paul
--
Paul Knight....Document Process Analyst...mobile: +1 781-883-1783
OASIS - Advancing open standards for the information society

Attachment: pkcs11-curr-v3.1-wd01.docx
Description: pkcs11-curr-v3.1-wd01.docx

---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that 
generates this mail.  Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php

--- End Message ---
--- Begin Message ---
Per the TC's submission request [1], please find the attached starter document for:
PKCS #11 Base Specification Version 3.1
WP-abbrev: pkcs11-base

When the TC first votes [6] to publish this Work Product in the OASIS Library, we expect it to be published at:
https://docs.oasis-open.org/pkcs11/pkcs11-base/v3.1/csprd01/pkcs11-base-v3.1-csprd01.docx
The permanent "Latest version" URI will be:
https://docs.oasis-open.org/pkcs11/pkcs11-base/v3.1/pkcs11-base-v3.1.docx

Please let me know if anything here fails to meet your expectations.
Further revisions to this Work Product must be maintained in Working Drafts, following procedures detailed in the OASIS TC Administration How-to Guide [2].
Working Drafts should be made available by uploading the document(s) to the TC's Kavi document repository, or (provisionally/temporarily) to the TC's Github or Subversion (SVN) repository, if it has been activated for your TC [3]. TCs are encouraged to use ZIP packaging when the WD releases contain multiple files (and directories).

For each WD revision, you will need to:
1) increment the Working Draft revision (number) from 01 to 02, 03, 04 etc., as successive Working Drafts are produced; the revision number needs to be updated at the top of the document in the stage identifier (Working Draft ##) and in the document identifier within the page footer.

2) supply the relevant publication/release/upload date for each successive Working Draft instance, using the prescribed date format: DD Month YYYY; the date needs to be updated at the top of the document (just below the stage identifier, Working Draft ##) and in the page footer.

3) provide suitable text for a document Abstract, updating this summary with successive revisions to provide an accurate description of the subject matter, goals, scope, etc.

4) keep the Acknowledgments (Appendix A) and Revision History (Appendix C) up-to-date with each WD revision.

5) consult the OASIS Naming Directives document when creating new artifacts that may be part of the Work Product (e.g., image files, XML schemas), observing the rules for name characters in files and proposed directories, and for proposed URIs/namespaces [4].

6) examine the instructions for construction of XML Namespace Identifiers (namespace URIs) and Namespace Documents [5] if your specification declares one or more XML namespaces or other namespace-related identifiers for (e.g.,) link relations, named properties, functions, dialects, faults, actions, or any named message types.  All such identifiers, if HTTP-scheme, must begin with: https://docs.oasis-open.org/[tc-shortname]/ns/xxxx

When the TC votes [6] to approve a Working Draft as a Committee Draft (CSD or CND), the Chair or other designated person must submit a "Committee Specification Draft Creation and Upload Request" accessible on the TC Administration Requests Page [7].

Upon receipt of this form, the TC Administrator will QC and process the Work Product for official publication in the OASIS Library (https://docs.oasis-open.org/) as a Committee Draft, including addition of the requisite cover page metadata and other boilerplate information.

=========== References:
[1] https://tools.oasis-open.org/issues/browse/TCADMIN-3472
[2] Developing Committee Specifications and Notes
https://www.oasis-open.org/resources/tcadmin/developing-committee-specifications-and-notes
Starting a Working Draft
https://www.oasis-open.org/resources/tcadmin/starting-a-working-draft
[3] Github and SVN Version control, via Tools
https://tools.oasis-open.org/
[4] OASIS Naming Directives
http://docs.oasis-open.org/specGuidelines/ndr/namingDirectives.html
[5] OASIS Naming Directives - Namespace Identifiers and Namespace Documents
http://docs.oasis-open.org/specGuidelines/ndr/namingDirectives.html#xml-namespaces
[6] Approval of a WD as a CD (CSD or CND)
https://www.oasis-open.org/resources/tcadmin/approving-a-committee-specification-or-note-draft
https://www.oasis-open.org/policies-guidelines/tc-process#committeeDraft
[7] TC Administration Requests Page, see Committee Specification Draft Creation / Upload Request
https://www.oasis-open.org/resources/tc-admin-requests

Best wishes,
Paul
--
Paul Knight....Document Process Analyst...mobile: +1 781-883-1783
OASIS - Advancing open standards for the information society

Attachment: pkcs11-base-v3.1-wd01.docx
Description: pkcs11-base-v3.1-wd01.docx

---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that 
generates this mail.  Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php

--- End Message ---

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]