-
Notifications
You must be signed in to change notification settings - Fork 18
Meetingminutes Minutes14042021
Bob Relyea edited this page Mar 5, 2025
·
1 revision
- Roll call (Tony) - quorum achieved.
- Tony taking minutes.
- Attendance noted in KAVI
- Agenda
- Roll call
- Review / approval of the agenda
- Approve Minutes (March 31, 2021)
- PKCS#11 V3.1
- Wiki & Actions Items Review (Closing off v3.1)
- Line by line review
- HSS discussion
- Strength Summary
- PKCS#11 Profile Test Case preconditions
- Continuation of item raised in March 17 Meeting
- Wiki & Actions Items Review (Closing off v3.1)
- New Business
- Next meeting
- Call for late arrivals
- Adjourn
- Greg S moved, Hamish C, Dieter B seconded. No objections, comments or abstentions. Agenda approved.
- Minutes posted for March 31, 2020
- Daniel M moved, Jonathan S seconded. No objections, comments or abstentions. Minutes approved.
- Proposal 1 - BobR to review profiles, Tim H to review header file
- Dieter noted WD04 was bring updated
- Daniel noted some changes were needed regarding IKE proposal - BobR clarified that this was key size range and needed some updates in the header file.
- Hamish to check AI4
- Further checking to be deferred until after wd04 has been published
- Daniel and Tim discussed this and agreed that perhaps there were some assumptions made that the profiles were covering more content (inc preconditions) than was specified. This was clarified.
- Tony C noted that we would need an interop/plugfest to test out the profiles & test cases
- Michelle highlighted content that still needed a discussion
- Tim stated that he simply needed a means to query information without having to parse and dissect the entire payload
- Michelle, BobR & Daniel discussed single attributes vs an attribute blob
- Agreement - For key gen we will reference identifiers in existing publications
- Remaining items are:
- Do we specify which key we are using or how many are left
- If we are focussing on how many left, how is this done?
- Do we specify which key we are using or how many are left
- Agreement - We will need an attribute that when called, returns a CK-ULong that is "at least" the number of keys remaining for for usage.
- Michelle to update proposal for review.
- Agreed - Keys remaining should be returned from the private key (not the public key)
- For public key, we just need strength identifier
- Further discussion including key strength to be handled via email so Michelle can finalise the proposal for next week.
- None
- Next meeting will be April 28, 2021.
- 1 noted
- Greg S moved. Daniel M seconded. No objections, comments or abstentions. Meeting adjourned.