W3C home > Mailing lists > Public > w3c-ietf-xmldsig@w3.org > July to September 2002

I-D ACTION:draft-ietf-xmldsig-xc14n-00.txt

From: <Internet-Drafts@ietf.org>
Date: Wed, 14 Aug 2002 07:27:55 -0400
Message-Id: <200208141127.HAA04516@ietf.org>
To: IETF-Announce: ;
Cc: w3c-ietf-xmldsig@w3.org
A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the XML Digital Signatures Working Group of the IETF.

	Title		: Exclusive XML Canonicalization, Version 1.0
	Author(s)	: J. Boyer, D. Eastlake, J. Reagle
	Filename	: draft-ietf-xmldsig-xc14n-00.txt
	Pages		: 17
	Date		: 13-Aug-02
Canonical XML [XML-C14N] specifies a standard serialization of XML
that, when applied to a subdocument, includes the subdocument's
ancestor context including all of the namespace declarations and
attributes in the 'xml:' namespace. However, some applications
require a method which, to the extent practical, excludes ancestor
context from a canonicalized subdocument. For example, one might
require a digital signature over an XML payload (subdocument) in an
XML message that will not break when that subdocument is removed from
its original message and/or inserted into a different context.  This
requirement is satisfied by Exclusive XML Canonicalization.

A URL for this Internet-Draft is:

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-xmldsig-xc14n-00.txt".

A list of Internet-Drafts directories can be found in
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
In the body type:
	"FILE /internet-drafts/draft-ietf-xmldsig-xc14n-00.txt".
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the

Received on Wednesday, 14 August 2002 07:29:15 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:10:10 UTC