Concise Binary Object Representation (CBOR) Tags for Date
draft-ietf-cbor-date-tag-01

The information below is for an old version of the document
Document Type Active Internet-Draft (cbor WG)
Last updated 2020-06-30 (latest revision 2020-06-09)
Replaces draft-jones-cbor-date-tag
Stream IETF
Intended RFC status (None)
Formats pdf htmlized (tools) htmlized bibtex
Reviews
Stream WG state In WG Last Call
Revised I-D Needed - Issue raised by WGLC
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
CBOR Working Group                                              M. Jones
Internet-Draft                                                A. Nadalin
Intended status: Standards Track                               Microsoft
Expires: December 11, 2020                                    J. Richter
                                             pdv Financial Software GmbH
                                                            June 9, 2020

       Concise Binary Object Representation (CBOR) Tags for Date
                      draft-ietf-cbor-date-tag-01

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 applications
   needing a numeric date representation without a time.  It is intended
   as the reference document for the IANA registration of the CBOR tags
   defined.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at https://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on December 11, 2020.

Jones, et al.           Expires December 11, 2020               [Page 1]
Internet-Draft              CBOR Tag for Date                  June 2020

Copyright Notice

   Copyright (c) 2020 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (https://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Requirements Notation and Conventions . . . . . . . . . .   3
   2.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   3
     2.1.  Concise Binary Object Representation (CBOR) Tags
           Registrations . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Security Considerations . . . . . . . . . . . . . . . . . . .   3
   4.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   3
     4.1.  Normative References  . . . . . . . . . . . . . . . . . .   3
     4.2.  Informative References  . . . . . . . . . . . . . . . . .   4
   Acknowledgements  . . . . . . . . . . . . . . . . . . . . . . . .   4
   Document History  . . . . . . . . . . . . . . . . . . . . . . . .   4
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   5

1.  Introduction

   The Concise Binary Object Representation (CBOR) [RFC7049] provides
   for the interchange of structured data without a requirement for a
   pre-agreed schema.  RFC 7049 defines a basic set of data types, as
   well as a tagging mechanism that enables extending the set of data
   types supported via an IANA registry.

   This specification defines a CBOR tag for a text string representing
   a date but not a time.  The tagged text string is represented as
   specified by the RFC 3339 [RFC3339] "full-date" production.

   This specification also defines a CBOR tag for an integer
   representing a date but not a time.  The tagged integer is an
   unsigned or negative value indicating the number of days since the
   IEEE Std 1003.1, 2013 Edition [POSIX.1] epoch date 1970-01-01.  As an
   implementation note, this value has a constant offset from the
   Modified Julian Date value (which is defined by the Smithsonian

Jones, et al.           Expires December 11, 2020               [Page 2]
Internet-Draft              CBOR Tag for Date                  June 2020
Show full document text