<?xml version="1.0" encoding="windows-1252"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta name="generator" content="HTML Tidy, see www.w3.org" />
<meta http-equiv="Content-Type"
content="text/html; charset=windows-1252" />
<title>XML Key Management Charter</title>
<link href="http://www.w3.org/StyleSheets/base.css"
rel="stylesheet" type="text/css" />
<style type="text/css">
  body { 
    margin-left: 10%; 
    margin-right: 10%; 
    font-family: sans-serif
  }
  h1,h2,h3,h4,h5,h6,ul,div {font-family: sans-serif}
  p {font-family: sans-serif}
  h1 { margin-left: -8% }
  h2 { margin-left: -4% }
  h2 { color: #006699 }
  h3 { color: black }
  h4 { color:#006699 }
  pre { color: green; font-weight: bold }
  em {color:blue; background: yellow}
  strong { text-transform: uppercase; font-weight: bold }
  code { font-family: monospace }
  u { color: rgb(255,0,0) }
  ins { color: red }
  b { color:#006699 }
  td { background: #CCFFFF }
  th { background: #A0A0A4 }
  caption { text-decoration: underline; margin-top: 1em }
  p.splash { color: #006699 }
  p.banner { margin-left: -4% }
  blockquote { color: #003366; font-style: italic }
  pre { font-family: monospace }
  .question {font-style: italic;}
  div.disclaimer {margin-left: -8%}
  div.group {margin-left: 4%}
  div.color {
     background: rgb(255,255,204);
     padding: .5em;
     border: none;
     margin-left:0.5%;
     width:100%
  }
  div.small {
     font-size:small;
     margin-left: 10%}
</style>

<style type="text/css">
 body {
  background-color: #ffffff;
 }
 h3.c6 {font-size: 80%}
 p.c5 {font-weight: bold}
 span.c4 {font-family: Courier}
 span.c3 {FONT-FAMILY: 'Courier New'}
 span.c2 {background-color: #FFFF00}
 p.c1 {font-size: 80%}
</style>
</head>
<body xml:lang="en" lang="en">
<h1><a href="http://www.w3.org/"><img
src="http://www.w3.org/w3c_home.gif" alt="W3C" border="0"
height="48" width="72" /></a> XML Key Management Working Group
Charter</h1>

<dl>
<dt>Chair(s):</dt>

<dd>Stephen Farrell, Baltimore</dd>

<dd>Shivaram Mysore, Sun</dd>

<dt>W3C Technology and Society Domain Leader</dt>

<dd>Daniel Weitzner &lt;<a
href="mailto:djw@w3.org">djw@w3.org</a>&gt;</dd>
</dl>

<div class="color">
<p>Status: This is a proposed W3C XML Key Management Charter being
submitted for W3C AC consideration.</p>
</div>

<h1>Introduction</h1>

<p>The XML Key Management Specification (<a
href="http://www.w3.org/TR/xkms/">XKMS 1.0</a>), which was
submitted as a W3C Note, builds upon elements defined in the <a
href="http://www.w3.org/Signature/">XML Signature</a> specification
and anticipates the use of the <a
href="http://www.w3.org/Encryption/2001/">XML Encryption</a>
specification to satisfy these requirements. The proposed work will
result in an XML Key Management Recommendation on the basis of the
XKMS submission. This proposal explains the need for such an
activity from market and technical perspectives, identifies a
number of interested companies and recommends that a W3C working
group begin in December 2001.</p>

<hr />
<h2>Table of Contents</h2>

<ul>
<li><a href="#_Mission">Mission Statement</a></li>

<li><a href="#_Scope">Scope</a> 

<ul>
<li>Requirements</li>

<li>Constraints</li>

<li>Demonstration Applications</li>
</ul>
</li>

<li><a href="#_Deliverables">Deliverables</a></li>

<li><a href="#_Duration">Duration and Milestones</a></li>

<li><a href="#_Confidentiality">Confidentiality</a></li>

<li><a href="#_Coordination">Coordination with Other
Groups</a></li>

<li><a href="#_Communication">Communication Mechanisms</a> 

<ul>
<li>Group Home Page</li>

<li>Mailing List</li>

<li>Teleconferences</li>

<li>Face to Face Meetings</li>

<li>Communications with the Public</li>
</ul>
</li>

<li><a href="#_IPR">IPR Disclosure</a></li>

<li><a href="#_Participants">Participants</a> 

<ul>
<li><a href="#_Team">Team</a></li>

<li><a href="#_Member">Member</a></li>

<li><a href="#_Individual">Individual</a></li>
</ul>
</li>
</ul>

<hr />
<h2><a id="_Mission" name="_Mission">Mission Statement</a></h2>

<p>The mission of this working group is to develop a specification
of XML application/protocol that allows a simple client to obtain
key information (values, certificates, management or trust data)
from a web service. This specification will be based on the XML Key
Management Specification (<a
href="http://www.w3.org/TR/xkms/">XKMS</a>) which is comprised of
two parts -- the XML Key Information Service Specification (X-KISS)
and the XML Key Registration Service Specification (X-KRSS).</p>

<p class="MsoNormal">X-KISS defines a protocol for a <i>Trust
service</i> that resolves public key information contained in <a
href="http://www.w3.org/TR/xmldsig-core/">XML Signature</a>
elements. The X-KISS protocol allows a client of such a service to
delegate part or all of the tasks required to process <span
class="c3">&lt;ds:KeyInfo&gt;</span> elements. A key objective of
the protocol design is to minimize the complexity of application
implementations by allowing them to become clients and thereby to
be shielded from the complexity and syntax of the underlying PKI
used to establish trust relationships. The underlying PKI may be
based upon a different specification such as <a
href="http://www.ietf.org/html.charters/pkix-charter.html">X.509/PKIX</a>,
<a
href="http://www.ietf.org/html.charters/spki-charter.html">SPKI</a>
or <a
href="http://www.ietf.org/html.charters/openpgp-charter.html">PGP</a>.</p>

<p class="MsoNormal">X-KRSS defines a protocol for a web service
that accepts registration of public key information. Once
registered, the public key may be used in conjunction with other
web services including X-KISS.</p>

<hr />
<h2><a id="_Scope" name="_Scope">Scope</a></h2>

<p>The core scope of this Working Group will be in specifying the
necessary protocol elements and Trust Service behavior for the XML
Key Management Specification.</p>

<p>The Working Group (WG) will:</p>

<ol>
<li>Refine, revise and amend the XKMS specification to: 

<ul>
<li>Distill the XKMS submission's requirements (both those stated
and those implicitly addressed by its functionality) into a
requirements document.</li>

<li>Correct errors and&nbsp;remove ambiguity.</li>

<li>Align with standards track proposals.</li>

<li>Apply lessons learned from implementation and interoperability
testing.</li>

<li>Verify that desired behavior is achieved.</li>
</ul>
</li>

<li>Optionally produce non-normative document(s) that set out best
practices for applying XKMS to applications that may include: 

<ul>
<li>Chained XKMS Services (including the n-corners model).</li>

<li>Interoperation with&nbsp;existing&nbsp; X.509 and PGP based
applications.</li>
</ul>
</li>

<li>Optionally produce a document that extends XKMS to provide
support for bulk registration of keys to be embedded in hardware
devices (e.g. cable modems and smart-cards).</li>

<li>Propose a new/revised charter for approval by the AC for
subsequent work once 1 and 2 have been achieved.</li>
</ol>

<p>The priority of the group shall be to achieve 1 and 2. However
it is advantageous to consider at least one concrete example when
considering the future extensibility of a specification and
therefore the group may consider 3 at the same time as 1 provided
that this does not delay the completion of the priority items.</p>

<h4><a id="_Requirements"
name="_Requirements">Requirements</a></h4>

<p>The following additional requirements must be met by the WG;
these requirements may be augmented and extended by the
requirements document:&nbsp;</p>

<ol>
<li>The PKI Interface must be simple and build upon the <span
class="c4">&lt;ds:KeyInfo&gt;</span> element specified by XML
Signature.</li>

<li>The XML Key Management Activity must be coordinated with and
use the deliverables of the XML Protocol, XML Schema, XML Signature
and XML Encryption activities to satisfy mandatory requirements
addressed by those activities. (See <a
href="#_Coordination">Coordination</a>) 

<ol>
<li>The Working Group must also evaluate XML Query with respect to
satisfying its own query query requirements.</li>
</ol>
</li>

<li>All required, recommended, and optional features of the
specification must be implemented in at least two independent
implementations before being advanced to Proposed Recommendation.
These features, and their specification, must be able to
interoperate in a secure fashion. Security and privacy concerns
must be addressed by the specification.</li>
</ol>

<h4><a id="_Constraints" name="_Constraints">Constraints</a></h4>

<p>The working group will not address the following issues:</p>

<ol>
<li>Design of new cryptographic algorithms.</li>

<li>Issues of non-repudiation, including but not limited to
'technical non-repudiation' and 'contractual non-repudiation'.</li>

<li>Sources of trusted time.</li>

<li>Models and data structures for establishing inter-domain trust,
including but not limited to 'cross-certification'.</li>

<li>Expression of existing PKI data structures in XML.</li>

<li>Specification of inter-domain trust semantics.</li>

<li>Authorization and Authorization Assertions.</li>

<li>Attribute Certificates.</li>

<li>Knowledge representation syntax.</li>
</ol>

<hr />
<h2><a id="_Deliverables"
name="_Deliverables">Deliverables</a></h2>

<p>This working group will deliver the following:</p>

<ol>
<li>A W3C Working Draft that captures the requirements&nbsp;</li>

<li>One or more W3C Recommendation(s) that specify the XML Key
Management syntax and protocol</li>

<li>An optional W3C Recommendation that defines a protocol, based
on the XML Key Management Recommendation, for bulk
registrations.</li>

<li>An optional W3C Note describing best practices for configuring
XKMS applications and Trust Services to permit clients that do not
provide support for certificate based PKI to interact with existing
certificate based applications.</li>

<li>An optional W3C Note describing best practices for configuring
XKMS to support chained service applications, including the
n-corners transaction model.</li>

<li>An optional W3C Note describing architectural options for using
XKMS to support security mechanisms for other Web Services.</li>

<li>If appropriate, draft charters for further work.</li>
</ol>

<hr />
<h2><a id="_Duration" name="_Duration">Duration and
Milestones</a></h2>

<p>This Working Group is scheduled for eleven months. Currently,
its expected lifetime is from December 2001 through November
2002.</p>

<dl>
<dt class="DefinitionTerm">July 2001</dt>

<dd>XKMS Workshop</dd>

<dt class="DefinitionTerm">December 2001</dt>

<dd class="DefinitionList">Working Group face-to-face meeting
(perhaps close to IETF #52)</dd>

<dt class="DefinitionTerm">January 2001</dt>

<dd class="DefinitionList">Last Call for Requirements Document</dd>

<dt class="DefinitionTerm">March 2002</dt>

<dd class="DefinitionList">Last Call for XKMS &amp; X-Bulk
Specification</dd>

<dt class="DefinitionTerm">May 2002</dt>

<dd class="DefinitionList">Candidate Recommendation for XKMS &amp;
X-Bulk Specification</dd>

<dt class="DefinitionTerm">August 2002</dt>

<dd class="DefinitionList">Proposed Recommendation for XKMS &amp;
X-Bulk Specification</dd>

<dt>November 2002</dt>

<dd>Recommendation for XKMS &amp; X-Bulk Specification</dd>
</dl>

<p>Once established, the Working Group can decide to perform tasks
in parallel by forming subgroups. These dates are subject to
revision due to editorial needs and external scheduling issues;
updates will be negotiated with the affected working groups and
participants and recorded on the XML Key Management WG home page.
Any change in a deliverable date must be brought to the attention
of the W3C Domain leader and Director.</p>

<hr />
<h2><a id="_Confidentiality"
name="_Confidentiality">Confidentiality</a></h2>

<p>This charter, the WG web page, and the mailing list and archives
will be publicly accessible.</p>

<hr />
<h2><a id="_Coordination" name="_Coordination">Coordination with
Other Groups</a></h2>

<h3>W3C Activities</h3>

<p class="MsoNormal">XML and XML derived activities have become a
strategic technology in W3C and elsewhere.&nbsp;</p>

<p class="MsoNormal">The Working Group (WG) shall solicit comments
from the following W3C working groups on the proposed requirements
and during W3C Last Call, the <a
href="http://www.w3.org/Guide/chair-roles.html">Chair</a> will
procure reviews before the specification will be advanced
further:</p>

<dl>
<dt><a href="http://www.w3.org/XML/Group/">XML Activity</a></dt>

<dd>While no dependencies are presently identified, the XML Key
Management WG should be prepared to coordinate with the XML
Activity (Schema, Core, XML Protocol, Query WGs, etc.) as
necessary.</dd>

<dt><a href="http://www.w3.org/2000/xp/">XML Protocol</a></dt>

<dd>The XML Key Management WG shall specify a protocol binding of
XKMS based on the deliverables of the XML Protocol WG</dd>

<dt><a href="http://www.w3.org/Signature/">XML Signature</a></dt>

<dd>XML Signature is a Candidate Recommendation.</dd>

<dt><a href="http://www.w3.org/Encryption/2001/">XML
Encryption</a></dt>

<dd>XML Encryption has issued a draft requirements document.</dd>
</dl>

<p class="MsoNormal">At the current time, there are no known
dependencies on the work produced by the Working Group.</p>

<h3><a id="external" name="external">External Groups</a></h3>

<p class="MsoNormal">The XML Protocol Working Group should liaise
with at least the following groups outside W3C:</p>

<dl>
<dt class="MsoDTerm"><a
href="http://www.ietf.org/"><b>IETF</b></a></dt>

<dd class="MsoDDef">The Working Group will cooperate closely with
the IETF on the use of XML Key Management to interface to a PKIX
conformant PKI. In addition the Working Group will cooperate
closely with IETF Working Groups that may develop profiles for
making use of the XML Key Management Recommendation (e.g. S/MIME,
TLS, IPSEC, DNSSEC)</dd>

<dt><a
href="http://www.ietf.org/html.charters/sacred-charter.html"><b>IETF-SACRED</b></a></dt>

<dd>The Working group will liaise with the IETF SACRED group with
the objective of harmonizing the SACRED protocol layer with the
X-KRSS roaming operation.</dd>

<dt class="MsoDTerm"><a
href="http://www.ebxml.org/"><b>ebXML</b></a></dt>

<dd class="MsoDDef">The Working Group will liaise via
cross-participation with the Transport, Routing and Packaging
project team within ebXML (electronic business XML). ebXML is a
joint activity of UN/CEFACT (the United Nations body responsible
for UN/EDIFACT), the international EDI standard, and OASIS
(Organization for the Advancement of Structured Information
Standards).</dd>

<dt><a
href="http://www.oasis-open.org/committees/security/index.shtml"><b>
SAML</b></a></dt>

<dd>The Working Group will liaise via cross-participation with the
OASIS Security Services Technical Committee developing the Security
Assertions Markup Language Specification.</dd>

<dt><a href="http://www.wapforum.org/"><b>WAP Forum</b></a></dt>

<dd>The Working group will liaise via cross-participation with the
WAP Forum to develop a XML Key Management profile for WAP
devices.</dd>

<dt><a href="http://www.etsi.org/"><b>European Telecommunications
Standards Institute</b></a></dt>

<dd>The Working group will consider the impact of the ETSI XML
Advanced Electronic Signatures proposal.</dd>
</dl>

<hr />
<h2><a id="_Communication" name="_Communication">Communication
Mechanisms</a></h2>

<p>Working group members are expected to participate in an
electronic mailing list, periodic teleconferences and face-to-face
meetings. The WG consensus venue is the mailing list. Note, straw
polls and assessments of consensus may be taken on teleconferences
and face-to-face meetings which will then be sent to the list via
minutes. If those decision are not opposed or questioned on the
list, they naturally stand as the WG's consensus.</p>

<p>(See <a href="#_Participants">Participants</a> for information
on the roles and commitments of working group members.)</p>

<p class="c5">NOTE: The proceedings of this Working Group are
public.</p>

<h3><a id="_Group" name="_Group">Group Home Page</a></h3>

<p>In order to maintain shared context of the group and to provide
access to the proceedings of the group, the <a
href="http://www.w3.org/Guide/chair-roles.html">Chair</a> maintains
a web page at http://www.w3.org/2001/XKMS/ (tbd).</p>

<p>Active participants are expected to have ready access to this
page and be familiar with its contents.</p>

<h3><a id="_Mailing" name="_Mailing">Mailing List</a></h3>

<p>Participants must subscribe to and participate in the <a
href="mailto:(www-xkms@w3.org">(www-xkms@w3.org</a>) mailing
list.</p>

<h3><a id="_Teleconference"
name="_Teleconference">Teleconferences</a></h3>

<p>As necessary, the Chair may convene teleconferences periodically
for the purpose of quickly addressing and resolving open issues and
tracking action items and deliverables.</p>

<p>The <a href="http://www.w3.org/Guide/chair-roles.html">Chair</a>
is responsible for producing an agenda at least 24 hours in advance
of each call, posting it along with the call details to the mailing
list, and causing minutes of the call to be posted promptly after
the call.</p>

<p>A public IRC channel may be available to complement/coordinate
teleconference discussion. However, the IRC conversation is not
necessarily part of the record: it must be stated on the
teleconference as an IRC message is not necessarily a sufficient
communication to the others on the teleconference.</p>

<h3><a id="_FTF" name="_FTF">Face to Face Meetings</a></h3>

<p>The working group will have a day face to face meeting in
December 2001. Meeting notice, advance agenda, and posting of
minutes shall follow W3C timing rules.</p>

<h3>Communication with the Public</h3>

<p>This working group is public.</p>

<hr />
<h2><a id="_IPR" name="_IPR">IPR Disclosure</a></h2>

<p>W3C promotes an open working environment. Whenever possible,
technical decisions should be made unencumbered by intellectual
property right (IPR) claims. W3C's policy for intellectual property
is set out in <a
href="http://www.w3.org/Consortium/Process/#ipr">section 1.5 of the
W3C Process document</a>.</p>

<p>Members of the XML Key Management Working Group and any other
Working Group constituted within the XML Key Management Activity
are expected to disclose any intellectual property they have in
this area. Any intellectual property essential to implement
specifications produced by this Activity must be at least available
for licensing on a <a
href="http://www.w3.org/TR/2001/WD-patent-policy-20010816/#def-RF">royalty
free license</a>. At the suggestion of the Working Group, and at
the discretion of the Director of W3C, technologies may be accepted
if they are licensed on reasonable, non-discriminatory terms.</p>

<p>Members disclose patent and other IPR claims by sending email to
the publicly archived WG list and the archived patent issues list
(that is readable by W3C Members and the W3C team): <a
href="http://lists.w3.org/Archives/Member/patent-issues/">patent-issues@w3.org</a>.
Members must disclose all IPR claims to this mailing list but they
may also copy other recipients.</p>

<p>The principal authors of the XKMS submission have stated their
<a
href="http://lists.w3.org/Archives/Public/www-xkms-ws/2001Aug/0036.html">
intent</a>, upon formation of a W3C working group to standardize
XKMS, to make all Intellectual Property Rights essential to
implement XKMS available to all implementers under a <a
href="http://www.w3.org/TR/2001/WD-patent-policy-20010816/#def-RF">royalty
free license</a> [<a
href="http://www.w3.org/TR/2001/WD-patent-policy-20010816/">W3C
Patent Policy Framework</a>]. During the AC Review and subsequent
Working Group formation the authors (and their Advisory Committee
representatives) will be asked to confirm that the XKMS Submission
is a Working Group <a
href="http://www.w3.org/TR/2001/WD-patent-policy-20010816/#sec-defs-contribution">
Contribution</a> [<a
href="http://www.w3.org/TR/2001/WD-patent-policy-20010816/">W3C
Patent Policy Framework</a>] usable under a royalty free
license.</p>

<hr />
<h2><a id="_Participants"
name="_Participants">Participants</a></h2>

<p>This section describes the expectations and requirements of
Staff, Member, and Public commitment necessary for this Working
Group to be started -- and eventually succeed. The actual roles
(chair, author, editor, contributor, implementor) and definitions
are to be defined by W3C Process and to be compatible with those of
the <a href="http://www.w3.org/Signature/Contributor.html">XML
Signature Working Group Contributor Policies</a>.</p>

<p>Contributors to this working group are expected to commit to 15%
(6 hours a week). Commitments for Author and Editor positions are
25% and 35% respectively. The Chairing commitment is expected to
require 40% of a single person's time.</p>

<h4>4.4.1 <acronym title="World Wide Web Consortium">W3C</acronym>
<a id="_Team" name="_Team">Team</a> commitment</h4>

<p>The W3C Team will dedicate 20% of a single person to this
activity for WG participation and the Staff Contact role:
coordinating with other Staff Contacts of the identified WGs, and
advising the Chair and WG on W3C Process and publishing
requirements.</p>

<h4>4.4.2 W3C <a id="_Member" name="_Member">Member</a>
commitment</h4>

<p>This is a public working group and anyone may contribute to the
Working Group. However, at the outset of the Activity, the
interested W3C member organizations are expected to identify one or
more individual contributors to the Working Group and the level of
contribution at which they are willing to participate.</p>

<h4>4.4.3 Public/<a id="_Individual"
name="_Individual">Individual</a> commitment</h4>

<p>Public contributors are welcome to commit to the completion of
any action item or to the fulfillment of the roles described in the
Contributor Policies. Note, materials sent to the public list are
part of the W3C site and subject to <a
href="http://www.w3.org/Consortium/Legal/ipr-notice-20000612">W3C
policies and licenses</a>. The W3C holds the copyright of all
Working Group deliverables (e.g., specifications).</p>
</body>
</html>

