Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.1 6/24/83; site hou3c.UUCP Path: utzoo!watmath!clyde!burl!hou3c!RSX-DEV@DEC-MARLBORO.ARPA From: RSX-DEV@DEC-MARLBORO.ARPA (John R. Covert) Newsgroups: net.mail.headers Subject: re: UTC time stamping & time zone designators Message-ID: <234@hou3c.UUCP> Date: Thu, 2-Feb-84 14:38:00 EST Article-I.D.: hou3c.234 Posted: Thu Feb 2 14:38:00 1984 Date-Received: Wed, 8-Feb-84 01:32:19 EST Sender: ka@hou3c.UUCP (Kenneth Almquist) Lines: 31 To: POSTEL@USC-ISIF.ARPA Enet-Address: "Castor::Covert" Phone: "(603) 884-8271 or DTN 264-8271" Usenet-Address: "{ucbvax,allegra,decvax}!decwrl!rhea!castor!covert" Regarding: Message from POSTEL@USC-ISIF of 2-Feb-84 0932-EST I wouldn't expect to find time zone designators in an ISO standard. ISO rarely resolves issues as complex as whether to call the time zone used in continental Europe HEC or MEZ. When dealing with an issue as close to the heart as the native tongue of the ISO member nations, only numbers can win the votes necessary to pass. We can banty this around forever without getting anywhere. Based on the inputs we have heard local time is the only thing we can be guaranteed will be put into a header because many machines and interfaces are purposefully simple to allow them access to the market and the net. A qualification by zone name is only useful visually since the zone names are not standardized. But this visual identification is useful to the reader. A qualification by UTC offset is nice and is an ISO standard. Since we aren't going to get every mailer to conform, we should state levels of conformance. At the lowest level, simply local time is provided. At the next level, local time is qualified by the UTC offset in the ISO format. At either level a text time zone identification can be added with the understanding that it has purely the effect of a comment and may not be parsed. --------