Connected: An Internet Encyclopedia
RFC 1123 - 5.2.14 RFC-822 Date and Time Specification: RFC-822 Section 5

Top: Connected: An Internet Encyclopedia
Up: Requests For Comments
Up: RFC 1123
Up: 5. ELECTRONIC MAIL -- SMTP and RFC-822
Up: 5.2 PROTOCOL WALK-THROUGH
Prev: 5.2.13 RFC-822 Message Specification: RFC-822 Section 4
Next: 5.2.15 RFC-822 Syntax Change: RFC-822 Section 6.1

### 5.2.14 RFC-822 Date and Time Specification: RFC-822 Section 5

The syntax for the date is hereby changed to:

       date = 1*2DIGIT month 2*4DIGIT

All mail software SHOULD use 4-digit years in dates, to ease the transition to the next century.

There is a strong trend towards the use of numeric timezone indicators, and implementations SHOULD use numeric timezones instead of timezone names. However, all implementations MUST accept either notation. If timezone names are used, they MUST be exactly as defined in RFC-822.

The military time zones are specified incorrectly in RFC-822: they count the wrong way from UT (the signs are reversed). As a result, military time zones in RFC-822 headers carry no information.

Finally, note that there is a typo in the definition of "zone" in the syntax summary of appendix D; the correct definition occurs in Section 3 of RFC-822.

Next: 5.2.15 RFC-822 Syntax Change: RFC-822 Section 6.1

Connected: An Internet Encyclopedia
RFC 1123 - 5.2.14 RFC-822 Date and Time Specification: RFC-822 Section 5