Concise Binary Object Representation (CBOR) Tags for Date
draft-jones-cbor-date-tag-01
| Document | Type |
Replaced Internet-Draft
(candidate for cbor WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Michael B. Jones , Anthony Nadalin , Joerg Richter | ||
| Last updated | 2020-04-23 (Latest revision 2020-04-21) | ||
| Replaced by | draft-ietf-cbor-date-tag | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | Call For Adoption By WG Issued | |
| Document shepherd | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-cbor-date-tag | |
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
The Concise Binary Object Representation (CBOR, 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 (RFC 3339 date/time string) and tag 1 (Posix "seconds since the epoch"). Since then, additional requirements have become known. This specification defines a CBOR tag for an RFC 3339 date text string, for applications needing a textual date representation without a time. It also defines a CBOR tag for days since the Posix epoch, for applicaitons needing a numeric date representation without a time. It is intended as the reference document for the IANA registration of the CBOR tags defined.
Authors
Michael B. Jones
Anthony Nadalin
Joerg Richter
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)