Consider requiring UTC and only UTC for the timeline section of Incident Reporting
Categories
(CA Program :: Common CA Database, enhancement)
Tracking
(Not tracked)
People
(Reporter: amir, Unassigned)
Details
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:125.0) Gecko/20100101 Firefox/125.0
Steps to reproduce:
Having a single time format for all incidents makes cross referencing between them significantly simpler.
|
||
Comment 1•1 years ago
|
||
+1
|
||
Comment 2•1 years ago
|
||
I would rater mandata a standard time-format like ISO 8601. As a CA it is much more error-prone to have to translate all local times to UTC than it is for a researcher who (automatically?) parses such reports.
As a CA it is much more error-prone to have to translate all local times to UTC than it is for a researcher who (automatically?) parses such reports.
Right but the onus of the work should be on the CAs to begin with. Also, the work for the writer is (1), while for readers its (n). So optimizing towards the consumers of the reports is what I'd be an advocate for. Time offsets (which I believe is what the current requirements are) are probably fine, but timezones are awful since they can change meanings depending on the state. Either way I still think that since this is reporting to effectively an international body, we should just use UTC.
If picking a specific format, I'd advocate for RFC 3339 with the following format: %Y-%M-%D %h:%mZ
I also found this website to be helpful about this: https://ijmacd.github.io/rfc3339-iso8601/
Description
•