Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!uakari.primate.wisc.edu!caen!news.cs.indiana.edu!arizona.edu!carat.arizona.edu!jms
From: jms@carat.arizona.edu (Joel M-for-Vnews Snyder)
Newsgroups: news.software.b
Subject: Re: Changes to CNEWS date parsing - what is now l
Message-ID: <24JUN199116325508@carat.arizona.edu>
Date: 24 Jun 91 23:32:00 GMT
References: <21JUN91230123@carat.arizona.edu> <1991Jun22.213542.2256@twinsun.com> <1991Jun24.202026.16593@zoo.toronto.edu>
Reply-To: jms@carat.arizona.edu
Distribution: world,local
Organization: University of Arizona MIS Department - Mosaic Group
Lines: 26
Nntp-Posting-Host: carat-p2p.mis.arizona.edu
News-Software: VAX/VMS VNEWS 1.4-b1  Lines: 27

OK.  Thanks for all your cards and letters.  If I take the intersection
of RFC822+RFC1036+RFC1023 (5.2.14), then I get the following date
(as implemented above) as the MOST preferred:

	24 Jun 1991 16:32 -0700

with lower case not significant, but judged to be "a good thing" by some
elders knowledgable about buggy software out there.  

HOWEVER, I'm looking at an August 1990 draft of the new NNTP spec, and it
says:

"Date and time now use ISO 3307 format, but for backward compatibility
the prior MMDDYY HHMMSS format may still be accepted.  Dates and
times are always in GMT."

How does this affect the date/time as discussed?

Wondering why they keep changing their mind,

jms

Joel M Snyder, 627 E Speedway, 85705  Phone: 602.626.8680 FAX: 602.795.0900
The Mosaic Group, Dep't of MIS, the University of Arizona, Tucson
BITNET: jms@sovset  Internet: jms@carat.arizona.edu  SPAN: 47541::carat::jms   
"Never contend with a man who has nothing to lose." - Gracian