RFC 4051: Additional XML Security Uniform Resource Identifiers (URIs)
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 6931.
Current document in this lineage: RFC 9231 — Additional XML Security Uniform Resource Identifiers (URIs)
In plain English — editorial summary, not part of the RFC
A number of Uniform Resource Identifiers (URIs) intended for use with XML Digital Signatures, Encryption, and Canonicalization are defined. These URIs identify algorithms and types of keying information. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4051
- Published
- April 2005
- Authors
- D. Eastlake 3rd
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- —
- Pages
- 17
- Also known as
- —
- Obsoleted by:
- RFC 6931
Topics
Standards lineage
This document is one revision in a chain of 3 RFCs, each formally replacing the one before it.
- RFC 4051 (2005)
- RFC 6931 (2013)
- RFC 9231 (2022) ✓
Read the full history of Additional XML Security Uniform Resource Identifiers (URIs) →
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 9580OpenPGPCurrent
July 2024
- RFC 4197Requirements for Edge-to-Edge Emulation of Time Division Multiplexed (TDM) Circuits over Packet Switching NetworksCurrent
October 2005
- RFC 4211Internet X.509 Public Key Infrastructure Certificate Request Message Format (CRMF)Updated
September 2005
- RFC 3854Securing X.400 Content with Secure/Multipurpose Internet Mail Extensions (S/MIME)Current
July 2004
- RFC 3851Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 3.1 Message SpecificationObsoleted
July 2004
- RFC 3850Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 3.1 Certificate HandlingObsoleted
July 2004
- RFC 4253The Secure Shell (SSH) Transport Layer ProtocolUpdated
January 2006
- RFC 3778The application/pdf Media TypeObsoleted
May 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?