This specification does not cater to local time zone True interoperability is best achieved by using Coordinated Universal Coordinated Universal Time (UTC)īecause the daylight saving rules for local time zones are soĬonvoluted and can change based on local law at unpredictable times, Times used in Internet protocols MUST be fully qualified.Ĥ. The problems with two digit years amply demonstrate why all dates and Software should detect non-numeric decades and interpret Wishing to robustly deal with dates generated by such broken This occurs if the program simply subtracts 1900 from the yearĪnd adds the decade to the US-ASCII character zero.
ISO 8601 SOFTWARE
Programs wishing to robustly deal withĭates generated by such broken software may add 1900 to three Program simply subtracts 1900 from the year and doesn't check Represent years after 1999 as three digits. O It is possible that a program using two digit years will if used only for logging or tracing purposes). Interpretation will not cause a protocol or processing failure Received, it should be accepted ONLY if an incorrect O The use of 2-digit years is deprecated. O Internet Protocols MUST generate four digit years in dates. The following requirements are to address the problems of ambiguity Section 3 of, and the appropriate ITU documents [ITU-R. RFC 3339 Date and Time on the Internet: Timestamps July 2002įor more information about time scales, see Appendix E of , Phonetic alphabet representation of the letter "Z". Offset of 00:00 often spoken "Zulu" from the ICAO Z A suffix which, when applied to a time, denotes a UTC Unambiguous representation of some instant in time. Timestamp This term is used in this document to refer to an The date format defined in section 5 of this document. The date/time format used by Internet Mail as defined Permissible strings in a protocol or language, as Shall also be divisible by four hundred an integralĪBNF Augmented Backus-Naur Form, a format used to represent Leap year In the Gregorian calendar, a year which has 366 days.Ī leap year is a year whose number is divisible byįour an integral number of times, except that if it isĪ centennial year (i.e. Restrictions in section 5.7 and Appendix D for how It is defined as theĭuration of 9,192,631,770 cycles of microwave lightĪbsorbed or emitted by the hyperfine transition ofĬesium-133 atoms in their ground state undisturbed by Second A basic unit of measurement of time in the International des Poids et Mesures (BIPM). UTC Coordinated Universal Time as maintained by the Bureau "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in thisĭocument are to be interpreted as described in RFC 2119. The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", RFC 3339 Date and Time on the Internet: Timestamps July 2002 2. O Date and time expressions indicate an instant in time.ĭescription of time periods, or intervals, is not covered here. Using the best available practice at the stated time. Such timestamps are expressed relative to universal time, O Timestamps can express times that occurred before the introduction The UTC time corresponding to 17:00 on 23rd MarchĢ005 in New York may depend on administrative decisions aboutĭaylight savings time. On the unknown or unknowable actions of politicians orĪdministrators. May be known, but the actual relationship to UTC may be dependent Usage in scheduling applications where a local time and location O All times expressed have a stated relationship (offset) toĬoordinated Universal Time (UTC). O All dates and times are assumed to be in the "current era", This limitedĬonsideration has the following consequences: Internet protocols: this document focuses on just one common usage, There are many ways in which date and time values might appear in Standard for representation of dates and times using the Gregorian
ISO 8601 ISO
This document includes an Internet profile of the ISO 8601 Problems encountered and makes recommendations to improve consistencyĪnd interoperability when representing and using date and time in Introductionĭate and time formats cause a lot of confusion and interoperability RFC 3339 Date and Time on the Internet: Timestamps July 2002 Appendix A. Representation of dates and times using the Gregorian calendar.ġ. Protocols that is a profile of the ISO 8601 standard for This document defines a date and time format for use in Internet Distribution of this memo is unlimited.Ĭopyright (C) The Internet Society (2002). Official Protocol Standards" (STD 1) for the standardization stateĪnd status of this protocol. Please refer to the current edition of the "Internet Internet community, and requests discussion and suggestions for This document specifies an Internet standards track protocol for the Request for Comments: 3339 Clearswift Corporationĭate and Time on the Internet: Timestamps
0 kommentar(er)
