RFC 9557: Date and Time on the Internet: Timestamps with Additional Information
RFC 9557: Date and Time on the Internet: Timestamps with Additional Information
https://datatracker.ietf.org/doc/rfc9557/
This document defines an extension to the timestamp format defined in RFC 3339 for representing additional information, including a time zone. It updates RFC 3339 in the specific interpretation of the local offset , which is no longer understood to "imply that UTC is the preferred reference point for the specified time".
RFC 9557: Date and Time on the Internet: Timestamps with Additional Information
https://datatracker.ietf.org/doc/html/rfc9557
This document defines an extension to the timestamp format defined in RFC 3339 for representing additional information, including a time zone. It updates RFC 3339 in the specific interpretation of the local offset , which is no longer understood to "imply that UTC is the preferred reference point for the specified time".
Anything of interest happen in 9-11?
AD 9 - Wikipedia
https://en.wikipedia.org/wiki/AD_9
What is the need of T in the new (2019) time format?
Basically title. 2019 edition of the Standard denotes the "T" prefix to time as mandatory (except in "unambiguous contexts"):
01:29:59 is now actually T01:29:59, with the former form now designated as an alternative
But date does not have a "D" prefix, not even in "ambiguous contexts".
1973-09-11 never needs to be something like eg.: D1973-09-11
Anyone know the reasoning behind this change and what is the intended use? The only time-only format with separators that I can think would be undecidable in ambiguous contexts would be hh:mm which I guess could be mistaken for bible verses?
