Skip to content

Meetingminutes Minutes16092015

Robert Relyea edited this page Mar 5, 2025 · 2 revisions

September 16, 2015 Meeting Minutes

Meeting commenced 8:00PM GMT

  • Roll call (Tony Cox)
  • Quorum achieved

Proposed agenda

  • v2.41 status
  • v3.0 status
  • Comment to list related to v2.41
  • NIST Guidance

Motion to approve Agenda

  • Tim Moves, Bob R Seconds, no objections, no abstentions. Agenda approved

Motion to approve meeting minutes

  • July 8th, 2015
  • August 5th, 2015
  • Tim Moves, Bob R Seconds, no objections, no abstentions. Agenda approved
  • September 2nd, 2015 - Deferred

v2.41 status

  • Bob G, Valerie & Tim have been working with OASIS staff to resolve the header files issue - this is still awaiting a meeting with OASIS for resolution.
  • Bob G plans to go back through all 5 documents with the editors to generate updated material for the errata to reduce resolution time once a decision is made.
  • This will impact some of the work that we've been working on will need to be held over until the 2.41 errata has been resolved.
  • Tim H: in KMIP - we have profiles specified in an XML encoding that are being worked through with OASIS and what this means is that the machine readable/xml components are listed as file references only within the specification text.
  • Bob G: So we'll need to look at how closely we need to follow that process and at which version we should implement it.
  • We have a range of items to cover off on in relation to V2.41 or perhaps holding off to v3.0 depending on discussions.

V3.0

  • Deferred until 2.40/2.41 approach is resolved

Comment to list related from Birgit Haas

  • Dina: Issue is that the key_type CKK_SHA_1_HMAC was introduced in v2.30. In v2.30 and 2.40 the spec text states that you can use C_CreateObject or C_GenerateKey, but it is not clear that which mechanism to use and how to handle it
  • Dina provided an overview of the comment posted to the comment list from Birgit Haas
  • Bob R provided some background - GENERIC_SECRET is what should be used
  • Need to write up an approach to resolving this including what the proposal needs to cover and which version it should be inserted into if there are changes - see action items for Bob G)
  • Tim suggested that this might just be examples showing how to perform the generation with both functions

NIST Implementation Guidance

  • Valerie asked a question about the NIST Implementation Guidance as it relates to the crypto within/outside the boundary - we need to find a way to make this work for PKCS11. Valerie has sent an email but no response yet.
  • Bob R provided some information on his recent experience.
  • Valerie noted that we do need to document some implementation guidance and should really be put in a major release.

New Business

  • None

Next meeting proposed agenda

  • We have a range of new items to consider that have arisen from the Borderless Cyber conference and how that applies to the direction of the TC
  • Need to start discussing RSA2016 and appoint a coordinator for the interop (Tony volunteered). This will need a ballot.
  • Further discussion of the NIST Implementation Guidance

Action Items

  • Bob & Valerie (with Tim): Have discussion on Header files (10062015)
  • Graham S to write up ES GCM & CCM: CKA_VALUE_LEN and C_UnwrapKey as a proposal (10062015)
  • Tim H: to update Wikipedia page for PKCS11 (27052015)
  • John L: Send an email about POSIX to David and bringing in the other interested parties: Tim H, John L, and Graham Steele. (13052015)
  • Valerie: create 3.0 suggestion document, move 2.40 suggestions over into new 3.0 suggestion document. (not started, yet) (09042014.01)
  • Bob to take responsibility to put together a 3.0 suggestion list to include mechanisms etc. (08072015)
  • Valerie: Check with her team to see if anyone will be picking up Darren's proposal from a few weeks back (10092014.01)
  • Tony: Put action items into Jira
  • John: Review comment made on list.
  • Valerie: Monitor FIPS140 implementation guidance to see the nature of requirements related to AES GCM IV generation.
 Once NIST releases implementation guidance, reopen this issue with the TC on how we would like to address this either
 in the Base Specification or the Usage Guide. (08072015)
  • Valerie: Write up ECDBH key derivation function as a proposal to be reviewed in the August meeting (08072015)
  • Bob R: Write up a proposal relating to the function table to be reviewed in the August meeting (08072015)
  • Bob G: Write up an approach to the comment raised by Brigit Haas and bring that forward at our next meeting (16092015)

Call for late arrivals

  • One new attendees - marked off

Motion to Adjourned

  • Tim Moves, Jim seconds, no abstentions, no objections. Motion approved

Meeting Adjourned at 8:39PM GMT

Clone this wiki locally