[Cbor] RFC 9581 on Concise Binary Object Representation (CBOR) Tags for Time, Duration, and Period

A new Request for Comments is now available in online RFC libraries.

        RFC 9581

        Title:      Concise Binary Object Representation (CBOR) 
                    Tags for Time, Duration, and Period 
        Author:     C. Bormann,
                    B. Gamari,
                    H. Birkholz
        Status:     Standards Track
        Stream:     IETF
        Date:       August 2024
        Mailbox:    cabo@tzi.org,
                    ben@well-typed.com,
                    henk.birkholz@ietf.contact
        Pages:      21
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-cbor-time-tag-12.txt

        URL:        https://www.rfc-editor.org/info/rfc9581

        DOI:        10.17487/RFC9581

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.

This document is a product of the Concise Binary Object Representation Maintenance and Extensions Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

The RFC Editor Team
Association Management Solutions, LLC