RFC 9581: Concise Binary Object Representation (CBOR) Tags for Time, Duration, and Period
In plain English — editorial summary, not part of the RFC
The Concise Binary Object Representation (CBOR, RFC 8949) 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 8949 defines two tags for time: CBOR tag 0 (RFC 3339 time as a string) and tag 1 (POSIX time as int or float). Since then, additional requirements have become known. The present document defines a CBOR tag for time that allows a more elaborate representation of time, as well as related CBOR tags for duration and time period. This document is intended as the reference document for the IANA registration of the CBOR tags defined.
Document record
- Document ID
- RFC9581
- Published
- August 2024
- Authors
- C. Bormann; B. Gamari; H. Birkholz
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- art
- Pages
- 21
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7384Security Requirements of Time Protocols in Packet Switched NetworksCurrent
October 2014
- RFC 7164RTP and Leap SecondsCurrent
March 2014
- RFC 8039Multipath Time SynchronizationCurrent
December 2016
- RFC 9616Delay-Based Metric Extension for the Babel Routing ProtocolCurrent
September 2024
- RFC 9523A Secure Selection and Filtering Mechanism for the Network Time Protocol with KhronosCurrent
February 2024
- RFC 9748Updating the NTP RegistriesCurrent
February 2025
- RFC 9760Enterprise Profile for the Precision Time Protocol with Mixed Multicast and Unicast MessagesCurrent
May 2025
- RFC 9769NTP Interleaved ModesCurrent
May 2025
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?