RFC 4049: BinaryTime: An Alternate Format for Representing Date and Time in ASN.1
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 6019.
Current version: RFC 6019 — BinaryTime: An Alternate Format for Representing Date and Time in ASN.1
In plain English — editorial summary, not part of the RFC
This document specifies a new ASN.1 type for representing time: BinaryTime. This document also specifies an alternate to the signing-time attribute for use with the Cryptographic Message Syntax(CMS) SignedData and AuthenticatedData content types; the binary-signing-time attribute uses BinaryTime. CMS and the signing-time attribute are defined in RFC 3852. This memo defines an Experimental Protocol for the Internet community.
Document record
- Document ID
- RFC4049
- Published
- April 2005
- Authors
- R. Housley
- Status
- EXPERIMENTAL
- Stream
- IETF
- Area
- —
- Pages
- 7
- Also known as
- —
- Obsoleted by:
- RFC 6019
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 3852Cryptographic Message Syntax (CMS)Obsoleted
July 2004
- RFC 3657Use of the Camellia Encryption Algorithm in Cryptographic Message Syntax (CMS)Current
January 2004
- RFC 3565Use of the Advanced Encryption Standard (AES) Encryption Algorithm in Cryptographic Message Syntax (CMS)Current
July 2003
- RFC 3560Use of the RSAES-OAEP Key Transport Algorithm in Cryptographic Message Syntax (CMS)Current
July 2003
- RFC 3370Cryptographic Message Syntax (CMS) AlgorithmsUpdated
September 2002
- RFC 3274Compressed Data Content Type for Cryptographic Message Syntax (CMS)Current
June 2002
- RFC 2984Use of the CAST-128 Encryption Algorithm in CMSCurrent
October 2000
- RFC 5485Digital Signatures on Internet-Draft DocumentsUpdated
March 2009
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?