*HEPKI-TAG Conference Call*
July 12, 2006

*Attendees*
Jim Jokl (chair) - Virginia
Eric Norman - Wisconsin
Scott Rea - Dartmouth
David Wasley - independent
Nathan Faut - KPMG
Neal McBurnett - Internet2
John Krienke - Internet2
Ben Chinowsky (scribe) - Internet2

*Action Items*(new)
[AI] Jim will revise the CA requirements doc per the discussion on the July 12 call.
[AI] Jim will review the action items and send Ben a list of changes and deletions.

(from previous calls)
[AI] Eric will experiment with delivery and trust of root and intermediate certs via the web in Mozilla-family browsers.
[AI] Scott will send out a pointer to the draft TAGPMA CA audit requirements.
[AI] Jim will incorporate Scott's digsig-tools information into the HEPKI-TAG web site.
[AI] All will ask their contacts what material their schools would find most useful in a PKI implementers workshop.
[AI] David will follow up on SAFE's open-source signing work.
[AI] All will send URLs for CA software (open-source or not) to TAG.
[AI] Eric will let TAG know when Ron DiNapoli's work on Aladdin eTokens on Macintosh is available for the group to look at.
[AI] All will look at http://www.gridpma.org for materials for the CA Audit project to point to or extract from.
[AI] Bob will send out pointers on UW's experience with the Federal Credential Assessment Framework (CAF).
[AI] All who can test the Eudora S/MIME plugin, or find others to do so, will contact Jim.
[AI] Jim will expand the signing-tools matrix with columns on APIs and scripting tools; multiple signatures (parallel vs. stacked); and whether or not the tool lets you add a trust anchor.
[AI] All who have time to investigate one or more of the signing tools at http://middleware.internet2.edu/hepki-tag/new/signing4.html will contact Jim.
[AI] Jim will continue looking at PKI Lite cert profiles for Rice's code-signing application.
[AI] Eric will call Mozilla's attention to the fact that they don't support the standards needed to recognize trust anchors on tokens, and nudge them to do something about it.
[AI] Eric will continue seeking feedback on his Top 10 lists, especially from HCISec.
[AI] Jim will get an OID for PKI Lite from MACE.
[AI] Mark will ask Jed Dobson for more information on OSG.
[AI] David will look at some of the products listed at http://middleware.internet2.edu/hepki-tag/new/signing4.html in the light of the list of questions there.
[AI] Neal will continue looking at OpenOffice, and Jim will look at eLock.
[AI] Jim will send the list more information on the Acrobat transcript-signing work at U. of Chicago.
[AI] Jim will draft a discussion of the pros and cons of hierarchical and flat campus PKIs for discussion on a future call.
[AI] All will send Jim further suggestions for TAG projects.
[AI] Jim will send mail to people who have expressed interest in various possible areas of work for TAG, and work toward finding a focus for the group.

*Discussion*
The call was devoted to reviewing the latest campus CA requirements document (http://middleware.internet2.edu/hepki-tag/new/HEPKI-CA-Req-Summary.html) and assigning priorities to the items. [AI] Jim will revise the CA requirements doc per the discussion on the July 12 call.

With respect to 2a), Eric argued that the cert needs to be exportable for backup. Jim noted that this is configurable, but the default is set to non-exportable so as to err on the side of protecting the user; here Jim is drawing on his experience with the U. of Virginia CA. The group agreed that it would be useful to discuss what other schools do in this area, and what should be considered best practice.

Once the CA requirements and priorities are finalized, Scott will be in charge of getting implementation started. Language and toolkit are still to be decided. Eric may be able to help with coding.