< draft-ietf-xmldsig-xc14n-01.txt   draft-ietf-xmldsig-xc14n-02.txt >
INTERNET-DRAFT John Boyer INTERNET-DRAFT John Boyer
PureEdge Solutions PureEdge Solutions
Donald E. Eastlake 3rd Donald E. Eastlake 3rd
Motorola Motorola
Joseph Reagle Joseph Reagle
W3C W3C
Expires: December 2003 June 2003 Expires: June 2004 December 2003
Exclusive XML Canonicalization, Version 1.0 Exclusive XML Canonicalization, Version 1.0
--------- --- ----------------- ------- --- --------- --- ----------------- ------- ---
<draft-ietf-xmldsig-xc14n-01.txt> <draft-ietf-xmldsig-xc14n-02.txt>
Status of This Document Status of This Document
Distribution of this draft is unlimited. Comments should be sent to Distribution of this draft is unlimited. Comments should be sent to
the XMLDSIG working group mailing list or to the authors. the XMLDSIG working group mailing list or to the authors.
This document is an Internet-Draft and is in full conformance with This document is an Internet Draft and is in full conformance with
all provisions of Section 10 of RFC 2026. Internet-Drafts are all provisions of Section 10 of RFC 2026. Internet Drafts are
working documents of the Internet Engineering Task Force (IETF), its working documents of the Internet Engineering Task Force (IETF), its
areas, and its working groups. Note that other groups may also areas, and its working groups. Note that other groups may also
distribute working documents as Internet-Drafts. distribute working documents as Internet Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet- Drafts as reference time. It is inappropriate to use Internet Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
Copyright Notice Copyright Notice
skipping to change at page 6, line 48 skipping to change at page 6, line 48
1.3 Limitations 1.3 Limitations
Exclusive XML Canonicalization has the limitations of Canonical XML Exclusive XML Canonicalization has the limitations of Canonical XML
[XML-C14N] plus two additional limitations as follows: [XML-C14N] plus two additional limitations as follows:
1. The XML being canonicalized may depend on the effect of XML 1. The XML being canonicalized may depend on the effect of XML
namespace attributes, such as xml:lang, xml:space, and xml:base namespace attributes, such as xml:lang, xml:space, and xml:base
appearing in ancestor nodes. To avoid problems due to the non- appearing in ancestor nodes. To avoid problems due to the non-
importation of such attributes into an enveloped document importation of such attributes into an enveloped document
subset, either they MUST be explicitly given in the apex nodes subset, either they MUST be explicitly given in a node of the
of the XML document subset being canonicalized or they MUST XML document subset being canonicalized where their effect is
always be declared with an equivalent value in every context in needed or which is an ancestor of the node where their effect is
which the XML document subset will be interpreted. needed or they MUST always be declared with an equivalent value
in every context in which the XML document subset will be
interpreted.
2. Applications that use the XML being canonicalized may depend on 2. Applications that use the XML being canonicalized may depend on
the effect of XML namespace declarations where the namespace the effect of XML namespace declarations where the namespace
prefix being bound is not visibly utilized. An example would be prefix being bound is not visibly utilized. An example would be
an attribute whose value is an XPath expression and whose an attribute whose value is an XPath expression and whose
evaluation therefore depends upon namespace prefixes referenced evaluation therefore depends upon namespace prefixes referenced
in the expression. Or, an attribute value might be considered a in the expression. Or, an attribute value might be considered a
QName [XML-NS] by some applications, but it is only a string- QName [XML-NS] by some applications, but it is only a string-
value to XPath: value to XPath:
<number xsi:type="xsd:decimal">10.09</number>. <number xsi:type="xsd:decimal">10.09</number>.
skipping to change at page 12, line 19 skipping to change at page 12, line 19
and XML Encryption [XML-Enc]. and XML Encryption [XML-Enc].
Identifier: Identifier:
http://www.w3.org/2001/10/xml-exc-c14n# http://www.w3.org/2001/10/xml-exc-c14n#
http://www.w3.org/2001/10/xml-exc-c14n#WithComments http://www.w3.org/2001/10/xml-exc-c14n#WithComments
Just as with [XML-C14N] one may use the "#WithComments" parameter to Just as with [XML-C14N] one may use the "#WithComments" parameter to
include the serialization of XML comments. This algorithm also takes include the serialization of XML comments. This algorithm also takes
an optional explicit parameter of an empty InclusiveNamespaces an optional explicit parameter of an empty InclusiveNamespaces
element with a PrefixList attribute. The value of this attribute, element with a PrefixList attribute. The value of this attribute is a
which may be null, is a white space delimited list of namespace white space delimited list of namespace prefixes, and where #default
prefixes, and where #default indicates the default namespace, to be indicates the default namespace, to be handled as per [XML-C14N]. The
handled as per [XML-C14N]. The list is in NMTOKENS format (a white list is in NMTOKENS format (a white space separated list). For
space separated list). For example: example:
<ds:Transform <ds:Transform
Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"> Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#">
<ec:InclusiveNamespaces PrefixList="dsig soap #default" <ec:InclusiveNamespaces PrefixList="dsig soap #default"
xmlns:ec="http://www.w3.org/2001/10/xml-exc-c14n#"/> xmlns:ec="http://www.w3.org/2001/10/xml-exc-c14n#"/>
</ds:Transform> </ds:Transform>
indicates the exclusive canonicalization transform, but that indicates the exclusive canonicalization transform, but that
namespaces with prefix "dsig" or "soap" and default namespaces should namespaces with prefix "dsig" or "soap" and default namespaces should
be processed according to [XML-C14N]. be processed according to [XML-C14N].
skipping to change at page 16, line 21 skipping to change at page 16, line 21
Phone: 1-888-517-2675 Phone: 1-888-517-2675
EMail: jboyer@PureEdge.com EMail: jboyer@PureEdge.com
Donald E. Eastlake 3rd Donald E. Eastlake 3rd
Motorola Motorola
155 Beaver Street 155 Beaver Street
Milford, MA 01757 USA Milford, MA 01757 USA
Telephone: +1-508-634-2066 (h) Telephone: +1-508-634-2066 (h)
+1-508-851-8280 (w) +1-508-786-7554 (w)
EMail: Donald.Eastlake@motorola.com EMail: Donald.Eastlake@motorola.com
Joseph M. Reagle Jr., W3C Joseph M. Reagle Jr., W3C
Massachusetts Institute of Technology Massachusetts Institute of Technology
Laboratory for Computer Science Laboratory for Computer Science
NE43-350, 545 Technology Square NE43-350, 545 Technology Square
Cambridge, MA 02139 Cambridge, MA 02139
Phone: +1.617.258.7621 Phone: +1.617.258.7621
EMail: reagle@w3.org EMail: reagle@mit.edu
Full Copyright Statement Full Copyright Statement
Copyright (C) 2003 The Internet Society & W3C (MIT, INRIA, Keio), All Copyright (C) 2003 The Internet Society & W3C (MIT, INRIA, Keio), All
Rights Reserved. Rights Reserved.
This document and translations of it may be copied and furnished to This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any and distributed, in whole or in part, without restriction of any
skipping to change at page 17, line 36 skipping to change at page 17, line 36
This document and the information contained herein is provided on an This document and the information contained herein is provided on an
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Expiration and File Name Expiration and File Name
This draft expires December 2003. This draft expires June 2004.
Its file name is draft-ietf-xmldsig-xc14n-01.txt. Its file name is draft-ietf-xmldsig-xc14n-02.txt.
 End of changes. 11 change blocks. 
18 lines changed or deleted 20 lines changed or added

This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/