idnits 2.17.1 draft-ietf-cbor-date-tag-02.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == The document doesn't use any RFC 2119 keywords, yet seems to have RFC 2119 boilerplate text. -- The document date (June 30, 2020) is 1396 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) ** Obsolete normative reference: RFC 7049 (Obsoleted by RFC 8949) Summary: 1 error (**), 0 flaws (~~), 2 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 CBOR Working Group M. Jones 3 Internet-Draft A. Nadalin 4 Intended status: Standards Track Microsoft 5 Expires: January 1, 2021 J. Richter 6 pdv Financial Software GmbH 7 June 30, 2020 9 Concise Binary Object Representation (CBOR) Tags for Date 10 draft-ietf-cbor-date-tag-02 12 Abstract 14 The Concise Binary Object Representation (CBOR, RFC 7049) is a data 15 format whose design goals include the possibility of extremely small 16 code size, fairly small message size, and extensibility without the 17 need for version negotiation. 19 In CBOR, one point of extensibility is the definition of CBOR tags. 20 RFC 7049 defines two tags for time: CBOR tag 0 (RFC 3339 date/time 21 string) and tag 1 (Posix "seconds since the epoch"). Since then, 22 additional requirements have become known. This specification 23 defines a CBOR tag for an RFC 3339 date text string, for applications 24 needing a textual date representation without a time. It also 25 defines a CBOR tag for days since the Posix epoch, for applications 26 needing a numeric date representation without a time. It is intended 27 as the reference document for the IANA registration of the CBOR tags 28 defined. 30 Status of This Memo 32 This Internet-Draft is submitted in full conformance with the 33 provisions of BCP 78 and BCP 79. 35 Internet-Drafts are working documents of the Internet Engineering 36 Task Force (IETF). Note that other groups may also distribute 37 working documents as Internet-Drafts. The list of current Internet- 38 Drafts is at https://datatracker.ietf.org/drafts/current/. 40 Internet-Drafts are draft documents valid for a maximum of six months 41 and may be updated, replaced, or obsoleted by other documents at any 42 time. It is inappropriate to use Internet-Drafts as reference 43 material or to cite them other than as "work in progress." 45 This Internet-Draft will expire on January 1, 2021. 47 Copyright Notice 49 Copyright (c) 2020 IETF Trust and the persons identified as the 50 document authors. All rights reserved. 52 This document is subject to BCP 78 and the IETF Trust's Legal 53 Provisions Relating to IETF Documents 54 (https://trustee.ietf.org/license-info) in effect on the date of 55 publication of this document. Please review these documents 56 carefully, as they describe your rights and restrictions with respect 57 to this document. Code Components extracted from this document must 58 include Simplified BSD License text as described in Section 4.e of 59 the Trust Legal Provisions and are provided without warranty as 60 described in the Simplified BSD License. 62 Table of Contents 64 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 65 1.1. Requirements Notation and Conventions . . . . . . . . . . 3 66 2. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3 67 2.1. Concise Binary Object Representation (CBOR) Tags 68 Registrations . . . . . . . . . . . . . . . . . . . . . . 3 69 3. Security Considerations . . . . . . . . . . . . . . . . . . . 3 70 4. References . . . . . . . . . . . . . . . . . . . . . . . . . 3 71 4.1. Normative References . . . . . . . . . . . . . . . . . . 4 72 4.2. Informative References . . . . . . . . . . . . . . . . . 4 73 Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 4 74 Document History . . . . . . . . . . . . . . . . . . . . . . . . 4 75 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 5 77 1. Introduction 79 The Concise Binary Object Representation (CBOR) [RFC7049] provides 80 for the interchange of structured data without a requirement for a 81 pre-agreed schema. RFC 7049 defines a basic set of data types, as 82 well as a tagging mechanism that enables extending the set of data 83 types supported via an IANA registry. 85 This specification defines a CBOR tag for a text string representing 86 a date without a time. The tagged text string is represented as 87 specified by the RFC 3339 [RFC3339] "full-date" production. 89 This specification also defines a CBOR tag for an integer 90 representing a date without a time. The tagged integer is an 91 unsigned or negative value indicating the number of days since the 92 IEEE Std 1003.1, 2013 Edition [POSIX.1] epoch date 1970-01-01. As an 93 implementation note, this value has a constant offset from the 94 Modified Julian Date value (which is defined by the Smithsonian 95 Astrophysical Observatory as the number of days since November 17, 96 1858); this value is the Modified Julian Date minus 40,587. 98 Note that since both tags are for dates without times, time zones and 99 leap seconds are not applicable to these values. 101 1.1. Requirements Notation and Conventions 103 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 104 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 105 "OPTIONAL" in this document are to be interpreted as described in BCP 106 14 [RFC2119] [RFC8174] when, and only when, they appear in all 107 capitals, as shown here. 109 2. IANA Considerations 111 2.1. Concise Binary Object Representation (CBOR) Tags Registrations 113 This section registers the following values in the IANA "Concise 114 Binary Object Representation (CBOR) Tags" registry [IANA.cbor-tags]. 116 o Tag: 1004 (value requested) 117 o Data Item: UTF-8 text string 118 o Semantics: RFC 3339 full-date string 119 o Reference: [[ this specification ]] 121 o Tag: 100 (ASCII 'd') (value requested) 122 o Data Item: Unsigned or negative integer 123 o Semantics: Number of days since the epoch date 1970-01-01 124 o Reference: [[ this specification ]] 126 3. Security Considerations 128 The security considerations of RFC 7049 apply; the tags introduced 129 here are not expected to raise security considerations beyond those. 131 A date, of course, has significant security considerations; these 132 include the exploitation of ambiguities where the date is security 133 relevant or where the date is used in access control decisions. 134 However, typically times will also be used when making access control 135 decisions, rather than dates without times. 137 4. References 138 4.1. Normative References 140 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 141 Requirement Levels", BCP 14, RFC 2119, 142 DOI 10.17487/RFC2119, March 1997, 143 . 145 [RFC3339] Klyne, G. and C. Newman, "Date and Time on the Internet: 146 Timestamps", RFC 3339, DOI 10.17487/RFC3339, July 2002, 147 . 149 [RFC7049] Bormann, C. and P. Hoffman, "Concise Binary Object 150 Representation (CBOR)", RFC 7049, DOI 10.17487/RFC7049, 151 October 2013, . 153 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 154 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 155 May 2017, . 157 4.2. Informative References 159 [IANA.cbor-tags] 160 IANA, "Concise Binary Object Representation (CBOR) Tags", 161 . 163 [POSIX.1] IEEE, "The Open Group Base Specifications Issue 7", 164 IEEE Std 1003.1, 2013 Edition, 2013, 165 . 168 Acknowledgements 170 Thanks to Carsten Bormann for supporting creation of this 171 specification. Parts of the explanatory text in this specification 172 come from draft-bormann-cbor-time-tag-02. 174 Thanks to these people for reviews of the specification: Carsten 175 Bormann, Jim Schaad, and Dale Worley. 177 Document History 179 [[ to be removed by the RFC Editor before publication as an RFC ]] 181 -02 183 o Addressed working group last call comments, including stating that 184 time zones are not applicable to these values. 186 -01 188 o Changed "positive or negative" to "unsigned or negative". 190 o Added an implementation note about the relationship to Modified 191 Julian Dates. 193 -00 195 o Initial working group version based on draft-jones-cbor-date- 196 tag-01 with no normative changes. 198 Authors' Addresses 200 Michael B. Jones 201 Microsoft 203 Email: mbj@microsoft.com 204 URI: https://self-issued.info/ 206 Anthony Nadalin 207 Microsoft 209 Email: tonynad@microsoft.com 211 Joerg Richter 212 pdv Financial Software GmbH 214 Email: joerg.richter@pdv-fs.de