RFC 3126: Electronic Signature Formats for long term electronic signatures
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 5126.
Current version: RFC 5126 — CMS Advanced Electronic Signatures (CAdES)
In plain English — editorial summary, not part of the RFC
This document defines the format of an electronic signature that can remain valid over long periods. This includes evidence as to its validity even if the signer or verifying party later attempts to deny (i.e., repudiates the validity of the signature). This memo provides information for the Internet community.
Document record
- Document ID
- RFC3126
- Published
- September 2001
- Authors
- D. Pinkas; J. Ross; N. Pope
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- sec
- Pages
- 84
- Also known as
- —
- Obsoleted by:
- RFC 5126
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 3125Electronic Signature PoliciesCurrent
September 2001
- RFC 2887The Reliable Multicast Design Space for Bulk Data TransferCurrent
August 2000
- RFC 2326Real Time Streaming Protocol (RTSP)Obsoleted
April 1998
- RFC 3114Implementing Company Classification Policy with the S/MIME Security LabelCurrent
May 2002
- RFC 3185Reuse of CMS Content Encryption KeysCurrent
October 2001
- RFC 2479Independent Data Unit Protection Generic Security Service Application Program Interface (IDUP-GSS-API)Current
December 1998
- RFC 2478The Simple and Protected GSS-API Negotiation MechanismObsoleted
December 1998
- RFC 2078Generic Security Service Application Program Interface, Version 2Obsoleted
January 1997
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?