W3C   XML Key Management Services WG

DRAFT 14th November 2002 XKMS Teleconference Minutes
Chairs: Stephen Farrell, Shivaram Mysore
Note Takers: Stephen Farrell

Last revised by $Author: smysore $ $Date: 2002/11/20 23:53:27 $


  1. Shivaram Mysore, Sun Microsystems
  2. Stephen Farrell, Baltimore
  3. Mike Just, Treasury Board of Canada Secretariat (TBS)
  4. Joseph Reagle, W3C
  5. Yassir Elley, Sun Microsystems
  6. Blair Dillaway, Microsoft
  7. Federick Hirsch, Nokia


  1. Phill Hallam-Baker, Verisign
  2. Ed Simon, XMLsec


Agenda is to go through the issues with the requirements document this week.

First checking actions from previous call.

Then AOB.

Last call's actions

  1. For Issue number explanation, refer to Issues List
  2. Issue #77, TLS: server auth, one ciphersuite, no client auth, ACTION Stephen Farrell to write text


  3. Issue #54, SOAP bindings clarification:ACTION Blair to send text to list


  4. Issue #57: ACTION Blair to find code & send to Phill/list


  5. Issue #98, open
  6. Issue #25, open
  7. Issue #78, ACTION Blair email re replay language resolves this


  8. Issue #79, text needed ACTION Stephen Farrell, define fixed locate message (UseKeyWith value)


  9. Issue #85, close. Add sentence that nothing is idempotent (ACTION Mike Just to add to issues list)


  10. Issue #86, ACTION Frederick to check if OCSP MUST in requirement is right


  11. Issue #90, close. part of #54
  12. Issue #89,92,96 are really editorial
  13. Issue #95, close. part of #78

Requirements Issues

Before getting into the issues list in detail: After we get next rev of requirements document first get W3C-wide last call for (need to update requirements document wrt message level security) and then ask OASIS WSS to review our requirements ACTION Joseph R. to provide requirements text.

The issues list thingys:

#72: Intent still valid, but maybe mechanism (specific justificatory text everywhere) isn't right. Split optional vs. unbounded (ACTION Frederick to change requirements); and (ACTION stephen) provide list of uses of unbounded and ask if we need justification Mike will open new issue against spec.

#73: Covered by #54 and therefore CLOSED

#74: Stays OPEN; (ACTION Mike J) to check if its done already (it may be)

#75: Since decided that that requirement 2.1.12 should be removed, but ACTION Stephen to re-raise on list esp wrt p#10 support. Meanwhile this is CLOSED (as a requirements issue)

#76: Can be CLOSED since the requirement is ok and we can wait to see what's what with the spec.

#82: Req 2.4.5 is where the change to handle general compounding is to be made.OPEN - ACTION Freederick propose text for requirements doc covering compounding


#87: Make this text a footnote to something (e.g. 2.2.X) and therefore CLOSED

ACTION Mike/Frederick New one: Remove requirement that we need support for MgmtData.

Additional Spec issues arising from call

Make sure we refer to SOAP 1.2 everywhere instead of XMLP (unless something happens in SOAP 1.2's last call.) ACTION: Mike to create new/reopen issue.


ACTION: Mike to update issues list prior to next call

ACTION: Joseph to get Mike write access to issues list [1] and Frederick for the requirements document [2]

ACTION Shivaram to update participant's list

ACTION: Newly affiliated folks to send new agreement to list (repeat introductory email)

Next Telecons