RFC 8943: Concise Binary Object Representation (CBOR) Tags for Date
In plain English — editorial summary, not part of the RFC
The Concise Binary Object Representation (CBOR), as specified in RFC 7049, is a data format whose design goals include the possibility of extremely small code size, fairly small message size, and extensibility without the need for version negotiation. In CBOR, one point of extensibility is the definition of CBOR tags. RFC 7049 defines two tags for time: CBOR tag 0 (date/time string as per RFC 3339) and tag 1 (POSIX "seconds since the epoch"). Since then, additional requirements have become known. This specification defines a CBOR tag for a date text string (as per RFC 3339) for applications needing a textual date representation within the Gregorian calendar without a time. It also defines a CBOR tag for days since the date 1970-01-01 in the Gregorian calendar for applications needing a numeric date representation without a time. This specification is the reference document for IANA registration of the CBOR tags defined.
Document record
- Document ID
- RFC8943
- Published
- November 2020
- Authors
- M. Jones; A. Nadalin; J. Richter
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- art
- Pages
- 6
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8984JSCalendar: A JSON Representation of Calendar DataCurrent
July 2021
- RFC 8727JSON Binding of the Incident Object Description Exchange FormatCurrent
August 2020
- RFC 9254Encoding of Data Modeled with YANG in the Concise Binary Object Representation (CBOR)Current
July 2022
- RFC 8392CBOR Web Token (CWT)Current
May 2018
- RFC 9542IANA Considerations and IETF Protocol and Documentation Usage for IEEE 802 ParametersCurrent
April 2024
- RFC 9595YANG Schema Item iDentifier (YANG SID)Current
July 2024
- RFC 9711The Entity Attestation Token (EAT)Current
April 2025
- RFC 5788IMAP4 Keyword RegistryUpdated
March 2010
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?