iTC Meeting Minutes 2023 05 04 - DSC-iTC/cPP GitHub Wiki

Agenda

Attendees

  • Brian Wood

  • Yi Mao

  • Jerry Myers

  • Jim Donndelinger

  • Stephan Mueller

  • Bob Clemons

  • Kunyan Liu

  • Shawn Geddis

Record of Decisions

  • None

Action Items

  • Assigned tasks will be reviewed and comments added

Minutes

The call started with a review of the pull requests that had been submitted. These had been approved and were agreed to merge on the call. Two required conflict resolutions and Brian would handle these after the call to complete the merges.

The call then moved on to a review of the current list of issues for the v1.1 project. These were discussed and assigned to people on the call for further commenting and review.

A few main points from the discussions:

  • The CCDB Crypto Working Group will release their updated SFRs for review likely within a month and Jim said he was recommending this be one of the groups to review the docs. We agreed and will look to see what the changes are. It wasn’t clear when the SD portion would be complete and ready, but it would be hoped to be within the timeframe for this update.

  • The CC:2022 question will need to be resolved. It was generally agreed that being compliant is necessary, but whether being compliant or fully CC:2022 wasn’t clear, and no one was quite sure of the effort needed to move between the two. Either way, given the timeframe for the release and use, it doesn’t make much sense to not look to become compliant with the CC:2022 at a minimum.

    • There was some discussion about this being a parallel track or serial. Brian pushed for serial so the cPP would be "finished" in its updates and then the new requirements could be compared, letting things progress from what is known. Others were not as sure and thought that changes should be reviewed for both. This will become more of an issue in the next few months either way, and is probably more an issue as we look to update the SD than the cPP itself.

The call ended at 1:09pm EDT.

⚠️ **GitHub.com Fallback** ⚠️