Errata Search
RFC Number:		Errata ID:
Source of RFC		Status:	All/Any Verified+Reported Verified Reported Held for Document Update Rejected
Area Acronym:	All/Any app art gen int ops rai rtg sec tsv wit	Type:	All/Any Editorial Technical
WG Acronym:		Submitter Name:
Other:	All/Any IAB INDEPENDENT IRTF Legacy Editorial	Date Submitted:
Summary Table Full Records

RFC 5322, "Internet Message Format", October 2008

Note: This RFC has been updated by RFC 6854

Source of RFC: IETF - NON WORKING GROUP
Area Assignment: app

---

Errata ID: 5035
Status: Rejected
Type: Technical
Publication Format(s) : TEXT
Reported By: Gene Hightower
Date Reported: 2017-06-09
Rejected by: Alexey Melnikov
Date Rejected: 2017-10-18

Section 3.3 says:

   time            =   time-of-day zone

   zone            =   (FWS ( "+" / "-" ) 4DIGIT) / obs-zone

It should say:

time            =       time-of-day FWS zone

zone            =       (( "+" / "-" ) 4DIGIT) / obs-zone

Notes:

The rfc5322 version of the syntax clearly forces the obs-zone to follow the time-of-day with no space. The syntax from rfc2822 seems to be what is actually in use in the real world. Why was this change made? Should it just be changed back?
--VERIFIER NOTES--
As per reply from Pete Resnick:

I believe this erratum report should be rejected. While it is true that
obs-zone does not begin with FWS, time-of-day ends with second, which
can be an obs-second, and obs-second ends with an optional CFWS.
Therefore, obs-zone is not forced to follow time-of-day with no space;
it just makes the space optional. And this allows for the original 822
syntax, which did not require space between the time-of-day and the
zone. (Somewhat goofy to allow that, but it is parseable.)

Report New Errata