RFC 3075: XML-Signature Syntax and Processing
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 3275.
Current version: RFC 3275 — (Extensible Markup Language) XML-Signature Syntax and Processing
In plain English — editorial summary, not part of the RFC
This document specifies XML (Extensible Markup Language) digital signature processing rules and syntax. [STANDARDS-TRACK]
Document record
- Document ID
- RFC3075
- Published
- March 2001
- Authors
- D. Eastlake 3rd; J. Reagle; D. Solo
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 64
- Also known as
- —
- Obsoleted by:
- RFC 3275
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3076Canonical XML Version 1.0Current
March 2001
- RFC 2807XML Signature RequirementsCurrent
July 2000
- RFC 2935Internet Open Trading Protocol (IOTP) HTTP SupplementCurrent
September 2000
- RFC 2803Digest Values for DOM (DOMHASH)Current
April 2000
- RFC 2802Digital Signatures for the v1.0 Internet Open Trading Protocol (IOTP)Current
April 2000
- RFC 3504Internet Open Trading Protocol (IOTP) Version 1, ErrataCurrent
March 2003
- RFC 3120A URN Namespace for XML.orgCurrent
June 2001
- RFC 2731Encoding Dublin Core Metadata in HTMLObsoleted
December 1999
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?