Please switch to iso standard for datetimes

[Brimstedt]

Date time fields would be better if using international standards as ISO 8601 rather than RFC 5322 which includes language specific strings.

[M-i-k-o-t-o]

Do you have a link to said "ISO 8601" standard?

[nightwatchcyber]

IETF standards generally use the format defined in section 3.3. of RFC 5322 (same as email): https://tools.ietf.org/html/rfc5322#section-3.3

[EdOverflow]

Do you have a link to said "ISO 8601" standard?

https://www.iso.org/obp/ui/#iso:std:iso:8601:-1:ed-1:v1:en

[M-i-k-o-t-o]

@EdOverflow

Only informative sections of standards are publicly available. To view the full content, you will need to purchase the standard by clicking on the "Buy" button.

[EdOverflow]

Only informative sections of standards are publicly available. To view the full content, you will need to purchase the standard by clicking on the "Buy" button.

Yes, you have to purchase ISO standards, @M-i-k-o-t-o.

[nightwatchcyber]

I am asking IETF members about this

[nightwatchcyber]

IETF consensus seems to point to RFC 3339, I updated the GitHub version of the draft to reflect that.

[nightwatchcyber]

See: https://www.rfc-editor.org/rfc/rfc9116.html#name-expires

The "Expires" field indicates the date and time after which the data contained in the "security.txt" file is considered stale and should not be used (as per Section 5.3). The value of this field is formatted according to the Internet profiles of [ISO.8601-1] and [ISO.8601-2] as defined in [RFC3339]. It is RECOMMENDED that the value of this field be less than a year into the future to avoid staleness.