w3.org

IETF/W3C XML-DSig Working Group

️Tue Aug 06 2002

XML Signature WG [ text]

On this page:

Nearby:

Chair(s):

Donald Eastlake 3rd <d3e3e3@gmail.com>

Joseph Reagle Jr. <reagle@w3.org>

Mailing Lists ( Help)

General Discussion: w3c-ietf-xmldsig@w3.org

Subscribe: w3c-ietf-xmldsig-request@w3.org

In Subject: (un)subscribe

Archive: http://lists.w3.org/Archives/Public/w3c-ietf-xmldsig/

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 IETF and W3C. W3C is hosting the email list and WG site publicly in accordance with IETF procedure. Please see the Charter for further information on the constitution of this WG. This WG does not address broader XML security issues including XML encryption and authorization.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.

If you want to join, or are new to the working group you should understand how to contribute, how to work with the chairs, when the next meetings is, and catch up on some background reading. Otherwise, just start participating on the list!

If you are interested in a light-weight introduction to XML Signatures, you may want to review the primer background reading.

Current Deliverables

Signature Syntax and Processing (interop-report)

REC: http://www.w3.org/TR/xmldsig-core/

Draft Standard: http://www.ietf.org/rfc/rfc3275.txt

Canonical XML (Interop-report)

REC: http://www.w3.org/TR/xml-c14n

Informational: RFC3076

Exclusive Canonical XML (interop-report)

REC: http://www.w3.org/TR/xml-exc-c14n

Informational: http://www.ietf.org/rfc/rfc3741.txt

XPath Filter (interop-report)

REC: http://www.w3.org/TR/xmldsig-filter2/

Additional XML Security URIs

Informational: http://www.ietf.org/rfc/rfc4051.txt

XML Signature Requirements

Note: http://www.w3.org/TR/xmldsig-requirements

Informational: http://www.ietf.org/rfc/rfc2807.txt

See previous deliverables for previous drafts and their interoperability matrices and histories.

Publicly Available Code, Tool Kits & SDKs

The software below is not normative. It is provided for illustration only.

Source

Apache XML Security for Java, Christian Geuer-Pollmann (BSD License)
GapXse for Java, University of Pisa (LGPL License)
Canonical XML and Exclusive Canonical XML for Python, Joseph Reagle and Richard Salz (W3C and Python Licenses)
Canonical XML for Perl, T.J. Mather (Perl License)
XML Security Library, Aleksey Sanin (MIT License)

Toolkits, SDKs, and Products

Test Vectors

XML Signature Syntax and Processing Interop Matrix (small set to demonstrate feature implementation and interoperation.)
Christian Geuer-Pollmann's collection of test vectors including those of Merlin Hughes (Baltimore) and Gregor Karlinger (IAIK).
Infomosaic's SecureXMLVerify() web service. (web form)

Miscellaneous

RelaxNG Schema for xmldsig-core

Meetings and Teleconferences

Minutes are produced in accordance with IETF Minute Policy.

Face-to-Face Announce and Minutes

IETF (48), Pittsburgh, USA. Minutes & Agenda.
Victoria CA. Thursday, April 20, 2000. Minutes, Logistics and Agenda.
IETF (47), Adelaide, Australia. Monday, March 27, 2000. Minutes & Agenda.
San Jose, CA. Friday, January 21, 2000. Minutes & Agenda.
IETF (46), Washington, DC. November 7-12 1999. Minutes & Agenda.
UCI, Irvine. August 30-31, 1999. Minutes & Agenda
IETF (45), Oslo, July 1999: Minutes & Agenda

Telecon Minutes

Optional teleconferences happen every other week (or week depending on schedule) on Thursdays at 12ET. See the archive 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.

010730-tele | 000907-tele | 000817-tele| 000302-tele
000217-tele | 000203-tele | 000106-tele | 991216-tele
991209-tele | 991202-tele | 991118-tele | 991104-tele
991028-tele | 991021-tele | 991014-tele | 991007-tele
990930-tele | 990923-tele | 990909-tele | 990820-tele
990805-tele
990722-tele

Chair Responsibilities

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.

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.

Joseph Reagle