RFC 3653 on XML-Signature XPath Filter 2.0
rfc-editor@rfc-editor.org Tue, 16 December 2003 00:50 UTC
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA08278 for <ietf-announce-web-archive@odin.ietf.org>; Mon, 15 Dec 2003 19:50:06 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14) id 1AW3HX-0002yX-Si for ietf-announce-list@asgard.ietf.org; Mon, 15 Dec 2003 19:41:47 -0500
Received: from ietf.org ([10.27.2.28]) by asgard.ietf.org with esmtp (Exim 4.14) id 1AW3Fn-0002wE-Iz for all-ietf@asgard.ietf.org; Mon, 15 Dec 2003 19:39:59 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA07895 for <all-ietf@ietf.org>; Mon, 15 Dec 2003 19:39:56 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AW3Fl-0006xE-00 for all-ietf@ietf.org; Mon, 15 Dec 2003 19:39:58 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AW3Fk-0006x7-00 for all-ietf@ietf.org; Mon, 15 Dec 2003 19:39:57 -0500
Received: from gamma.isi.edu ([128.9.144.145]) by ietf-mx with esmtp (Exim 4.12) id 1AW3Fk-0006x4-00 for all-ietf@ietf.org; Mon, 15 Dec 2003 19:39:56 -0500
Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id hBG0dus22151; Mon, 15 Dec 2003 16:39:56 -0800 (PST)
Message-Id: <200312160039.hBG0dus22151@gamma.isi.edu>
To: IETF-Announce:;
Subject: RFC 3653 on XML-Signature XPath Filter 2.0
Cc: rfc-editor@rfc-editor.org, w3c-ietf-xmldsig@w3.org
From: rfc-editor@rfc-editor.org
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Mon, 15 Dec 2003 16:39:56 -0800
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=-10.5 required=5.0 tests=AWL,MIME_BOUND_NEXTPART, NO_REAL_NAME,USER_IN_DEF_WHITELIST autolearn=no version=2.60
Sender: owner-ietf-announce@ietf.org
Precedence: bulk
A new Request for Comments is now available in online RFC libraries. RFC 3653 Title: XML-Signature XPath Filter 2.0 Author(s): J. Boyer, M. Hughes, J. Reagle Status: Informational Date: December 2003 Mailbox: jboyer@PureEdge.com, Merlin.Hughes@betrusted.com, reagle@mit.edu Pages: 15 Characters: 32258 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-xmldsig-xpf2-01.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3653.txt XML Signature recommends a standard means for specifying information content to be digitally signed and for representing the resulting digital signatures in XML. Some applications require the ability to specify a subset of a given XML document as the information content to be signed. The XML Signature specification meets this requirement with the XPath transform. However, this transform can be difficult to implement efficiently with existing technologies. This specification defines a new XML Signature transform to facilitate the development of efficient document subsetting implementations that interoperate under similar performance profiles. This document is the W3C XML Signature XPath-Filter 2.0 Recommendation. This document has been reviewed by W3C Members and other interested parties and has been endorsed by the Director as a W3C Recommendation. It is a stable document and may be used as reference material or cited as a normative reference from another document. W3C's role in making the Recommendation is to draw attention to the specification and to promote its widespread deployment. This enhances the functionality and interoperability of the Web. This document is a product of the XML Digital Signatures Working Group of the IETF. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs.
- RFC 3653 on XML-Signature XPath Filter 2.0 rfc-editor