RFC 3741: Exclusive XML Canonicalization, Version 1.0
In plain English — editorial summary, not part of the RFC
Canonical XML 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. This memo provides information for the Internet community.
Document record
- Document ID
- RFC3741
- Published
- March 2004
- Authors
- J. Boyer; D. Eastlake 3rd; J. Reagle
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- sec
- Pages
- 16
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3653XML-Signature XPath Filter 2.0Current
December 2003
- RFC 3275(Extensible Markup Language) XML-Signature Syntax and ProcessingCurrent
March 2002
- RFC 3688The IETF XML RegistryCurrent
January 2004
- RFC 3858An Extensible Markup Language (XML) Based Format for Watcher InformationCurrent
August 2004
- RFC 3870application/rdf+xml Media Type RegistrationCurrent
September 2004
- RFC 3920Extensible Messaging and Presence Protocol (XMPP): CoreObsoleted
October 2004
- RFC 3921Extensible Messaging and Presence Protocol (XMPP): Instant Messaging and PresenceObsoleted
October 2004
- RFC 3922Mapping the Extensible Messaging and Presence Protocol (XMPP) to Common Presence and Instant Messaging (CPIM)Current
October 2004
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?