iTC Meeting Minutes 2024 08 29 - DSC-iTC/cPP GitHub Wiki

Agenda

Attendees

  • Brian Wood

  • Bob Clemens

  • Joachim Vandermissen

  • Stan Potter

  • Yi Mao

  • David Thompson

Record of Decisions

  • None

Action Items

  • None

Minutes

The call started with a review of the open pull requests.

Brian said he would skip Proposed Draft version update as this was for the final publication of this draft and the date may still change.

The next to be reviewed, #361 was new and related to the FCS_CKM_EXT.3 EAs as there weren’t any. After some review, Joachim said he would look at the KMD section and consider adding some additional text. It was agreed that this SFR should not have any test requirements.

Next the Dependency Table update was reviewed. This had several changes that needed to be made based on the errata and other inconsistencies in the text that was added. Brian will update this for review.

The call then turned to the Crypto EA pull request. There was a lot of discussion about how this should work. Bob asked why there were 6 test cases, and Joachim said it was the smallest set he found in his research. The agreement was that this should be customized for each of the SFRs based on what NIST has, with the minimum number matching NIST so NIAP would be able to agree that anyone not using ACVP had at least met the minimum expectations.

Bob provided an example of what he has written so far based on the feedback from the Crypto WG. That is more specific to each algorithm and mode, but is likely to take a long time to complete as each algorithm/mode needs to be individually defined (with cross references to the spec, tests and the expectations defined in NIST). Brian said that looked great, but was not going to provide anything for the iTC to use any time soon.

Brian stated that basically the only options were to revert back to the previous crypto requirements (at least back to the matching algorithms from the v1 document) so those EAs could be used. This would mean taking out all the new support and also losing things like support for FIPS 186-5 that are needed. The agreement is that this isn’t good for the document, so using this method is preferred at this time and if the CCDB has questions/comments the SD would be updated to accommodate them (same when the Crypto WG publishes their EAs, they will be incorporated).

Updates on the EA from Joachim will be done in the next week or so at which point Brian will try to wrap up publication for this release.

Brian stated that it is unlikely we will be fully published by the ICCC but should be past the last review before preparing for publication, so it should be acceptable given we would be looking at about 3 months from now needed to publish and the ICCC is in 2 months.

The call ended at 1:01pm EDT.

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