iTC Meeting Notes 2019 05 30 - biometricITC/cPP-biometrics GitHub Wiki
Agenda:
https://github.com/biometricITC/cPP-biometrics/wiki/iTC-Meeting-Agenda-2019-05-30
Call started at 10am EDT
Attendees
- Brian Wood
- Naruki Kai
- Fiona Patterson
- Shawn Geddis
Record of Decisions
- TB Issue #9 was reviewed and closed
- TB PR #6 was reviewed and closed after minor edits based on the call.
Action Items
- Brian Wood will submit an abstract to present the current status of the Biometrics Security iTC at the ICCC 2019
- Brian will send out a reminder about the public review ballot today (voting closes on Monday, June 3)
- Brian will propose updated text for issue #143 to remove the reference to security sensitive services
- Brian will propose updates to the Toolbox Overview for issue TB #4 and update the public review document to include this as part of the review
Minutes
The call started with a quick review of the task list (and a note that the public review needs to be added to the list).
The next topic was a quick review of the voting status as of the time of the call. The current totals are 11 Yes, 1 Abstention, 1 No and a second No from someone related to the group but not on the mailing list.
Naruki provided a quick update on the scheme discussions which are still ongoing. No explicit resolution has been provided at this point and it isn't clear how quickly one will come.
Next the group discussed officially changing the short name of the iTC from BS-iTC to BIO-iTC. It was agreed to stick to BIO-iTC since that was more common to other iTC groups (as opposed to bioiTC). The group agreed to this and would move forward with this as the official short name.
Brian then brought up the topic of submitting an abstract and proposal to the ICCC 2019 review committee to present the current status (at the time) of the iTC. It was felt that Brian should make the presentation as the chair of the iTC.
Open issues were then discussed.
The first issue was #143. The group agreed to the change though Shawn pointed out that the security sensitive services can mean many things. Brian proposed to rewrite the sentence to instead point out the the SD is assuming Use Case 1 and then leave the security sensitive services mention there instead. This was agreed to and will be reviewed by the group once the change has been made.
The next issue was TB #4. The group discussed the number of acceptable subjects for testing, and discussed the comment by Naruki that the lab could add more subjects as part of their AVA_VAN testing. Fiona thought that it would be a good topic to get comments on, so Brian proposed updating the Toolbox Overview to list the number of subjects and then to add this to the documents under public review with an explicit note to consider this question.
The issue TB #7 was then discussed. It was generally agreed that the print/scan/print was probably not a great test (though Fiona pointed out that there are a lot of attacks doing this). We will continue discussing over the next calls while Naruki looks at how to propose an update related to this testing method.
The last topic of discussion focused on the changes to the documents needed for the public review period. This covered all the PRs in the agenda. The first three (1661, 162, 163) are all changing "cPP Module" to "PP-Module" or related changes. There was a question about removing "collaborative" as well, but it was felt this wasn't critical after some discussion and will be left (it could be removed if there are comments on it being included).
The group discussed whether the PP-Module vs PP should be thought about again, in part because of the comments from Nils and AVA_VAN. One thought that was brought up by Fiona was the creation of a small Base-PP that the PP-Module could be attached to. Basically this small Base-PP would have some basic SFR which could provide enough for it to be a PP, and than a PP-Config would be created to attach the PP-Module to it. A key point to this would be that the new Base-PP would not have AVA_VAN, and since the PP-Module accepts the Base-PP SARs, it would answer the questions from Nils while also not needing to maintain 2 full documents. The group will look into this to see if it may be a feasible answer to this question.
PR 165 will be updated as part of Issue 143.
PS 167 was quickly discussed and agreed to be approved for merge after the call.
PR 164 was then discussed as the major document that needs to be reviewed and approved in preparation of the public review. The document will be updated according to the issue TB #4 and then it was agreed to be approved for release.
Brian will continue to collect the votes on the ballot measure (shared with Naruki and Nils directly) to tally the results. Brian will send this out next week after sharing the proposed voting email.
The next call will be in 2 weeks, according to the normal schedule. The meeting software may be changed for that call.
The call ended at 11:10am EDT.