Date: Tue, 25 Jul 2000 16:58:49 +0200 From: Bernd Luevelsmeyer <bernd.luevelsmeyer@heitec.net> To: Phil Pennock <pdp@nl.demon.net> Cc: freebsd-bugs@FreeBSD.org Subject: Re: misc/20159: strftime() can't produce ISO8601 format timezone representation Message-ID: <397DAB29.4307F6AA@heitec.net> References: <E13GqO3-000HRe-00@samhain.noc.nl.demon.net> <200007242210.PAA15988@freefall.freebsd.org> <20000725002527.A67116@samhain.noc.nl.demon.net> <397CD82D.F67AA13E@heitec.net> <20000725134616.A71153@samhain.noc.nl.demon.net> <20000725142452.A71696@samhain.noc.nl.demon.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Phil Pennock wrote: > > On 2000-07-25 at 13:46 +0200, Phil Pennock wrote: > > The use of -0000 comes from use in various rfc822-style headers - > > primarily Received: - although I don't have a handy reference indicating > > the appropriate RFC - it's not 822. > > The bibliography for rfc822 references: > ANSI. "Representations of Universal Time, Local Time Differen- > tials, and United States Time Zone References for Information > Interchange," X3.51-1975. American National Standards Insti- > tute: New York (1975). > > I don't have access to that document to check it. It would be > interesting to know if C99 is contradicting an ANSI standard or merely > established MTA practice for 'not telling you' timezone representation. I'd say, if ISO 8601 and the C Standard agree, then that ought to be good enough. As to the 'not telling you' in 'received:'-headers: not telling the TZ essentially invalidates the time stamp, because if you don't know the TZ then the time stamp doesn't tell you anything. Hence, these mail servers not only hide their TZ but also the 'received'-time. I don't think this is a good practice. Concerning RFC 822 and time specifications, RFC 1123 has corrections and clarifications: --------------8<------------ 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. --------------8<------------ Greetings, Bernd To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?397DAB29.4307F6AA>