HEPKI-TAG Conference Call
July, 3 2002
* Jim Jokl, Virginia
* Jeff Schiller, MIT
* Bob Brentrup, Dartmouth
* Eric Norman, Wisconsin
* Bob Morgan, Washington
* Judith Boettcher, CREN
* Michelle Gildea, CREN
* Jeanette Fielden, Internet2
* Neal McBurnett, Internet2
* Steve Olshansky, Internet 2
The group finalized that there would not be a recommendation to incorporate in a personal identity certificate the U.S. Department of Education's OPEID/FICE identifier number and/or the Federal Institutional Entity Identification Number (EIN) in the Subject field of an End Entity certificate for use. It was also decided that the group would not recommend that higher education CA's should include these numbers in the Issuer field of the certificates that they sign.
Jim requested suggestions for useful S/MIME documents that need to be developed. One suggestion is creating case studies of S/MIME use at different institutions. Another idea is to collect documentation on how popular clients use S/MIME so institutions don't have to create these from scratch. Consensus was that there is a need for more generic, overview documents. There is information on the landscape of PKI available at: http://www.cren.net/crenca/cproject/wave1/index.html. [AI] 3 July 2002 (Judith) Forward introduction from a document on getting started with digital certificates to the list.
Digital Signature Eforms tools. One consideration is that these are usually active content that could change considerably after the documents are certified. Is there a way to create a binding tool or alternate way to address certification of the actual content? For example PDF files offer control over content. Is there a way of providing notification that certain elements of the document have changed since it was certified?
Volunteers were solicited to document, in a short description, what they're doing with respect to hardware tokens. A list of which items need descriptions will be sent to the list soliciting volunteers.
There is information available on CREN member discounts on several types of equipment.
1. [AI] 3 July 2002 (Judith)
forward introduction from
a document on the demonstration
sites to the list.
2. [AI] July 3, 2002 (Neal, Bob, Jim) Draft explanations of active content and potential problems for different applications (Adobe, MS Word etc).
3. [AI] July 3, 2002 (Jim) Email list for volunteers to document hardware tokens.
4. [AI] July 3, 2002 (Michelle) Forward document on various product and application costs to the list.