Another abandoned server code base... this is kind of an ancestor of taskrambler.
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 

383 lines
17 KiB

<?xml version="1.0" encoding="iso-8859-1"?>
<!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 http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
<title>IETF/W3C XML-DSig Working Group</title>
<link rel="stylesheet" type="text/css" href="WG.css" />
<style type="text/css">
<!--
-->
</style>
</head>
<body xml:lang="en" lang="en">
<h1><a href="http://www.ietf.org"><img
src="http://ietf.org/images/ietflogo2e.gif" alt="IETF" border="0" height="48"
width="92" /></a> <a href="http://www.w3.org/"><img
src="http://www.w3.org/Icons/WWW/w3c_home" alt="W3C" border="0" height="48"
width="72" /></a> &nbsp; XML Signature WG <small><small>[ <a
href="http://cgi.w3.org/cgi-bin/html2txt?url=http://www.w3.org/Signature/Overview.html">text</a>]</small></small></h1>
<dl>
<dt>On this page:</dt>
<dd><a href="#Mission">Mission</a> | <a href="#CurrentWork">Current
Drafts</a> | <a href="#Code">Code &amp; Toolkits</a> | <a
href="#responsibilities">The Chairs</a> | <a
href="#Meetings">Meetings&amp;Calls</a> | <a
href="#Background">Background Reading</a></dd>
<dt>Nearby:</dt>
<dd><a href="charter-20020607">Charter</a> | <a href="#email">List
Archive</a> |&nbsp;<a href="Deliverables.html">Older Drafts</a> | <a
href="Participants.html">Participants</a> | <a
href="Contributor.html">Contributor Policies</a> | <a
href="Disclosures.html">Patent Disclosures</a> | <a
href="/1999/05/XML-DSig-CFP-990521.html">Briefing Package</a> | <a
href="Activity.html">W3C Activity Statement</a></dd>
<dt>Chair(s):</dt>
<dd>Donald Eastlake 3rd &lt;<a
href="mailto:d3e3e3@gmail.com">d3e3e3@gmail.com</a>&gt;</dd>
<dd><a href="http://www.w3.org/People/Reagle/">Joseph Reagle</a> Jr.
&lt;<a href="mailto:reagle@w3.org">reagle@w3.org</a>&gt;</dd>
<dt><a id="email" name="email">Mailing Lists</a> ( <a
href="http://lists.w3.org/Archives/Public/w3c-ietf-xmldsig/1999AprJun/0001.html">Help</a>)</dt>
<dd>General Discussion: <a
href="mailto:w3c-ietf-xmldsig@w3.org">w3c-ietf-xmldsig@w3.org</a></dd>
<dd>Subscribe: <a
href="mailto:w3c-ietf-xmldsig-request@w3.org">w3c-ietf-xmldsig-request@w3.org</a></dd>
<dd>&nbsp;&nbsp;&nbsp; In Subject: (un)subscribe</dd>
<dd>Archive: <a
href="http://lists.w3.org/Archives/Public/w3c-ietf-xmldsig/">http://lists.w3.org/Archives/Public/w3c-ietf-xmldsig/</a></dd>
</dl>
<h2><a id="recent" name="recent">Recent Work</a></h2>
<ul>
<li><a href="/2007/xmlsec/">2007/2008 XML Security Specifications Maintenance WG</a></li>
<li><a href="/2008/xmlsec/">2008/2010 XML Security Working Group</a></li>
</ul>
<h2><a id="Mission" name="Mission">Mission Statement</a></h2>
<p>The mission of this working group is to develop an XML compliant syntax
used for representing the signature of Web resources and portions of protocol
messages (anything referencable by a URI) and procedures for computing and
verifying such signatures. This is a joint Working Group of the <a
href="http://www.ietf.org">IETF</a> and <a href="http://www.w3.org">W3C</a>.
W3C is hosting the email list and WG site publicly in accordance with IETF
procedure. Please see the <a href="charter-20020607">Charter</a> for further
information on the constitution of this WG. This WG <em>does not</em> address
broader <a
href="http://www.nue.et-inf.uni-siegen.de/~geuer-pollmann/xml_security.html">XML
security</a> issues including <a
href="http://lists.w3.org/Archives/Public/xml-encryption/">XML encryption</a>
and authorization.<strong>This WG has successfully advanced all chartered
deliverables to their final state and the charter has expired; presently the
mailing list may be used to ask questions about the specifications or interop
report.</strong></p>
<p>If you want to join, or are new to the working group you should understand
how to <a href="Contributor.html">contribute</a>, how to <a
href="#responsibilities">work with the chairs</a>, when the next <a
href="#Meetings">meetings</a> is, and catch up on some <a
href="#Background">background reading</a>. Otherwise, just start
participating on the list!</p>
<p>If you are interested in a light-weight introduction to XML Signatures,
you may want to review the <a href="#primers">primer background
reading</a>.</p>
<h2><a id="CurrentWork" name="CurrentWork">Current Deliverables</a></h2>
<dl>
<dt>Signature Syntax and Processing (<a
href="http://www.w3.org/Signature/2001/04/05-xmldsig-interop.html">interop-report</a>)</dt>
<dd>REC: <a
href="http://www.w3.org/TR/xmldsig-core/">http://www.w3.org/TR/xmldsig-core/</a></dd>
<dd>Draft Standard: <a
href="http://www.ietf.org/rfc/rfc3275.txt">http://www.ietf.org/rfc/rfc3275.txt</a></dd>
<dt>Canonical XML (<a
href="2000/10/10-c14n-interop.html">Interop-report</a>)<br />
</dt>
<dd>REC: <a
href="http://www.w3.org/TR/xml-c14n">http://www.w3.org/TR/xml-c14n</a></dd>
<dd>Informational: <a
href="http://www.ietf.org/rfc/rfc3076.txt">RFC3076</a></dd>
<dt>Exclusive Canonical XML (<a
href="2002/02/01-exc-c14n-interop.html">interop-report</a>)</dt>
<dd>REC: <a
href="http://www.w3.org/TR/xml-exc-c14n">http://www.w3.org/TR/xml-exc-c14n</a></dd>
<dd>Informational: <a href="http://www.ietf.org/rfc/rfc3741.txt">http://www.ietf.org/rfc/rfc3741.txt</a></dd>
<dt>XPath Filter (<a
href="http://www.w3.org/Signature/2002/05/xmldsig-filter2-interop">interop-report</a>)</dt>
<dd>REC: <a
href="http://www.w3.org/TR/xmldsig-filter2/">http://www.w3.org/TR/xmldsig-filter2/</a></dd>
<dt>Additional XML Security URIs</dt>
<dd>Informational: <a
href="http://www.ietf.org/rfc/rfc4051.txt">http://www.ietf.org/rfc/rfc4051.txt</a></dd>
<dt>XML Signature Requirements</dt>
<dd>Note: <a
href="http://www.w3.org/TR/xmldsig-requirements">http://www.w3.org/TR/xmldsig-requirements</a></dd>
<dd>Informational: <a
href="http://www.ietf.org/rfc/rfc2807.txt">http://www.ietf.org/rfc/rfc2807.txt</a></dd>
</dl>
<p>See <a id="Past" href="Deliverables.html" name="Past">previous
deliverables</a> for previous drafts and their interoperability matrices and
histories.</p>
<h2><a id="Code" name="Code">Publicly Available Code, Tool Kits &amp;
SDKs</a></h2>
<p>The software below is not normative. It is provided for illustration
only.</p>
<p>Source</p>
<ul>
<li><a href="http://xml.apache.org/security/index.html">Apache XML
Security</a> for Java, Christian Geuer-Pollmann (BSD License)</li>
<li><a href="http://gapxse.sourceforge.net">GapXse</a> for Java, University
of Pisa (LGPL License)</li>
<li><a href="http://dev.w3.org/cvsweb/2001/xmlsec-python/">Canonical XML
and Exclusive Canonical XML for Python</a>, Joseph Reagle and Richard
Salz (W3C and Python Licenses)</li>
<li><a href="http://tjmather.com/xml-canonical/">Canonical XML for
Perl</a>, T.J. Mather (Perl License)</li>
<li><a href="http://www.aleksey.com/xmlsec/">XML Security Library</a>,
Aleksey Sanin (MIT License)</li>
</ul>
<br />
<p>Toolkits, SDKs, and Products</p>
<ul>
<li><del>Baltimore</del></li>
<li><a href="http://www.datapower.com/products/xs40.html">DataPower</a></li>
<li><a
href="http://www.entrust.com/developer/java/index.htm">Entrust/Toolkit&trade;
; for Java&trade;</a></li>
<li><a
href="http://jcewww.iaik.tu-graz.ac.at/products/ixsil/index.php">IAIK XML
Signature Library (IXSIL)</a></li>
<li><a href="http://www.alphaworks.ibm.com/tech/xmlsecuritysuite">IBM XML
Security Suite</a></li>
<li><a href="http://www.infomosaic.net/">Infomosaic</a></li>
<li><a href="http://msdn.microsoft.com/netframework/">Microsoft</a></li>
<li><a href="http://www.sw.nec.co.jp/soft/xml_s/appform_e.html">NEC
XMLDSIG</a></li>
<li><a href="http://www.phaos.com/e_security/prod_xml.html">Phaos</a></li>
<li><a href="http://www.ponton-consulting.de/english/index_en.html">Ponton
Consulting</a></li>
<li><a href="http://www.rsasecurity.com/products/bsafe/certj.html">RSA
BSAFE Cert-J</a></li>
<li><a href="http://www.setcce.org/xsign.htm">SETCCE</a></li>
<li><a
href="http://www.ubisecure.com/index.php?page=ubisignature">Ubisecure</a></li>
<li><a
href="http://www.xmltrustcenter.org/xmlsig/developer/verisign/index.htm">Verisign</a><br
/>
</li>
<li><a href="http://www.wedgetail.com/xmlsecurity/">Wedgetail</a></li>
</ul>
<br />
<p>Test Vectors</p>
<ul>
<li><a href="2001/04/05-xmldsig-interop.html">XML Signature Syntax and
Processing Interop Matrix</a> (small set to demonstrate feature
implementation and interoperation.)</li>
<li><a
href="http://cvs.apache.org/viewcvs.cgi/xml-security/data/">Christian
Geuer-Pollmann's collection of test vectors</a> including those of <a
href="http://cvs.apache.org/viewcvs.cgi/xml-security/data/ie/baltimore/merlin-examples/">Merlin
Hughes (Baltimore)</a> and <a
href="http://cvs.apache.org/viewcvs.cgi/xml-security/data/at/iaik/">Gregor
Karlinger (IAIK)</a>.</li>
<li><a
href="http://lists.w3.org/Archives/Public/w3c-ietf-xmldsig/2002AprJun/0006.html">Infomosaic's
SecureXMLVerify() web service</a>. (<a
href="http://www.infomosaic.net/XMLSign/SecureXMLVerifyWS.htm">web
form</a>)</li>
</ul>
<p></p>
<p>Miscellaneous</p>
<ul>
<li><a href="http://www.oasis-open.org/committees/relax-ng/">RelaxNG</a> <a
href="2002/07/xmldsig-core-schema.rng">Schema for xmldsig-core</a></li>
</ul>
<h2><a id="Meetings" name="Meetings">Meetings</a> and Teleconferences</h2>
<p>Minutes are produced in accordance with <a
href="http://www.ietf.org/instructions/minutes.html">IETF Minute
Policy.</a></p>
<h3>Face-to-Face Announce and Minutes</h3>
<ul>
<li>IETF (48), Pittsburgh, USA. <a
href="Minutes/000803-Pittsburgh/">Minutes</a> &amp; <a
href="http://lists.w3.org/Archives/Public/w3c-ietf-xmldsig/2000JulSep/0157.html">Agenda.</a></li>
<li>Victoria CA. Thursday, April 20, 2000. <a
href="Minutes/000420-Victoria/Overview.html">Minutes,</a> <a
href="http://www.pureedge.com/about/dsig/index.htm">Logistics</a> and <a
href="http://lists.w3.org/Archives/Public/w3c-ietf-xmldsig/2000AprJun/0027.html">Agenda</a>.</li>
<li>IETF (47), Adelaide, Australia.&nbsp; Monday, March 27, 2000. <a
href="Minutes/000327-Adelaide/Overview.html">Minutes</a> &amp; <a
href="http://lists.w3.org/Archives/Public/w3c-ietf-xmldsig/2000JanMar/0228.html">Agenda</a>.</li>
<li>San Jose, CA. Friday, January 21, 2000. <a
href="Minutes/SanJose/Overview.html">Minutes</a> &amp; <a
href="http://lists.w3.org/Archives/Public/w3c-ietf-xmldsig/2000JanMar/0051.html">Agenda</a>.</li>
<li>IETF (46), Washington, DC. November 7-12 1999. <a
href="Minutes/DC-Minutes/Overview.html">Minutes</a> &amp; <a
href="Minutes/DC-Agenda.html">Agenda</a>.</li>
<li><a href="Minutes/Irvine-Logistics.html">UCI, Irvine</a>. August 30-31,
1999. <a href="Minutes/Irvine-Minutes.html">Minutes</a> &amp; <a
href="Minutes/Irvine-Agenda.html">Agenda</a></li>
<li>IETF (45), Oslo, July 1999: <a
href="Minutes/990713-oslo.html">Minutes</a> &amp; <a
href="Minutes/Oslo-Agenda.html">Agenda</a></li>
</ul>
<h3>Telecon Minutes</h3>
<p>Optional teleconferences happen every other week (or week depending on
schedule) on Thursdays at 12ET. See the <a
href="http://lists.w3.org/Archives/Public/w3c-ietf-xmldsig/">archive</a> for
the latest teleconference announcement. Minutes are posted to the list; WG
members are obligated to review, correct, or counter any proposals or
consensus achieved on the call on the list.</p>
<ul>
<li><a href="Minutes/010730-tele.html">010730-tele |</a> <a
href="Minutes/000907-tele.html">000907-tele</a> | <a
href="Minutes/00817-tele.html">000817-tele</a>| <a
href="Minutes/000302-tele.html">000302-tele</a></li>
<li><a href="Minutes/000217-tele.html">000217-tele</a> | <a
href="Minutes/000203-tele.html">000203-tele</a> | <a
href="Minutes/000106-tele.html">000106-tele</a> | <a
href="Minutes/991216-tele.html">991216-tele</a></li>
<li><a href="Minutes/991209-tele.html">991209-tele</a> | <a
href="Minutes/991202-tele.html">991202-tele</a> | <a
href="Minutes/991118-tele.html">991118-tele</a> | <a
href="http://lists.w3.org/Archives/Public/w3c-ietf-xmldsig/1999OctDec/0244.html">991104-tele</a></li>
<li><a href="Minutes/991028-tele.html">991028-tele</a> | <a
href="Minutes/991021a-tele.html">991021-tele</a> | <a
href="Minutes/991014-tele.html">991014-tele</a> | <a
href="Minutes/991007-tele.html">991007-tele</a></li>
<li><a href="Minutes/990930-tele.html">990930-tele</a> | <a
href="Minutes/990923-tele.html">990923-tele</a> | <a
href="Minutes/990909-tele.html">990909-tele</a> | <a
href="Minutes/990820-tele.html">990820-tele</a></li>
<li><a
href="http://lists.w3.org/Archives/Public/w3c-ietf-xmldsig/1999JulSep/0145.html">990805-tele</a></li>
<li><a href="Minutes/990722-tele.html">990722-tele</a></li>
</ul>
<h2>Chair <a id="responsibilities"
name="responsibilities">Responsibilities</a></h2>
<p>Any correspondence to either Chair in that capacity should include both
email addresses in the distribution. Any technical question, proposal, or
discussion must be distributed to the list. An email to a Chair that does not
include the list in the distribution may be considered private correspondence
and might not be added to the agenda for WG consideration; we need public
records of proposals, consideration, and re-consideration as we move forward
in achieving a group consensus.</p>
<p>Presently, the chair responsibilities are divided as shown below. As
already stated, requests on these topics should be directed to the specified
owner with the other chair or the WG list cc'd as appropriate.</p>
<p><a id="reagle" href="http://www.w3.org/People/Reagle/"
name="reagle">Joseph Reagle</a></p>
<ol>
<li>Manage Web site and smart-list.</li>
<li>Facilitate WG consensus on <a
href="http://www.w3.org/TR/xmldsig-requirements">XML Signature
Requirements</a> document.</li>
</ol>
<p><a id="eastlake" name="eastlake">Don Eastlake</a></p>
<ol>
<li>Moderate mailing list discussion and teleconferences.</li>
<li>Facilitate WG consensus XML Signature specification.</li>
</ol>
<h2><a id="Background" name="Background">Background</a></h2>
<h3><a id="primers" name="primers">Primers and Guides</a></h3>
<ul>
<li><a href="http://www.xml.com/pub/a/2001/08/08/xmldsig.html">An
Introduction to XML Digital Signatures</a>.</li>
<li><a
href="http://www-106.ibm.com/developerworks/xml/library/s-xmlsec.html/index.html">An
Introduction to XML Encryption and XML Signature</a></li>
<li><a
href="http://msdn.microsoft.com/webservices/understanding/xmlfundamentals/default.aspx?pull=/library/en-us/dnwebsrv/html/underxmldigsig.asp">Understanding
XML Digital Signature</a></li>
</ul>
<h3><a id="required" name="required">Required Technical Reading</a></h3>
<ul>
<li><a href="ftp://ftp.isi.edu/in-notes/rfc1958.txt">Architectural
Principles of the Internet</a> (RFC1958)</li>
<li><a href="http://www.w3.org/DesignIssues/Architecture.html">Web
Architecture from 50,000 feet.</a></li>
</ul>
<ul>
<li><a href="http://www.w3.org/TR/REC-xml">Extensible Markup Language (XML)
1.0 Specification</a>, Recommendation</li>
<li><a href="/TR/REC-xml-names/">Namespaces in XML</a>, Recommendation</li>
<li><a href="http://www.w3.org/TR/xmlschema-1/">XML Schema</a>, Working
Draft</li>
<li><a id="xpath" href="http://www.w3.org/TR/xpath" name="xpath">XML Path
Language (XPath) Version 1.0</a>, Recommendation</li>
</ul>
<h3><a id="optional" name="optional">Optional Technical Reading</a></h3>
<ul>
<li><a href="http://www.w3.org/DSig/signed-XML99/Overview.html">The W3C
Signed XML Workshop Report and Summary</a></li>
<li><a href="/TR/WD-xptr">XML Pointer language (XPointer)</a></li>
<li><a href="http://www.w3.org/TR/xml-infoset/">XML Information Set</a></li>
<li><a href="ftp://ftp.isi.edu/in-notes/rfc1847.txt">RFC1847. S/MIME</a>
(CMS)</li>
</ul>
<h3><a id="process" name="process">Process Reading</a></h3>
<ul>
<li>IETF: <a href="http://www.ietf.org/rfc/rfc2026.txt">Internet Standards
Process -- Revision 3</a> (<a
href="http://asg.web.cmu.edu/rfc/rfc2026.html">html</a>) and <a
href="http://www.ietf.org/rfc/rfc2418.txt">Working Group Guidelines and
Procedures</a>.</li>
<li>W3C: <a href="http://www.w3.org/Consortium/Process/">Process
Document</a> and <a
href="http://www.w3.org/Guide/Overview.html">Guidebook for Working Group
Chairs</a></li>
<li>Reagle: <a
href="http://www.w3.org/People/Reagle/work-style.html">workstyle</a>.</li>
</ul>
<hr />
<address>
Donald Eastlake 3rd &lt; <a
href="mailto:d3e3e3@gmail.com">d3e3e3@gmail.com</a>&gt;<br />
Joseph Reagle &lt;<a href="mailto:reagle@w3.org">reagle@w3.org</a>&gt;
</address>
<p>Last revised by $Author: roessler $ $Date: 2008/06/02 11:54:23 $</p>
</body>
</html>