Javascript disabled? Like other modern websites, the IETF Datatracker relies on Javascript.
Please enable Javascript for full functionality.
(Extensible Markup Language) XML-Signature Syntax and Processing
draft-ietf-xmldsig-core-2-03
The information below is for an old version of the document that is already published as an RFC.
| Document | Type |
This is an older version of an Internet-Draft that was ultimately published as RFC 3275.
|
|---|---|---|
| Authors | Joseph M. Reagle Jr. , Donald E. Eastlake 3rd , David Solo | |
| Last updated | 2020年01月21日 (Latest revision 2002年01月18日) | |
| RFC stream | Internet Engineering Task Force (IETF) | |
| Intended RFC status | Draft Standard | |
| Formats | ||
| Additional resources | Mailing list discussion | |
| Stream | WG state | WG Document |
| Document shepherd | (None) | |
| IESG | IESG state | Became RFC 3275 (Draft Standard) |
| Consensus boilerplate | Unknown | |
| Telechat date | (None) | |
| Responsible AD | (None) | |
| Send notices to | (None) |
draft-ietf-xmldsig-core-2-03
A new Request for Comments is now available in online RFC libraries. RFC 3275 Title: (Extensible Markup Language) XML-Signature Syntax and Processing Author(s): D. Eastlake 3rd, J. Reagle, D. Solo Status: Standards Track Date: March 2002 Mailbox: Donald.Eastlake@motorola.com, reagle@w3.org, dsolo@alum.mit.edu Pages: 73 Characters: 164198 Obsoletes: 3075 I-D Tag: draft-ietf-xmldsig-core-2-03.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3275.txt This document specifies XML (Extensible Markup Language) digital signature processing rules and syntax. XML Signatures provide integrity, message authentication, and/or signer authentication services for data of any type, whether located within the XML that includes the signature or elsewhere. This document is a product of the XML Digital Signatures Working Group of the IETF. This is now a Draft Standard Protocol. This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. 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.