XML Key Management Services WG

DRAFT 23rd January 2002 XKMS Teleconference Minutes
Chairs: Stephen Farrell, Shivaram Mysore
Note Takers: Shivaram Mysore, Stephen Farrell

Participants

• Shivaram Mysore, Sun Microsystems
• Frederick Hirsch, Zolera
• Stephen Farrell, Baltimore Technologies
• Mike Just, Entrust
• Phill Hallam-Baker, Verisign
• Yassir Elley, Sun Microsystems
• Rich Salz, Zolera
• Mack Hicks, Bank Of America
• Pieter Kasselman, Baltimore
• Joseph Reagle, W3C

Regrets

• Blair Dillaway, Microsoft

Requirements Document

• Issues:
• Editorial
• • See comment from Joesph and Yassir regarding "co-ordination with other groups like SAML"; Mike/Fedrick to put links to respective charters
  • Move Privacy considerations to a seperate section
  • Template Mode -

                   Mike: Can we wrap several XKRSS requests into one XKRSS request
                   Phill: Why enumerate? Lets scrap bullet 7
                   See protocol design 3. from Joseph

  • Joseph: Requirements to address Security considerationss see 3.2.11 from Joseph email - we are doing queuries and so we should be worried about security.
  • An application needs to talk to a Locate Service so that it knows where to Register a service - Locate before Register; Mechanism of populating a database for Locates and Registration of out of Scope (see section 2.3.8)
• X509 Issues
• • If we support X509, then we have to support X509 Cert, Chain, CRL and OCSP; else, we should not support X509
  • Phill - If the Server supports X509, it should do so completely - i.e., it should not depend on the client being aware of X509
  • XKMS Service must be PKIX compliant
  • After some discussion, we felt OCSP may not be required - Mack stated: "may be XKMS is a way of moving forward by not supporting some legacy stuff - and the as the spec states you can turn off different protocols"
  • X-BULK requires PKCS 10 - see section 2.1.12
• SOAP Profiling
• • SAML uses SOAP 1.1
  • concensus agreement - we should use SOAP 1.1 and do SOAP Profiling
  • Require encoding - Yes
• SAML Issues
• Terminology
• • See email from Joseph - define and use terminology appropriately - Verification means returning True or False; Validation means Certificate or Key Validation
  • Stephen: Clarifiy Assertions w.r.t SAML and other types of Assertions
  • XKMS applications must be XML namespace aware - define it better

• - 4-corner  - defined/mentioned in requirements? 
      mack: wants xkms usable for 4-corner
      ...
      result: mack to post suggested text to list saying
      that we'll make it possible for xkms to support
      4-corners

Status Update

• XKMS Specification - Phill Baker
• Align specification with XML DSig, Encryption and SAML
• Update Locate and Validate sections
• Dealing with appending response in Registration requests

• X-BULK - Stephen Farrell (for Merlin)
• The spec has been posted on the website. Please provide feedback.

Next Step - Last Call for Requirements Document

• next revision by feb 1
• 1 week wg last call, feb 8th,
• then publish "public" version with 2 week review
• at same time: officially "publish" current xkms & xbulk drafts

Next Telecon & Face to Face details

• Next Telecon
• Date: probably last week of February or early March 2002

• Next F2F
• Date: around 23 or 24 April, 2002
• Venue: Washington DC, in conjunction with NIST working group meeting (see http://www.cs.dartmouth.edu/~pki02/)
• Time: whole day

Action Items

1. Stephen/Shivaram: Plan to get Editor's copy and 1st draft on the website
2. Stephen/Shivaram: Start generating Issues List
3. Phill: Update XKMS Spec by next telecon
4. Fedrick/Mike: Update Requirements by Feb 1st
5. Stephen/Shivaram: Plan, setup and announce next Telecon
6. Stephen/Shivaram: Plan, setup and announce next F2F
7. Stephen/Shivaram/Joseph: Get Editors copy, 1st drafts, announce last call, etc
8. Mack: Send proposal on supporting 4-corner model in XKMS to the list