P4
A DESCRIPTION OF THE REQUEST :
RFC_1123_DATE_TIME uses the date format as specified in RFC 1123, which updates RFC 822. However, RFC 822 was obsoleted by RFC 2822, which in turn was obsoleted by RFC 5322.
JUSTIFICATION :
Most notably, RFC 5322 specifically allows and gives meaning to the "-0000" time zone: "it is used to indicate that the time was generated on a system that may be in a local time zone other than Universal Time and that the date-time contains no information about the local time zone."
So in Java terms, the datetime must be treated as a java.time.LocalDateTime
It also specifies that military time zones should all be considered equivalent to "-0000" (unless there is out-of-band information confirming their meaning). While the current RFC_1123_DATE_TIME constant doesn't support military time zones, the new constant could support them, by simply considering them equivalent to "-0000".
RFC_1123_DATE_TIME uses the date format as specified in RFC 1123, which updates RFC 822. However, RFC 822 was obsoleted by RFC 2822, which in turn was obsoleted by RFC 5322.
JUSTIFICATION :
Most notably, RFC 5322 specifically allows and gives meaning to the "-0000" time zone: "it is used to indicate that the time was generated on a system that may be in a local time zone other than Universal Time and that the date-time contains no information about the local time zone."
So in Java terms, the datetime must be treated as a java.time.LocalDateTime
It also specifies that military time zones should all be considered equivalent to "-0000" (unless there is out-of-band information confirming their meaning). While the current RFC_1123_DATE_TIME constant doesn't support military time zones, the new constant could support them, by simply considering them equivalent to "-0000".